template-infrastructure-module

Solid

Add or extend generic infrastructure/ packages — Layer 1 modules with SKILL.md, AGENTS.md, tests in tests/infra_tests/, 60% coverage. USE WHEN new reusable package under infrastructure/, extending validation/rendering/llm, or skill manifest entry — even without infrastructure_module prompt.

DevOps & Infrastructure 19 stars 1 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 81/100

Stars 20%
43
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
77
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Infrastructure module ## Natural invoke - "Add infrastructure/foo/ package with CLI and tests" - "Extend infrastructure/validation with a new gate" - "New generic utility reusable across projects" ## Inputs to confirm - **Module name** — under `infrastructure/<package>/`. - **Public API** — functions/classes to export in `__init__.py` and `__all__`. ## Workflow 1. **Layout** — `__init__.py`, core logic module(s), optional `cli.py`, `AGENTS.md`, `README.md`, `SKILL.md` with YAML frontmatter. 2. **Implement** — generic (no project-specific paths hard-coded); type hints; `TemplateError` hierarchy. 3. **Tests** — `tests/infra_tests/<package>/`; no mocks; ≥60% on `infrastructure/`. 4. **Exports** — re-exporting `__init__.py` must declare `__all__` (MED5). 5. **Register skill** — `uv run python -m infrastructure.skills write` after adding `SKILL.md`. 6. **Wire docs** — update `infrastructure/AGENTS.md` module map if significant. ## Deliverables - Package tree + test path - Coverage snippet from pytest ## Verification commands ```bash uv run pytest tests/infra_tests/<area>/ -v --cov=infrastructure --cov-fail-under=60 uv run python -m infrastructure.skills check uv run python -m infrastructure.skills check --all-exports ``` ## When NOT to use - **Project-specific domain code** → [code-development](../code-development/SKILL.md) in `projects/*/src/` ## References - [`infrastructure/AGENTS.md`](../../../infrastructure/AGENTS.md) - [`docs/rules/api_design.md`](../../...

Details

Author
docxology
Repository
docxology/template
Created
1 years ago
Last Updated
today
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

template-code-development

Standards-compliant code for the Research Project Template — infrastructure or project src/, thin orchestrators, type hints, no mocks. USE WHEN implementing an algorithm, utility, analysis method, optimizer, new module in projects/*/src or infrastructure/, or user says add code following template architecture — even without docs/prompts. Not for end-to-end feature spanning manuscript + pipeline (use template-feature-addition).

19 Updated today
docxology
DevOps & Infrastructure Listed

infra-tools

Infrastructure and DevOps tooling (Terraform, K8s, Config Mgmt). Use when the project needs this capability or the user / team manifest asks for it. Use for specialized `infra-tools` work when listed in TEAM.yaml or explicitly requested.

2 Updated today
rogue-dev-studio
DevOps & Infrastructure Listed

craft-infra

The Craftsman standard for production infrastructure — deployment, env/config, CI/CD, IaC, health/readiness, scaling, platform/edge rate limiting, build/release, rollback. Use WHENEVER work touches infra: deploy, CI gates, env vars, IaC, load failures, platform rate limiting, pooling runtime constraints, or production runtime. Trigger on "deploy this", "set up CI", "add rate limiting", "configure env vars", or "why did it fall over under load". Owns the platform layer — see "Scope boundaries" in the body for handoffs to craft-backend, craft-security, craft-db, craft-testing, and craft-observability.

1 Updated 4 days ago
gul-labs