agentleFS
Sign inStart free
DestinyItemManagerDestinyItemManager/DIM/.github/copilot-instructions.md

DIM

Copilot instructions2.2k starsChanged 3 years agoMITView on GitHub

Always follow the Contributing Guide.

Trending

Quiet since September.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 1 mentionAug 2026: 1 mentionSep 2026: 2 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the DestinyItemManager/DIM repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about DestinyItemManager/DIM

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,336 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.

The file

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

10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always follow the Contributing Guide.

    line 3
  2. Distinctive:

    Prefer using "function" to declare functions over const arrow functions.

    line 9
  3. Very specific:

    All CSS should be put in CSS modules.

    line 13
  4. Distinctive:

    Do not use inline styles.

    line 14
  5. Distinctive:

    Do not use string classNames, only use CSS modules.

    line 15
  6. Distinctive:

    Use the clsx helper to combine classNames or conditionally include classes.

    line 16
  7. Very specific:

    Run pnpm test -- -u to update snapshots.

    line 21
  8. Very specific:

    Run pnpm build:beta to make sure the code builds.

    line 22
  9. Very specific:

    Run pnpm test to run all tests.

    line 23
  10. Very specific:

    Only ever add strings to config/i18n.json.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 3,779 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

General DIM Code Style

Always follow the Contributing Guide.

JS

  • Pure JavaScript files should be named in lowercase kebab-case, with a .ts extension. These should not use a default export.
  • Files with JSX should be named in PascalCase with a .tsx extension. In general we should have a separate file for each component. The component should be that module's default export, and the file should have the same name as the component.
  • Prefer using "function" to declare functions over const arrow functions.

CSS

  • All CSS should be put in CSS modules. The CSS module file should have the same name as the file it is used from but with the extension .m.scss. The classes from the module should be imported as styles and referenced in JSX.
  • Do not use inline styles.
  • Do not use string classNames, only use CSS modules.
  • Use the clsx helper to combine classNames or conditionally include classes.

Tests

  • For unit tests, prefer defining a table of inputs and expected outputs, and then looping through that to create tests. This is also called "table-style testing".
  • Run pnpm test -- -u to update snapshots. This is especially necessary when adding new search terms.
  • Run pnpm build:beta to make sure the code builds.
  • Run pnpm test to run all tests.

Localization

  • Only ever add strings to config/i18n.json. Then run pnpm i18n and commit the updated src/locale/en.json file.

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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