build-backend
Skill15 starsChanged 3 months agoMITView on GitHub
Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Pdiamondz1/hma_project_foundationtheir own version, first seen Oct 9, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Pdiamondz1/hma_project_foundation★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- examples/AGENTS.mdAGENTS.md
- build-frontendSkill
- engineering-loopSkill
- maintain-codex-wikiSkill
- operate-devopsSkill
- orchestrate-engineeringSkill
- review-codeSkill
- review-securitySkill
- test-softwareSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Keep multi-write operations atomic where partial state would violate invariants.
- Distinctive: line 17
Do not query or mutate production data without explicit authorization.
- Distinctive: line 18
Do not fabricate migration, framework, or API behavior.
- Distinctive: line 19
Avoid broad service abstractions that are used once.
- Distinctive: line 23
Read references/contracts-and-data.md when the task changes a public API, schema, transaction, job, or integration.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Build Backend
Domain contract
- Trace changed behavior from input through validation, authorization, domain logic, persistence, side effects, and response mapping.
- Preserve published contracts unless the request explicitly changes them.
- Enforce authorization at a trustworthy server-side boundary.
- Validate untrusted input before domain or persistence operations.
- Keep multi-write operations atomic where partial state would violate invariants.
- Design external calls for timeouts, retries, idempotency, and duplicate delivery where applicable.
- Do not query or mutate production data without explicit authorization.
- Do not fabricate migration, framework, or API behavior; verify version-sensitive details.
- Avoid broad service abstractions that are used once.
Execute and verify
Read references/contracts-and-data.md when the task changes a public API, schema, transaction, job, or integration.
Implement the smallest change at the owning layer. Cover success, invalid input, authorization, and material failure paths. Prefer:
reproducing/focused test → contract/integration test → type/lint → buildFor migrations, validate forward behavior and document rollback or roll-forward strategy.
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.