mental / website
AGENTS.md5 starsChanged yesterdayMITView on GitHub
Project-specific guidance for AI coding agents. SETUP (once, in app entry e.g. main.tsx) — without these, components render unstyled: import "@astryxdesign/core/reset.css"; import "@astryxdesign/core/astryx.css"; WORKFLOW — start every page from a template, never from scratch: 1. astryx build "<idea>" — names the template to scaffold from and the parts it lacks. 2. astryx template <name> <path> — scaffold it; keep its frame, gap and padding; replace the content. 3. astryx template <Block> for parts it lacks; astryx component <Name> to read…
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Before you deliver a build, run astryx doctor --built <dir>.
- Very specific: line 22
Read astryx docs layout before changing a template's frame.
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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.
Files
AGENTS.md
Project-specific guidance for AI coding agents.
<!-- ASTRYX:START -->Astryx v0.7.4 · 173 components
CLI: run every command as npx astryx <cmd> (shown below as astryx ...).
SETUP (once, in app entry e.g. main.tsx) — without these, components render unstyled: import "@astryxdesign/core/reset.css"; import "@astryxdesign/core/astryx.css";
WORKFLOW — start every page from a template, never from scratch:
astryx build "<idea>"— names the template to scaffold from and the parts it lacks.astryx template <name> <path>— scaffold it; keep its frame, gap and padding; replace the content.astryx template <Block>for parts it lacks;astryx component <Name>to read props before using one. Changing an existing page? Keep it: skip step 2 and add blocks/components inside its sections. Before you deliver a build, runastryx doctor --built <dir>; don't deliver it if it fails.
RULES:
- No
<div>— components handle all layout and spacing. - Read
astryx docs layoutbefore changing a template's frame. - Dense data = rows (Table, List/Item), not Card-wrapped lists. Badge = counts only.
- Style with component props first, then tokens (var(--color-|--spacing-|--radius-*)). No raw hex/px. No StyleX/Tailwind compiler here — don't use xstyle/utility classes directly. Some templates use StyleX and need a compiler plugin; see
astryx docs styling-overview. - Palettes and custom colors go through the theme, never :root overrides. Run
astryx theme add <slug>to import;theme eject <slug>only forks source. Seeastryx docs theme. - SELF-CHECK: re-read the file; replace any raw
<div>/<span>, imported .css/@apply, or hardcoded #hex/px with the component or a token.
astryx help lists every command. Key ones beyond the workflow:
search "<query>" find any component / hook / doc / template
discover <words> integrations you could add
docs <topic> getting-started, principles, tokens, theme … (astryx docs lists all)
docs cli commands and API reference
docs authoring build an integration package, and every field it holds
upgrade --from <old version> --apply run after a dependency bump
<!-- ASTRYX:END -->Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 28,693 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.
In this repository30 other files it gives its agents.
- docs/agents.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/claude-desktop-skills.mdcCursor rule
- .cursor/rules/claude-mod.mdcCursor rule
- .cursor/rules/codex-desktop-skills.mdcCursor rule
- .cursor/rules/desktop-and-publishing-skills.mdcCursor rule
- .cursor/rules/release.mdcCursor rule
- claude-code-mods-guideSkill
- claude-desktop-extensionsSkill
- claude-desktop-modsSkill
- claude-desktop-pluginsSkill
- codex-desktop-extensionsSkill
- codex-desktop-pluginsSkill
- codex-desktop-skillsSkill
- copilot-desktop-extensionsSkill
- cursor-extensions-and-pluginsSkill
- opencode-pluginsSkill
- publishing-mental-to-storesSkill
- claude-code-mods-guideSkill
- claude-desktop-extensionsSkill
- claude-desktop-modsSkill
- claude-desktop-pluginsSkill
- codex-desktop-extensionsSkill
- codex-desktop-pluginsSkill
- codex-desktop-skillsSkill
- copilot-desktop-extensionsSkill
- cursor-extensions-and-pluginsSkill
- opencode-pluginsSkill
- publishing-mental-to-storesSkill
- mental-setupSkill
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.

