agent-sage / rules
Cursor rule0 starsChanged 5 months agoMITView on GitHub
Sage agent system — always load root Agents.md and route through SDLC agents.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,243 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 repository15 other files it gives its agents.
- Agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- about-sageSkill
- sage-architectSkill
- sage-buildSkill
- sage-designSkill
- sage-devopsSkill
- sage-engineerSkill
- sage-handoffSkill
- sage-initSkill
- sage-orchestratorSkill
- sage-planSkill
- sage-qaSkill
- sage-releaseSkill
- sage-statusSkill
The file
We split this sage-system.mdc 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 10
Always read Agents.md first.
- Very specific: line 12
When doing SDLC work, use /sage-* slash commands.
- Very specific: line 14
Do not skip phases except those listed in manifest.skipped_phases.
≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule 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
--- description: Sage agent system — always load root Agents.md and route through SDLC agents. alwaysApply: true --- # Sage system This project uses the **Sage** SDLC agent system. Always read [Agents.md](../../Agents.md) first. It is the root contract linked to all phase agents in `agents/`. When doing SDLC work, use `/sage-*` slash commands. Set `workflow_profile` in manifest per [workflows/profiles.md](../../workflows/profiles.md). Do not skip phases except those listed in `manifest.skipped_phases`. Never skip plan, build, qa, or release. Agent registry, skills mirror, and flow: see the top of Agents.md. Keep `.cursor/skills/` aligned with the Skills mirror table when adding or removing agents.
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.

