agentleFS
Sign inStart free
material-extensionsmaterial-extensions/vscode-material-icon-theme/.github/copilot-instructions.md

vscode-material-icon-theme

Copilot instructions3k starsChanged 22 months agoMITView on GitHub

To contribute effectively to this project, follow these guidelines: Always ensure that your contributions comply with the project's guidelines and do not introduce any disallowed content.

We split this copilot-instructions.md into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow the project style: Ensure all changes adhere to the existing code and documentation style.

    line 5
  2. Distinctive:

    Use Material Design color palette: When working with icons, use colors from the Material Design color palette.

    line 6
  3. Distinctive:

    Design pixel-perfect icons: Create icons that are sharp and clear at 16x16 pixels.

    line 8
  4. Distinctive:

    Write clean, modular, and well-documented code: Document your code thoroughly and ensure it is easy to understand and maintain.

    line 9
  5. Distinctive:

    Test your changes: Always test your changes to ensure they do not break existing functionality.

    line 10
  6. Distinctive:

    Use colors from the Material Design color palette.

    line 14
  7. Distinctive:

    Ensure icons have proper spacing (Read CONTRIBUTING.md).

    line 15
  8. Distinctive:

    Clone existing icons when possible: If you need a variant of an existing icon with a different color, clone the icon through configuration …

    line 19
  9. Very specific:

    Contribute to translations: If you notice errors in translations, you can help fix them by editing the appropriate translation files …

    line 20
  10. Distinctive:

    Always ensure that your contributions comply with the project's guidelines and do not introduce any disallowed content.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

Copilot instructions

To contribute effectively to this project, follow these guidelines:

  1. Follow the project style: Ensure all changes adhere to the existing code and documentation style. Review the project's codebase to understand the conventions used.
  2. Use Material Design color palette: When working with icons, use colors from the Material Design color palette. This ensures visual consistency across the project.
  3. Adhere to the project architecture: Familiarize yourself with the project's architecture. The core logic is separated from the extension logic. The core handles icon manifest generation, icon associations, and translation. The extension interacts with the VS Code API. Make sure to respect the dependency rules between modules.
  4. Design pixel-perfect icons: Create icons that are sharp and clear at 16x16 pixels. Align icons to a 16x16 grid to ensure sharpness and avoid blurriness. More details are available in the CONTRIBUTING.md.
  5. Write clean, modular, and well-documented code: Document your code thoroughly and ensure it is easy to understand and maintain.
  6. Test your changes: Always test your changes to ensure they do not break existing functionality.
  7. Keep it simple: Aim for simplicity in your solutions and avoid unnecessary complexity.

  8. Add new icons appropriately:

    • Use colors from the Material Design color palette.
    • Ensure icons have proper spacing (Read CONTRIBUTING.md).
    • Assign icons uniquely to file names, extensions, or folder names according to the project guidelines.
    • Provide separate icons for different color themes if necessary (Read CONTRIBUTING.md).
  9. Clone existing icons when possible: If you need a variant of an existing icon with a different color, clone the icon through configuration without creating a new SVG (Read CONTRIBUTING.md).
  10. Contribute to translations: If you notice errors in translations, you can help fix them by editing the appropriate translation files (package.nls*.json).

Always ensure that your contributions comply with the project's guidelines and do not introduce any disallowed content.

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 3 mentionsJul 2026: 5 mentionsAug 2026: 11 mentionsSep 2026: 11 mentionsOct 2026: 16 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the material-extensions/vscode-material-icon-theme repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about material-extensions/vscode-material-icon-theme

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub (50 times).

On GitHub · 50

45 more on GitHub
  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free