sdlc-kit
AGENTS.md1 starsChanged 10 days agoMITView on GitHub
This repo uses the sdlc-kit ticket workflow: a Jira or Linear ticket in, a reviewed merge request out (GitLab or GitHub). The kit's rules, skills and scripts live in .cursor/, whichever agent you are. Before any ticket work, read and follow: - .cursor/rules/00-ticket-workflow.mdc: the phases, state files and hard rules - .cursor/rules/10-general-standards.mdc: size limits, naming and structure Before editing a file, read the standards for its kind: - backend Python: .cursor/rules/20-backend-standards.mdc - frontend TypeScript: .cursor/rules/30-frontend-standards.mdc - models, migrations, repositories and…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 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 repository22 other files it gives its agents.
- .cursor/rules/00-ticket-workflow.mdcCursor rule
- .cursor/rules/10-general-standards.mdcCursor rule
- .cursor/rules/20-backend-standards.mdcCursor rule
- .cursor/rules/30-frontend-standards.mdcCursor rule
- .cursor/rules/40-database-standards.mdcCursor rule
- .cursor/rules/50-testing-standards.mdcCursor rule
- backend-implementSkill
- chatSkill
- codebase-exploreSkill
- db-migrationSkill
- frontend-implementSkill
- gitlab-mrSkill
- implementation-planSkill
- jira-createSkill
- mr-feedbackSkill
- mr-reviewSkill
- quick-fixSkill
- run-checksSkill
- self-reviewSkill
- ticket-intakeSkill
- ticket-qaSkill
- write-testsSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- could be automatic: a setting could enforce it
- Distinctive: line 6
Before any ticket work, read and follow:
- Distinctive: line 10
Before editing a file, read the standards for its kind:
- Very specific: line 16
Use the skill the workflow names for each phase (.agents/skills/<name>/SKILL.md, linked to .cursor/skills/).
- Distinctive: line 18
Never merge, approve or force-push, and never touch Perforce, staging, production or Elasticsearch mappings.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
sdlc-kit
This repo uses the sdlc-kit ticket workflow: a Jira or Linear ticket in, a reviewed merge request out (GitLab or GitHub). The kit's
rules, skills and scripts live in .cursor/, whichever agent you are.
Before any ticket work, read and follow:
.cursor/rules/00-ticket-workflow.mdc: the phases, state files and hard rules.cursor/rules/10-general-standards.mdc: size limits, naming and structure
Before editing a file, read the standards for its kind:
- backend Python:
.cursor/rules/20-backend-standards.mdc - frontend TypeScript:
.cursor/rules/30-frontend-standards.mdc - models, migrations, repositories and search code:
.cursor/rules/40-database-standards.mdc - tests:
.cursor/rules/50-testing-standards.mdc
Use the skill the workflow names for each phase (.agents/skills/<name>/SKILL.md, linked to .cursor/skills/).
Work is done only when bash .cursor/skills/run-checks/scripts/check_all.sh prints ALL PASS.
Never merge, approve or force-push, and never touch Perforce, staging, production or Elasticsearch mappings.
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.