backend
Skill0 starsChanged 5 months agoMITView on GitHub
Design and generate external backend API code (any language/framework — Go, Rust, Python, PHP, JavaScript, Ruby, etc.) that serves a Next.js JSX frontend. Use for API endpoints, auth, validation, and data modeling on a separate backend server.
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
2
Distinctive
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 18
Follow existing convention if one exists.
- Distinctive: line 25
Never return untyped raw objects
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Read
.agents/software-principles/SKILL.mdfirst.
Pre-Code Checklist
- Resource + HTTP method + action
- Request → response contract (input shape, output shape, errors)
- Auth requirement (public / authenticated / role-gated)
- Failure scenarios + validation rules
Response Envelope
Follow existing convention if one exists. If starting fresh, pick one shape and apply consistently. Never mix shapes across endpoints.
Required regardless of shape:
- Success and error responses must be distinguishable
- Validation errors must include field-level detail, not just a generic message
- Error responses must never expose stack traces, query strings, or internal paths
- Never return untyped raw objects
Design Rules
- Versioning — prefix all routes
/api/v1/ - Endpoints — plural nouns, kebab-case:
/api/v1/posts,/api/v1/post-categories - Query params —
page,limit,sort,filter[key]=value - Auth —
Authorization: Bearer <token>(JWT/opaque) or HTTP-only cookie (same parent domain) - Pagination — all list endpoints:
data: { items: T[], pagination: { page, limit, totalItems, totalPages } } - CORS — exact origin only. Never wildcard with credentials
- Naming — camelCase or snake_case — consistent throughout project
- Docs — expose OpenAPI spec at
/api/docsor/openapi.jsonwhen feasible
Architecture
- Route handlers thin — business logic in service/use-case layer
- Global error handler → catches all unhandled errors → safe fallback response
- DB connection pooling. Async/non-blocking I/O
Security (non-negotiable)
- Secrets via env vars only — never hardcoded
- Parameterized queries/ORM — no string-concatenated SQL
- Hash passwords (bcrypt/argon2 or language equivalent)
- Rate-limit auth endpoints (login, register, password reset)
- Limit request body size
- Security headers in production (X-Frame-Options, CSP, HSTS)
- Validate all input at boundary before processing
Never Do
- Trust unvalidated client input or hardcode secrets
- Business logic directly in route handlers
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- langwatch/langwatch★ 5ksame name
- AlexPEClub/ai-coding-starter-kit★ 382same name
- hushh-labs/hushh-research★ 39same name
- ElmatadorZ/skynetclaw★ 16same name
- DojoCodingLabs/code-sensei★ 14same name
- darknecrocities/SkillBuilder★ 13same name
- udaysharmadev/Skills★ 11same name
- mnzralee/claude-multi-agent-architecture★ 8same name
- darker2016/WorkbuddySkillGroups4DSH★ 6same name
- MarvelCollin/agent-skills★ 4same name
8 more not listed
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.
Used alongsideProjects with it also use security, help and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
0xSeroSkillsecurity
Also in 4 projects that use this
MicrosoftSkillhelp
Entry point for the MedImageInsight plugin, covering the getting-started walkthrough, how the skills work, what MI2 is, and troubleshooting.
Also in 3 projects that use this
VercelSkilldeploy
Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".
Also in 3 projects that use this
NVIDIASkilltesting
Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.
Also in 3 projects that use this
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- frontend-designSkill
- frontendSkill
- fullstackSkill
- software-principlesSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

