backend-designer-skill

Design backend architectures and API contracts from architecture artifacts.

Updated Jan 20, 2026

Search Tags:#design #architecture #decisions #backend #auth #service-design #api-contracts

Ready to run

npx skills add https://github.com/Galharel/my-codex-skills --skill backend-designer-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend-designer-skill
Source: https://github.com/Galharel/my-codex-skills/tree/main/backend-designer-skill
Command: npx skills add https://github.com/Galharel/my-codex-skills --skill backend-designer-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design backend architectures, define API contracts, establish core service boundaries, and choose language/framework options based on architecture and story artifacts. It guides decisions around backend stack, authentication strategy, and service design to reduce later rework.

Core Features & Use Cases

Define canonical backend architecture and API surface from architecture artifacts.
Establish clear domain boundaries, core services, and responsibilities to align with business requirements.
Provide recommended language/framework choices with rationale (plus alternatives and trade-offs) to support architecture decisions.

Quick Start

Use this skill to synthesize a backend design from the provided architecture artifacts and produce a concrete design package.

Frequently Asked Questions about backend-designer-skill

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

FAQPage Schema

How do I design backend architecture and API contracts from story artifacts?▼

You design backend architecture and API contracts by synthesizing architecture handoff documents and story maps into a concrete design package. This process defines domain boundaries, core services, and language frameworks to align service design with business requirements.

What is the best way to choose a backend stack and authentication strategy?▼

Choosing a backend stack and authentication strategy involves evaluating architecture artifacts to provide recommended language frameworks with rationale. This approach outlines alternatives and trade-offs to support architecture decisions and reduce later rework.

How do I establish core service boundaries and domain responsibilities?▼

Establishing core service boundaries requires analyzing architecture packets and PRD fallbacks to define canonical backend architecture. This aligns service responsibilities and API surfaces directly with mapped business requirements.

Can I define API style and error handling decisions using architecture packets?▼

Yes, you can define API style and error handling decisions by processing architecture packet JSON files. The output produces authoritative backend design documents specifying data access, observability, and API contracts.

Does this backend service design approach work without external dependencies?▼

Yes, this backend service design approach works without external dependencies because it operates entirely on local architecture and story artifacts. It generates standalone design packets and markdown documentation directly from your provided inputs.