agentleFS
elvladislavoelvladislavo/claude-skills/.claude/skills/performance-optimization/SKILL.md

performance-optimization

Skill0 starsChanged 19 days agoNo licenceView on GitHub

Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

132 other projects use a version of this, 62 of them edited; most edited versions we compared are an older text (32 of 58); 2 new projects in the last 4 weeks, against 1 the 4 before.

How people change it

Most projects run an older version: 32 of 58 add nothing and lack rules this one has, most likely added since.

Of the 58 edited versions we compared: 13 keep every rule, 32 are an older text, 13 made changes of their own.

Not in older versions

  1. Unbounded data fetching. Every list endpoint paginates with a limit and a stable order. [Pattern](references/optimization-patterns.md#unbounded-data-fetching).missing from 32 of 32
  2. Missing image optimization. Every image declares width and height (CLS). The LCP image gets fetchpriority="high", modern formats (AVIF, WebP) through <picture>, and srcset/sizes for resolution switching; …missing from 32 of 32
  3. Use two complementary layers when the surface is user-facing:missing from 32 of 32
  4. When either guard fires, return to Step 1 and establish a fresh baseline before proposing another fix.missing from 32 of 32
  5. Use the symptom to decide what to measure first:missing from 1 of 32

Rules people drop

  1. Unbounded data fetching. Every list endpoint paginates with a limit and a stable order. [Pattern](references/optimization-patterns.md#unbounded-data-fetching).dropped by 13 of 13
  2. Missing image optimization. Every image declares width and height (CLS). The LCP image gets fetchpriority="high", modern formats (AVIF, WebP) through <picture>, and srcset/sizes for resolution switching; …dropped by 13 of 13
  3. Use two complementary layers when the surface is user-facing:dropped by 5 of 13
  4. When either guard fires, return to Step 1 and establish a fresh baseline before proposing another fix.dropped by 5 of 13
  5. When NOT to use: Don't optimize before you have evidence of a problem. Premature optimization adds complexity that costs more than the performance it gains.dropped by 4 of 13
  6. Use the symptom to decide what to measure first:dropped by 4 of 13
  7. No performance monitoring in productiondropped by 3 of 13
  8. After any performance-related change:dropped by 2 of 13

Rules people add

  1. Key design decides correctness. Every input that changes the response belongs in the key: tenant, locale, permissions, feature flags. A key that omits the viewer is how one user's data gets served to another, and that ships as a performance win.added by 8 of 13

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Rising: 2 new projects took it in the last 4 weeks, 2× the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 1 new projectWeek of Oct 18: 1 new projectWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 3 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use input-systems.

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.
  • ukanwatSkill

    input-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

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 114 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 114 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.