backend

Design modular, auditable, multi-tenant backends and APIs with OAuth2/OIDC.

Updated Nov 27, 2025
One-click install
npx skills add https://github.com/HenderOrlando/booklyapp --skill backend-henderorlando
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend
Source: https://github.com/HenderOrlando/booklyapp/tree/main/.windsurf/skills/backend
Command: npx skills add https://github.com/HenderOrlando/booklyapp --skill backend-henderorlando

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complex challenge of designing and building secure, scalable, and maintainable backend systems and APIs for various industries.

Core Features & Use Cases

  • Modular Design: Promotes a clean separation of concerns using hexagonal architecture and DDD principles.
  • API Development: Supports REST and GraphQL with robust versioning, error handling, and pagination.
  • Security & Auth: Implements strong authentication (OAuth2/OIDC) and authorization (RBAC/ABAC).
  • Multi-tenancy: Ensures data isolation and role management for different tenants.
  • Data Modeling: Guides proper database schema design, indexing, and migrations, including ledger patterns when necessary.
  • Asynchronous Operations: Manages background jobs and event-driven architectures.
  • Observability: Integrates logging, metrics, and tracing for operational insight.
  • Use Case: Developing a new financial service platform requiring secure multi-tenant data handling, auditable transactions, and real-time notifications.

Quick Start

Use the backend skill to design a secure, multi-tenant API for a SaaS product.

Frequently Asked Questions about backend

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

FAQPage Schema
How do I design a secure multi-tenant backend architecture for a SaaS API?

To build a multi-tenant API, enforce strict data isolation per tenant, implement OAuth2/OIDC for authentication, and apply RBAC or ABAC for authorization. Using DDD and hexagonal architecture ensures modular, auditable backend operations.

What is the best way to structure a modular backend using Domain-Driven Design and CQRS?

Structuring a modular backend with DDD and CQRS involves separating read and write models, encapsulating business logic in domain layers, and using hexagonal architecture to decouple core logic from API adapters and data persistence mechanisms.

How do I handle asynchronous jobs and event-driven architecture in an API backend?

Handling asynchronous jobs in an API backend requires integrating background job queues and event-driven architecture patterns. This manages long-running operations and ensures resilient background processing without blocking main API request threads.

How do I implement API versioning and error handling for REST and GraphQL endpoints?

Implementing API versioning and error handling requires defining explicit versioning strategies for REST and GraphQL endpoints. Proper data modeling, consistent error responses, and pagination ensure robust and maintainable API interfaces over time.

Does this backend architecture approach support both SQL and NoSQL database persistence?

Yes, this backend architecture approach supports both SQL and NoSQL database persistence. It guides proper database schema design, indexing, and migrations, including specific ledger patterns when necessary for auditable financial transactions.

How do I add observability and operational tracing to a distributed backend system?

Adding observability to a distributed backend system requires integrating comprehensive logging, metrics collection, and distributed tracing. This provides deep operational insight into background jobs, queues, and overall API health monitoring.