c132. Native Design Prototyping

Stage 1, split from c130's initial prompt on 2026-11-09. The passages below are Mark's words from ../c130.native-app/initial-prompt.md, unchanged. Program plan: ../c130.native-app/plan.md.

From c130's initial prompt

• implement our brand in this GPUI kit to get the benefit of much simpler native deployment.
• Design the app in our Qpoint flavored GPUI
  • This flavor is more subtle-to-non-existent at first
• Research and understand the things we need to know about this new ecosystem. Let's summarize for both the designers and the builders so we know the new system we're working in. We may work with the Figma mcp, our illustrator rendering skills to create design prototypes for the designers wo manually work on. We'll cross that bridge later, but research resources that are already out ther
• Design prototyping. Let's evaluate and define a process for mocking up aspects of the GPUI kit UI and workflow as we currently do (see phase work under pages). I'd like to continue our patter of prototype, experiment and refine in design, then push into the real app. What should that look like? What tools at our disposal? agent tools?

Pointers

• The primer this cycle builds on: ../c130.native-app/research/ (c130 Phase 1), especially agent-tooling.md and platform.md.
• How design prototypes pages today: app/pages/pages/phase0..phase4/, app/data/page-registry.ts, the /figma-to-vue, /illustrator, /capture skills, and the lab's review walk (/pages/phase4/review-walk).
• The app the prototypes push into: c131.

Create a plan, ask any clarifying questions, suggest patterns I may not be considering.