backend

Develop server-side backends, APIs, and authentication logic with layered architecture.

94|49|Updated Mar 25, 2026

Search Tags:#architecture #security #api #validation #backend #ddd #services

Ready to run

npx skills add https://github.com/josipjelic/orchestrated-project-template --skill backend-josipjelic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend
Source: https://github.com/josipjelic/orchestrated-project-template/tree/main/.claude/skills/backend
Command: npx skills add https://github.com/josipjelic/orchestrated-project-template --skill backend-josipjelic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams design and implement the server-side of applications, including API endpoints, business logic, authentication, background jobs, and third-party integrations, while keeping architecture boundaries and security in focus.

Core Features & Use Cases

Endpoint design and implementation: create and modify API handlers within defined architectural boundaries.
Security and auth: enforce authentication/authorization and validate inputs across services.
Performance and maintainability: apply layering (handler → service → repository) and choose appropriate migration and deployment strategies.

Quick Start

Create a new authenticated GET /health endpoint that returns service status.

Frequently Asked Questions about backend

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

FAQPage Schema

How do I structure API endpoints with clear architectural boundaries?▼

Secure backend APIs by enforcing authentication and authorization logic across all services. Input validation is applied to incoming requests to prevent unauthorized access and maintain secure, scalable operations across the server-side application.

How do I implement authentication logic for a backend service?▼

What's the best way to handle database migrations and deployment for scalable APIs?▼

Handle database migrations by choosing appropriate migration strategies that align with the project's tooling and patterns. This maintains performance and maintainability while ensuring scalable operations across services and databases.

Does this backend architecture approach work with domain-driven design?▼

Yes, this backend architecture approach works with domain-driven design by applying clear architectural boundaries and layered implementation. It supports DDD principles through proper separation of handler, service, and repository layers.

Why does input validation matter for backend security and service operations?▼

Input validation matters for backend security because it prevents malicious or malformed data from reaching your services and databases. Enforcing validation across all entry points maintains secure, scalable operations throughout the application.