backend
Skill1 starsChanged 6 days agoMITView on GitHub
Backend engineering guidance - API design and contracts, data modeling and databases, authentication and authorization implementation (sessions vs JWT, password hashing - see codexpiator:security for the threat-model/hardening side), error handling and logging, caching, background jobs and queues, resilience and rate limiting, backend performance, and backend testing. Use for any server-side/API/data-layer question.
21 other projects use a version of this.
Adopted by
Most recently taken up by
- nomorehappypath/nomorehappypaththeir own version, first seen Nov 15, 2026
- gabros20/backend-skilltheir own version, first seen Nov 1, 2026
- hushh-labs/hushh-researchtheir own version, first seen Nov 1, 2026
- darknecrocities/SkillBuildertheir own version, first seen Nov 1, 2026
- marcusbelz/di2-starter-kittheir own version, first seen Oct 31, 2026
- hilmifawwazsaad/NextJS-js-Boilerplatetheir own version, first seen Oct 20, 2026
Used with
Projects with it also use help, supabase and 3 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.
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
OpenAISkillsupabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector).
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 4 projects that use this
MicrosoftSkillapi-design
Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.
Also in 3 projects that use this
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- langwatch/langwatch★ 5ksame name
- AlexPEClub/ai-coding-starter-kit★ 382same name
- hushh-labs/hushh-research★ 40same name
- nomorehappypath/nomorehappypath★ 22same name
- ElmatadorZ/skynetclaw★ 16same name
- DojoCodingLabs/code-sensei★ 14same name
- darknecrocities/SkillBuilder★ 13same name
- udaysharmadev/Skills★ 13same name
- mnzralee/claude-multi-agent-architecture★ 8same name
- darker2016/WorkbuddySkillGroups4DSH★ 6same name
11 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.
In this repository9 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-integrationSkill
- architectureSkill
- devopsSkill
- dx-gitSkill
- frontendSkill
- securitySkill
- routerSkill
- testing-qaSkill
The file
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 18 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 9
Read the specific file below for the concern at hand.
- Distinctive: line 30
Before considering backend work done:
“Common” is measured: kept by at least 6 in 10 of the 18 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
Codexpiator Backend
Single-purpose reference files for backend engineering decisions. Read the specific file below for the concern at hand.
| File | Read this when... |
api-design.md | Designing endpoints, naming, pagination, response shape (for breaking-change/versioning policy, see codexpiator-architecture/api-contracts-and-versioning.md) |
data-modeling-and-db.md | Schema design, indexing, migrations, SQL vs NoSQL |
auth-and-authorization.md | Authentication mechanism, session/token trade-offs, password storage |
error-handling-and-logging.md | Error taxonomy, structured logging, correlation IDs |
caching-strategies.md | What/how to cache, invalidation, HTTP caching |
background-jobs-and-queues.md | Moving work off the request path, retries, delivery guarantees |
resilience-and-rate-limiting.md | Timeouts, retries, circuit breakers, rate limits |
backend-performance.md | Profiling, DB bottlenecks, scaling direction |
backend-testing.md | Unit vs integration tests, test data for the backend |
For deeper security hardening beyond the how-to in
auth-and-authorization.md, invoke the codexpiator:security skill —
that skill covers the threat model, this one covers the implementation
approach.
Mandatory pre-completion gate for any backend change
Before considering backend work done:
- For a Python project, confirm dependencies are managed via
uv,pdm, orpoetryand the code passes Ruff (see${CLAUDE_PLUGIN_ROOT}/shared/stack-recommendations.md). - Write and run real tests covering every function/endpoint
touched, including edge cases (empty input, boundary values,
invalid/malformed input, concurrent-write scenarios where
relevant) — not just the happy path. Run the full test suite, not
just the new tests in isolation. See
backend-testing.mdandcodexpiator-testing-qa/tdd-workflow.md. 2b. Any new non-idempotent create/payment/webhook endpoint has idempotency-key handling (api-design.md); propose it if the user didn't ask. - For anything security-sensitive (auth, input handling, data
access), also invoke the
codexpiator:securityskill and run its relevant checks — security behavior needs to be tested as thoroughly as functional behavior, not assumed correct because it looks right. - Suggest running
/codexpiator:auditif the change was significant — see${CLAUDE_PLUGIN_ROOT}/shared/collaboration-and-audit-practice.md.
Also see that same shared file for when to ask a clarifying question
(AskUserQuestion when available) instead of guessing.
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.

