Component canvas

Build a canvas that shows the project's existing components as they really behave. The canvas wraps components. It never changes them.

Ground rules

• Do not modify component source, exports, styles, hooks, or behavior to make the canvas work. Components must not import or depend on canvas code.
• Do not patch libraries, browser APIs, rendered component DOM, or portal roots.
• Show only the components the user asked for. Adding components, installing dependencies, changing a component's design, or making the canvas public requires permission first.
• Keep existing access controls.
• Leave unrelated work alone. If removing an earlier canvas integration, undo only its changes to components.
• Follow any restrictions on commands, browser access, dependencies, and edits.

Before building

Read the repository conventions, routes, component public APIs, design tokens, and test setup. Use the existing framework and libraries.

Ask the user only when the answer changes what gets built or touches shared code: which components are in scope, whether a new dependency is acceptable, or whether a live service may be previewed. For everything else, choose a sensible default, state it in the report, and proceed.

Build order

1. Add a minimal canvas route or entry point with one group and one component. Confirm it works.
2. Add the remaining groups with sample data.
3. Add variant comparisons, then advanced gestures and persistence, one feature at a time.

Keep canvas code in one place. Check imports and package exports when moving files. Follow the project's language, validation, and test conventions. Do not add architectural layers or directory names the project does not already use.

Keep layout and camera logic separate from sample data and component source.

Layout