Specx Add Infrastructure Adapter
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.
Install
npx skills add maksimzayats/specx --skill specx-add-infrastructure-adaptergit clone --depth 1 https://github.com/maksimzayats/specx.git /tmp/specx
mkdir -p ~/.claude/skills
cp -r /tmp/specx/.agents/skills/specx-add-infrastructure-adapter ~/.claude/skills/specx-add-infrastructure-adapterPersonal 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 Infrastructure Adapter Use this skill whenever code talks to external systems. Read `references/adapter.md` before writing adapters. ## Workflow 1. Define or reuse a repository under `repositories/` for owned persistence. Repository ports inherit `BaseRepository` and mark required methods with `@abstractmethod`. 2. Define or reuse a gateway under `gateways/` for outbound business capabilities to external systems such as OpenAI, payments, email, queues, or external HTTP APIs. Gateway ports inherit `BaseGateway`, mark required methods with `@abstractmethod`, declare external effects, and do not return entities. 3. Put concrete implementations under `core/<scope>/infrastructure/<technology>/`. 4. Inject external clients, session factories, Redis clients, SDK clients, or project-owned client factories. Do not hide client construction inside business methods. Generated HTTP adapters use `httpx2`, imported from the `httpx2` namespace; do not generate new legacy `httpx` imports. 5. A bounded short-lived client factory may stay beside its scope adapter. Put every app-owned pooled client factory or wrapper under top-level `infrastructure/<technology>/`, even with only one current consumer. 6. Give long-lived app-owned infrastructure resources an explicit async `close()` method; FastAPI lifecycle owns calling it on shutdown. 7. Keep technical query/request code in infrastructure.
Details
- Skill name
specx-add-infrastructure-adapter- Repository
- maksimzayats/specx
- Path
.agents/skills/specx-add-infrastructure-adapter/SKILL.md- License
- MIT
- Repo updated
- 8 August 2026
FAQ
What does the Specx Add Infrastructure Adapter skill do?
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.
How do I install the Specx Add Infrastructure Adapter skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add maksimzayats/specx --skill specx-add-infrastructure-adapter. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Specx Add Infrastructure Adapter 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.
Bus Drivers I2c Spi
293mohitmishra786/low-level-dev-skills
I2C and SPI bus driver skill for Linux client drivers. Use when writing i2c_driver or spi_driver, register access over bus, DMA SPI transfers, or ACPI/DT client binding. Activates on queries about i2c_client, spi_driver, regmap I2C, SPI transfer, or Linux I2C SPI subsystem.
Rolecard Workshop Ops
224LiarMTTT/TavernWeave
Diagnose, review, operate, or deploy a generic rolecard workshop made of a static catalog, package gateway, object storage, OAuth ownership, review workflow, and reverse proxy. Use for health checks, API-contract alignment, publish/update/withdraw flows, privacy review, CORS and callback diagnosis, container or proxy planning, and explicitly authorized deployment. Start read-only; never deploy, rotate credentials, revoke access, or mutate production unless the user clearly authorizes that action and target.
Containers Internals
293mohitmishra786/low-level-dev-skills
Linux containers internals skill for namespaces, cgroups, and OCI. Use when understanding clone/unshare namespaces, cgroups v2 limits, overlayfs, runc, seccomp profiles, capabilities, or escape mitigations. Activates on queries about namespaces, cgroups, overlayfs, runc, seccomp-bpf, OCI spec, or container escape.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.