When to use
Use as the landing surface for a tool people open daily.
Find components, patterns, tokens, and docs
Pattern
A home that answers “is the system healthy?” before anyone opens a deeper page.
Preview
Appearance is not enough. This is the contract for when the control earns a place in the product.
Use as the landing surface for a tool people open daily.
Don't force this layout onto a task with a different risk profile or a different set of fields.
Surface counts, recent change, and the first problem worth fixing.
Every field in the pattern keeps a visible label, and primary actions remain real buttons. Error copy sits next to the field that failed.
<Dashboard>
<Stat label="Components" value={18} />
<Health score={92} />
<RecentChanges />
</Dashboard>