Skip to content
cccskills
FreePublished on GitHub

build-backend

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (3)

  • SKILL.md1.6 KB
  • agents/openai.yaml211 B
  • references/contracts-and-data.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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 → build

For migrations, validate forward behavior and document rollback or roll-forward strategy.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Select the smallest useful Codex engineering workflow from this repository's existing skills. Use when a task spans multiple engineering concerns, the user is unsure which skill to invoke, or loading every specialist would waste context; return a recommendation only and do not execute the engineering task.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Implement a repository code or configuration change through reproduction, focused checks, review, and evidence. Use for end-to-end features and fixes; not for explanation-only, review-only, research, content publishing, or production operations.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows, check wiki health, reconcile conflicting guidance, or promote verified knowledge.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

Plan and implement infrastructure, CI/CD, container, deployment, observability, and operational configuration changes with least privilege, staged validation, and rollback awareness. Use for pipelines, infrastructure as code, Kubernetes, containers, release automation, monitoring, and production-readiness work; do not use to perform destructive production actions without explicit authorization.

The English summary is being prepared. Showing the original description.

Phelan164/codex-howto14Updated Oct 17, 2026

See all skills by Phelan164

Report a problem with this skill