Knowledge Islands Design System standard
You are applying the Knowledge Islands Design System standard - one way to keep the knowledge behind a user interface: values in the token source, the practical how in a design guide, stable behaviour in Specifications, the why in Decision Records, and checks that keep them true. Read the Design System standard before establishing, auditing or changing a design system; the rubric publishes its checkable criteria, the annotated board gives the method for the interface's standing review board, the design levels set how a round of design is drawn, exemplars point at a conforming repository, and sources records its provenance.
What this skill owns
- The placement model - which home holds each kind of design knowledge: values, how, what, why, when and proof.
- The component library - every component library sorted by atomic design into tokens, atoms, molecules, organisms, templates and pages, with one components document giving each component its signature, what it owns and does not own, and its hand-offs; and the shells, designed from the outside in, each owning its state.
- The design work method - review, brief, options, decision, build, consolidate and retire, and what each stage leaves behind, with options drawn at three levels: information architecture, wireframe and mock-up.
- The annotated board - the standing projection of the built interface, with numbered pages and coded regions the owner quotes, and
scripts/annotate-board.ts, which prints the in-page region collector and builds the coded overlays and their local previews from a site's board plan and screenshots.
- The floor - four requirements every adopting design system meets: one home for values, readable contrast, meaning never by colour alone, and keyboard parity.
- The mechanical checker -
ki repo audit --skill ki-design-system checks the .ki.toml declaration, that the token sources, design guide and design checks exist, that the guide names its token sources, and that the guide repeats no literal colour value.
A repository's own design guide, tokens and decisions stay with that repository. The formats of guides, Specifications, Decision Records and work records stay with ki-guides, ki-specs, ki-decision-records and ki-work-roadmap; token build mechanics for content sites stay with ki-repo-website-content.
Operating modes
Carries the universal AUDIT · CONFORM · EDUCATE · REFRESH. Invoked as help / -h / ?, it explains itself and stops - the generated HELP block (name, purpose, invocation, modes, off-ramps), taking no action. With no mode it does the same, then, in an interactive session only, offers the mode choice via AskUserQuestion, prompting for any argument-hint target the chosen mode shows.
Mode EDUCATE
→ Read references/mode-educate.md
Mode AUDIT
→ Read references/mode-audit.md
Mode CONFORM
→ Read references/mode-conform.md
Mode REFRESH
→ Read references/mode-refresh.md
Notes
- Method, not content - this skill never prescribes how an interface looks. A repository's guide, tokens and decisions do that; the skill says where they live and how they stay true.
- Design work - when a request changes what readers see, follow the stages in Design work, from brief to rule: review on the annotated board, then brief, options and an owner's decision come before the build, and consolidation into the guide, Specifications, Decision Records and checks comes after it.
- Projections - a design tool outside the repository, such as a design-system artifact or a canvas, is refreshed from the token source and the guide and is never edited as the source; the annotated board is refreshed from the running interface.
- The
ki host owns findings, dry-run publication, reporting, and post-conform verification; judgment aspects are counted as unevaluated rather than emitted as synthetic mechanical findings.
1---2name: ki-design-system3ki-kind: governance4ki-applicability: declaration-only5ki-guild: design6ki-depends-on: []7ki-shared-dependencies: [ki-skills:rubric]8contributes: ['.ki.toml']9description: >10 Create, audit or refresh how a repository keeps its user-interface design: the token source, the design guide,11 the component library sorted by atomic design, shells and their state, design Specifications and Decision Records,12 the checks, the annotated board, and design work from brief to rule, drawn as information architecture, wireframes13 and mock-ups. Use for visual design method; use `ki-design` for design of any kind, `ki-design-inspiration` for14 visual references, and `ki-repo-packages` for packaging a web component library.15argument-hint: 'audit [dir] | conform [dir] | help | educate [dir] | refresh'16metadata:17 source: https://skillmd.com/skills/knowledgeislands/ki-design-system18---1920# Knowledge Islands Design System standard2122You are applying the **Knowledge Islands Design System standard** - one way to keep the knowledge behind a user interface: values in the token source, the practical how in a design guide, stable behaviour in Specifications, the why in Decision Records, and checks that keep them true. Read [the Design System standard](references/standards-design-system.md) before establishing, auditing or changing a design system; [the rubric](references/rubric.md) publishes its checkable criteria, [the annotated board](references/standards-annotated-board.md) gives the method for the interface's standing review board, [the design levels](references/standards-design-levels.md) set how a round of design is drawn, [exemplars](references/exemplars.md) point at a conforming repository, and [sources](references/sources.md) records its provenance.2324## What this skill owns25261. **The placement model** - which home holds each kind of design knowledge: values, how, what, why, when and proof.272. **The component library** - every component library sorted by atomic design into tokens, atoms, molecules, organisms, templates and pages, with one components document giving each component its signature, what it owns and does not own, and its hand-offs; and the shells, designed from the outside in, each owning its state.283. **The design work method** - review, brief, options, decision, build, consolidate and retire, and what each stage leaves behind, with options drawn at three levels: information architecture, wireframe and mock-up.294. **The annotated board** - the standing projection of the built interface, with numbered pages and coded regions the owner quotes, and [`scripts/annotate-board.ts`](scripts/annotate-board.ts), which prints the in-page region collector and builds the coded overlays and their local previews from a site's board plan and screenshots.305. **The floor** - four requirements every adopting design system meets: one home for values, readable contrast, meaning never by colour alone, and keyboard parity.316. **The mechanical checker** - `ki repo audit --skill ki-design-system` checks the `.ki.toml` declaration, that the token sources, design guide and design checks exist, that the guide names its token sources, and that the guide repeats no literal colour value.3233A repository's own design guide, tokens and decisions stay with that repository. The formats of guides, Specifications, Decision Records and work records stay with `ki-guides`, `ki-specs`, `ki-decision-records` and `ki-work-roadmap`; token build mechanics for content sites stay with `ki-repo-website-content`.3435## Operating modes3637Carries the universal **AUDIT · CONFORM · EDUCATE · REFRESH**. Invoked as `help` / `-h` / `?`, it explains itself and stops - the generated HELP block (name, purpose, invocation, modes, off-ramps), taking no action. With no mode it does the same, then, in an interactive session only, offers the mode choice via `AskUserQuestion`, prompting for any `argument-hint` target the chosen mode shows.3839### Mode EDUCATE4041→ Read [references/mode-educate.md](references/mode-educate.md)4243### Mode AUDIT4445→ Read [references/mode-audit.md](references/mode-audit.md)4647### Mode CONFORM4849→ Read [references/mode-conform.md](references/mode-conform.md)5051### Mode REFRESH5253→ Read [references/mode-refresh.md](references/mode-refresh.md)5455## Notes5657- **Method, not content** - this skill never prescribes how an interface looks. A repository's guide, tokens and decisions do that; the skill says where they live and how they stay true.58- **Design work** - when a request changes what readers see, follow the stages in [Design work, from brief to rule](references/standards-design-system.md#design-work-from-brief-to-rule): review on the annotated board, then brief, options and an owner's decision come before the build, and consolidation into the guide, Specifications, Decision Records and checks comes after it.59- **Projections** - a design tool outside the repository, such as a design-system artifact or a canvas, is refreshed from the token source and the guide and is never edited as the source; the annotated board is refreshed from the running interface.60- The `ki` host owns findings, dry-run publication, reporting, and post-conform verification; judgment aspects are counted as unevaluated rather than emitted as synthetic mechanical findings.