Install
$ agentstack add skill-glamgarondiscord-claude-saas-blueprint-perf ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Phase 1 — Identifier les bottlenecks
Lancer d'abord :
python scripts/project_health.py # vue globale
Web 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
``sql 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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: GlamgarOnDiscord
- Source: GlamgarOnDiscord/claude-saas-blueprint
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.