backend-api-engineer
Skill0 starsChanged 23 days agoMITView on GitHub
Build and review maintainable backend endpoints, service boundaries, validation, error contracts, pagination and integration reliability.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- brathod1432/skill-stacktheir own version, first seen Jul 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- brathod1432/skill-stack★ 0same 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 repository28 other files it gives its agents.
- agent-skill-security-auditorSkill
- backend-debuggingSkill
- backup-disaster-recoverySkill
- code-review-prSkill
- database-transaction-integritySkill
- dependency-supply-chain-auditorSkill
- devops-ci-cdSkill
- documentation-handoverSkill
- frontend-design-directionSkill
- llm-api-integrationSkill
- load-resilience-testingSkill
- mcp-integration-builderSkill
- observability-monitoringSkill
- performance-accessibilitySkill
- playwright-webapp-testingSkill
- privacy-data-governanceSkill
- product-business-analystSkill
- project-bootstrap-environmentsSkill
- qa-release-gatekeeperSkill
- qa-test-strategySkill
- react-artifacts-builderSkill
- security-authorization-auditorSkill
- skill-authoring-toolkitSkill
- skill-evaluation-benchmarkSkill
- software-architectSkill
- technical-project-orchestratorSkill
- theme-design-systemSkill
- visual-assets-designSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 11
Place business rules in a testable domain/service layer.
- Distinctive: line 14
Add unit + integration + negative tests for normal and failure behavior.
- Distinctive: line 15
Document compatibility impacts and migration/flag requirements before release.
- Distinctive: line 18
Do not perform production writes or expose credentials while debugging.
≈ “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
Backend API engineering
- Inspect live code, framework conventions, API contracts, data model, auth middleware and current tests before implementing.
- Specify the endpoint or event contract: actors, request/response schema, status/error codes, idempotency and pagination where needed.
- Enforce validation, authorization and ownership on the server; do not trust client-provided role or scope values.
- Place business rules in a testable domain/service layer; keep transport handlers thin and errors consistent.
- Define timeouts, bounded retries and circuit-breaker behavior for external dependencies; avoid retrying non-idempotent operations blindly.
- Coordinate transaction boundaries and invariants with database-transaction-integrity; consider version/rollback compatibility.
- Add unit + integration + negative tests for normal and failure behavior. Verify observability without leaking credentials or personal data.
- Document compatibility impacts and migration/flag requirements before release.
Output: contract, touched components, behavior changes, verification evidence, security/reliability risks. Do not perform production writes or expose credentials while debugging.
Reference service boundary
The examples/reference-platform project demonstrates transaction-safe application-domain logic for bookings and receipts. No HTTP API or real identity provider is bundled: design response contracts and server-side authentication separately, and verify route-to-service authorization through integration tests. A green domain test cannot establish API compliance.
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.