Starting a new product
Answer the product decisions, adopt the Foundation, choose a product theme, use the baseline components, and make the product-local catalog part of the build.
New product guide →A complete foundation to start from. A living catalog to build with. Eventually, a governance layer so product interfaces stay coherent as they evolve.
The source contract stays stable. Theme decisions change the product’s expression without rewriting every component job.
These are adoption paths — not the foundation, living catalog, and later governance named above. New products start from the baseline. Existing products keep their intent and make the hidden system explicit before cleaning it up.
Answer the product decisions, adopt the Foundation, choose a product theme, use the baseline components, and make the product-local catalog part of the build.
New product guide →Analyze first, then move through Import → Catalog → Names → Cleanup → Rules → Wire without redesigning the imported UI while you are still trying to understand it.
From Prototype guide →After design-system completeness, strengthen the engineering track: Reproduce → Contract → Prove → Harden → Contain → Open.
Engineering Foundation guide →Live catalogs are the primary door. Included is the completeness checklist. Theme Workbench is how expression changes without rewriting jobs.