From cms-cultivator
Performance analysis and Core Web Vitals optimization for Drupal and WordPress. Supports depth modes (--quick, --standard, --comprehensive) and scope/format/target flags. Spawns a performance-specialist agent.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cms-cultivator:performance-auditThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Comprehensive performance analysis and Core Web Vitals optimization using the performance-specialist agent.
Comprehensive performance analysis and Core Web Vitals optimization using the performance-specialist agent.
/audit-perf — Full performance audit (standard depth)/audit-perf --quick --scope=current-pr — Pre-commit Core Web Vitals check/audit-perf --comprehensive --format=summary — Pre-release deep audit with executive summary/audit-perf --standard --format=json — CI/CD integration output/audit-perf queries — Legacy focus area (still supported)--quick — Core Web Vitals only (~5 min)--standard — CWV + major bottlenecks (default, ~15 min)--comprehensive — Full profiling + recommendations (~30 min)--scope=current-pr — Only files changed in current PR--scope=frontend — Only frontend files (CSS, JS, images)--scope=backend — Only backend files (PHP, SQL, caching)--scope=module=<name> — Specific module/directory--scope=file=<path> — Single file--scope=entire — Full codebase (default)--format=report — Detailed report with metrics (default)--format=json — Structured JSON for CI/CD--format=summary — Executive summary--format=metrics — Core Web Vitals metrics only--target=good — Report only if failing "good" thresholds (LCP > 2.5s, INP > 200ms, CLS > 0.1)--target=needs-improvement — Report if needing improvement (LCP > 4.0s, INP > 500ms, CLS > 0.25)queries, n+1, assets, bundles, caching, vitals, lcp, inp, cls
When Task() or bash tools are unavailable, perform performance analysis directly:
audit-perf-YYYY-MM-DD-HHMM.md and present path to userSupported checks in Tier 1: code-level query patterns, caching strategy, asset markup, CMS-specific anti-patterns.
When running in Claude Code with Task() available:
--scope=current-pr:
git diff --name-only origin/main...HEAD | grep -E '\.(php|tsx?|jsx?|css|scss|sql)$'
Task(cms-cultivator:performance-specialist:performance-specialist,
prompt="Analyze performance and optimize Core Web Vitals with:
- Depth mode: {depth}
- Scope: {scope}
- Format: {format}
- Target threshold: {target or 'none'}
- Focus area: {focus or 'complete analysis'}
- Files to analyze: {file_list}
Check database queries, caching strategies, asset optimization, and rendering for Drupal and WordPress. Save report to audit-perf-YYYY-MM-DD-HHMM.md and present the file path.")
| Metric | Good | Needs Improvement | Poor |
|---|---|---|---|
| LCP | < 2.5s | 2.5s–4.0s | > 4.0s |
| INP | < 200ms | 200ms–500ms | > 500ms |
| CLS | < 0.1 | 0.1–0.25 | > 0.25 |
Drupal: Cache tags/contexts/max-age, EntityQuery optimization, Views caching, BigPipe, CSS/JS aggregation
WordPress: Transient caching, WP_Query optimization (no_found_rows, update_post_term_cache), object cache (Redis/Memcached), conditional asset loading
| Metric | Target |
|---|---|
| Total JS | < 200KB |
| Total CSS | < 100KB |
| Images | < 1MB total |
| HTTP Requests | < 50 |
npx claudepluginhub kanopi/claude-toolbox --plugin cms-cultivatorAutomatically analyzes performance issues and suggests optimizations for web pages, database queries, and API calls. Focuses on Core Web Vitals, N+1 problems, and caching.
Diagnoses web performance issues, fixes Core Web Vitals (LCP, INP, CLS), optimizes bundles, assets, and render performance. Use for slow pages or dropping traffic due to speed.
Systematically measures, analyzes, and improves page loading speed, Core Web Vitals, bundle size, and runtime performance using Lighthouse audits and web performance best practices.