A design system is a set of refusals.

A design system is a set of patterns, and most of its work is refusal. A pattern is a problem that recurs, with a known solution, such as how a form reports an error or how an app frame behaves on a phone. A component is only a pattern packaged for reuse. Each refusal keeps a pattern whole, so nobody solves the same problem again on the next screen. Without that, every screen solves it again, and AI makes this worse, because it generates each screen alone and each one looks fine.

Some answers inside a pattern are measured. A fingertip needs a target of about 44 pixels, text needs enough contrast to read, and people group what sits close together. These are floors, so Kookie UI builds them into its defaults. Everything above the floors is judgement, such as a corner radius or an accent colour. A judgement should be made once and named as a judgement, because false precision is as wrong as a missing rule.

Patterns are sorted by what they do, not by how they look. Tabs and a segmented control look like the same row of segments, but tabs move you to another view and a segmented control changes the view you are on. One component with two variants would teach that they are the same pattern, so they stay two components. Spacing is a pattern too: the distance between two components is a relation that only their container knows, so no Kookie UI component has a margin.

The hardest requests to refuse have a real problem and a good reason. A system that accepts each good reason, one at a time, fills with parts that nobody decided as a whole, so the better question is whether a change makes the whole system more correct. A refusal is a default, and an override stays possible and easy to spot. When a refusal is wrong, somebody builds the part outside the system, and that shows where the system must change.