agentleFS
Sign inStart free
bherbruckbherbruck/solidcraft/assets/AGENTS.md

solidcraft / assets

AGENTS.md15k starsChanged 18 days agoApache-2.0View on GitHub

Read assets/README.md before changing media, fonts, artwork or their consumers. For any UI icon, icon assignment or review-tool change, also read assets/icons/ui/AGENTS.md and assets/icons/ui/STYLE_GUIDE.md before editing. These files are the specification; chat history and old previews are not required. - Keep one editable authority per resource. UI SVGs are masters, not exports of a second competing drawing library. source/ retains genuine native source and the separately compiled Rust viewport glyphs. - Keep only production inputs, necessary shipped exports, authoring tools…

1 other project uses a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about bherbruck/solidcraft

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

See all 75

Talked about on GitHub, YouTube, Bluesky and Hacker News (75 times).

On GitHub · 46

41 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 5

On Hacker News · 1

The file

We split this AGENTS.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read assets/README.md before changing media, fonts, artwork or their consumers.

    line 3
  2. Very specific:

    Keep one editable authority per resource.

    line 8
  3. Very specific:

    Keep only production inputs, necessary shipped exports, authoring tools and provenance here.

    line 11
  4. Very specific:

    Do not add historical alternatives, duplicate resolutions that packaging does not consume, copied screenshots, node_modules, Python …

    line 14
  5. Very specific:

    Add an exact ATTRIBUTION.md row for every non-Markdown asset, including tool code, web UI sources and metadata.

    line 17
  6. Very specific:

    Never copy or derive iconography from commercial CAD products.

    line 19
  7. Very specific:

    Run cargo xtask assets and cargo xtask icons.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

Resource work — mandatory

Read assets/README.md before changing media, fonts, artwork or their consumers. For any UI icon, icon assignment or review-tool change, also read assets/icons/ui/AGENTS.md and assets/icons/ui/STYLE_GUIDE.md before editing. These files are the specification; chat history and old previews are not required.

  • Keep one editable authority per resource. UI SVGs are masters, not exports of a second competing drawing library. source/ retains genuine native source and the separately compiled Rust viewport glyphs.
  • Keep only production inputs, necessary shipped exports, authoring tools and provenance here. Put screenshots, contact sheets, audits, caches, test output, review inbox files and package staging under ignored target/.
  • Do not add historical alternatives, duplicate resolutions that packaging does not consume, copied screenshots, node_modules, Python bytecode or generated inventory CSVs to this collection. Preserve native editable source documents.
  • Add an exact ATTRIBUTION.md row for every non-Markdown asset, including tool code, web UI sources and metadata. Remove rows for intentionally retired files.
  • Never copy or derive iconography from commercial CAD products. Use original SolidCraft artwork, analytic geometry and the approved local references.
  • Run cargo xtask assets and cargo xtask icons. Full repository gates still apply before a commit. Never refresh acceptance hashes to bypass a failed check.

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