encore-skills
CLAUDE.md2 starsChanged 15 days agoMITView on GitHub
This repo contains workflow skills for Claude Code, Cursor, and Codex. It dogfoods itself: this repo is also a project that Claude, Cursor, and Codex can work on, using its own skills. Understand → Plan → Implement → Validate → Ship or Loop
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/analyze-issue.mdcCursor rule
- .cursor/rules/create-mr.mdcCursor rule
- .cursor/rules/eng-workflow.mdcCursor rule
- .cursor/rules/fix-issue.mdcCursor rule
- .cursor/rules/gitlab-config.mdcCursor rule
- .cursor/rules/pm-workflow.mdcCursor rule
- .cursor/rules/review-code.mdcCursor rule
- .cursor/rules/summarize-issue.mdcCursor rule
- .cursor/rules/triage-issue.mdcCursor rule
- .cursor/rules/write-issue.mdcCursor rule
- analyze-issueSkill
- create-mrSkill
- eng-workflowSkill
- fix-issueSkill
- gitlab-configSkill
- pm-workflowSkill
- review-codeSkill
- summarize-issueSkill
- triage-issueSkill
- write-issueSkill
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
- Very specific: line 15
Create skills/<name>/SKILL.md with frontmatter: name, description
- Very specific: line 16
Run ./scripts/setup.sh --claude to install into Claude Code
- Very specific: line 17
Run ./scripts/setup-cursor.sh and ./scripts/setup-codex.sh to regenerate .cursor/rules/ and AGENTS.md — commit the results so Cursor/Codex …
≈ “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.
Files
encore-skills
This repo contains workflow skills for Claude Code, Cursor, and Codex. It dogfoods itself: this repo is also a project that Claude, Cursor, and Codex can work on, using its own skills.
Structure
skills/— canonical skill sources (one directory per skill, each with SKILL.md). Single source of truth — never edit generated adapters below directly.scripts/— setup scripts for each tool (setup-claude.sh,setup-cursor.sh,setup-codex.sh,setup.shentry point,uninstall.sh,upgrade.sh)docs/— specs and plans.cursor/rules/*.mdc— generated, committed adapter for Cursor (self-hosted mode: each file just@-referencesskills/<name>/SKILL.md, no content duplicated)AGENTS.md— generated, committed adapter for Codex (self-hosted mode: table of skill names/paths, no content duplicated)
Adding a skill
- Create
skills/<name>/SKILL.mdwith frontmatter:name,description - Run
./scripts/setup.sh --claudeto install into Claude Code - Run
./scripts/setup-cursor.shand./scripts/setup-codex.shto regenerate.cursor/rules/andAGENTS.md— commit the results so Cursor/Codex users of this repo stay in sync
Skills follow the human-thinking workflow
Understand → Plan → Implement → Validate → Ship or Loop
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
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.

