agentleFS
FranciscoMorettiFranciscoMoretti/sparka/AGENTS.md

sparka

AGENTS.md1.2k starsChanged 21 days agoApache-2.0View on GitHub

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

7 rules. About 0 are common, 5 are distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Bun for packages and scripts.

    line 5
  2. Very specific:

    Run bun lint, bun test:types, and the relevant tests before handing off code changes.

    line 7
  3. Distinctive:

    Prefer concrete code and evidence over high-level advice.

    line 13
  4. Distinctive:

    Remove unused code rather than preserving compatibility aliases or dead exports.

    line 14
  5. Distinctive:

    Use the strategic-testing skill when deciding whether to add or change tests.

    line 18
  6. Distinctive:

    Before changing any component, page, or styles, read the making-ui-changes skill and follow it - reuse before you create, add/update the …

    line 19
  7. Very specific:

    When changing apps/chat routes or page states, update the corresponding capture in packages/chat-visual-tests/pages.

    line 24

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

ChatJS Agent Instructions

Repository

  • Use Bun for packages and scripts.
  • The monorepo contains applications in apps/ and shared packages in packages/.
  • Run bun lint, bun test:types, and the relevant tests before handing off code changes. Do not run a production build merely to type-check.

Agent guidance

  • Repository rules follow agents.md and live in AGENTS.md files. The nearest file in the directory tree adds to or overrides this file for its subtree.
  • On-demand workflows live in .agents/skills/<name>/SKILL.md and follow the Agent Skills specification.
  • Prefer concrete code and evidence over high-level advice. Keep communication concise.
  • Remove unused code rather than preserving compatibility aliases or dead exports.

Testing

  • Use the strategic-testing skill when deciding whether to add or change tests.
  • Before changing any component, page, or styles, read the making-ui-changes skill and follow it - reuse before you create, add/update the story or capture in the same change, check the blast radius on shared components, and prove the change with a visual test.
  • When a registry tool in packages/registry/src/tools/<id> declares a rendererExport in its manifest, it must ship a renderer.tsx exporting it and a co-located renderer.visual.tsx browser test that renders it in every state in one snapshot. The registry-coverage unit test enforces this; run bun run check in packages/registry to verify types, unit, and visual tests.

Reference app visual coverage

  • When changing apps/chat routes or page states, update the corresponding capture in packages/chat-visual-tests/pages. Follow the suite instructions; this maintainer suite stays outside scaffolded apps.

Download now (ZIP)

Trending

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

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek 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 projects
Aug 2026Sep 2026Oct 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.

Who's talking about FranciscoMoretti/sparka

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

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.