Agent skill · software engineering · jeremylongshore
prism-recon
Frontend reconnaissance — map the component tree, routing, state management, build config, and assess quality. Use when asked to "understand this frontend", "frontend assessment", or "what's the UI built with".
Why this skill is useful
Adds specific commands and patterns for frontend stack assessment 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 Reconnaissance 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 Scan the project to identify the complete frontend stack: Check for framework: next.config., nuxt.config., svelte.config., astro.config., vite.config., remix.config. Check package.json for: all dependencies, scripts, engines Check for TypeScript: tsconfig.json — note strictness level Check for monorepo: pnpm-workspace.yaml, turbo.json, nx.json, lerna.json Check deployment: vercel.json, netlify.toml, fly.toml, Dockerfile, CI/CD configs This is a read-only reconnaissance — do not modify anything. Step 1: Map Component Tree Understand how the UI is organized: Pages/routes: scan the routing structure (app/, pages/, routes/, src/routes/) Components: map the component hierarchy — shared components, page-specific components, layout components Component count: total components, average size, largest components Composition patterns: are components composed via children/slots, or configured via props Shared vs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/prism-recon