AI-Software-Engineering-Workflow-Template / rules
Cursor rule0 starsChanged 6 months agoMITView on GitHub
AI coding execution rules
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,243 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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/architecture-rules.mdcCursor rule
- .cursor/rules/project-rules.mdcCursor rule
- implementation-reportSkill
- launch-checkSkill
- mvp-scope-checkSkill
- plan-from-issueSkill
- review-artifactSkill
- scale-automation-reviewSkill
- validate-ideaSkill
- implementation-reportSkill
- launch-checkSkill
- mvp-scope-checkSkill
- plan-from-issueSkill
- review-artifactSkill
- scale-automation-reviewSkill
- validate-ideaSkill
The file
Show its rules and text
We split this ai-coding-rules.mdc into the rules it gives an agent
15 rules. About 0 are common, 14 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈14
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 12
Read AI_WORKFLOW.md and TOOLCHAIN.md
- Distinctive: line 13
Read required project documents (see Required Reading in AGENTS.md)
- Distinctive: line 17
WAIT for human confirmation before modifying code
- Distinctive: line 22
Only modify files within the task's Allowed Files scope.
- Distinctive: line 23
Do NOT modify Forbidden Files.
- Distinctive: line 24
Do NOT expand task scope.
- Distinctive: line 25
Do NOT refactor unrelated code.
- Distinctive: line 26
Do NOT introduce new dependencies without justification.
- Distinctive: line 27
Do NOT bypass or skip tests.
- Distinctive: line 28
Do NOT bypass Human Gate — every Stage Gate requires human approval to proceed.
- Distinctive: line 29
Do NOT skip Plan Artifact — always generate and get approval before coding.
- Distinctive: line 33
STOP immediately and report if:
- Distinctive: line 65
When receiving feedback from the supervisor agent or user, translate it into concrete engineering constraints.
- Distinctive: line 66
Do not interpret vague feedback loosely — ask for clarification if needed.
- Distinctive: line 67
Update your task understanding after receiving feedback.
≈ “Common” is an estimate: at least 1 in 5 of the 6,809 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: AI coding execution rules globs: alwaysApply: true --- # AI Coding Rules ## Before Writing Code 1. Read AGENTS.md 2. Read AI_WORKFLOW.md and TOOLCHAIN.md 3. Read required project documents (see Required Reading in AGENTS.md) 4. Identify which Stage Gate the current task belongs to (see docs/11_stage_gates.md) 5. Understand the current Issue or task's scope, boundaries, and acceptance criteria 6. Generate a Plan Artifact before implementing 7. WAIT for human confirmation before modifying code ## Execution Rules - Work in small steps. Do not make large, sweeping changes. - Only modify files within the task's Allowed Files scope. - Do NOT modify Forbidden Files. - Do NOT expand task scope. - Do NOT refactor unrelated code. - Do NOT introduce new dependencies without justification. - Do NOT bypass or skip tests. - Do NOT bypass Human Gate — every Stage Gate requires human approval to proceed. - Do NOT skip Plan Artifact — always generate and get approval before coding. ## Stop Conditions STOP immediately and report if: 1. You are about to modify a forbidden file. 2. The task scope is creeping. 3. You would change core architecture. 4. You want to introduce a new dependency. 5. Tests are failing but you want to continue adding features. 6. The UI/interaction result deviates from expectation. 7. Multiple agents would modify the same core file. 8. You cannot determine the risk of a change. 9. You are unsure about the correct approach. 10. You are implementing without Idea Gate validation. 11. MVP scope is expanding beyond what was agreed. 12. You want to skip Plan Artifact or Human Review. 13. CI is failing but you want to merge. 14. Launch metrics are undefined but release is requested. 15. You want to automate a process that requires human judgment. Stopping is not failure — it prevents errors from compounding. ## After Completing Changes You MUST output: 1. **Modified files**: List all changed file paths and reasons. 2. **Test results**: What tests you ran and whether they passed. 3. **Risk assessment**: Possible side effects, TODO items, documentation updates needed. 4. **Review suggestions**: Which files need human review and why. 5. **Artifact status**: Which Artifact was generated and its review status. ## Feedback Handling - When receiving feedback from the supervisor agent or user, translate it into concrete engineering constraints. - Do not interpret vague feedback loosely — ask for clarification if needed. - Update your task understanding after receiving feedback. - Direction-level feedback may trigger a Stage Gate decision (refine, narrow, redesign, etc.).
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.

