agentleFS
alamenaialamenai/terrae/CLAUDE.md

terrae

CLAUDE.md245 starsChanged 9 months agoMITView on GitHub

@.claude/rules/overview.md @.claude/rules/typescript.md @.claude/rules/javascript.md @.claude/rules/react.md @.claude/rules/nextjs.md @.claude/rules/security.md @.claude/rules/clean-code.md

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Always check isLoaded from useMap() before accessing the map instance

    line 25
  2. Distinctive:

    Commit messages must follow conventional commits format (enforced by commitlint)

    line 28
  3. Very specific:

    Do not add Co-Authored-By lines to commit messages

    line 29
  4. Distinctive:

    Do not commit until you review the changes with the user

    line 30

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

@.claude/rules/overview.md @.claude/rules/typescript.md @.claude/rules/javascript.md @.claude/rules/react.md @.claude/rules/nextjs.md @.claude/rules/security.md @.claude/rules/clean-code.md

Common Commands

  • npm run dev - Start Next.js dev server
  • npm run build - Production build
  • npm run lint - Run ESLint
  • npm run format - Format with Prettier
  • npm run format:check - Check formatting
  • npm run test:run - Run tests once
  • npm run test:coverage - Run tests with coverage
  • npm run registry:build - Build component registry to ./public
  • npx tsc --noEmit - Type-check without emitting

Project Gotchas

  • Mapbox GL requires "use client" on all map components
  • The useMap() hook only works inside the <Map> provider context
  • Always check isLoaded from useMap() before accessing the map instance
  • Registry components are installed into user projects, so never include side effects beyond the component's purpose
  • Husky pre-commit hook runs npm run build and will fail the commit if the build breaks
  • Commit messages must follow conventional commits format (enforced by commitlint)
  • Do not add Co-Authored-By lines to commit messages
  • Do not commit until you review the changes with the user

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.