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".
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. page-specific:** ratio of reusable to one-off components ### Step 2: Map Architecture Understand the technical architecture: - **Routing:** file-based, config-based, or library-based — nested routes, dynamic routes, catch-all routes - **State management:** what library (Zustand, Redux, Pinia, Svelte stores, React Context), how is state organized, is there a clear pattern - **Data fetching:** server components, loaders, API routes, client-side fetching, tRPC, GraphQL — what patterns are used - **API integration:** how does the frontend talk to the backend — REST, GraphQL, tRPC, direct DB access - **Styling:** Tailwind, CSS Modules, styled-components, vanilla CSS — is there a design system or token system - **Build config:** Vite, webpack, Turbopack — any custom plugins, aliases, or unusual configuration ### Step 3: Assess Quality Metrics Measure the current state: - **Bundle size:** check build output if available, or estimate from dependencies - **Dependency count:** total deps, heavy deps, potentially unused deps - **Dependency freshness:** how many major versions behind on key dependencies (framework, React, etc.) - **Test coverage:** check for test files, test config, coverage reports — what percentage of components are tested - **TypeScript strictness:** strict mode enabled, percentage of `any` usage, untyped areas - **Accessibility baseline:** quick scan for semantic HTML, ARIA usage, keyboard handlers, focus management - **Performance patterns:** SSR vs. CSR split, code splitting usage, image optimization ### Step 4: Present Assessment ``` ## Frontend Reconnaissance ### Stack - **Framework:** [name + version] - **Language:** [TypeScript/JavaScript — strictness level] - **Styling:** [approach] - **State management:** [library/pattern] - **Build tool:** [name + config notes] - **Hosting:** [platform] - **Testing:** [framework — coverage level] ### Architecture - **Pages:** [count] routes — [routing pattern] - **Components:** [count] total — [count] shared, [count] page-specific - **Data fetching:** [pattern] — [server/client split] - **API integration:** [approach] ### Health Indicators | Metric | Status | Notes | |--------|--------|-------| | Bundle size | [size or unknown] | [assessment] | | Dependencies | [count] | [freshness, issues] | | Test coverage | [percentage or unknown] | [what's tested] | | TypeScript | [strict/loose/none] | [any usage level] | | Accessibility | [baseline assessment] | [key gaps] | | Performance | [assessment] | [SSR/CSR, code splitting] | ### Strengths - [what's well done] ### Risks - [what could cause problems] ### Modernization Recommendations 1. [highest value improvement] — [effort] — [impact] 2. [next improvement] — [effort] — [impact] 3. [next improvement] — [effort] — [impact] ``` Reconnaissance report — present facts, highlight risks, recommend improvements. Do not make changes. ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.