agentleFS
Sign inStart free
connext-solutionsconnext-solutions/flowctl/CLAUDE.md

flowctl

CLAUDE.md1 starsChanged 5 days agoApache-2.0View on GitHub

- Path-scoped rules live in .claude/rules/ and load when you touch matching files. - Skills: new or large work → superpowers:brainstorming then superpowers:writing-plans; code → superpowers:test-driven-development; structure discussions use the mattpocock-skills:codebase-design vocabulary (module, interface, seam, adapter, depth — see CONTEXT.md). - Look code up with codegraph first, grep second. - Hooks (.claude/settings.json, scripts in .claude/hooks/): - guard-bash denies bun --bun, bun test, --no-verify, force push and printing .env; asks before git reset --hard, rm -rf and pushing to main. -…

  • Reads credentials
  • Deletes or force-pushes

The file

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Look code up with codegraph first, grep second.

    line 9

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

@AGENTS.md

Claude Code specifics

  • Path-scoped rules live in .claude/rules/ and load when you touch matching files.
  • Skills: new or large work → superpowers:brainstorming then superpowers:writing-plans; code → superpowers:test-driven-development; structure discussions use the mattpocock-skills:codebase-design vocabulary (module, interface, seam, adapter, depth — see CONTEXT.md).
  • Look code up with codegraph first, grep second.
  • Hooks (.claude/settings.json, scripts in .claude/hooks/):
    • guard-bash denies bun --bun, bun test, --no-verify, force push and printing .env; asks before git reset --hard, rm -rf and pushing to main.
    • dup-export rejects an export whose name another packages/*/src file already exports. If the clash is unrelated, put // dup-ok: <reason> on the line above the export.
    • format-file runs oxfmt + oxlint on each edited .ts file; lint errors come back to you.
    • stop-check runs bun run check before you stop when packages/ or scripts/ changed; fix what it reports.

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.

Check your setup, free