Skip to content
cccskills
FreePublished on GitHub

cxc-dev-backend

Use for APIs, servers and app databases. Triggers: REST, GraphQL, migration, query optimization, middleware, caching, queues, 백엔드, API 작업, 마이그레이션, 쿼리 최적화.

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

See how to install

Files included (25)

  • SKILL.md3.8 KB
  • agents/openai.yaml164 B
  • references/core/01-backend-setup.md4.1 KB
  • references/core/02-connections-queues.md5.7 KB
  • references/core/03-request-contracts.md4.3 KB
  • references/core/04-production-delivery.md5.9 KB
  • references/core/anti-slop-backend.md4.8 KB
  • references/core/api-design.md6.6 KB
  • references/core/api-lifecycle.md8.6 KB
  • references/core/architecture.md6.0 KB
  • references/core/caching.md6.1 KB
  • references/core/crud-api.md2.6 KB
  • references/core/health-checks.md1.1 KB
  • references/core/llm-integration.md9.4 KB
  • references/core/ml-serving.md8.3 KB
  • references/core/mobile-api.md10.8 KB
  • references/core/observability.md8.6 KB
  • references/core/process-isolation.md3.0 KB
  • references/core/resilience.md1.5 KB
  • references/core/security.md445 B
  • references/stacks/database.md4.8 KB
  • references/stacks/node.md4.4 KB
  • references/stacks/python.md4.5 KB
  • scripts/README.md590 B
  • scripts/scaffold-audit.sh5.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Dev-Backend — Production-Grade Backend Engineering

Ownership boundary: This skill owns API design, app architecture, database optimization, error handling, middleware, queues, long-lived connections, and app-level observability/health hooks. Deployment strategy, rollback proof, rollout shape, SLOs, alert routing, incident response, and operational readiness gates are owned by dev-devops. Backend exposes the app-level hooks that DevOps operational gates consume.

Build reliable, secure, and maintainable server-side applications. This skill is a routing role that activates by change-surface: whenever the work primarily touches APIs, servers, services, jobs, data access, schemas, migrations, or operational backend behavior, use this skill and then read the relevant references.

Before backend work, read dev for classification, fast paths, rule authority, family invariants, verification, and safety; current/public evidence follows its Conditional Routes.

Modular References

ConditionReference
C2 ordinary CRUD/resource sliceCRUD API alone suffices
New/changed API style or C3+ API workAPI design
Versioning, deprecation, or API migrationAPI lifecycle
Stack detection, ambiguous technology, or architecture/protocol selectionSetup; C3+: Architecture
New endpoints, classes, or modulesAnti-slop
SSE/WebSocket, runtime timeouts/drain/request IDs, or async queuesConnections and queues
Layer placement, error mapping/Result, middleware order, or response contractsRequest contracts
Caching, observability, template evaluation, performance, SEO, handoff, or delivery checklistProduction delivery
Production/long-lived servicesObservability, health checks
CPU-bound/untrusted workProcess isolation
Cache optimizationCaching patterns
Node/TypeScript, Python, or database workNode, Python, database, respectively
ML deployment, RAG/LLM integration, or mobile APIsML serving, LLM integration, mobile API, respectively
Auth/input/security policycxc-dev-security
Deployment, analytics, frontend contracts, testing, RCA, or scaffoldingHandoff owners

Read api-design.md + anti-slop-backend.md first, then the relevant stack file. For C2 ordinary slices, crud-api.md alone suffices; read api-design.md/architecture.md for new API styles or C3+ work.

3. Error Handling

For error mapping and the conditional Result pattern, read Error handling.

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

Use for AST search and codemods. Triggers: ast-grep, sg, function/call/class/import, empty catch, missing await, YAML rules.

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

lidge-jun/codexclaw47Updated Oct 9, 2026

Use for coding, PR delivery, scaffolding and QA. Triggers: develop, fix, refactor, test, review, docs, browse, stacked PR, 개발, 수정, 검토, 스택 PR.

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

lidge-jun/codexclaw47Updated Oct 9, 2026

Use for module boundaries and dependencies. Triggers: circular import, coupling, barrel, re-export, validation placement, 모듈 경계, 순환 참조.

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

lidge-jun/codexclaw47Updated Oct 9, 2026

Use for code/PR/diff review and refactor audits. Triggers: review this, before merge, antipattern, 리뷰, 코드 리뷰, 머지 전에 확인.

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

lidge-jun/codexclaw47Updated Oct 9, 2026

Use for analytics and data pipelines. Triggers: ETL, ELT, data quality, SQL optimization, schema drift, backfill, 데이터 파이프라인, 데이터 품질, 백필.

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

lidge-jun/codexclaw47Updated Oct 9, 2026

Use for debugging and system comprehension. Triggers: debug this, root cause, how does X work, reverse engineer, 왜 안 돼, 디버깅, 원인 분석, 로직 파악, 뜯어봐.

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

lidge-jun/codexclaw47Updated Oct 9, 2026

See all skills by lidge-jun

Report a problem with this skill