Scaffold archipy adapter
Skill SyntaxArc/archipy-plugin/skills/scaffold-archipy-adapter
Scaffold a domain adapter under repositories/{domain}/adapters/ for an ArchiPy app. Use when adding infrastructure integrations or thin wrappers around ArchiPy adapters.From its SKILL.md
npx -y skills add SyntaxArc/archipy-plugin --skill scaffold-archipy-adapterAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, as published. Nobody here has run it
Scaffold ArchiPy Adapter
Before writing files
Ask the user for:
- Domain name (e.g.
user,order) - Adapter purpose / file stem (e.g.
db,cache→user_db_adapter.py) - Sync or async (or both as separate classes)
- Whether an in-memory mock is needed for BDD
- Whether this wraps an existing ArchiPy adapter or a new external client
Prefer ArchiPy
If ArchiPy already ships the client (Redis, Postgres, Kafka, …), prefer:
uv add "archipy[<extra>]"
and a thin domain wrapper — not a full reimplementation.
Generate
repositories/<domain>/
├── adapters/
│ └── <domain>_<purpose>_adapter.py # e.g. user_db_adapter.py
└── <domain>_repository.py # create stub if missing
- Thin wrapper: wrap ArchiPy adapter (or external client); own entity construction / query building; map client errors →
domain errors with
raise ... from e. - Optional mock: same module suffix or sibling file only if BDD needs an in-memory double.
- Ports: depend on ArchiPy ports when wrapping library adapters; add a local ABC only when the domain needs a custom contract.
Constraints
- Sync and async must be separate classes.
- No business logic in adapters — map data and talk to infrastructure only.
- Do not create a top-level
adapters/<name>/package — domain adapters live under repositories. - Wire via DI in
configs/containers.py.