tpo-backend-architecture

Defines backend architecture layers, security checklists, and review gates for technical product owners.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-backend-architecture-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tpo-backend-architecture
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/tpo-backend-architecture
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill tpo-backend-architecture-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backend projects often lack consistent architectural rules, leading to scattered business logic, missing authorization checks, unsafe error handling, and untestable code. This Skill gives a Technical Product Owner Agent a complete, reusable rulebook for planning, specifying, and reviewing backend work. ## Core Features & Use Cases - Layered Architecture Rules: Defines API, Application, Domain, Infrastructure, and Observability layers with clear responsibilities and forbidden behaviors for each. - Security & Validation Checklists: Covers authentication, object-level authorization, input validation, structured errors, idempotency, transactions, and secrets handling. - Task & Review Templates: Provides a ready-to-use backend task template for AI developer agents and a review checklist covering tests, observability, and production readiness. - Use Case: When planning a new feature like a payments module, use this Skill to generate a task specification with API contracts, authorization rules, idempotency requirements, and acceptance criteria, then review the implementation against the checklist. ## Quick Start Ask the agent to plan the backend architecture and task specification for a new feature using the backend architecture guidelines.

Frequently Asked Questions about tpo-backend-architecture

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

FAQPage Schema
How do I structure a backend application with clean architecture layers?

Separate the backend into API, Application, Domain, Infrastructure, and Observability layers. The API layer handles routing and validation, the Application layer runs use cases and transactions, the Domain layer owns business rules, and Infrastructure handles databases and external APIs.

What should a backend code review checklist include?

Check request validation, authentication, object-level authorization, structured errors, isolated data access, transaction boundaries, idempotency, adapter-based integrations, and safe logging. Also verify tests cover success, failure, authorization, and edge cases.

How do I write a backend task specification for a developer or AI agent?

Define the goal, scope, expected files and modules, API contract, data changes, business rules, authorization rules, side effects, observability requirements, required tests, and acceptance criteria. This Skill provides a ready-made Markdown template for exactly that.

When should backend operations be idempotent?

Idempotency is required for payments, billing changes, imports, external webhooks, retried AI actions, notifications, order creation, and account creation. Always ask what happens if the same request is sent twice.

Is route-level authorization enough for backend APIs?

No. Being logged in must not grant access to any object by ID. Authorization should be object-level, checking ownership, role, team membership, or explicit permission, with audit logs for sensitive actions.