backend-engineer

Design secure backend REST/GraphQL APIs with authentication and microservices patterns.

Updated Sep 9, 2025
One-click install
npx skills add https://github.com/htafolla/chrono-warp-drive --skill backend-engineer-htafolla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-engineer
Source: https://github.com/htafolla/chrono-warp-drive/tree/main/.opencode/skills/backend-engineer
Command: npx skills add https://github.com/htafolla/chrono-warp-drive --skill backend-engineer-htafolla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design and build backend REST/GraphQL services with secure authentication, reliable microservices patterns, and predictable performance.

Core Features & Use Cases

  • API Design: Resource-oriented plural nouns, correct HTTP methods and status codes, versioned routes, cursor-based pagination, and consistent error responses for maintainable client integrations.
  • Authentication & Authorization: JWT with refresh tokens, OAuth2 for third-party access, HTTPS-only transport, rate limiting, and secure password hashing (bcrypt/argon2).
  • Microservices & Reliability: API gateway routing and rate limiting, circuit breakers, message queues for async work, event sourcing for auditable trails, and distributed tracing with OpenTelemetry.

Quick Start

Ask the AI to produce a backend API design and authentication plan for a microservice that needs versioned endpoints, cursor pagination, JWT + refresh auth, and p95 latency under 200ms.

Frequently Asked Questions about backend-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a backend API with JWT refresh tokens and OAuth2?

To design a backend API with JWT refresh tokens and OAuth2, implement HTTPS-only transport, secure password hashing using bcrypt or argon2, and configure rate limiting to control access. This ensures robust authentication and authorization for client integrations.

What is the best way to structure REST API pagination and error responses?

The best way to structure REST API pagination and error responses is using cursor-based pagination for reliable data fetching and consistent error formats. This resource-oriented approach uses plural nouns, correct HTTP methods, and versioned routes for maintainable client integrations.

How do circuit breaker patterns and API gateways improve microservices reliability?

Circuit breaker patterns and API gateways improve microservices reliability by routing requests, enforcing rate limits, and preventing cascading failures. Combined with message queues for async work, they build resilient server architectures that maintain service availability under heavy load.

When should I use cache-aside versus write-through caching strategies?

Use cache-aside versus write-through caching strategies based on your performance targets and resource constraints. Cache-aside loads data on demand, while write-through synchronizes data to the cache and database simultaneously, ensuring predictable response p95 latency for backend services.

Does this approach support distributed tracing and event sourcing for auditable workflows?

Yes, this approach supports distributed tracing and event sourcing for auditable workflows. By implementing OpenTelemetry and event sourcing patterns, your microservices generate auditable trails, enabling precise request tracking and consistent system state reconstruction across async workflows.