Quick Start¶
Get started with CMS Cultivator in minutes! This guide covers the most common workflows.
CMS Cultivator provides two ways to work:
1. Talk naturally - Agent Skills automatically help when you need it
2. Use commands - Explicit /command for full control
Natural Conversation (Agent Skills)¶
Just describe what you need in plain English:
"I need to commit my changes"
→ Automatically generates commit message
"Is this button accessible?"
→ Checks accessibility instantly
"This database query is slow"
→ Analyzes for N+1 issues and suggests fixes
"Does this follow Drupal coding standards?"
→ Runs PHPCS and reports violations
"I need tests for this UserManager class"
→ Generates PHPUnit test scaffolding
No need to remember command names! Claude automatically helps based on context.
See Agent Skills Guide for all 9 available skills.
Explicit Commands (Full Control)¶
When you want comprehensive analysis or specific workflows:
Your First Commands¶
1. Create a Pull Request¶
When you're ready to create a pull request:
What it does:
- Analyzes your git changes
- Generates comprehensive PR description
- Detects Drupal/WordPress-specific changes
- Lists configuration changes, database updates, and more
- Creates the PR on GitHub via gh CLI
2. Review Your Own Changes¶
Before creating a PR, check your work:
What it analyzes: - PR size and complexity - Breaking changes - Code quality issues - Security concerns - Generates test plan
3. Run an Accessibility Audit¶
Check your code for WCAG compliance:
What it checks: - Color contrast ratios - ARIA attributes - Semantic HTML - Keyboard navigation - Form labels and validation - Alt text for images
4. Analyze Performance¶
Find performance bottlenecks:
What it analyzes: - Database queries and N+1 problems - Asset sizes and optimization - JavaScript bundle analysis - Caching effectiveness
5. Check Security¶
Scan for vulnerabilities:
What it scans: - Dependency vulnerabilities - Exposed secrets - OWASP Top 10 issues - Permission problems
6. Verify Code Quality¶
Check coding standards:
What it checks: - PHPCS violations - ESLint issues - Drupal/WordPress standards
Common Workflows¶
Workflow 1: Before Creating a PR¶
# 1. Self-review your changes
/pr-review self
# 2. Run quality checks
/quality-standards
# 3. Check for security issues
/audit-security secrets
# 4. Create the PR (auto-generates description)
/pr-create PROJ-123
Workflow 2: Making Commits¶
# 1. Stage your changes
git add .
# 2. Generate commit message
/pr-commit-msg
# 3. Commit with selected message
git commit -m "[selected message]"
Workflow 3: Code Review¶
# 1. Review the PR
/pr-review 456
# 2. Focus on specific areas if needed
/pr-review 456 security # Security review
/pr-review 456 breaking # Breaking changes check
/pr-review 456 performance # Performance review
# 3. Check specific concerns
/audit-a11y contrast
/audit-perf queries
/audit-security deps
Workflow 4: Before Deployment¶
# 1. Run comprehensive audits
/audit-perf
/audit-a11y
/audit-security
# 2. Generate release artifacts
/pr-release changelog
/pr-release deploy
# 3. Create compliance reports
/audit-perf report
/audit-a11y report
/audit-security report
Workflow 5: Working on Kanopi Projects¶
# 1. Run Kanopi quality checks
# (commands automatically use ddev composer scripts)
/quality-analyze # Uses ddev composer code-check
/quality-standards # Uses ddev composer code-sniff
/test-coverage # Uses ddev cypress-run
# 2. Check performance
/audit-perf # Suggests ddev theme-build
# and ddev critical-run
# 3. Security audit
/audit-security # Uses ddev composer audit
Command Categories Quick Reference¶
🔄 PR Workflow¶
/pr-create [ticket] # Create PR with generated description
/pr-review [pr-number|self] [focus] # Review PR or analyze your own changes
/pr-commit-msg # Generate commit message
/pr-release [focus] # Generate changelog and deployment docs
♿ Accessibility¶
/audit-a11y # Comprehensive WCAG audit
/audit-a11y report # Generate compliance report
/audit-a11y checklist # WCAG 2.1 AA checklist
/audit-a11y [focus] # Check specific aspects (contrast, aria, headings, forms, alt-text, keyboard)
/audit-a11y fix # Generate code fixes
⚡ Performance¶
/audit-perf # Full-stack performance analysis
/audit-perf lighthouse # Lighthouse audit
/audit-perf report # Executive performance report
/audit-perf [focus] # Focused analysis (queries, n+1, assets, bundles, caching)
/audit-perf [metric] # Core Web Vitals optimization (lcp, inp, fid, cls)
🔒 Security¶
/audit-security # Comprehensive security audit
/audit-security [focus] # Focused scans (deps, secrets, permissions)
/audit-security report # Security compliance report
📝 Documentation¶
/docs-generate # Analyze documentation status
/docs-generate api # Generate API documentation
/docs-generate readme # Update README
/docs-generate changelog # Generate changelog
/docs-generate guide user # Generate user guide
🧪 Testing¶
/test-generate [type] # Generate test scaffolding
/test-coverage # Analyze test coverage
/test-plan # Generate QA test plan
📊 Code Quality¶
Focus Parameters¶
Many commands accept optional focus parameters to analyze specific areas:
PR Review Focus¶
/pr-review self # Full self-assessment
/pr-review self size # Size and complexity
/pr-review self breaking # Breaking changes
/pr-review self testing # Test plan generation
/pr-review 456 # Full review
/pr-review 456 code # Code quality focus
/pr-review 456 security # Security focus
/pr-review 456 performance # Performance focus
Performance Focus¶
/audit-perf queries # Database queries only
/audit-perf n+1 # N+1 detection only
/audit-perf assets # Asset optimization only
/audit-perf bundles # JavaScript bundles only
/audit-perf caching # Caching effectiveness only
Accessibility Focus¶
/audit-a11y contrast # Color contrast only
/audit-a11y aria # ARIA attributes only
/audit-a11y headings # Heading structure only
/audit-a11y forms # Form accessibility only
/audit-a11y keyboard # Keyboard navigation only
Security Focus¶
/audit-security deps # Dependency vulnerabilities only
/audit-security secrets # Exposed secrets only
/audit-security permissions # Permission issues only
Quality Focus¶
/quality-analyze refactor # Refactoring opportunities
/quality-analyze complexity # Code complexity analysis
/quality-analyze debt # Technical debt assessment
Tips & Best Practices¶
1. Run Checks Early and Often¶
# Don't wait until the end of the sprint
/audit-a11y # Check accessibility during development
/audit-perf queries # Catch N+1 queries early
/audit-security secrets # Before committing code
2. Self-Review Before Creating PRs¶
# Catch issues before code review
/pr-review self # Full self-assessment
# Fix any issues found
/pr-create PROJ-123 # Create PR when ready
3. Use Focus Parameters for Speed¶
# When you know what you're looking for
/pr-review 456 security # Just security review
/audit-perf queries # Just check database queries
/audit-a11y contrast # Just check color contrast
4. Combine with Git Workflows¶
# Pre-commit
/pr-commit-msg
# Pre-PR
/pr-review self
/quality-standards
/audit-security secrets
# Post-merge
/docs-generate changelog
5. Generate Reports for Stakeholders¶
# Before client demos
/audit-perf report # Performance metrics
/audit-a11y report # Accessibility compliance
/audit-security report # Security posture
Next Steps¶
- Explore All Commands - Detailed command reference
- Kanopi Tools Integration - Use with DDEV add-ons
- Contributing - Help improve CMS Cultivator