| name | cnap-guru |
| description | CNAP canon for Enexis infrastructure. Use when work involves CNAP, PAX, Enexis cloud landing zones or golden paths, `*.cnap.enexis.nl`, or when `terraform-engineer` or `pax-specialist` is active in an Enexis repo. |
CNAP Guru
Treat the synced CNAP documentation as the canon for CNAP-specific decisions.
1. Ensure the canon is present
Resolve <skill-dir> to the directory containing this SKILL.md, then run:
bash <skill-dir>/scripts/sync-docs.sh
The script clones a missing cache and refreshes a stale one. If it fails, follow references/sync-troubleshooting.md.
Complete when: the command exits successfully and <skill-dir>/references/cnap-docs/src/docs/ exists.
2. Read the evidence
Search the docs root with rg using the user's terms, then read the relevant pages rather than relying on search snippets. Scope the first search when the subject is clear:
- PAX workloads and Kubernetes:
pax-container-platform/
- AWS or Azure accounts and IAM boundaries:
cloud-landing-zones/
- Task procedures and golden paths:
how-to-guides/
- Exact limits, ports, policy names, and configuration:
reference/
- Telemetry:
observability/; Checkov and security policy: security/
Search the whole docs root when the subject crosses sections.
Complete when: every CNAP-specific fact or decision needed for the task has support in a page you read, or you have identified the gap in the canon.
3. Apply the canon
Let the canon override generic Terraform, Kubernetes, networking, CI/CD, and cloud conventions. Mark guidance outside the canon as general guidance or an unresolved gap. Cite each CNAP-specific claim or design choice with its path relative to references/cnap-docs/src/docs/.
Treat the cache as read-only. Route documentation changes to the upstream cnap_user_documentation repository.
Complete when: every CNAP-specific claim or choice in the work is backed by a cited canon path or explicitly identified as absent from the canon.
