agentleFS
Sign inStart free
charanjit-singhcharanjit-singh/lovable-skills/skills/performance-budget/SKILL.md

performance-budget

Skill10 starsChanged 6 months agoMITView on GitHub

Use when the app feels slow, bundle is large, or optimizing LCP, INP, CLS, images, or unnecessary re-renders. Not for SEO copy or accessibility-only passes.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No duplicate fetches — dedupe with SWR/React Query keys (typed-api-hooks-forms / tanstack-query-alternative).

    line 22
  2. Very specific:

    Prefer one joined Supabase select over many parallel hooks on same screen.

    line 23
  3. Distinctive:

    Import icons/components individually.

    line 34
  4. Distinctive:

    Check for duplicate date/libs (moment + dayjs).

    line 35
  5. Distinctive:

    Avoid main-thread long tasks from sync JSON parse of huge payloads.

    line 40

“Common” is measured: kept by at least 6 in 10 of the 3 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Performance budget

Measure first

Identify: LCP element, large JS chunks, N+1 network, layout shift sources.

Images

  • WebP/AVIF; explicit width/height or aspect ratio to prevent CLS.
  • Lazy load below fold; priority only for LCP hero.

Data

  • No duplicate fetches — dedupe with SWR/React Query keys (typed-api-hooks-forms / tanstack-query-alternative).
  • Prefer one joined Supabase select over many parallel hooks on same screen.
  • Paginate large lists; virtualize tables > 100 rows when needed.

React

  • Memoize expensive lists only when profiling shows need — avoid premature useMemo everywhere.
  • Split routes with lazy React.lazy + Suspense for heavy admin sections.
  • Defer non-critical third-party scripts (analytics).

Bundle

  • Import icons/components individually; avoid barrel importing huge libs.
  • Check for duplicate date/libs (moment + dayjs).

Targets (guidance)

  • LCP < 2.5s on mid mobile where possible.
  • Avoid main-thread long tasks from sync JSON parse of huge payloads.

Output

List findings: issue | impact (high/med/low) | recommended fix.

Download now (ZIP)

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.

Check your setup, free