"Engineering handoff is straightforward: it happens through the PR. Design system updates and prototypes. I can point to what changed, what needs refining in the design system, and what is "prototype-only". Engineers can reuse components directly, and use the prototype code as reference - because it runs on the same stack, with the same components. Before going into the setup, a few honest trade-offs we've run into:"
"Dust runs on React, in a monorepo. Our design system (Sparkle) lives there too. Sparkle gives us two complementary places to work: Storybookfor building and documenting components in isolation (variants, interactions, visual regression). It's our component catalog. Playground is just a small Vite app nested inside Sparkle. It is a fast development server, it starts quickly, refreshes instantly as you edit, and stays lightweight. The key point: both environments consume the same Sparkle source and Tailwind styles, so prototypes reuse real components and tokens by default."
Engineering handoff happens via pull requests that include runnable prototypes and design system updates. Designers identify what changed, what needs refining, and what is prototype-only. Prototypes run on the same stack and use the same components, allowing engineers to reuse components directly and reference prototype code. Trade-offs include sandbox limits that fail to reproduce real latency or backend quirks, flaky preview feedback workflows, occasional tooling or environment time sinks, premature visual polish, and unclear guidance on what to reuse versus what is prototyping. The stack uses React in a monorepo with Sparkle, Storybook, and a lightweight Vite playground, both sharing source and Tailwind styles.
Read at Medium
Unable to calculate read time
Collection
[
|
...
]