performance-optimization
Skill0 starsChanged 3 months agoMITView on GitHub
Use when optimizing performance — measure first, then profile, bundle, and fix loading or runtime. Covers Core Web Vitals targets, profiling workflows, and React/Next.js patterns.
125 other projects use a version of this.
Adopted by
Most recently taken up by
- valentinesamuel/claude-skillstheir own version, first seen Nov 8, 2026
- ishandutta2007/Awesome-Claude-Skillstheir own version, first seen Nov 8, 2026
- ishandutta2007/Awesome-Agent-Skillstheir own version, first seen Nov 8, 2026
- paramcodes/skillstheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- DnsQueen/orcinus-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use constraint-driven-development, using-agent-skills and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 15 projects that use this
LLl0k0laDSkillusing-agent-skills
Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
Also in 33 projects that use this
LLl0k0laDSkillshipping-and-launch
Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
Also in 42 projects that use this
HK-hubSkilldeprecation-and-migration
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when deciding whether to maintain or sunset existing code.
Also in 39 projects that use this
ukanwatSkillinput-systems
Architect game input — action mapping (abstracting keys into named actions), rebinding with conflict detection and persistence, multi-device support (keyboard, gamepad, touch), analog deadzones, and feel features like input buffering and coyote time, plus accessibility. Engine-neutral. Use when the user mentions input mapping, rebind controls, gamepad support, deadzone, input buffering, coyote time, or accessible controls.
Also in 4 projects that use this
Other versions125 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 125
- addyosmani/agent-skills★ 114ksame name
- sanity-io/sanity★ 6.4ksame name
- gamedev-skills/awesome-gamedev-agent-skills★ 6.4ksame name
- compozy/compozy★ 2.9ksame name
- ollaya-dev/ollaya★ 1.4ksame name
- buddy-compiler/buddy-mlir★ 773same name
- ThibautBaissac/rails_ai_agents★ 665same name
- derHaken/SuperAntigravity★ 439same name
- ukanwat/aaabench★ 399same name
- ukanwat/overtime★ 399same name
115 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository64 other files it gives its agents.
- subagent-driven-developmentSkill
- crazy-skills-catalogSkill
- frontend-designSkill
- system-architectureSkill
- git-workflow-and-versioningSkill
- using-git-worktreesSkill
- documentation-and-adrsSkill
- readme-generationSkill
- accessibilitySkill
- adverse-reviewSkill
- aeoSkill
- agent-designerSkill
- api-and-interface-designSkill
- best-practicesSkill
- browser-testing-with-devtoolsSkill
- canvas-designSkill
- ceo-advisorSkill
- ci-cd-and-automationSkill
- content-creatorSkill
- context-engineeringSkill
- create-voltagentSkill
- cto-advisorSkill
- deep-researchSkill
- doubt-driven-developmentSkill
- frontend-ui-engineeringSkill
- gdprSkill
- idea-refineSkill
- incremental-implementationSkill
- interview-meSkill
- iso27001Skill
- local-seo-managerSkill
- mcp-server-builderSkill
- observability-and-instrumentationSkill
- performanceSkill
- planning-and-task-breakdownSkill
- product-manager-toolkitSkill
- research-orchestratorSkill
- saas-metrics-coachSkill
- seoSkill
- soc2Skill
- source-driven-developmentSkill
- spec-driven-developmentSkill
- tech-debt-trackerSkill
- voltagent-best-practicesSkill
- voltagent-core-referenceSkill
- voltagent-docs-bundleSkill
- web-quality-auditSkill
- using-crazy-skillsSkill
- writing-skillsSkill
- core-web-vitalsSkill
- context-compressionSkill
- prompt-enhancementSkill
- token-efficiencySkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- verification-before-completionSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- security-and-hardeningSkill
- brainstormingSkill
- The first 60 shown.
The file
Files
Performance Optimization
Measure-first performance. Composite of addyosmani/agent-skills performance-optimization + web-quality/performance + vercel-labs/vercel-react-best-practices (663k).
When to use
- Performance requirements exist or you suspect regressions
- LCP, INP, CLS are outside thresholds or bundle is large
- React/Next.js data fetching, bundle, or cache needs review
Workflow
- Measure first — Do not optimize without numbers. Collect field (CrUX/RUM) + lab (Lighthouse, trace). Record baseline: LCP, INP, CLS, bundle size, JS ≤300KB compressed.
- Profile — Identify the bottleneck (critical rendering path, bundle, images, fonts, server response, N+1). Use
performancetraces, bundle analyzer, query plan. - Fix the bottleneck only — One fix at a time (code splitting, image optimization, font subsetting, caching, server response). Keep measured failures separate from hypotheses.
- Verify — Re-measure with same tooling. Confirm improvement at 75th percentile, no regression elsewhere.
Verification
- Baseline measured before any optimization
- Single bottleneck identified and fixed (not speculative batch)
- Re-measurement shows improvement, thresholds met (LCP ≤2.5s, INP ≤200ms, CLS ≤0.1 at p75)
- Bundle budgets respected: JS <300KB, CSS <100KB, above-fold images <500KB (compressed)
References
- Source:
addyosmani/agent-skillsperformance-optimization,addyosmani/web-quality-skillsperformance,vercel-labs/agent-skillsvercel-react-best-practices
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

