Agent skill
perf
Performance optimization skill. Core Web Vitals via Lighthouse, bundle size analysis, metrics tracking over time. Use when: (1) optimizing frontend performance, (2) analyzing bundle size, (3) tracking metrics regression. Triggers: /perf, 'performance audit', 'core web vitals', 'bundle size'.
Install this agent skill to your Project
npx add-skill https://github.com/alfredolopez80/multi-agent-ralph-loop/tree/main/.claude/skills/perf
SKILL.md
Perf — Performance Optimization v3.0
Measure, analyze, and optimize performance.
Actions
/perf audit <url>
Run Lighthouse via /browser-test and extract performance metrics:
- LCP (Largest Contentful Paint) — target < 2.5s
- FID (First Input Delay) — target < 100ms
- CLS (Cumulative Layout Shift) — target < 0.1
- TTFB (Time to First Byte) — target < 800ms
/perf bundle <path>
Analyze JavaScript bundle size:
- Total bundle size
- Per-chunk breakdown
- Tree-shaking opportunities
- Duplicate dependencies
/perf track
Compare current metrics against previous run:
- Store results in
.claude/quality-results/perf/ - Show delta (improved/regressed)
- Flag regressions as ADVISORY
Integration
/browser-testprovides raw Lighthouse data/gatesStage 5 (BROWSER) includes perf checks/shipchecklist includes perf audit
Reference Checklist
See: docs/reference/performance-checklist.md (created with this skill)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
browser-test
Browser testing using Chrome DevTools MCP and Playwright for visual verification. Start dev server, navigate, screenshot, Lighthouse audit, console errors, network check. Use when: (1) verifying frontend changes, (2) accessibility auditing, (3) performance testing, (4) visual regression. Triggers: /browser-test, 'test in browser', 'visual test', 'lighthouse audit'.
crafting-effective-readmes
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
stop-slop
A skill for removing AI-generated writing patterns ('slop') from prose. Eliminates telltale signs of AI writing like filler phrases, excessive hedging, overly formal language, and mechanical sentence structures. Use when: writing content that should sound human and natural, editing AI-generated drafts, cleaning up prose for publication, or any content that needs to sound authentic rather than AI-generated. Triggers: 'stop-slop', 'remove AI tells', 'clean up prose', 'make it sound human', 'edit AI writing'.
bugs
Bug hunting with Codex CLI Use when: (1) /bugs is invoked, (2) task relates to bugs functionality.
adversarial
Multi-Agent Adversarial Analysis System for code security
senior-software-engineer
Global skill enforcing senior software engineering best practices
Didn't find tool you were looking for?