agentleFS
Sign inStart free
orbyn-devorbyn-dev/orbyn-fullstack-skills/CLAUDE.md

orbyn-fullstack-skills

CLAUDE.md4 starsChanged 10 days agoMITView on GitHub

Read AGENTS.md and resolve the harness first (its top section), then only the shared skills relevant to the task. Canonical skills are linked at this outer workspace's .claude/skills. Resolve the nested target and read its own root/nested instructions and local skills in place, including any future project-owned AGENT.md or AGENTS.md. Target rules, user scope and host permissions govern their applicable boundaries; resolve real conflicts before dependent work. No shared skills are installed into targets. Workspace setup does not apply optional…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Read AGENTS.md and resolve the harness first (its top section), then only the shared skills relevant to the task.

    line 5

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

Read AGENTS.md and resolve the harness first (its top section), then only the shared skills relevant to the task. Canonical skills are linked at this outer workspace's .claude/skills. Resolve the nested target and read its own root/nested instructions and local skills in place, including any future project-owned AGENT.md or AGENTS.md. Target rules, user scope and host permissions govern their applicable boundaries; resolve real conflicts before dependent work. No shared skills are installed into targets. Workspace setup does not apply optional model presets or configure MCP providers.

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