Visualize and document every view in your frontend at a glance
Automatically map all the views and routes in your frontend codebase into a structured overview. Great for onboarding, audits, and keeping navigation architecture visible as the project grows.
Scan my frontend project and produce a complete view map. For each route, identify the component it renders, any nested child routes, and the main data sources or API calls it depends on. Output the result as a structured tree with route path, component name, and a one-line description of what the view does. Flag any routes that are missing a component or appear unreachable.
Frontend View Mapper scans your project's routing configuration and component
tree to produce a structured map of every view, route, and its key dependencies.
The output is a living document you can reference during reviews or share with
new team members.
A clear, navigable map of every screen in the frontend — no more grepping
through router files to understand what the app actually renders.
Find broken setup docs before new contributors do
Detect drifting documentation (broken links, wrong setup steps, missing prerequisites) by testing docs as code and filing fix PRs/issues automatically.
New repo? Running in minutes, not days
Point your Claw at an unfamiliar repo and it figures out how to get it running. Excellent starter recipe because it turns a messy pile of config files into a concrete setup plan you can follow.
Real sources, named experts, actual quotes
Deep research that finds primary sources with named individuals, community sentiment from Reddit/HN/X, and news coverage. No summaries of summaries — actual quotes with URLs.
Email and calendar without leaving your terminal
Full Gmail control via the gog CLI. Read, send, search, organize emails. Create events, set reminders, RSVP to invitations. All from natural language or CLI commands.