backend

Implement API endpoints, business logic, authentication, and background jobs in a layered backend architecture.

1|Updated Apr 23, 2026

Search Tags:#architecture #authorization #authentication #api #validation #backend #services

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backend development often involves repetitive setup, coupling concerns, and inconsistent security and validation across APIs. This skill provides a disciplined pattern for building and evolving server-side endpoints, services, and integrations while preserving architecture boundaries.

Core Features & Use Cases

Enforces architecture boundaries and layered design for backend systems, including endpoint handlers, services, and repositories.
Covers authentication/authorization, migrations, and interaction with external services, with guardrails for validation and error handling.
Use cases include adding a new API endpoint, implementing business logic, integrating a third-party service, or optimizing server performance and caching.

Quick Start

Configure a new backend module by following the onboarding prompt to scaffold endpoints, services, and security scaffolding.

Frequently Asked Questions about backend

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

FAQPage Schema

How do I structure a scalable backend with clean architecture boundaries?▼

Building a scalable backend requires domain-driven design and layered architecture to separate endpoint handlers, services, and repositories. This separation preserves architecture boundaries, ensuring server-side code remains maintainable and secure.

What is the best way to add authentication and authorization to an API?▼

Implementing API authentication requires dedicated security scaffolding and guardrails within the backend architecture. This ensures proper validation and error handling for secure access control across your server-side stack.

Can I use this backend architecture pattern with Python or Go projects?▼

Yes, this backend architecture pattern applies to projects across Node.js, Python, Java, Go, or any stack. It enforces domain-driven design, migrations, and safe deployment practices using the project's existing tooling.

How do I integrate a third-party service without coupling backend concerns?▼

Integrating external services requires isolating the interaction within dedicated service layers to prevent coupling concerns. This maintains consistent validation and error handling across the backend architecture.

Why do I need input validation and migrations for new API endpoints?▼

Input validation and migrations are needed for new API endpoints to enforce safe deployment practices and maintain data integrity. They provide necessary guardrails within the layered architecture to handle errors securely.