Loading...
Loading...
Found 44 Skills
Audit and optimize Convex application performance, covering hot path reads, write contention, subscription cost, and function limits. Use when a Convex feature is slow, reads too much data, writes too often, has OCC conflicts, or needs performance investigation.
Orchestrates comprehensive performance audits across full-stack monorepos. Coordinates performance-expert, design-consistency-auditor, accessibility, security-expert, and qa-reviewer skills to audit frontend, backend, database, browser extensions, and shared packages.
Conduct comprehensive web performance audits. Measure page speed, identify bottlenecks, and recommend optimizations to improve user experience and SEO.
Runtime performance audit worker (L3). Checks blocking IO in async, unnecessary allocations, sync sleep in async, string concat in loops, missing to_thread for CPU-bound, redundant data copies. Returns findings with severity, location, effort, recommendations.
Web performance audits with Core Web Vitals, bottleneck identification, optimization recommendations. Use for page load times, performance reviews, UX optimization, or encountering LCP, FID, CLS issues, resource blocking, render delays.
Coordinates 3 specialized audit workers (query efficiency, transaction correctness, runtime performance). Researches DB/ORM/async best practices, delegates parallel audits, aggregates results into single Linear task in Epic 0.
Audit web performance using Chrome DevTools MCP. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed.
Load PROACTIVELY when task involves optimizing speed, reducing bundle size, or improving responsiveness. Use when user says "make it faster", "reduce bundle size", "fix slow queries", "optimize rendering", or "check Core Web Vitals". Covers bundle analysis and tree-shaking, database query optimization (N+1, indexing), React rendering performance (re-renders, memoization), network waterfall optimization, memory leak detection, server-side performance, and Core Web Vitals (LCP, FID, CLS) improvement.
Read-only audit of performance and reliability — event-loop discipline, streaming and backpressure, memory and CPU diagnostics, shutdown/timeout/job habits, resilience topology (circuit breakers, retry budgets, queue bounds), and frontend delivery (Core Web Vitals, bundle size, hydration) — with evidence per finding and a SHIP / FIX / BLOCK verdict. Use when a service or page is slow, memory climbs, tail latency is bad, a worker OOMs, before a load event, or 'почему тормозит'. Measures and reports; rewrites no hot paths. Do not use for retry/idempotency contracts (awesome-error-standards) or render style rules (awesome-code-standards).
Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.
Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.
Read-only whole-project deep audit — architecture and module boundaries, documentation-vs-code fidelity, design-principle adherence (YAGNI/KISS/SOLID), and extensibility (how easily someone builds from source and adds a new provider/plugin/adapter) — producing a prioritized report with a SHIP / FIX / BLOCK verdict. Framework- and language-agnostic. Use when the user asks to 'audit/analyze the architecture', 'review the whole codebase design', 'does the code match the README/docs', 'how hard is it to add a new X', 'is this codebase ready to build on', or 'проведи глубокий анализ проекта', 'оцени архитектуру', 'соответствует ли код документации'. Do not use for a single diff/PR (use awesome-code-review), a named vulnerability (awesome-security-audit), runtime latency/memory (awesome-performance-audit), public-client disclosure (awesome-leak-audit), comment/naming cleanup (awesome-code-cleanup), or design-stage shaping of a new system or API (awesome-design-doc, awesome-api-design).