2026-09-11 / Field note

A foundation should preserve decisions

Why a useful starter defines boundaries without pretending the product is already designed.

A good foundation removes repeated setup work. A great one also preserves the decisions that are expensive to rediscover.

Define the boundary

The public website and the product application have different jobs. The site earns attention through clarity and pace. The application helps someone complete work with predictable controls, resilient states, and less visual noise.

They should still feel related. Typography, spacing, language, and a small set of visual signals can connect them without forcing both surfaces into the same layout.

Keep examples honest

Example views should show how components assemble into real workflows. They should not claim that billing, data, or identity is connected when those modules are disabled.

That distinction makes the starter safer to adopt—and much easier to trust.