cms-cultivator

Comprehensive accessibility audit with WCAG 2.1 Level AA compliance using accessibility specialist

Comprehensive Google Tag Manager performance audit analyzing container size, tag execution, trigger efficiency, and Core Web Vitals impact

Comprehensive live site audit using live-audit specialist (orchestrator)

Comprehensive performance analysis and Core Web Vitals optimization using performance specialist

Comprehensive security vulnerability scanning and compliance reporting using security specialist

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.

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.

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 orchestrates complete design-to-code workflows by analyzing design inputs, generating responsive CMS components, spawning responsive-styling-specialist for CSS generation, creating test pages, spawning browser-validator-specialist for comprehensive validation, and reporting detailed technical results with file paths and specifications.

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.

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.

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.

Automatically check code against PHPCS, ESLint, WordPress Coding Standards, or Drupal Coding Standards when user asks about code style, standards compliance, or best practices. Invoke when user mentions "coding standards", "code style", "linting", "PHPCS", "ESLint", or asks if code follows conventions.

Automatically generate conventional commit messages when user has staged changes and mentions committing. Analyzes git diff and status to create properly formatted commit messages following conventional commits specification. Invoke when user mentions "commit", "staged", "committing", or asks for help with commit messages.

Automatically analyze test coverage when user asks which code is tested, mentions coverage gaps, or shows code asking about testing. Identifies untested code paths and suggests test additions. Invoke when user asks "what's not tested?", "coverage", "untested code", or "which tests are missing?".