Request access
Now inviting teams to the private beta

Find the screens nobody drew.

PathKit maps every path through your mobile flow, the happy one and every one that fails, before your agent builds the app without them.

Request access
Welcome
Phone number
Enter the code
Create your username
Add your rivals
Paywall
No one loses quietly

01One press in the Figma plugin, or a folder of screenshots. Nothing is written back to your file.

One flow, from import to agent

Bring the flow in.

From the Figma plugin, a Figma link, Mobbin, or a folder of screenshots.

Every path, followed.

Each control is wired to where it leads, from the prototype or from the picture.

Then the screen nobody drew.

Resend code leads nowhere yet. The gap goes on the canvas, where the team will see it.

Answered where it lives.

Reply, resolve, or say it is not needed. A dismissed suggestion stays dismissed.

Handed to your agent.

The flow and its open suggestions go to Claude, ChatGPT, Cursor or Codex over MCP.

The Rivals onboarding comes into PathKit as six screens. Every control is wired to the screen it leads to. Resend code on Enter the code leads to a screen nobody drew, Code expired, which PathKit marks on the canvas and raises as a suggestion that can be answered or handed to a coding agent.

  • EC-112, important. A screen you cannot reach
  • EC-118, important. A failure with no screen
  • EC-124, important. Ends here, no way onward
  • EC-131, important. No back, no close
  • EC-101, suggested. A button going nowhere
  • EC-107, suggested. Several dead buttons, one screen
  • EC-140, suggested. A state nobody drew
  • EC-156, optional. Can load, can never fail
  • EC-163, optional. Search with no empty result
  • EC-201, important. Takes typing, no error
  • EC-205, important. Delete with no confirm
  • EC-202, suggested. Can be empty, no empty state
  • EC-204, suggested. Fetches, cannot fail or go offline
  • EC-206, suggested. A button wired to nothing
  • EC-203, optional. Fetches, no loading state
  • EC-207, optional. Filed as one thing, looks like another
How it fits

Figma in. Your agent out.

Bring a page from Figma or a folder of screenshots. Hand the reviewed flow to your team as a link, and to your coding agent over MCP.

One onboarding flow12/41

29 screens nobody drew. The file had 12, the shipped app has 41.

16 checks, EC-101 to EC-207.

16 checks.
No score. Every one points at a place on a screen.

Every path, in order5 steps

The Rivals onboarding in five steps: Welcome, Phone number, Enter the code, Create your username, Add your rivals.

ShareFree on every plan

Read only and no login. Readers never count as seats.

MCPClaude · ChatGPT · Cursor · Codex
> get_flow "Rivals onboarding"   7 screens, 7 wires  10 open suggestions   EC-118  "Resend code"          has no screen  fix     design it, rewire it
Figma pluginor screenshots

One press brings the page in. Nothing is written back to your file.