Design system

Foundations

Active default design-system source and review contracts for building JudgmentKit interfaces: tokens, typography, icons, components, patterns, provenance, and accessibility.

Token roles
9

Semantic foundation roles.

Type roles
5

System font stacks.

Icons
1737

lucide-static@1.21.0

Foundation assets

This route is the active design-system source for implementation_contract.design_system_source.mode: "judgmentkit_default". A complete design_system_adapter can switch the contract to external_design_system; missing authorities do not fall back to JudgmentKit defaults.

  • 9 roles

    Tokens

    Semantic roles for surfaces, text, borders, focus, statuses, decisions, risk, disabled states, and receipts.

    Open Tokens

  • 5 roles

    Typography

    System font stacks for body, heading, label, numeric, and diagnostic text.

    Open Typography

  • 1737 icons

    Icons

    A committed Lucide catalog for selecting one consistent icon family.

    Open Icons

  • 17 contracts + specimens

    Components

    Core component contracts for actions, fields, choices, dialogs, tables, panels, cards, and status.

    Open Components

  • 8 patterns + specimens

    Patterns

    Surface contracts for marketing, workbench, review, form, dashboard, report, setup, and conversation work.

    Open Patterns

  • WCAG 2.2 AA

    Accessibility

    Baseline checks for contrast, semantics, keyboard operation, focus, states, motion, and responsive behavior.

    Open Accessibility

How to review

  1. Confirm the interface supports the right task and workflow.
  2. Use foundations to review hierarchy, meaning, consistency, and source constraints.
  3. Check accessibility evidence when color, type, or icons communicate meaning.
  4. Reference stable asset names when implementation or review feedback needs precision.

Principles

  • Start with the work the interface supports; foundations refine that work after the structure is sound.
  • Use visible labels, semantic HTML, and accessibility evidence when color, type, or icons carry meaning.
  • Use component and pattern contracts to review behavior before choosing renderer components.
  • Use complete source details for review, but keep source mechanics out of the primary browsing path.

Examples

  • Review a generated interface

    Use
    Start with the task and workflow, then use foundations to check consistency, hierarchy, and meaning.
    Watch for
    Do not use visual polish as proof that the interface supports the right work.