mcpField
B
backend-engineer

backend-engineer

github.com/siviter-xyzDevelopment22342 installsUpdated 32w ago
Repository

About backend-engineer

A backend engineering skill for developers designing and implementing backend systems. It offers technology selection guidance and references covering APIs, security, performance, testing, and operations.

Key features

  1. 01Language and framework selection guidance
  2. 02REST, GraphQL, and gRPC design
  3. 03Security and authentication practices
  4. 04Database and performance guidance
  5. 05Testing and CI/CD references
  6. 06Deployment and monitoring practices

Use cases

  1. 01Choosing a backend stack for a project
  2. 02Designing APIs and authentication
  3. 03Planning tests and production deployment

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/siviter-xyz/dot-agent --skill backend-engineer

After installing, type/backend-engineerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
api-design.md
architecture.md
authentication.md
devops.md
implementation-workflow.md
performance.md
security.md
technologies.md
testing.md

Details

From the project README

Backend Engineer

Production-ready backend development with modern technologies, best practices, and proven patterns.

When to Use

  • Designing RESTful, GraphQL, or gRPC APIs
  • Building authentication/authorization systems
  • Optimizing database queries and schemas
  • Implementing caching and performance optimization
  • OWASP Top 10 security mitigation
  • Designing scalable microservices
  • Testing strategies (unit, integration, E2E)
  • CI/CD pipelines and deployment
  • Monitoring and debugging production systems

Technology Selection Guide

Languages: Node.js/TypeScript (full-stack), Python (data/ML), Go (concurrency), Rust (performance) Frameworks: NestJS, FastAPI, Django, Express, Gin Databases: PostgreSQL (ACID), MongoDB (flexible schema), Redis (caching) APIs: REST (simple), GraphQL (flexible), gRPC (performance)

See: references/technologies.md for detailed comparisons

Reference Navigation

Core Technologies:

  • references/technologies.md - Languages, frameworks, databases, message queues, ORMs
  • references/api-design.md - REST, GraphQL, gRPC patterns and best practices

Security & Authentication:

  • references/security.md - OWASP Top 10, security best practices, input validation
  • references/authentication.md - OAuth 2.1, JWT, RBAC, MFA, session management

Performance & Architecture:

  • references/performance.md - Caching, query optimization, load balancing, scaling
  • references/architecture.md - Microservices, event-driven, CQRS, saga patterns

Quality & Operations:

  • references/testing.md - Testing strategies, frameworks, tools, CI/CD testing
  • references/devops.md - Docker, Kubernetes, deployment strategies, monitoring
  • references/implementation-workflow.md - Unified implementation workflow

Key Best Practices

Security: Argon2id passwords, parameterized queries, OAuth 2.1 + PKCE, rate limiting, security headers

Performance: Redis caching (90% DB load reduction), database indexing, CDN, connection pooling

Testing: 70-20-10 pyramid (unit-integration-E2E), contract testing for microservices

DevOps: Blue-green/canary deployments, feature flags, Kubernetes, Prometheus/Grafana monitoring, OpenTelemetry tracing

Quick Decision Matrix

NeedChoose
Fast developmentNode.js + NestJS
Data/ML integrationPython + FastAPI
High concurrencyGo + Gin
Max performanceRust + Axum
ACID transactionsPostgreSQL
Flexible schemaMongoDB
CachingRedis
Internal servicesgRPC
Public APIsGraphQL/REST
Real-time eventsKafka

Implementation Checklist

API: Choose style → Design schema → Validate input → Add auth → Rate limiting → Documentation → Error handling

Database: Choose DB → Design schema → Create indexes → Connection pooling → Migration strategy → Backup/restore → Test performance

Security: OWASP Top 10 → Parameterized queries → OAuth 2.1 + JWT → Security headers → Rate limiting → Input validation → Argon2id passwords

Testing: Unit 70% → Integration 20% → E2E 10% → Load tests → Migration tests → Contract tests (microservices)

Deployment: Docker → CI/CD → Blue-green/canary → Feature flags → Monitoring → Logging → Health checks

Implementation Workflow

When implementing backend code, follow unified implementation workflow patterns. See references/implementation-workflow.md for details.

Comments

Markdown supported