performance-auditlisted

Deep performance audit for Python and React codebases. Use this skill ANY TIME the user shares code and mentions performance, slow queries, latency, re-renders, optimization, profiling, bottlenecks, or memory issues — even if they don't use the word "audit". Also trigger when the user pastes code and asks "is this efficient?", "why is this slow?", "how can I improve this?", or shares ORM/database code (Django, SQLAlchemy, Prisma, TypeORM) where N+1 query risks are high. Covers: N+1 queries, missing indexes, loop anti-patterns, React re-render storms, missing memoization, bundle bloat, async misuse, memory leaks, caching strategy opportunities (query caching, HTTP caching, client-side caching, cache invalidation triggers), and 20+ other patterns across both stacks.
SoluDevTech/ai-driven · ★ 3 · API & Backend · score 57

Install: claude install-skill SoluDevTech/ai-driven

# Performance Audit Skill Perform systematic, production-grade performance audits on Python and React code. Always be direct: name the exact line/pattern, explain the cost, and provide a fixed version. --- ## Step 1 — Detect the domain(s) Scan the provided code or file list: - **Python indicators**: `.py` files, `import`, `def`, `class`, ORM imports (`django`, `sqlalchemy`, `tortoise`, `peewee`), `async def`, `FastAPI`, `Flask`, `Celery` - **React indicators**: `.jsx`, `.tsx`, `.js` with JSX, `useState`, `useEffect`, `React`, `Next.js`, `Vite` - **Both**: monorepo or full-stack projects — run both audits → Load **only** the relevant reference file(s) before proceeding: - Python: read `references/python-patterns.md` - React: read `references/react-patterns.md` --- ## Step 2 — Structured audit pass For each domain detected, systematically scan for every pattern listed in the reference file. Do **not** skip patterns just because they seem unlikely — check the code explicitly. Use this internal checklist approach: 1. Read the full code once for context 2. Second pass: match each pattern category from the reference file 3. Tag every finding with a severity level (see below) --- ## Step 3 — Caching strategy analysis (always run, for every domain detected) This is a mandatory second pass focused exclusively on caching opportunities and invalidation. Run it independently from the performance pattern scan — do not merge findings. Load the `## Caching Strategies` section f