# Design-system context as the constraint layer ## Short narrative `Your design system should be the prompt` is strong launch language, but the strategic classification should stay honest: design-system context is currently a trust/differentiator layer that supports several wedges, not automatically a standalone active wedge. ## Why this wedge matters Question it answers: > What makes Mode's AI output feel trustworthy instead of generic? Narrative: > Serious product teams care whether an AI change respects the components, tokens, patterns, and code conventions they already use. Design-system context is the constraint layer that makes real-product change believable. This protects us from the bad interpretation: > "AI UI tools always invent a second design system that engineering has to clean up." The stronger story is: > Mode uses product, component, and design-system context as constraints for scoped UI changes, then keeps the result reviewable instead of pretending fidelity is automatic. ## How it supports the launch spine This is a trust layer for the launch spine. It can supply memorable language like `Your design system should be the prompt`, but it should stay proof-gated and supporting unless market testing shows it has primary pull. ## Strategic bet Design-system fidelity matters because it makes real-product AI credible. It may become a primary wedge for design-system leads or Design Engineers if testing shows audience pull, but it should remain proof-gated. ## Why Mode is suited Mode can make product/code/component context central to the workflow. When proof assets show component reuse, token adherence, or inspectable diffs, this layer becomes a credible differentiator. ## Product entry / CTA path Use the existing product's components, tokens, and patterns as constraints for a scoped UI change. ## Proof needed Show the component/context trace: what existing component or token was used, what changed, and how engineering can inspect the result. Do not claim perfect fidelity unless the proof demonstrates it. ## Launch-spine relevance This layer can power a memorable hook while supporting active wedges like real-product design, production-aware AI, one UI issue, and engineering review. ## Risks / confusions - Can sound like a design-system-only tool. - Competitors also claim components/tokens; proof needs to be concrete. - Should not be promoted to `active_launch` until Alex sees evidence that it creates primary market pull.