Specx Add Delivery Controller
Add delivery controllers for specx services, especially FastAPI HTTP routes. Use when creating top-level `delivery/` request/response schemas, one controller per scoped use-case set, route registration, FastAPI lifecycle managers, HTTP error translation, delivery-only auth/rate-limit/request services, or integration tests that exercise the delivery edge.
Install
npx skills add maksimzayats/specx --skill specx-add-delivery-controllergit clone --depth 1 https://github.com/maksimzayats/specx.git /tmp/specx
mkdir -p ~/.claude/skills
cp -r /tmp/specx/.agents/skills/specx-add-delivery-controller ~/.claude/skills/specx-add-delivery-controllerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# specx Add Delivery Controller
Use this skill at the framework boundary. Read `references/controller.md`
before adding controller code.
## Workflow
1. Put controllers under `delivery/fastapi/controllers/<scope>.py`.
2. Put request and response schemas under `delivery/fastapi/schemas/`.
3. Use one controller per scoped set of use cases, for example
`TasksController` for create/get/list task routes.
4. Put controller-only helpers such as auth dependencies, rate limiters, and
request-context readers under `delivery/fastapi/services/`.
5. Make controllers inherit `BaseController`, schemas inherit
`BaseFastAPISchema`, delivery helpers inherit `BaseDeliveryService`, and
FastAPI lifespan managers inherit `BaseLifecycle[FastAPI]`.
6. Add docstrings with scope and a concrete `Example:` to controllers, schemas,
and delivery services.
7. Inject use cases or delivery services with `Injected[...]`. A simple
delivery-owned `/healthz` response needs no core workflow; inject
`core/health` use cases when readiness checks a required external dependency
or probe policy is reused across deliveries.
8. Map request schema/path data into the use case's same-file `Command` or
`Query` input.
9. Call the use case.
10. Map the result into a response schema.
11. Declare the success status explicitly when it is not `200`, such as `201`
for a resource-creating `POST` or `204` for a response with no body.Details
- Skill name
specx-add-delivery-controller- Repository
- maksimzayats/specx
- Path
.agents/skills/specx-add-delivery-controller/SKILL.md- License
- MIT
- Repo updated
- 8 August 2026
FAQ
What does the Specx Add Delivery Controller skill do?
Add delivery controllers for specx services, especially FastAPI HTTP routes. Use when creating top-level `delivery/` request/response schemas, one controller per scoped use-case set, route registration, FastAPI lifecycle managers, HTTP error translation, delivery-only auth/rate-limit/request services, or integration tests that exercise the delivery edge.
How do I install the Specx Add Delivery Controller skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add maksimzayats/specx --skill specx-add-delivery-controller. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Specx Add Delivery Controller popular?
It lives in maksimzayats/specx, which has 198 GitHub stars and 33 forks.
Related skills
Specx Add Core Service
198maksimzayats/specx
Add or refactor a specx core scope service. Use when implementing focused reusable business/application behavior under a core scope services package, extracting logic from a use case, injecting deterministic collaborators, accepting an active unit of work, choosing between Service and Capability, or keeping business decisions away from delivery and infrastructure.
Specx Add Core Use Case
198maksimzayats/specx
Add or refactor a specx core scope use case. Use when implementing an externally meaningful application action under a core scope use_cases package, adding same-file command/query inputs, result DTOs, coordinating services, opening a unit-of-work transaction, or moving behavior out of delivery or infrastructure into class-based application code.
Specx Add Infrastructure Adapter
198maksimzayats/specx
Add technical infrastructure adapters for specx core scopes. Use when implementing SQLAlchemy repositories and Alembic-backed persistence, Redis stores, HTTP/network clients, file or queue adapters, unit-of-work implementations, gateway implementations for external APIs or SDKs such as OpenAI, or explicit `diwire` bindings for core scope repository and gateway ports.
Specx Component Architecture
198maksimzayats/specx
Design or review specx core scope boundaries in Python services. Use when deciding where code belongs across packaged scoped foundation bases, optional local foundation extensions, `core/`, capabilities, delivery, infrastructure, `shared/`, and `ioc`; when adding guardrails or splitting use cases, services, DTOs, schemas, ports, and adapters.
Specx Diwire Composition
198maksimzayats/specx
Wire dependency injection for a specx Python service with `diwire`. Use when adding `ioc/container.py`, explicit dependency registrations for capabilities, repositories, gateways, UoW managers, clients, settings, or factories, `Injected[...]` constructor fields, FastAPI app factory/lifecycle composition, test overrides, or rules that keep containers out of core use cases and services.
Solana
101quicknode/solana-finance-claude-plugin
Use when working on Solana software, including one or more of: Solana client code using TypeScript, Rust libraries that use Solana crates, Anchor programs, Quasar programs, LiteSVM tests, including Rust program files, TypeScript tests, and Anchor.toml or Quasar.toml configuration. Designed to create minimal, reusable code without unnecessary duplication.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.