backend-designer-skill

Design backend architecture, API contracts, core business logic boundaries, and language/framework choices based on architecture/story artifacts. Use when selecting backend stack, auth strategy, and service design.

Jump to install

Repository: diegosouzapw/awesome-omni-skill
Last source activity: February 28, 2026 at 04:04
Detected SKILL.md language: English
Stars: 50
Forks: 19

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/diegosouzapw/awesome-omni-skill --skill backend-designer-skill

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

2 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

artifact-tracking

Token-efficient tracking for AI orchestration. CLI-first for status updates (~50 tokens), agent fallback for complex ops (~1KB). Use when: updating task status, querying blockers, creating progress files, validating phases.

2026-03-02

ash-ai

AshAi extension guidelines for integrating AI capabilities with Ash Framework. Use when implementing vectorization/embeddings, exposing Ash actions as LLM tools, creating prompt-backed actions, or setting up MCP servers. Covers semantic search, LangChain integration, and structured outputs.

2026-03-02

ask-oracle

This skill should be used when solving hard questions, complex architectural problems, or debugging issues that benefit from GPT-5 Pro or GPT-5.1 thinking models with large file context. Use when standard Claude analysis needs deeper reasoning or extended context windows.

2026-03-02

View all from this repository

Backend Designer Skill

Purpose

Produce backend design artifacts that define the API surface, core logic boundaries, and platform choices (language, framework, runtime). Provide recommended defaults and alternatives with pros/cons.

Inputs (authoritative order)

docs/architecture.packet.json

docs/architecture.handoff.backend.md

docs/story-map.json and docs/prd.packet.json (fallback)

If required inputs are missing, ask targeted questions and proceed with clearly labeled TBDs.

Output Files (write under docs/)

docs/backend.design.packet.json (authoritative)

docs/backend.design.md (derived summary)

Required Decisions

Language + framework: recommend and justify (e.g., Python + FastAPI vs Django; Node + NestJS; Go).

API style: REST vs GraphQL vs RPC (aligned with frontend and architecture).

Core logic boundaries: domain services/modules and responsibilities.

Authn/Authz: JWT/session/OAuth/SSO; role/permission model.

Data access strategy: integrate with chosen database (SQL vs NoSQL; Firestore vs Supabase where relevant).

Error handling, retries, observability: define expected behaviors.

Relentless Clarification (Always Use)

Proactively ask questions whenever a decision affects APIs, data access, auth, or reliability. Do not rely on implicit assumptions. Offer up to 3 options with pros/cons and ask the user to choose. Continue until the plan leaves no open decisions. Example format:

Question: (precise decision)

Options:

Option A: pros/cons
Option B: pros/cons

Ask: "Which option should I proceed with?"

Sync Rules

Backend defines the canonical API contract unless explicitly delegated.

Record any API mismatches or unclear data dependencies for the Design Synchronizer.

Preserve traceability to story IDs and FR/NFR IDs.

name	backend-designer-skill
description	Design backend architecture, API contracts, core business logic boundaries, and language/framework choices based on architecture/story artifacts. Use when selecting backend stack, auth strategy, and service design.