template-infrastructure-module
SolidAdd 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.
Install
Quality Score: 81/100
Skill Content
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
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).
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.
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.