agentleFS
alexei-ledalexei-led/ccgram/CLAUDE.md

ccgram

CLAUDE.md288 starsChanged 7 days agoMITView on GitHub

- Before a cross-module import: archfit policy can-import <file> <target>. denied names the rule and what to do instead; unconstrained is not permission. - Before you finish: archfit check --format agent. Follow next_action; change.status: pass is a correct finish, even with exit code 2. - Module owner, layer, allowlists and rules for a path: archfit policy where <path>. - At session start, or when unsure the hooks run: archfit doctor. - Never edit .archfit.yaml, .archfit-baseline.json or .archfit-labels.yaml, and never add…

  • In this repositoryOne other file it gives its agents.

The file

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

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

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before a cross-module import: archfit policy can-import <file> <target>.

    line 5
  2. Very specific:

    Before you finish: archfit check --format agent.

    line 6
  3. Very specific:

    Never edit .archfit.yaml, .archfit-baseline.json or .archfit-labels.yaml, and never add a waiver, to make a check pass.

    line 9

≈ “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
<!-- archfit:start --><!-- Generated by `archfit agents-md` from .archfit.yaml. Edit the config, not this block. -->

Architecture guardrails (archfit)

  • Before a cross-module import: archfit policy can-import <file> <target>. denied names the rule and what to do instead; unconstrained is not permission.
  • Before you finish: archfit check --format agent. Follow next_action; change.status: pass is a correct finish, even with exit code 2.
  • Module owner, layer, allowlists and rules for a path: archfit policy where <path>.
  • At session start, or when unsure the hooks run: archfit doctor.
  • Never edit .archfit.yaml, .archfit-baseline.json or .archfit-labels.yaml, and never add a waiver, to make a check pass.
  • restore_evidence: do what the result names (install the analyzer, merge or rebase the target), then run again. ask_owner, or an unknown you cannot clear: stop, report the rule and what you need, and ask the architecture owner.
<!-- archfit: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.

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.