agentleFS
charlietlambcharlietlamb/ferix/CLAUDE.md

ferix

CLAUDE.md10 starsChanged 10 months agoMITView on GitHub

Whenever you make changes make sure to run bun lint, bun format, bun knip to ensure the code is meeting code standards. After making changes to apps/code, also run: - bun test in apps/code - Run all tests to ensure nothing is broken Never use any. Always prefer strong types. When working in an app that uses Effect make sure to use Effect schemas to validate data. When importing from Phospher Icons in apps/web make sure to add the Icon…

The file

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

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After making changes to apps/code, also run:

    line 3
  2. Distinctive:

    Never use any. Always prefer strong types.

    line 6
  3. Distinctive:

    When working in an app that uses Effect make sure to use Effect schemas to validate data.

    line 8
  4. Distinctive:

    When importing from Phospher Icons in apps/web make sure to add the Icon postfix to these icons as without this they're deprecated.

    line 10
  5. Distinctive:

    Always import at the top of the file never inline like import("asdf").asdf

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 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

Whenever you make changes make sure to run bun lint, bun format, bun knip to ensure the code is meeting code standards.

After making changes to apps/code, also run:

  • bun test in apps/code - Run all tests to ensure nothing is broken

Never use any. Always prefer strong types.

When working in an app that uses Effect make sure to use Effect schemas to validate data.

When importing from Phospher Icons in apps/web make sure to add the Icon postfix to these icons as without this they're deprecated.

Always import at the top of the file never inline like import("asdf").asdf

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.