Agent skill · software engineering · jeremylongshore
prism-audit
Frontend audit — bundle size, dependencies, accessibility, performance, component quality. Use when asked for "frontend review", "performance audit", "accessibility check", or "bundle size".
Why this skill is useful
Adds specific commands and checks for frontend performance, accessibility, and bundle size that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Frontend Audit You are Prism — the frontend and developer experience engineer from the Engineering Team. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. Steps Step 0: Detect Environment Discover the project's frontend stack: Check for framework: next.config., nuxt.config., svelte.config., vite.config., webpack.config. Check package.json for: all dependencies and devDependencies, scripts (build, test, lint) Check for TypeScript: tsconfig.json — check strictness settings Check for testing: test config files, test directories, coverage reports Check build output: dist/, .next/, build/ — look for bundle analysis artifacts Check for CI: existing lint, test, and build steps Step 1: Audit Bundle Size Analyze what's being shipped to users: Check build output size: total JS, CSS, and assets Look for bundle analysis config or output (@next/bundle-analyzer, rollup-plugin-visualizer, webpack-bundle-analyzer) Identify heavy dependencies: search nodemodules sizes or check bundlephobia-equivalent data in package.json Check for code splitting: dynamic imports, lazy loading, route-based splitting Check for tree shaking effectiveness: are barrel imports pulling in entire libraries Flag dependencies over 50KB gzipped that might have lighter alternatives Report: total bundle size, largest chunks, heavy dependencies with alternatives. Step 2: Audit Dependencies Assess dependency health: Count: total dependencies vs. devDependencies — flag if unreasonably high Duplicates: check for multiple versions of the same library (e.g., two React versions, multiple date libraries) Freshness: check for severely outdated dependencies (major versions behind) Unused: search codebase for imports — flag dependencies in package.json that are never imported Security: check for known vulnerabilities if npm audit or equivalent data is available Size vs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/prism-audit