The rule: no error shown to you requires engineering knowledge to interpret. When Prototo can’t recover automatically, it tells you what to do.

​
The error translation layer

What you seeWhat to do
A component couldn’t be foundRun: proto reset
A screen has an errorAsk Claude Code: fix any errors in the [ScreenName] screen
Prototo is already runningClose the other terminal window first
Prototo needs to updateRun: proto update
Can’t reach your deviceCheck you’re on the same WiFi
Something went wrongRun: proto reset

​
proto reset — the escape hatch

proto reset
This fixes 90% of issues. Silently it kills the bundler, clears caches, and restarts the environment with the Simulator open. You’ll see: Proto restarted. Simulator is updating.

​
A screen has an error

If Claude Code generates a screen that won’t compile, the error translation layer responds: 
A screen has an error. Ask Claude Code:
"fix any errors in the [ScreenName] screen"
Paste that into Claude Code. It reads the file, identifies the issue, rewrites it. Resolved without you seeing the underlying error.

​
The Simulator isn’t opening

Make sure Xcode is installed and you’ve run: 
xcode-select --install
Then try: 
proto reset

​
Claude Code isn’t reading my design system

CLAUDE.md and DESIGN.md must be at the root of your project folder — not inside any subfolder. Open Claude Code from inside the project folder: 
cd myapp
claude

​
proto design isn’t working

Make sure you’re inside a Proto project folder: 
cd myapp
proto design

​
A custom component library isn’t generating right screens

Add 2–3 component examples to an ## Examples section in DESIGN.md, then ask Claude Code to regenerate the screen. Two or three examples cover most libraries — Claude extrapolates the rest.

​
I need to start fresh

Delete the project folder and run: 
npm create proto@latest myapp

​
Still stuck?

Open an issue on GitHub: github.com/sherizan/proto/issues Or reach out via prototo.app.