// Apply WCAG accessibility standards when building UI components, forms, interactive elements, or any user-facing interface. Covers semantic HTML, ARIA attributes, keyboard navigation, color contrast, and screen reader support.
Execute a structured code review protocol that inspects code quality against the full rule set. Use when auditing code written by yourself or another agent, during code audit workflows, or when the user asks for a code review. Produces a findings document with severity tags.
Structured research protocol for investigating technologies, patterns, and APIs before implementation. Use when exploring unfamiliar technologies, evaluating library options, or documenting technical findings. Covers multi-tool search strategy, research log conventions, and training data fallback honesty protocol.
Document significant architectural decisions using the ADR (Architecture Decision Record) format. Use during research phases when choosing between approaches, when introducing new dependencies or patterns, or when the user asks to document a technical decision.
Apply REST/HTTP API design conventions when implementing endpoints, handlers, middleware, request validation, or response formatting. Covers resource naming, status codes, error formats, versioning, and pagination.
Apply Kubernetes deployment and GitOps patterns when configuring container orchestration, deployment strategies (rolling, blue-green, canary), ArgoCD/Flux manifests, or Kubernetes secrets management. Supplement to ci-cd-principles.
Apply CI/CD pipeline design patterns when configuring build pipelines, deployment processes, release strategies, Dockerfiles, or GitHub Actions workflows. Covers pipeline stages, artifact management, environment promotion, and rollback strategies.
| name | accessibility-principles |
| description | Apply WCAG accessibility standards when building UI components, forms, interactive elements, or any user-facing interface. Covers semantic HTML, ARIA attributes, keyboard navigation, color contrast, and screen reader support. |
| user-invocable | false |
Follow WCAG 2.1 Level AA as the baseline for all user-facing interfaces.
<nav>, <main>, <article>, <section>, <button>, <form>) over generic <div> and <span><h1>, with proper heading hierarchy (h1 → h2 → h3, no skipping)<label> elements associated with form inputs (via for/id or wrapping)<table> for tabular data, never for layoutoutline: none without replacement)aria-label or aria-labelledby for elements without visible text labelsaria-live regions for dynamic content updates (toasts, notifications)role attributes only for custom widgets that lack native semanticsaria-expanded, aria-controls for disclosure patterns (dropdowns, accordions)<img> elements have descriptive alt text (or alt="" for decorative images)aria-describedby)required attribute)<div> buttons)?