Software Development Skills

Static performance audit of a route, page, server function, or module — finds N+1 query patterns, missing DB indexes for filtered/joined columns, oversized SELECT fetches, blocking sequential awaits that could parallelize, unmemoized React hot-path computations, oversized client bundles from accidental server-only imports leaking to the client, and synchronous file/network reads inside request handlers. Reads files; does not run benchmarks. Reports findings ranked by likely impact with concrete fixes (add index on X, batch with dataloader, Promise.all these awaits, dynamic-import this dep, move this to the loader). Trigger phrases — "audit perf", "this page is slow", "why is this slow", "/audit-perf", "perf review", "find n+1", "check for performance issues", "audit query performance", "bundle size audit". Skip for — single-line tweaks, copy edits, infra-level perf (DB tuning, k8s sizing), and runtime profiling needs (recommend a real profiler).

Reorganize a directory of loose, ungrouped files (images dumped in public/, scripts piled in src/, assets at the root of a feature folder) into a clear grouped layout, then update every reference — imports, string paths, CSS url(), , OG/metadata tags, tsconfig aliases, and other configs — so builds and runtime URLs stay intact. Use when the user says "this folder is a mess", "organize this directory", "regroup these files", "tidy up public/", "group these images", "restructure assets/", "this folder needs structure", or points at a flat pile of files and asks for a better layout. Skip for: splitting an oversized single file (use file-modularity), pure renames without grouping (use a rename refactor), or removing dead files (use rip-out).