Skip to content
Skills Library
Programming · Review & audit

web-performance

/web-performance

Use when writing or changing web app code (front, backend, DB) to apply performance defaults, or when asked to audit performance (\"audit perf\", \"why is it slow\") -- 31 rules across front, backend+DB and infra, each with status, evidence and user cost. Advisory: audits and recommends, never edits during the audit. Do NOT use for lint/quality (sniper) or SEO-only audits (fuse-seo).

Repository
agents ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
4
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when writing or changing web app code (front, backend, DB) to apply performance defaults, or when asked to audit performance (\"audit perf\", \"why is it slow\") -- 31 rules across front, backend+DB and infra, each with status, evidence and user cost. Advisory: audits and recommends, never edits during the audit. Do NOT use for lint/quality (sniper) or SEO-only audits (fuse-seo).

Triggers from the description

audit perf\why is it slow\
Original author description

Use when writing or changing web app code (front, backend, DB) to apply performance defaults, or when asked to audit performance (\"audit perf\", \"why is it slow\") -- 31 rules across front, backend+DB and infra, each with status, evidence and user cost. Advisory: audits and recommends, never edits during the audit. Do NOT use for lint/quality (sniper) or SEO-only audits (fuse-seo).

How it works

  1. Mode 1 -- Default (always on, inside your current task only)
  2. Mode 2 -- Audit (on request: "audit perf", "why is it slow")
  3. Reference Guide
  4. Forbidden
Original SKILL.md headings · 70 lines, 826 words
SKILL.md preview
---
name: web-performance
description: "Use when writing or changing web app code (front, backend, DB) to apply performance defaults, or when asked to audit performance (\"audit perf\", \"why is it slow\") -- 31 rules across front, backend+DB and infra, each with status, evidence and user cost. Advisory: audits and recommends, never edits during the audit. Do NOT use for lint/quality (sniper) or SEO-only audits (fuse-seo)."
user-invocable: true
references: references/front.md, references/backend-db.md, references/infra.md
related-skills: react-effects-audit, fuse-browser-usage, verification, challenge
---

<objective>
Web Performance gives domain experts 31 performance rules (numbered 1-31, stable across reports) in two modes. **Default mode** is always on: while writing code for its task, the expert applies the relevant rules by itself. **Audit mode** runs on request: baseline measurement, every rule reviewed with evidence, absent rules ranked by gain, then a STOP for the owner's validation before any fix.

The skill is advisory. It never builds architecture (job queue, Redis, tracing, regions, load balancing) without the owner's go, and the audit phase never edits code.
</objective>

# Web Performance

## Mode 1 -- Default (always on, inside your current task only)

When you write or change code, apply these as defaults -- no request needed, no refactor of code your task does not touch:

| Area | Default |
|---|---|
| Images | Framework image component (`next/image`, Astro `<Image>`/`<Picture>`), WebP/AVIF, `sizes`, explicit dimensions; `loading="lazy"` below the fold, never on the LCP image |
| Loading UI | Skeleton matching the final layout when the layout is known; spinner only for unknown shape or short actions |
| Inputs | Debounce search/autocomplete; cancel stale requests (`AbortController`) |
| Data fetching | Independent requests in parallel (`Promise.all`, `Http::pool`); one shared cache (TanStack Query, `fetch` cache, server components) -- no duplicate calls for the same data |
| Lists / APIs | Paginate list endpoints; virtualize lists that render hundreds of rows |
| DB | Eager-load relations (`with()`, `include`/`select`), select the columns you use, index the columns you filter/sort on in the migration you write |
| External calls | Explicit timeout on every outbound HTTP/AI call |
| AI output | Stream tokens to the UI when the response is user-facing |
| Third-party scripts | Deferred (`next/script` `lazyOnload`/`afterInteractive`, `defer`/`async`) |
| Fonts | Self-hosted WOFF2 (`next/font`, Fontsource), only the weights you use |
| Rendering | Server or build-time rendering by default; client code only where interactivity needs it |
| Mutations | Optimistic update with rollback on error when the outcome is predictable |

Architecture rules (7 job queue, 10 Redis, 18 OpenTelemetry, 19 same region, 28 load balancing) are **never** introduced by default. If relevant to your task, add one line to your report: `perf proposal: rule N -- why`.

## Mode 2 -- Audit (on request: "audit perf", "why is it slow")

Read-only plus measurement. Load only the references for the domains present.

1. **Baseline** (what the project allows): lab Core Web Vitals with Lighthouse on the running app (`bun <fuse-seo plugin>/scripts/check-cwv.ts <url>` (deps in the seo plugin's package.json), or `npx lighthouse <url> --only-categories=performance --output=json`); JS size from the build output; slow queries / request timings from logs. No baseline possible -> say so; the ranking is then marked **estimated**.
2. **Stack + domains**: detect the stack (rule `01-project-detection`); keep the domains that apply -- front (`references/front.md`), backend + DB (`references/backend-db.md`), infra (`references/infra.md`). A pure static site has no backend-db domain.
3. **Review every rule** of those domains. Status is one of `applied` / `absent` / `not applicable` / `not verifiable from code`, with evidence `file:line` or the measurement. `absent` -> one sentence on what it costs the end user.
4. **Rank** absent rules by measured (else estimated) gain vs effort and risk. Architecture rules are tagged `proposal -- needs owner go`.
5. **STOP.** Present the report and wait for the owner to validate specific rule numbers. No edit before.
6. **Fix validated rules one at a time**, by the stack's domain expert: real check after each (tests / build / run the app) and a before/after on the same metric. Regression -> roll back before the next rule.

### Report format

```
| # | Rule | Status | Evidence | User cost | Rank |
|---|------|--------|----------|-----------|------|
| 15 | Lazy-load below-fold images | absent | app/page.tsx:42 | +1.2 MB on first load on mobile | 1 |
```

Then the ranked list of absent rules: `rank. #N rule -- expected gain (measured|estimated) -- effort -- risk`.

### Use by the lead

On an "audit perf" request the lead may run one domain expert per domain present (front / backend), each loading only its reference, then merge the tables by rule number.

## Reference Guide

| Reference | Rules | When |
|---|---|---|
| [front.md](references/front.md) | 1, 2, 4, 13, 14, 15, 20, 21, 22, 23, 26, 29, 31 | UI, rendering, assets, client JS |
| [backend-db.md](references/backend-db.md) | 3, 5, 7, 8, 10, 12, 16, 17, 24, 25 | API, server code, queries, DB |
| [infra.md](references/infra.md) | 6, 9, 11, 18, 19, 27, 28, 30 | Hosting, CDN, headers, deps, monitoring |

## Forbidden

- Editing code during the audit, or before the owner validates the rule numbers
- Building an architecture rule (7, 10, 18, 19, 28) without the owner's go
- A status without evidence; a gain presented as measured when it is estimated
- Blanket changes outside the current task in default mode
Files in this package (4)
  • SKILL.md 6 KB
  • references/backend-db.md 6 KB
  • references/front.md 7 KB
  • references/infra.md 5 KB

Versions

RepositoryScoreLicence
This page · fusengine/agents100MIT
wrongstack/wrongstack100MIT
nimadorostkar/Claude-Skills-collection100MIT
meyshad/skillforge100MIT
sharabarinillia/SEO-GEO-Vercel-Playbook-Skill100MIT
KILN-skills/kiln100MIT
ziniman/ai-instruct100Apache-2.0
reddygopalkrishna/developer-agent-skills100MIT
SkillMedev/skills100MIT

Database snapshot: 13.11.2026 · package version e4c95a90198f (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90audit-performance
    Audit performance against Core Web Vitals and performance budgets when the user asks to check performance, audit speed, or analyze web vitals
  • 100plan-perf-audit
    Plan-only performance audit across web, mobile, backend, and data; measures first, fixes nothing. Use when "performance audit plan", "perf burndown", "measure before optimize", or "N+1 audit plan". Apply fixes → audit-performance.
  • 90best-practices
    Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities". Do NOT use for accessibility (use web-accessibility),…
  • 95memstack-development-performance-audit
    Use this skill when the user says 'performance audit', 'why is it slow', 'optimize performance', 'page speed', 'Core Web Vitals', 'lighthouse', 'load time', or needs to diagnose and fix frontend or backend performance issues. Do NOT use for code reviews or security audits.
  • 100web-quality-audit
    Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".
  • 100web-quality-audit
    Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to \"audit my site\", \"review web quality\", \"run lighthouse audit\", \"check page quality\", or \"optimize my website\".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.