Skip to content

docs: require catalogue and token regeneration after UI kit changes #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
devKojo merged 1 commit into from
Nov 7, 2026
+5 −1
Merged

docs: require catalogue and token regeneration after UI kit changes #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,11 @@ Active decisions and practices are in `docs/frontend/README.md` (ADR-F001 to ADR
- Reusable UI lives in `packages/ui` (`@imp/ui`), never in `apps/web`. Features use `Ui*`
components, not raw `<button>`/`<input>`.
- Semantic tokens only (`var(--ui-*)`), logical CSS properties, no hard-coded colours/sizes,
no `v-html`. Run `npm run check -w @imp/ui` and `npm test -w @imp/ui` before opening a PR.
no `v-html`. The UI kit checks run in CI.
- Generated files: after changing a `@imp/ui` component's props, slots or events, run
`npm run catalogue:build -w @imp/ui` and commit the regenerated `component-catalogue.md` and
`composition.generated.ts`; after editing `tokens.json`, run `npm run tokens:build -w @imp/ui`.
CI fails with "stale" otherwise.
- Strings come from the catalogue (`i18n/en.ts`) or props; every state in spec section 11 uses
`UiSystemState`; status uses `UiStatusChip` vocabularies.
- No module-level mutable state in SSR code; no storing participant form state in browser storage.
Loading