perf
Skill2 starsChanged 6 months agoMITView on GitHub
Audit et optimisation des performances SaaS. Bottlenecks DB, bundle, Server Components, background jobs. Next.js + Supabase.
21 other projects use a version of this.
Adopted by
Most recently taken up by
- swap-cameroon/kuro-antigravity-configtheir own version, first seen Nov 15, 2026
- alexj11324/Mikkatheir own version, first seen Nov 15, 2026
- jisuzzzz/haechitheir own version, first seen Nov 8, 2026
- umararshad4/honey-stacktheir own version, first seen Nov 1, 2026
- jameskrupnik/indie-app-skillstheir own version, first seen Oct 15, 2026
- snowzhaozhj/claude-devtools-rstheir own version, first seen Oct 9, 2026
Used with
Projects with it also use incident, security and 6 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.
JkudjoSkillincident
Production incident response — structured triage, hypothesis tree, safe remediation, incident record
Also in 4 projects that use this
0xSeroSkillsecurity
Also in 5 projects that use this
Microsoft AzureSkilltest
Also in 5 projects that use this
OpenAISkillobservability
Vercel Observability expert guidance — Drains (logs, traces, speed insights, web analytics), Web Analytics, Speed Insights, runtime logs, custom events, OpenTelemetry integration, and monitoring dashboards. Use when instrumenting, debugging, or optimizing application performance and user experience on Vercel.
Also in 3 projects that use this
Microsoft AzureSkilldocs
Also in 4 projects that use this
MicrosoftSkillapi-design
Guide for designing and documenting RESTful APIs. Use when asked to design an API, create endpoints, or document an API.
Also in 4 projects that use this
- +1 more from Azure
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- alamenai/terrae★ 245same name
- OutThisLife/brooklyn-skills★ 215same name
- zeuikli/claude-code-workspace★ 155same name
- microsoft/webui★ 102same name
- alexj11324/Mikka★ 87same name
- epicsagas/epic-harness★ 20same name
- jmylchreest/aide★ 19same name
- jisuzzzz/haechi★ 17same name
- QAInsights/perf-skills★ 16same name
- fullymiddleaged/Clawness★ 5same name
11 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 repository32 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- apexSkill
- api-genSkill
- assets-pipelineSkill
- brainstormSkill
- debugSkill
- deep-updateSkill
- deploy-checkSkill
- depsSkill
- docs-genSkill
- e2e-testsSkill
- env-setupSkill
- featureSkill
- fixSkill
- forkSkill
- meta-promptSkill
- migrateSkill
- onboardSkill
- oneshotSkill
- prdSkill
- qualitySkill
- refactorSkill
- reviewSkill
- saas-initSkill
- schema-genSkill
- scope-taskSkill
- session-startSkill
- stripeSkill
- ui-auditSkill
- uiSkill
- variationsSkill
The file
Files
Phase 1 — Identifier les bottlenecks
Lancer d'abord :
python scripts/project_health.py # vue globaleWeb App (Next.js) :
- Server Components vs Client Components inutiles (
"use client"abusif ?) - Re-renders inutiles (props instables, Context trop large)
- N+1 queries (boucle avec query DB à chaque itération)
- Images non optimisées (pas de
next/image) - Composants lourds non lazy-loadés (
dynamic(() => import(...))) - Bundle size : analyser
next buildoutput — alerter si JS client > 500KB - Pas de
cache()sur les Server Components qui refetch les mêmes données
API + DB :
- Index manquants sur FK et champs de recherche fréquents
- Endpoints sans pagination (retournent tout)
- Opérations lentes dans le handler (email, PDF, webhook) → doivent être async
- Connection pooling Supabase : utiliser le pooler (port 6543), pas direct
Background jobs :
- Emails, webhooks, exports PDF, traitements IA → ne JAMAIS bloquer le handler
- Solutions recommandées : Trigger.dev v4 ou Inngest (voir
docs/integrations/ai-tools-2026.md) - Pattern :
POST /api/invoice→ créer job → return 202 → Trigger.dev exécute en fond
Edge :
- Endpoints légers (auth check, redirects) → Edge Runtime (
export const runtime = 'edge') - DB géo-distribuée pour faible latence globale : Turso (SQLite edge) ou Neon (serverless Postgres)
Phase 2 — Quick wins (par ordre d'impact)
- Index DB manquants — impact immédiat, 0 code à changer
CREATE INDEX ON public.invoices (organization_id, created_at DESC); - Pagination sur tous les endpoints de liste (
limit+cursor) - Lazy load composants lourds (éditeurs, charts, maps)
- Cache React Query :
staleTime: 5 * 60 * 1000sur les queries stables - next/image pour toutes les images + formats WebP/AVIF
- Debounce les inputs de recherche (300ms)
- Passer en async les opérations lentes (email → Resend en background)
Phase 3 — Optimisations avancées
- Streaming + Suspense : perceived performance sur les pages lentes
- ISR : contenu semi-statique avec
revalidate - PgBouncer / Supabase pooler : connection pooling DB (déjà intégré Supabase)
- Trigger.dev : background jobs pour tâches IA longues (génération, analyse)
Output
Rapport avec :
- Bottlenecks identifiés par sévérité (CRITICAL / WARNING / INFO)
- Quick wins appliqués immédiatement
- Recommandations pour les optimisations avancées + estimation d'impact
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.

