cms-cultivator

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

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

Create WordPress block pattern from Figma design or screenshot using design specialist

Create Drupal paragraph type from design using design specialist (Drupal MCP optional)

Validate design implementation in browser using browser validator specialist with Chrome DevTools MCP

Automate Kanopi's Drupal/Pantheon DevOps setup for a new project

Generate documentation (API, README, guides, changelog) using documentation specialist

List and cleanup cloned drupal.org repositories in the local cache

Full drupal.org contribution workflow - create issue and merge request together

Create, update, or list issues on drupal.org using guided manual workflow

Create or list merge requests for drupal.org projects via git.drupalcode.org

Export audit report to CSV for project management tools (Teamwork, Jira, Monday, etc.)

Generate conventional commit messages from staged changes using workflow specialist

Generate PR description and create pull request using workflow specialist

Generate changelog, deployment checklist, and update PR for release using workflow specialist

Review a pull request or analyze your own changes using workflow specialist

Comprehensive code quality analysis and technical debt assessment using code-quality specialist

Check code against coding standards (PHPCS, ESLint, WordPress/Drupal) using code-quality specialist

Create, update, and manage Teamwork tasks with expert project management guidance

Analyze test coverage and identify untested code paths using testing specialist

Generate test scaffolding (unit, integration, e2e) using testing specialist

Generate comprehensive QA test plan based on code changes using testing specialist

Install official WordPress agent-skills from WordPress/agent-skills repository

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.

Create, update, or manage issues on drupal.org for contributed modules using a guided manual workflow. Invoke when user mentions "drupal.org issue", "create issue", "bug report", "feature request", "update issue status", or needs to interact with the drupal.org issue tracker.

Create merge requests for drupal.org projects via git.drupalcode.org. Handles git operations (clone, branch, push) using native git commands. Issue fork creation requires a manual step. Invoke when user mentions "merge request", "MR", "patch", "contribute code", "drupal contribution", or needs to push changes to a drupal.org project.

Use this agent when you need a comprehensive multi-dimensional site audit for Drupal or WordPress projects. This agent should be used proactively before launches, after major updates, or when users need holistic site health assessment. It orchestrates complete audits by spawning four specialist agents in parallel (performance-specialist, accessibility-specialist, security-specialist, code-quality-specialist), waiting for all results, synthesizing findings into unified reports with severity categorization, calculating overall health scores, identifying issue overlaps, and creating prioritized remediation roadmaps with critical → high → medium → low issues.

Use this agent when you need to analyze or optimize performance for Drupal or WordPress projects. This agent should be used proactively after adding database queries, implementing caching, modifying assets, or when Core Web Vitals need improvement. It will analyze LCP, INP, CLS metrics, database query performance, caching strategies, and asset optimization opportunities.

Use this agent when you need mobile-first responsive CSS/SCSS for Drupal or WordPress components. This agent should be used proactively when creating new UI components, implementing design mockups, or after the design-specialist analyzes design requirements. It will generate production-ready styles with proper breakpoints (768px, 1024px), WCAG AA color contrast compliance (4.5:1 normal text, 3:1 large text), touch-friendly interfaces (44px minimum targets), proper focus indicators, reduced motion support, and responsive typography with exact technical specifications.

Use this agent when you need to check security vulnerabilities for Drupal or WordPress code. This agent should be used proactively after handling user input, database operations, authentication logic, or file operations, especially before committing changes or creating pull requests. It will scan for OWASP Top 10 vulnerabilities including SQL injection, XSS, CSRF, and authentication issues.

Use this agent when you need to create, update, or manage Teamwork tasks, export audit findings to project management, or link code changes to tickets. Expert in Drupal, WordPress, and NextJS project architecture. Should be used when users mention "Teamwork", "create task", "export to Teamwork", provide ticket numbers (PROJ-123 format), or when other agents need to create issues from findings. It will create tasks using appropriate templates, update existing tasks, export audit results as formatted tasks, and link git commits/PRs to Teamwork tickets.

Platform-specific context to include in all Teamwork tasks.

Detailed patterns for handling edge cases and error scenarios.

All four standard task templates with their use cases and required sections.

Real-world examples demonstrating common operations.

Use this agent when you need to generate tests, create test plans, or analyze test coverage for Drupal or WordPress projects. This agent should be used proactively after writing new code, before committing changes, or when preparing comprehensive test strategies. It will generate PHPUnit, Jest, and Cypress test scaffolding, create QA test plans, and identify untested code paths. Coordinates with security-specialist and accessibility-specialist for specialized test scenarios.

Use this agent when you need to orchestrate pull request workflows for Drupal or WordPress projects. This agent should be used proactively when users have staged changes and need commit messages, want to create pull requests, need code review, or are preparing releases. It generates conventional commit messages from staged changes, creates comprehensive PR descriptions, analyzes PR changes for review, coordinates release management with changelogs, and delegates to testing-specialist, security-specialist, and accessibility-specialist for comprehensive quality checks before PR creation.

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?".

Automatically extract technical requirements from design references when user mentions Figma, uploads images, or says "implement this design". Analyzes colors, typography, spacing, layout, and maps to WordPress blocks or Drupal paragraph fields. Provides detailed specifications for developers including exact values, responsive behavior, and accessibility requirements.

Automatically generate documentation when user mentions needing API docs, README files, user guides, developer guides, or changelogs. Analyzes code and generates appropriate documentation based on context. Invoke when user mentions "document", "docs", "README", "API documentation", "guide", "changelog", or "how to document".

Quick help with drupal.org contribution workflows including git commands, branch naming, issue fork setup, and merge request creation. Invoke when user asks "how do I contribute to drupal.org?", "drupal.org git workflow", "issue fork", "drupal merge request", or needs help with git.drupalcode.org commands.

Quick help with drupal.org issue templates, formatting, contributing patches, and best practices. Invoke when user asks "how do I write a bug report?", "drupal.org issue template", "issue formatting", "I have a patch", "contribute back", "submit my fix", "I fixed a bug in a module", or needs help structuring issue descriptions or contributing code to drupal.org projects.

Automatically analyze performance issues when user mentions slow pages, performance problems, or optimization needs. Performs focused performance checks on specific code, queries, or components. Invoke when user says "this is slow", "performance issue", "optimize", or asks about speed.

Automatically generate mobile-first responsive CSS/SCSS when creating component styles or mentioning responsive design. Implements standard breakpoints (768px, 1024px), ensures WCAG AA color contrast, creates touch-friendly interfaces (44px minimum targets), adds proper focus indicators, supports reduced motion, scales typography responsively, and provides detailed technical specifications with exact values.

Automatically scan code for security vulnerabilities when user asks if code is secure or shows potentially unsafe code. Performs focused security checks on specific code, functions, or patterns. Invoke when user asks "is this secure?", "security issue?", mentions XSS, SQL injection, or shows security-sensitive code.

Automatically export audit findings, security issues, performance problems, or accessibility violations to Teamwork tasks when other agents complete their analysis. Converts technical findings into actionable project management tasks with appropriate priorities and templates. Invoke when audit agents finish reports, user says "export to Teamwork", or findings need project tracking.

Automatically look up Teamwork task status, details, or project information when user mentions ticket numbers, asks "what's the status of", or needs quick project context. Performs focused queries without creating or modifying data. Invoke when user asks "status of PROJ-123", "what's in that ticket?", "show me task details", or references Teamwork ticket numbers.

Automatically create properly formatted Teamwork tasks when user provides task details, mentions creating tickets, or shares work that needs tracking. Performs context-aware template selection and ensures all required sections are included. Invoke when user says "create a task", "make a ticket", "track this work", or provides requirements to document.

Automatically generate comprehensive QA test plans when user mentions testing requirements, QA needs, or asks what should be tested. Analyzes code changes and features to create structured test scenarios. Invoke when user mentions "test plan", "QA", "what to test", "testing requirements", or "test scenarios".

Automatically generate test scaffolding when user writes new code without tests or mentions needing tests. Supports unit, integration, e2e, and data tests for PHP and JavaScript. Invoke when user mentions "tests", "testing", "coverage", "write tests", or shows new untested code.