CRUX-Compress / rules
Cursor rule8 starsChanged 2 months agoMITView on GitHub
Ensures engineering specs use CRUX-specific agents instead of generalPurpose
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 repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/crux-memories-integration.crux.mdcCursor rule
- .cursor/rules/crux-memories-integration.mdCursor rule
- .cursor/rules/_CRUX-RULE.mdcCursor rule
- .cursor/rules/docs-sync.crux.mdCursor rule
- .cursor/rules/docs-sync.crux.mdcCursor rule
- .cursor/rules/docs-sync.mdCursor rule
- .cursor/rules/example/coding-standards-demo.crux.mdcCursor rule
- .cursor/rules/example/coding-standards-demo.mdCursor rule
- .cursor/rules/ignore-example-rules.crux.mdCursor rule
- .cursor/rules/ignore-example-rules.crux.mdcCursor rule
- .cursor/rules/ignore-example-rules.mdCursor rule
- .cursor/rules/skill-and-agent-references.mdcCursor rule
- .cursor/rules/spec-agent-allocation.crux.mdCursor rule
- .cursor/rules/spec-agent-allocation.crux.mdcCursor rule
- .cursor/rules/spec-implementation-hygiene.mdcCursor rule
- .cursor/rules/version-bump.crux.mdCursor rule
- .cursor/rules/version-bump.crux.mdcCursor rule
- .cursor/rules/version-bump.mdCursor rule
- .cursor/rules/zip-contents-protection.crux.mdCursor rule
- .cursor/rules/zip-contents-protection.crux.mdcCursor rule
- .cursor/rules/zip-contents-protection.mdCursor rule
- crux-skill-memory-compressSkill
- crux-skill-memory-crudSkill
- crux-skill-memory-extractSkill
- crux-skill-memory-indexSkill
- crux-skill-memory-meditation-coordinationSkill
- crux-skill-memory-meditation-ensembleSkill
- crux-skill-memory-meditation-quickSkill
- crux-skill-memory-meditation-reportSkill
- crux-skill-memory-meditation-researchSkill
- crux-skill-memory-meditation-reviewSkill
- crux-skill-memory-rebalanceSkill
- crux-skill-memory-reference-trackerSkill
- crux-utilsSkill
The file
We split this spec-agent-allocation.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 8
When creating or executing engineering specs (/zoto-spec-create, /zoto-spec-execute) in this repository, assign subtasks to CRUX agents — …
≈ “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
Spec Agent Allocation
When creating or executing engineering specs (/zoto-spec-create, /zoto-spec-execute) in this repository, assign subtasks to CRUX agents — never use generalPurpose.
Allocation Rules
- Architecture, design, documentation, and eval strategy →
crux-platform-architect - Code implementation, bug fixes, refactoring, writing evals/tests →
crux-software-engineer - CRUX compression/decompression →
crux-cursor-rule-manager - Memory lifecycle → mode-scoped thin agents:
- Dream extraction →
crux-memory-dream - REM Sleep rebalance →
crux-memory-rem - Recall / query / display (incl.
--totalCanvas) →crux-memory-recall - Ad-hoc create →
crux-memory-remember - Delete →
crux-memory-forget
- Dream extraction →
- Code quality audits, security, CI/CD →
integrity-expert - Documentation sync after source changes →
docs-sync-agent
When Building Specs
During /zoto-spec-create, populate the Assigned Subagent field in each subtask with the appropriate CRUX agent name from the table above based on the subtask's nature.
When Executing Specs
During /zoto-spec-execute, the executor must spawn the agent type specified in each subtask's metadata. If a subtask says generalPurpose, remap it to the correct CRUX agent before spawning.
Rationale
CRUX agents carry domain-specific system prompts, repository conventions, and CRUX notation fluency that generalPurpose agents lack. Using them produces higher-quality output with fewer iterations.
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.