mini-spec
AGENTS.md5 starsChanged 51 days agoMITView on GitHub
This repo uses the mini-spec methodology. Cursor loads it via .cursor/rules/mini-spec.mdc (alwaysApply: true) — same workflow as the Claude Code skill in .claude/skills/mini-spec/SKILL.md. Install minispec: add the release binary to your PATH, or set environment variable MINISPEC to its full path. Run minispec check-version and align with the version in .claude/skills/mini-spec/README.md. Claude parity: For isolated design-heavy work (equivalent to invoking spec-agent), enable the rule mini-spec — spec agent from the rule picker or mention it in chat. Release and contribution…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository6 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/minimap.mdcCursor rule
- .cursor/rules/mini-spec.mdcCursor rule
- .cursor/rules/mini-spec-spec-agent.mdcCursor rule
- minimapSkill
- mini-specSkill
The file
We split this AGENTS.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
- Very specific: line 7
Install
minispec: add the release binary to your PATH, or set environment variable MINISPEC to its full path.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.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
Agent instructions (Cursor)
Mini-spec
This repo uses the mini-spec methodology. Cursor loads it via .cursor/rules/mini-spec.mdc (alwaysApply: true) — same workflow as the Claude Code skill in .claude/skills/mini-spec/SKILL.md.
Install minispec: add the release binary to your PATH, or set environment variable MINISPEC to its full path. Run minispec check-version and align with the version in .claude/skills/mini-spec/README.md.
Claude parity:
| Claude | Cursor |
| Skill auto-invoked | Rule mini-spec.mdc always applies |
TaskCreate / TaskUpdate | Cursor todos (see rule) |
~/.claude/bin/minispec | minispec on PATH or MINISPEC |
code-simplifier plugin | In-session simplification pass (rule) |
spec-agent subagent | Use Agent mode + optional rule below |
For isolated design-heavy work (equivalent to invoking spec-agent), enable the rule mini-spec — spec agent from the rule picker or mention it in chat.
Other
Release and contribution notes for maintainers: CLAUDE.md.
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.