perflisted

# DLC: Performance Analysis Run performance checks against the current project and create a GitHub issue with findings. Before running, **read [../dlc/references/ISSUE-TEMPLATE.md](../dlc/references/ISSUE-TEMPLATE.md) now** for the issue format, and **read [../dlc/references/REPORT-FORMAT.md](../dlc/references/REPORT-FORMAT.md) now** for the findings data structure. ## Step 1: Identify Performance-Sensitive Areas Scan the project to determine which performance checks are applicable: | Indicator | Check Type | Tools | |-----------|-----------|-------| | `webpack.config.*` / `vite.config.*` / `next.config.*` | Bundle analysis | `webpack-bundle-analyzer`, `vite-bundle-analyzer`, `@next/bundle-analyzer` | | `lighthouse` in deps or CI config | Lighthouse | `lighthouse` CLI | | `bench` / `benchmark` dirs or scripts | Benchmarks | Project-specific (e.g. `vitest bench`, `cargo bench`, `go test -bench`) | | `docker-compose*` / `Dockerfile` | Container analysis | `dive`, `docker image inspect` | | `tsconfig.json` / `package.json` (with build scripts) | Build time | Time the build command | ## Step 2: Run Performance Tools ### Bundle Analysis (Web Projects) Select the tool based on detected build config — run only the first matching tool: ```bash # Detect bundler and run the matching analysis if [ -f webpack.config.js ] || [ -f webpack.config.ts ]; then npx webpack --json 2>/dev/null | jq '.assets[] | {name, size}' elif [ -f vite.config.js ] || [ -f vite.config.ts ]; then n