cms-cultivator

Use this agent when you need to check WCAG 2.1 Level AA compliance for Drupal or WordPress components. This agent should be used proactively after creating UI components, forms, or interactive elements, especially before committing changes or creating pull requests. It will validate semantic HTML, ARIA attributes, keyboard navigation, color contrast (4.5:1 minimum), and screen reader compatibility. Invoke when user mentions "accessibility", "a11y", "WCAG", "screen reader", "keyboard navigation", "color contrast", or asks "is this accessible?", "does this meet accessibility standards?", or requests a comprehensive accessibility audit.

Use this agent when you need to validate design implementations in real browsers for Drupal or WordPress projects. This agent should be used proactively after code generation, when users say "test this" or "validate", or before marking work complete. It will test responsive behavior at multiple breakpoints (320px, 768px, 1024px+), check WCAG AA accessibility compliance (contrast ratios, keyboard navigation, ARIA attributes), capture annotated screenshots at each breakpoint, validate interactions (hover, click, focus states), check console for errors, and generate detailed technical validation reports with file paths and specific remediation steps.

Use this agent when you need to analyze code quality, coding standards compliance, or technical debt for Drupal or WordPress projects. This agent should be used proactively after writing significant code changes, especially before committing changes or creating pull requests. It will check PHPCS/ESLint compliance, cyclomatic complexity, design patterns, SOLID principles, and identify code smells. Invoke when user mentions "code quality", "technical debt", "refactor", "PHPCS", "coding standards", "complexity", or asks "is this good code?", "does this meet standards?", or requests a code quality analysis.

Use this agent when you need to convert design references into production-ready CMS code for WordPress or Drupal projects. This agent should be used proactively when users provide Figma URLs, screenshots, or design mockups and want them implemented as WordPress block patterns or Drupal paragraph types. It generates CMS-specific code from design specifications and returns file paths. The invoking skill handles CSS generation and browser validation as separate steps. Invoke when user provides a Figma URL, shares design mockups or screenshots, mentions "design-to-code", "block pattern", "paragraph type", or asks to implement a design in WordPress or Drupal.

Use this agent when you need to generate or update comprehensive documentation for Drupal or WordPress projects. This agent should be used proactively after completing new features, before major releases, or when onboarding new team members. It will generate API docs (PHPDoc, JSDoc), user guides, developer documentation, README files, and changelogs following CMS-specific standards. Invoke when user mentions "documentation", "docs", "API docs", "README", "PHPDoc", "JSDoc", "changelog", or asks to document code, generate a developer guide, or write user-facing documentation.

Comprehensive WCAG 2.1 Level AA accessibility audit for Drupal and WordPress projects. Spawns accessibility-specialist for full site analysis. Invoke when user runs /audit-a11y, requests a full accessibility audit, needs a WCAG compliance report, or asks for comprehensive accessibility analysis across pages or modules. Supports --quick, --standard, --comprehensive depth modes and scope/format flags.

Automatically check specific elements or code for accessibility issues when user asks if something is accessible or mentions WCAG compliance. Performs focused accessibility checks on individual components, forms, or pages. Invoke when user asks "is this accessible?", "WCAG compliant?", or shows code/elements asking about accessibility.

Export audit findings from markdown report files to Teamwork-compatible CSV format for project management tools (Jira, Monday, Linear also supported). Auto-activates when user asks to "export audit to CSV", "create tasks from audit", or provides an audit report file and asks to export it. Invoke when user provides audit report filename and wants CSV output for project management import.

Generate client-facing executive summaries from existing audit report files. Transforms technical CMS Cultivator audit findings into non-technical stakeholder reports. Invoke when user asks to "generate a client report from this audit", "create an executive summary", "make a non-technical version of this audit", or "summarize audit findings for stakeholders". Requires an existing audit report file as input.

Automatically validate implementations in real browsers after code is written or when user says "test this". Uses Chrome DevTools MCP to test responsive breakpoints (320px, 768px, 1024px), check accessibility compliance (WCAG AA contrast, keyboard navigation, ARIA), validate interactions, and generate detailed technical reports with file paths and specific fixes.