agentleFS
afaraha8403afaraha8403/mental/website/AGENTS.md

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
  1. Very specific:

    Before you deliver a build, run astryx doctor --built <dir>.

    line 18
  2. Very specific:

    Read astryx docs layout before changing a template's frame.

    line 22

≈ “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.

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

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:

  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 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, run astryx doctor --built <dir>; don't deliver it if it fails.

RULES:

  • No <div> — components handle all layout and spacing.
  • Read astryx docs layout before 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. See astryx 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 -->

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.

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.