Specx Project Tooling
Add strict Python project tooling for a specx service. Use when creating or updating `pyproject.toml`, `uv` dependency groups and lock checks, Ruff formatting and linting, mypy strict mode, pytest and HTTPX2 test configuration, Makefile commands, root `AGENTS.md` command guidance, or CI-like local guardrails.
Install
npx skills add maksimzayats/specx --skill specx-project-toolinggit clone --depth 1 https://github.com/maksimzayats/specx.git /tmp/specx
mkdir -p ~/.claude/skills
cp -r /tmp/specx/.agents/skills/specx-project-tooling ~/.claude/skills/specx-project-toolingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# specx Project Tooling Use this skill to make the repository executable and checkable. Read `references/tooling.md` before editing tooling files. ## Workflow 1. Use `specx init <path>` for the fresh framework-neutral baseline. It renders the canonical `pyproject.toml`, Makefile, `.python-version`, health core/IOC scaffold, mirrored unit tests, and root guidance, then runs `uv add specx diwire` and `uv add --dev mypy pytest ruff` unless `--no-sync` is passed. Let uv select and record compatible releases rather than rendering dependency floors. 2. Preserve the repo's Python version if it already exists. For a new repo, default to Python 3.14. The initializer accepts any `major.minor` value; do not hardcode a release allowlist that blocks future Python versions. 3. Use `uv` metadata in `pyproject.toml`. 4. For a new project, verify current compatible releases against the official package indexes and documentation before copying reference floors. Preserve intentional versions in an existing repo unless the user asks to upgrade. 5. Add runtime dependencies only for real runtime features. For a starter API, include `specx`, FastAPI, `diwire`, `pydantic-settings`, and Uvicorn. 6. Add dev dependencies for pytest, Ruff, mypy, HTTP testing, and ASGI lifespan testing when there is a FastAPI app. 7. Keep mypy strict. Do not enable the DIWire mypy plugin for constructor-field injection; it is only needed if an existing project intentionally uses
Details
- Skill name
specx-project-tooling- Repository
- maksimzayats/specx
- Path
.agents/skills/specx-project-tooling/SKILL.md- License
- MIT
- Repo updated
- 8 August 2026
FAQ
What does the Specx Project Tooling skill do?
Add strict Python project tooling for a specx service. Use when creating or updating `pyproject.toml`, `uv` dependency groups and lock checks, Ruff formatting and linting, mypy strict mode, pytest and HTTPX2 test configuration, Makefile commands, root `AGENTS.md` command guidance, or CI-like local guardrails.
How do I install the Specx Project Tooling skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add maksimzayats/specx --skill specx-project-tooling. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Specx Project Tooling 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 Sqlalchemy Migrations
198maksimzayats/specx
Add or repair Alembic migrations for specx SQLAlchemy services. Use when adding SQLAlchemy models or repositories, replacing metadata.create_all schema bootstraps, creating async Alembic env.py, adding migration Makefile targets, generating initial revisions, or testing migration drift.
TDD Methodoly Expert
194thedaviddias/skill-check
Use when implementing features or fixing bugs with strict Test-Driven Development (TDD). Activate for coding tasks that require new functionality, refactoring, or comprehensive test coverage, especially when the user mentions TDD or Test Driven Development.
Specx Tests
198maksimzayats/specx
Add or refine tests for specx Python services. Use when creating unit tests for use cases/services, integration tests for FastAPI controllers or infrastructure adapters, e2e smoke tests, architecture import guardrails, DI override tests, pytest fixtures, or coverage and boundary checks.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.