Skip to content
cccskills
FreePublished on GitHub

backend-mindset

Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

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

See how to install

Files included (8)

  • SKILL.md2.2 KB
  • references/api-design.md4.7 KB
  • references/architecture.md5.4 KB
  • references/authentication.md6.9 KB
  • references/code-quality.md7.3 KB
  • references/performance.md8.2 KB
  • references/security.md6.2 KB
  • references/testing.md5.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Backend Development Skill

References

FileCovers
references/api-design.mdREST, GraphQL, gRPC — URL rules, status codes, protocol selection
references/authentication.mdOAuth 2.1, JWT, RBAC, MFA, session management
references/security.mdOWASP Top 10 (2025), rate limiting, headers, secrets
references/performance.mdIndexing, caching patterns, load balancing, async processing
references/architecture.mdMicroservices patterns, event-driven, CQRS, scalability
references/testing.mdTDD, test pyramid, contract testing, migration tests
references/code-quality.mdSOLID, design patterns, refactoring signals

Quick Decision Guide

NeedChoose
Public / browser clientsREST or GraphQL
Internal high-throughputgRPC
Flexible data fetchingGraphQL
StreaminggRPC (bidirectional) or SSE
Single team, unclear domainMonolith
Multiple autonomous teamsMicroservices
Audit trail requiredEvent Sourcing
Read/write load imbalanceCQRS
Task >200ms off request pathAsync queue
Session across instancesRedis (never in-process)

Defaults

  • Every non-public endpoint requires explicit auth declaration — no implicit defaults
  • Input validation at every system boundary (API handler, event consumer, file parser)
  • Parameterized queries everywhere — never string-interpolate user input
  • Rate limiting on auth endpoints, public API, and file upload (see security.md for thresholds)
  • Integration tests hit real infrastructure (Testcontainers) — in-memory substitutes hide real bugs
  • TDD: write the failing test before any implementation
  • Services return result envelopes — never throw for expected failures (404, 400, 409)

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

Terse output mode — strips filler/articles/hedging, ~75% token reduction. Activate whenever: context is filling up, user says be brief/terse/caveman/less tokens, or CAVEMAN_TRIGGERED appears in context. Persists every response until CAVEMAN_RELEASED or user says stop/normal mode.

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

DangQuangSE/team-development-skills19Updated Oct 9, 2026

Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.

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

DangQuangSE/team-development-skills19Updated Oct 9, 2026

Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.

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

DangQuangSE/team-development-skills19Updated Oct 9, 2026

ck-fix

Free

Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).

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

DangQuangSE/team-development-skills19Updated Oct 9, 2026

Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.

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

DangQuangSE/team-development-skills19Updated Oct 9, 2026

Create a machine-readable phased JSON plan bundle from a spec or feature description. Produces a compact master manifest plus per-phase step files for resumable ck:cook execution.

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

DangQuangSE/team-development-skills19Updated Oct 9, 2026

See all skills by DangQuangSE

Report a problem with this skill