aidd-template-scale / rules
Cursor rule0 starsChanged 2 months agoMITView on GitHub
Docker Compose (local development)
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,144 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 repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/CLAUDE.mdcCursor rule
- .cursor/rules/code-style.mdcCursor rule
- .cursor/rules/github-cli-pr.mdcCursor rule
- .cursor/rules/git.mdcCursor rule
- .cursor/rules/git-worktree.mdcCursor rule
- .cursor/rules/ticket-driven-workflow.mdcCursor rule
- address-pr-feedbackSkill
- agentic-e2eSkill
- close-ticketSkill
- docs-app-syncSkill
- review-dependabot-prSkill
- screen-to-specSkill
- spec-lookupSkill
- spec-to-screenSkill
- start-ticketSkill
- address-pr-feedbackSkill
- agentic-e2eSkill
- close-ticketSkill
- docs-app-syncSkill
- review-dependabot-prSkill
- screen-to-specSkill
- spec-lookupSkill
- spec-to-screenSkill
- start-ticketSkill
The file
We split this docker-compose-local.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
- Very specific: line 13
Run docker compose / docker-compose only after cd docker-dev.
- Very specific: line 14
Do not run compose from the repository root with -f docker-dev/compose.yaml in new docs or agent answers.
- Very specific: line 24
If docker-dev/ does not exist yet, skip Docker steps and note that in the PR.
≈ “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: false description: Docker Compose (local development) globs: docker-dev/** --- # Docker Compose (local development) Apply only when a `docker-dev/` directory exists in your project. ## Rule - Run `docker compose` / `docker-compose` **only after** `cd docker-dev`. - Do not run compose from the repository root with `-f docker-dev/compose.yaml` in new docs or agent answers. ## Example ```bash cd docker-dev docker compose up -d --build docker compose exec <service> <command> ``` If `docker-dev/` does not exist yet, skip Docker steps and note that in the PR.
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.