Design systems
Bring an approved visual system into planning, prototypes, implementation and review without replacing design judgement.
Guides in this section
Design-system implementation guideThis guide is for maintainers integrating the portable capability into EWAI projects and hosts. It adds no server backend, connector, or design-system management UI: the supported boundary is local CLI/domain functions, installed skills, pr…
Design-system pack authoring guideUse a pack when guidance should be reused across features or projects. Keep a one-off delivery decision local; promote it only after evidence shows it is a repeatable rule.
Design-system review guideUse $ewai-design-system-review when a prototype or implemented surface exists. The review baseline is the immutable receipt linked by the selected artefact’s manifest, not whichever pack happens to be installed today.
Design-system user guideUse a design-system pack when new screens should follow the product's existing design decisions. The pack can describe components, layout, wording, accessibility and how empty or error states should behave.…
Product owner guide to EWAI design systemsA design system helps you make the intended product experience repeatable. It is broader than visual tokens and components: it can capture the experience promise, product principles, interaction behaviour, content, meaningful states, respon…