levistack / rules
Cursor rule0 starsChanged 18 days agoMITView on GitHub
Constraints for changing the levistack catalog: edit source files only, then sync and check.
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,183 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 repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/comments.mdcCursor rule
- .cursor/rules/commit-messages.mdcCursor rule
- .cursor/rules/git-workflow.mdcCursor rule
- .cursor/rules/no-worktrees.mdcCursor rule
- manage-stackSkill
- convert-as-skillSkill
- create-agentSkill
- create-agents-mdSkill
- create-commandSkill
- create-hookSkill
- create-ruleSkill
- create-skillSkill
- retrospectiveSkill
- super-architectureSkill
- super-cachingSkill
- super-elixirSkill
- super-nodejsSkill
- super-protobufSkill
- super-tech-blueprintSkill
- atomic-semantic-commitSkill
- code-reviewSkill
- create-bruno-collectionSkill
- create-documentationSkill
- create-ticketsSkill
- ready-specSkill
- write-adrSkill
- write-changelogSkill
- write-mr-descriptionSkill
- write-planSkill
- write-postmortemSkill
- write-runbookSkill
- noslopSkill
- output-saversSkill
- safe-refactorSkill
- tddSkill
- verifySkill
- get-movingSkill
- later-listSkill
- standupSkill
- challenge-meSkill
- codebase-learnerSkill
- researchSkill
- second-opinionSkill
- traceSkill
- color-kitSkill
- design-system-kitSkill
- diagramSkill
- infographicSkill
- product-polish-workflowSkill
- prototype-wireframeSkill
- ui-ux-kitSkill
- evidenceSkill
- find-skillsSkill
- handoffSkill
- rumblingSkill
- use-levistackSkill
The file
We split this manage-stack.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
- could be automatic: a setting could enforce it
- Very specific: line 8
Follow .cursor/skills/manage-stack/SKILL.md before adding or changing a skill, rule, agent, command, or hook.
- Very specific: line 11
Do not hand-edit generated output.
- Very specific: line 14
Before reporting done: npm run sync && git diff --exit-code, then npm run validate, then npm test.
≈ “Common” is an estimate: at least 1 in 5 of the 6,668 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: "Constraints for changing the levistack catalog: edit source files only, then sync and check." alwaysApply: true --- # Managing this stack Follow `.cursor/skills/manage-stack/SKILL.md` before adding or changing a skill, rule, agent, command, or hook. Edit `.cursor/agents/`, `.cursor/rules/`, and `.cursor/skills/` only; `.claude/agents`, `.claude/rules`, and `.claude/skills` symlink here (`npm run sync` refreshes them). - Edit only `skills/`, `agents/`, `rules/`, `commands/`, and `hooks/`. Update `docs/agents/README.md` when the agent roster changes. - Do not hand-edit generated output. Run `npm run sync`. That includes `.claude-plugin/`, `.cursor-plugin/`, `.codex-plugin/`, `skills/<group>/.claude-plugin/`, `generated/`, `hooks/hooks.json`, and the generated tables in `README.md` and `hooks/README.md`. - A skill `name` equals its folder. `description` says when to use it, is quoted, and is at most 1024 characters. - Nothing employer-owned, no secrets, no personal data. Never add repo-root `THIRD_PARTY.md`. - Before reporting done: `npm run sync && git diff --exit-code`, then `npm run validate`, then `npm test`.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.