Skip to main content
Hand a running app to your agent and it builds a .sightmap/ directory in your repo — driving the browser and running the CLI through the sightmap-authoring skill. The app can be a local dev server, preview deployment, or hosted URL. The agent writes the YAML; you review the diff before committing it.
1

Install the CLI and skills (once)

sightmap skills install writes sightmap-authoring and sightmap-browser to ~/.agents/skills. Pass --target <dir> to use another directory. See Install for the npx, Go, and browser-install options.This is the one-time human setup. From here on, your agent runs the browser session and the CLI through these skills.
2

Hand your agent the app

Point your agent at the running app and give it a prompt like:
Build a sightmap for this app at http://localhost:3000/. Start a browser session, inspect the main routes with sightmap snapshot --coverage, verify each selector with sightmap sel-probe, and name components until every view has zero orphaned T3 nodes. Let me review the YAML before committing it.
Through the sightmap-authoring skill, the agent starts the session itself:
browser start launches Chrome and the local corpus server, which reloads the YAML whenever the agent changes it.
Prefer to drive it yourself? Run sightmap browser start from your project root, leave it in the foreground, and use another terminal for the loop commands below.
3

The agent runs the edit-verify loop

For each route, the agent repeats this loop:
snapshot --coverage reads the page, reports coverage, and suggests selectors for unattributed nodes. The agent probes a selector, updates .sightmap/, and runs it again.
T1 nodes have their own component name. T2 nodes sit inside a named component. T3 nodes have no named ancestor. The agent keeps iterating until each view reports 0 orphaned T3 ✓.
4

Review and commit

The agent validates and lints as it works:
validate checks the YAML structure and exits nonzero on errors; lint reports advisory quality issues. When the agent reports the views clean, review the new or changed YAML and commit it:

​
Keep the corpus current

If the app has no stable selector for a component, add data-component="ComponentName" to the source. This gives Sightmap an explicit runtime hook. When a route or component changes, have your agent rerun sightmap snapshot --coverage on the affected pages. Existing selectors and memory entries remain in the corpus, while coverage exposes new orphaned nodes.

​
Next steps