agentleFS
emanuelegreco29emanuelegreco29/codexpiator/skills/codexpiator-backend/SKILL.md

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

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.
  • MicrosoftSkill

    help

    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

  • OpenAISkill

    supabase

    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

  • VercelSkill

    deploy

    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

  • NVIDIASkill

    testing

    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

  • MicrosoftSkill

    api-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

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
  1. Distinctive:

    Read the specific file below for the concern at hand.

    line 9
  2. Distinctive:

    Before considering backend work done:

    line 30

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Codexpiator Backend

Single-purpose reference files for backend engineering decisions. Read the specific file below for the concern at hand.

FileRead this when...
api-design.mdDesigning endpoints, naming, pagination, response shape (for breaking-change/versioning policy, see codexpiator-architecture/api-contracts-and-versioning.md)
data-modeling-and-db.mdSchema design, indexing, migrations, SQL vs NoSQL
auth-and-authorization.mdAuthentication mechanism, session/token trade-offs, password storage
error-handling-and-logging.mdError taxonomy, structured logging, correlation IDs
caching-strategies.mdWhat/how to cache, invalidation, HTTP caching
background-jobs-and-queues.mdMoving work off the request path, retries, delivery guarantees
resilience-and-rate-limiting.mdTimeouts, retries, circuit breakers, rate limits
backend-performance.mdProfiling, DB bottlenecks, scaling direction
backend-testing.mdUnit 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:

  1. For a Python project, confirm dependencies are managed via uv, pdm, or poetry and the code passes Ruff (see ${CLAUDE_PLUGIN_ROOT}/shared/stack-recommendations.md).
  2. 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.md and codexpiator-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.
  3. For anything security-sensitive (auth, input handling, data access), also invoke the codexpiator:security skill and run its relevant checks — security behavior needs to be tested as thoroughly as functional behavior, not assumed correct because it looks right.
  4. Suggest running /codexpiator:audit if 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.