Skip to content

DangQuangSE/team-development-skills / .agents/skills/backend-mindset

backend-mindset

Verified

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.

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)
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall