superlite / rules
Cursor rule249 starsChanged 14 days agoMITView on GitHub
One feature per git worktree so multiple features can proceed safely in parallel
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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- commands/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/no-cursor-commit-notes.mdcCursor rule
- diagnosisSkill
- draftingSkill
- feature-prototypeSkill
- inventingSkill
- mvp-prototypeSkill
- proofSkill
- shippingSkill
- swarmSkill
- testingSkill
- using-superliteSkill
- writing-specsSkill
The file
We split this feature-worktrees.mdc into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Never develop two features in the same checkout.
≈ “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: One feature per git worktree so multiple features can proceed safely in parallel alwaysApply: true --- # Feature worktrees Never develop two features in the same checkout. - **Before code** for a feature (feature-mode integration, multi-file builds, harness work): cut or reopen a dedicated branch and worktree, e.g. `git worktree add -b superlite/<topic> .superlite/worktrees/<topic> <base>`, then move the agent root into that worktree. - **Prototype** sandboxes stay at `.superlite/sandboxes/<topic>-proto` (via `superlite-cli proto start`). They are not a substitute for the integration worktree. At finish, `superlite-cli proto discard` removes the sandbox, and the flow removes the integration worktree from the main checkout. A keep with uncommitted work stays. - **Do not** layer feature B onto a checkout that already has feature A's uncommitted or in-progress work, or onto a dirty shared `main` while A is open elsewhere. - **Exempt:** trivial one-line / one-file fixes the user asked to do on the current branch. - Details: `AGENTS.md`, `commands/feature.md` step 6, `docs/feature-flow.md`.
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.