메뉴
Use when building web APIs, backend services, or encountering FastAPI/Django/Express/GraphQL questions, microservices architecture, authentication, or message queues - routes to 11 specialist skills rather than giving surface-level generic advice
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when working on a Python task and unsure which specialist to load - routes to type-system, mypy-resolution, project-tooling, delinting, testing, async, scientific-computing, ML-workflows, debugging-and-profiling, or Textual-TUI specialists based on symptoms
Use when starting any UX/UI design task — visual design, IA, interaction, accessibility (WCAG 2.2), user research across mobile, web, desktop, game, and AI surfaces, plus first-principles audience-derived needs analysis. Routes to 11 specialist sheets.
Use when a Claude is taking **standing ownership** of a software product across many sessions — discovery, strategy, specs, and value validation — deciding *what to build, why, for whom,* and *whether it worked*, with continuity, decision provenance, and an authority boundary that escalates irreversible or outward-facing actions to the human owner. Owns the product disciplines: opportunity assessment (JTBD, problem validation, business case), vision/strategy/positioning and intent-roadmapping, PRDs with falsifiable acceptance criteria, delivery orchestration and acceptance, product-value metrics and experimentation, and the product anti-pattern catalog. Orchestrates rather than reimplements: routes sequencing/flow/WSJF to `/axiom-program-management`, plans to `/axiom-planning`, solution/architecture to `/axiom-solution-architect`, research method to `/lyra-ux-designer`. Do **not** load to build one feature, choose an architecture, or manage delivery flow for already-decided work.
This skill should be used when the user asks to "track work", "create an issue", "find something to work on", "what should I work on next", "triage bugs", "close an issue", "check what's blocked", "plan a milestone", "review sprint progress", "coordinate agents", or when working in a project that uses filigree for issue tracking. Provides workflow patterns, team coordination protocols, and operational guidance for the filigree issue tracker.
Use when designing a system that spans more than one process, machine, or failure domain and a partition, crash, or duplicate must not silently corrupt state. Use when you see split-brain, lost writes under partition, duplicate processing, stuck or half-applied sagas, retry storms, dual writes drifting apart, or "works in staging, melts under load." Architecture-level — how to design correctness under partial failure, not how to deploy it. Single-service API internals → `axiom-web-backend`; CI/CD and ops → `axiom-devops-engineering`; replay/seed determinism → `axiom-determinism-and-replay`; broker/event-sourcing mechanics → the event-driven pack.
Use when designing a system whose past behaviour must be recoverable as a fact — RL training substrates, multi-agent simulations, deterministic game engines, replay-debuggable services, multiplayer lockstep, or any pipeline where "I cannot reproduce that bug" is unacceptable. Use when teams disagree about what "snapshot", "seed", or "replay" mean across modules. Use when cross-machine or cross-process determinism is required, or a regulator will ask "what was the input at tick T?". Architecture-level — how to design a deterministic system. For verifying an existing simulation against known patterns, use `/check-determinism` from yzmir-simulation-foundations instead.
| name | using-web-backend |
| description | Use when building web APIs, backend services, or encountering FastAPI/Django/Express/GraphQL questions, microservices architecture, authentication, or message queues - routes to 11 specialist skills rather than giving surface-level generic advice |
This router directs you to specialized web backend skills. Each specialist provides deep expertise in their domain.
Core principle: Different backend challenges require different specialist knowledge. Routing to the right skill gives better results than generic advice.
Use this router when encountering:
IMPORTANT: All reference sheets are located in the SAME DIRECTORY as this SKILL.md file.
When this skill is loaded from:
skills/using-web-backend/SKILL.md
Reference sheets like fastapi-development.md are at:
skills/using-web-backend/fastapi-development.md
NOT at:
skills/fastapi-development.md ← WRONG PATH
When you see a link like [fastapi-development.md](fastapi-development.md), read the file from the same directory as this SKILL.md.
| User Question Contains | Route To | Why |
|---|---|---|
| FastAPI, Pydantic, async Python APIs | fastapi-development.md | FastAPI-specific patterns, dependency injection, async |
| Django, ORM, views, middleware | django-development.md | Django conventions, ORM optimization, settings |
| Express, Node.js backend, middleware | express-development.md | Express patterns, error handling, async flow |
| REST API, endpoints, versioning, pagination | rest-api-design.md | REST principles, resource design, hypermedia |
| GraphQL, schema, resolvers, N+1 | graphql-api-design.md | Schema design, query optimization, federation |
| Microservices, service mesh, boundaries | microservices-architecture.md | Service design, communication, consistency |
| Message queues, RabbitMQ, Kafka, events | message-queues.md | Queue patterns, reliability, event-driven |
| JWT, OAuth2, API keys, auth | api-authentication.md | Auth patterns, token management, security |
| Rate limiting, throttling, quotas | api-authentication.md | Security hardening section — token-bucket, per-tenant quotas |
| Database connections, ORM, migrations | database-integration.md | Connection pooling, query optimization, migrations |
| API testing, integration tests, mocking | api-testing.md | Testing strategies, contract testing, mocking |
| OpenAPI, Swagger, API docs | api-documentation.md | API docs (also see: muna-technical-writer) |
Before routing, check if these packs are more appropriate:
ordis-security-architect (threat modeling, OWASP, security patterns)lyra-ux-designer (error messages, API ergonomics)axiom-python-engineering (Python-specific engineering)muna-technical-writer (technical writing, clarity)STOP: Do not attempt to answer web backend questions yourself.
Instead:
[skill-name] skill for this"If you catch yourself doing any of these, STOP and route to a specialist:
All of these mean: You're being a jack-of-all-trades. Route to the specialist.
| Excuse | Reality |
|---|---|
| "I can handle this backend question myself" | Specialists provide deeper expertise than generic knowledge |
| "These are all backend topics" | Backend spans 11 distinct specialist domains |
| "I'll just give a quick answer" | Quick answers miss edge cases and production patterns |
| "The user didn't ask for specialized help" | Better results come from routing to specialists proactively |
| "Specialist skill not available, I'll answer instead" | State which skill would help, explain routing, guide user to install if needed |
User: "I need to build a REST API with FastAPI. How should I structure my dependency injection?"
Your response: "I'll use the fastapi-development.md skill to help you structure dependency injection properly. This specialist skill covers FastAPI patterns in depth."
[Then apply fastapi-development skill]
User: "My GraphQL API has N+1 problems and we're splitting our monolith into microservices."
Your response: "You have two distinct specialist areas:
Let me address the GraphQL N+1 problem first with the graphql-api-design skill..."
[Apply each specialist skill to its domain]
Without routing: Surface-level answers covering multiple domains broadly With routing: Deep expertise addressing edge cases, production patterns, and domain-specific best practices
Specialist skills = better results.
After routing, load the appropriate specialist skill for detailed guidance: