Appearance
Design system e-manažer — pointer
The design system is a living artifact with its own versioning; the repo does not copy it. This document is the pointer every feature links to instead of repeating token values, and the place where the reconciliation dates live. Rules for what a design leaves behind in the repo are in SKILLS/feature-analysis/foundations/design-artifacts.md.
Where it lives
| What | Where | Last checked |
|---|---|---|
| Design system (Claude Design artifact) | 94vFHirA9HbeNVadRkeCY2 — https://claude.ai/artifact/94vFHirA9HbeNVadRkeCY2 | 2026-09-23 |
| Figma source | e-manažer UI — https://www.figma.com/design/FzVyDJ7cvq1lSTIpL7jSwK/e-manažer-UI | 2026-09-23 |
| Token snapshot in the repo | design-system/tokens.json | exported 2026-09-23 |
| Component list in the repo | design-system/components.md | exported 2026-09-23 |
How to use it
- Figma first, system second. Figma carries the layout; the design system carries the tokens and the component rules. Where the two disagree on colour or contrast, the system wins — it fixed several values to reach WCAG AA — and the deviation is written into the feature's own design review so Figma can follow.
- Link, do not copy. A feature document names the components and tokens it uses (
PageHeader variant="detail",brand-600) and links here. Token values are repeated nowhere else in the repo. - Re-export the snapshot when the system changes. The snapshot is what tells a reviewer whether a screen was drawn against today's tokens. Re-export
tokens.jsonandcomponents.md, update the dates above, and say in the feature's design review what moved.
Shared patterns
Patterns that span several features and are drawn the same way everywhere. A feature document links here and says which entry points its screens carry; it does not redraw the pattern.
History
Two different things are called "Historie" in the application; they get different entry points so a reader can tell them apart at a glance. Decided 2026-10-06 across Building Management (object canvas v18), Gauge Management (form v16) and Reading Management (screens v55); the full rule set is in Formulář objektu — zadání, kapitola 5.
| Record history (audit log) | Value history (versioned field) | |
|---|---|---|
| Shows | who changed what and when on the whole record | which value applied from when — the validFrom versions of one field or one group of fields |
| Source | the shared Per-Record History view of the audit log | the entity's own versions (buildingParameter, buildingEnergyProfile, gaugeDistributionRateHistory, gaugeUsageAllocation, …) |
| Entry point | detail header: Button secondary Historie with the clock icon, left of Vrátit změny, shown only while nothing is unsaved; list row: clock icon between Detail and Smazat | field: the Historie addon segment of InputField / Select (text, no icon) plus the hint "Platí od D. M. RRRR" under the field; group of fields: a row with a dashed divider, uppercase group name, "Platí od …" and Button secondary sm Historie |
| Opens | modal Historie záznamu | modal Historie hodnoty: Platí od · value (one column per field for a group) · Změnil · Kdy, newest first, badges Platná and Od budoucna, read-only, link Otevřít historii záznamu |
Rules: the clock icon belongs to record history only; neither entry point is drawn on a creation form (the first version is written by the first save); a value with an unsaved change cannot open its history; saving a versioned change always goes through the Uložit změny dialog — Nová verze od data (default today) or Oprava platné verze — one choice for the whole save, and a new version with the same Platí od as the current one is a correction.
Open points of the system itself
Carried here so features do not each rediscover them:
- Contrast of white text on
brand-500(3.39 : 1) — the system usesbrand-600for primary buttons and active tabs until Figma follows. - The required-field mark is
error-600in the system, a different red in Figma. - Figma has text sizes below the system's scale (11–13.5 px); the system rounds them to 12 / 14.
- The gauge side panel (
SidePanelwith grouped entities) exists in features before it exists in the system — to be generalised as a component.