torque / rules
Cursor rule94 starsChanged 13 months agoMITView on GitHub
Never manually edit StackBlitz template files - they are auto-generated
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,181 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 repository2 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdcCursor rule
The file
We split this no-manual-stackblitz-template-edits.mdc into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 31
Run the generation script to update all StackBlitz templates:
- Distinctive: line 36
If you need to make changes to StackBlitz templates, suggest running the generation script instead of editing files directly.
≈ “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: Never manually edit StackBlitz template files - they are auto-generated globs: "stackblitz-templates/**/*.ts, stackblitz-templates/**/*.tsx, stackblitz-templates/**/*.json, stackblitz-templates/**/*.md" alwaysApply: true --- # StackBlitz Templates Auto-Generation Rule **NEVER manually edit files in `stackblitz-templates/` (except for `stackblitz-templates/_templates/`).** These files are automatically generated through a script. Any manual changes will be overwritten. ## What you CAN edit: - ✅ `stackblitz-templates/_templates/*` - These are the source templates - ✅ `examples/*` - The original example files ## What you CANNOT edit: - ❌ `stackblitz-templates/async-tools/` - ❌ `stackblitz-templates/basic-conversation/` - ❌ `stackblitz-templates/composition-utilities/` - ❌ `stackblitz-templates/custom-generation-context/` - ❌ `stackblitz-templates/multiple-tool-variations/` - ❌ `stackblitz-templates/quick-start/` - ❌ `stackblitz-templates/schema-composition/` - ❌ `stackblitz-templates/tool-calling/` ## How to make changes: 1. Edit the source files in `examples/` directory 2. Edit templates in `stackblitz-templates/_templates/` if needed 3. Run the generation script to update all StackBlitz templates: ```bash bun run scripts/generate-stackblitz-templates.ts ``` If you need to make changes to StackBlitz templates, suggest running the generation script instead of editing files directly.
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.