coding-agent-fabric / rules
Cursor rule1 starsChanged 9 months agoApache-2.0View on GitHub
This project uses: This repository is structured as a pnpm workspace (see pnpm-workspace.yaml). Always use the workspace: protocol when referencing local packages in package.json: pnpm uses a content-addressable store and a non-flat node_modules structure. This ensures:
- Installs packages
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 repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-and-fixSkill
- bumpup-versionsSkill
- clean-projectSkill
- fix-issueSkill
- improve-claude-configSkill
- initialize-projectSkill
- lint-and-fixSkill
- manage-adrSkill
- manage-changelogSkill
- node-upgradeSkill
- security-vulnerability-auditSkill
- setup-dev-envSkill
- sync-readmeSkill
- test-and-fixSkill
- test-integration-dockerSkill
The file
We split this tech-stack.mdc 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 29
Always use the workspace: protocol when referencing local packages in package.json:
≈ “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
---
alwaysApply: true
---
# Tech Stack
This project uses:
- **Package Manager:** [pnpm](https://pnpm.io/)
- **Node.js Version:** (read from [.node-version](mdc:.node-version))
## pnpm Workspace & Monorepo Best Practices
This repository is structured as a pnpm workspace (see [pnpm-workspace.yaml](mdc:pnpm-workspace.yaml)).
### Common Commands
- **Install All Dependencies:** `pnpm install`
- **Add Dependency:**
- To current package: `pnpm add <pkg>`
- As dev dependency: `pnpm add -D <pkg>`
- To workspace root: `pnpm add -w <pkg>`
- **Run Scripts:**
- In current package: `pnpm <script>` (e.g., `pnpm test`)
- In all packages: `pnpm -r <script>`
- In specific package: `pnpm --filter <pkg-name> <script>`
### Workspace Protocol
Always use the `workspace:` protocol when referencing local packages in `package.json`:
```json
{
"dependencies": {
"@my-project/common": "workspace:*"
}
}
```
### Dependency Management
pnpm uses a content-addressable store and a non-flat `node_modules` structure. This ensures:
- **Strictness:** You cannot access dependencies that are not explicitly declared in your `package.json`.
- **Efficiency:** Disk space is saved by sharing package files across projects.
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.