Specx Component Architecture
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.
Install
npx skills add maksimzayats/specx --skill specx-component-architecturegit clone --depth 1 https://github.com/maksimzayats/specx.git /tmp/specx
mkdir -p ~/.claude/skills
cp -r /tmp/specx/.agents/skills/specx-component-architecture ~/.claude/skills/specx-component-architecturePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# specx Scope Architecture Use this skill before broad structural changes or when a feature crosses more than one layer. Read `references/boundaries.md` for the full rules. ## Boundary Model - `core/<scope>/`: application behavior and contracts. Inner packages are `capabilities/`, `dtos/`, `entities`, `exceptions/`, `gateways/`, `repositories/`, `services/`, and `use_cases/`. - `core/<scope>/infrastructure/`: scope-owned external IO adapters such as SQLAlchemy repositories, Redis stores, HTTP clients, file storage, and queues. Inner core packages must not import it. - Scoped specx foundation packages: packaged base classes under `specx.core.foundation`, `specx.delivery.foundation`, and `specx.infrastructure.foundation`. Every non-foundation source class must inherit an explicit packaged base directly or through a project-local base; local bases explicitly inherit the packaged or framework base they extend. - `foundation/`: optional project-local extension point for base definitions only: real project-local base categories or stateful framework bases that must not be shared globally, such as a SQLAlchemy declarative base. - `delivery/`: runnable framework apps, controllers, schemas, auth dependencies, request parsing, response serialization, HTTP error translation, app lifecycle managers, and delivery-only services. - `infrastructure/`: app-wide technical resources such as SQLAlchemy session
Details
- Skill name
specx-component-architecture- Repository
- maksimzayats/specx
- Path
.agents/skills/specx-component-architecture/SKILL.md- License
- MIT
- Repo updated
- 8 August 2026
FAQ
What does the Specx Component Architecture skill do?
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.
How do I install the Specx Component Architecture skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add maksimzayats/specx --skill specx-component-architecture. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Specx Component Architecture 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 Delivery Controller
198maksimzayats/specx
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.
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.
Specx Foundation
198maksimzayats/specx
Use specx foundation bases in Python services, or add a tiny project-local `foundation/` base for missing categories or stateful framework bases.
Specx Project Structure
198maksimzayats/specx
Create or reshape a Python FastAPI service repo into the specx clean core/delivery architecture using packaged scoped foundation bases. Use when starting an API backend, adding the first src package, or establishing `AGENTS.md`, `core/`, optional local `foundation/`, `delivery/`, infrastructure, `ioc/`, migrations, and tests.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.