Canvas
Inspect your product's screens and states visually before you publish.
The canvas renders your specs as actual screens, so you can see your product instead of only reading about it. Use it to confirm that your screens and their states match your intent before you publish a release. To follow along, open a project with at least one RPML screen file that renders.
Walk your screens
- Open the project in the workbench.
- Select a screen file in the file tree — the canvas renders that page.
- Step through its primary states and variants as your spec models them: empty, loading, error, permission-restricted, and so on.
- Note any gaps, then fix them by editing the file directly or asking the in-app agent.
- Re-check after your edits, and only then publish.
Why it's worth the time
- Your key user journeys become visible as screens, not just prose buried in a chat log.
- You can point a teammate — or an agent — at a specific screen file when reporting a problem.
Troubleshooting
| Issue | What's going on |
|---|---|
| The canvas is blank | The file may be a doc-mode file (like README.rpml) or contain invalid RPML. Validate it, or open an actual page file. |
| The spec doesn't look like a polished design mock | That's expected. OriginAI specs are implementation-depth product context, not a pure visual design tool. |