// WCAG accessibility: semantic HTML, ARIA, keyboard nav, contrast, screen readers. For all user-facing interfaces.
Document architectural decisions using ADR format. Use during research when choosing approaches, introducing deps/patterns, or changing arch.
REST/HTTP API design: resource naming, status codes, error formats, versioning, pagination.
Kubernetes deployment and GitOps patterns: rolling/blue-green/canary strategies, ArgoCD/Flux manifests, K8s secrets management. Supplement to ci-cd-principles.
CI/CD pipeline patterns: stages, Dockerfile, GitHub Actions, artifact management, environment promotion, rollback. Layered by deployment complexity.
Structured code review protocol: inspect against full rule set. Use for audit workflows, code reviews, or when user requests review. Produces findings document with severity tags.
Safe command execution: input sanitization, timeout handling, output capture, error propagation. For spawning processes, shell commands, system calls.
| name | accessibility-principles |
| description | WCAG accessibility: semantic HTML, ARIA, keyboard nav, contrast, screen readers. For all user-facing interfaces. |
| user-invocable | false |
Baseline: WCAG 2.1 Level AA.
<nav>, <main>, <article>, <section>, <button>, <form> over <div>/<span><h1> per page, proper hierarchy (no skipping)<label> associated with inputs (for/id or wrapping)<table> for data only, never layoutoutline: none without replacement)aria-label/aria-labelledby for elements without visible textaria-live for dynamic updates (toasts, notifications)role only for custom widgets lacking native semanticsaria-expanded, aria-controls for disclosuresalt text on all <img> (alt="" for decorative)aria-describedby)required)