agentleFS
RafaelFerSilvaRafaelFerSilva/refinement-agent-skills/.claude/CLAUDE.md

refinement-agent-skills

CLAUDE.md2 starsChanged 15 days agoMITView on GitHub

Compatibility bridge for Claude Code. Any AI workflow change goes into AGENTS.md, never here.

The file

Files
CLAUDE.md
<!-- Why this file exists: Claude Code reads CLAUDE.md as project instructions and would ignore AGENTS.md if this file carried content of its own. The import below keeps AGENTS.md the single source of truth. It lives in .claude/ rather than at the repository root because this repository is also a plugin, and a CLAUDE.md at a plugin root is never loaded as context: `claude plugin validate` warns about it, while `<cwd>/.claude/CLAUDE.md` loads as project memory like the root file does. HTML comments are stripped before entering agent context. -->

@../AGENTS.md

Compatibility bridge for Claude Code. Any AI workflow change goes into AGENTS.md, never here.

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.