Skip to content
Playbook
Install
The Playbook

screen-map

Screenshots every route of your running app, graphs the links and finds the orphan pages.

The problem

Every app that's been around for a while has screens nobody can find anymore: a settings page from two redesigns ago, an onboarding step you can only reach from an old email. A link crawler never sees them, because nothing links to them. screen-map reads the routes from your source, so it finds the screens your nav forgot.

Matt Waite, founder

Get it

npx @excellent-so/screen-map build

Source on GitHubPackage on npm

Version 0.2.4 · MIT license

Quick start
# in your project's root, with the dev server running
npx @excellent-so/screen-map build
npx @excellent-so/screen-map open

# a dev server on another address
npx @excellent-so/screen-map build --base=http://localhost:3001

How to use it

  1. Start your app's dev server. screen-map needs Node 20 or later and Chrome (Chromium, Edge and Brave work too).
  2. In the project's root, run npx @excellent-so/screen-map build. It writes the map to .screenmap/, so add that folder to .gitignore.
  3. Run npx @excellent-so/screen-map open and read the board: orphans have no links in, dead ends have no links out.
  4. Select screens, write a note and copy a brief for your agent, or turn the notes into a markdown file or a GitHub issue.

Where it came from

Route discovery and the orphan report work for Next.js App Router apps, where screen-map reads every route from your app/ folder with no config file. Any other app gets the crawl: it follows links from / on the running app, screenshots the pages it reaches and maps the links between them.

It screenshots each screen in headless Chrome, graphs the links it finds in your source (<Link href>, router.push, redirect) and on the rendered pages, and crawls the running app to check them. It runs on your machine and has no runtime dependencies.

Version 0.1.0 reached npm on July 9, 2026. The repo went public on November 6, and 0.2.4 is the current release.

Excellent checks AI agents' work the same way, by looking where the work landed: the code, the build, the file. excellent.so