back to gallery
design language·tidal-quarry-dispatch

Tidal Quarry Dispatch

A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.

Download DESIGN.md

Portable DESIGN.md source of truth for most agents and apps.

the spec

specification

philosophy
summary
Tidal Quarry Dispatch is a coastal operations language for scheduling stone-yard salvage crews around tide windows, weighbridge capacity, and weather holds. It treats the interface like a damp quarry dispatch board: measured slabs, survey marks, load tickets, and tide cuts create hierarchy without generic SaaS chrome.
values
operational legibility under pressurematerial restraint from stone, paper, and brineone dominant dispatch artifact instead of module inventorymeasured asymmetry that keeps priority obvious
anti-values
×generic analytics dashboards×soft floating card stacks×decorative nautical illustrations×status colors masquerading as identity
tokens
borders4 items
accent width
4px
character
dark wet-edge outlines plus short seaweed gate bars separate active tide windows
default width
1px
style
solid with occasional double score line
colors12 items
accent
#B9894B
background
#EEE7D7
border
#3D4037
error
#8E3E32
info
#4E6570
muted
#6E6A5D
primary
#31594A
secondary
#77684E
success
#31594A
surface
#F8F1E1
text
#24251F
warning
#A66D2C
motion3 items
duration
180ms
easing
cubic-bezier(.2,.7,.2,1)
philosophy
interactions slide along the tide-ruler axis or notch inward; never fade as the only state change
radii5 items
full
9999px
lg
4px
md
2px
none
0
sm
0
shadows3 items
lg
inset 0 0 0 1px rgba(61,64,55,0.95), 10px 10px 0 rgba(49,89,74,0.14)
md
inset 0 0 0 1px rgba(61,64,55,0.9), 6px 6px 0 rgba(119,104,78,0.16)
sm
inset 0 -1px 0 rgba(36,37,31,0.18)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64, 96
surfaces3 items
bg pattern
low-contrast quarry grid with tide ticks every 36px on the dispatch axis
card style
hard-edged slabs with internal score lines and small ticket overlays for selected records
treatment
matte limestone paper with sparse speckle and square slab joints
typography8 items
base size
16px
body font
Source Serif 4
google fonts url
https://fonts.googleapis.com/css2?family=Azeret+Mono:wght@400;600;700&family=Bricolage+Grotesque:wght@500;700;800&family=Source+Serif+4:opsz,wght@8..60,400;8..60,600&display=swap
heading font
Bricolage Grotesque
letter spacing
-0.02em
line height
1.48
mono font
Azeret Mono
scale ratio
1.28
rules
composition
One dominant dispatch board owns the screen: a tide-ruler axis on the left locks time, while the main slab grid breaks once for an oversized active berth ticket that interrupts the rows.
density

Moderately dense operations data with compact rows, tight code clusters, and large intentional gaps around tide changes and hold decisions.

hierarchy
Display headings use compressed geometric weight, narrative instructions use serif text, and operational codes use mono stamps; priority is created by position on the tide ruler before color.
signature patterns
Tide-ruler axis appears in navigation, tables, and forms as alternating tick bands that controls alignment and reveals temporal priority.Quarry-score slabs use square containers, inset score lines, and offset bottom-right block shadows that read as stone cuts rather than floating cards.Pinned ticket overlays mark selected or editable content with off-white strips, tiny staple squares, and mono load codes instead of modal-heavy workflows.Seaweed gate bars are short 4px structural accents on active controls, focused fields, and tide-window rows, never generic one-sided borders on rounded cards.
layout
breakpoints

mobile 375px, tablet 768px, desktop 1200px and above

grid
Desktop uses a 72px tide axis, 240px dispatch rail, and flexible slab board; tablet collapses the rail above the board; mobile turns tide ticks into section dividers.
whitespace

Use 8px inside code clusters, 24px between related slab groups, and 96px around tide-window breaks so the largest gap is at least twelve times the tightest gap.

guidance
do
  • Anchor every screen to a visible tide or measurement axis.
  • Use square slabs, score lines, and ticket overlays to make product hierarchy structural.
  • Style every input, select, checkbox, slider, and table state with gate bars or notches.
  • Keep accent use limited to seaweed gates and amber caution stamps.
avoid
  • Do not create generic card rows with soft radii or default drop shadows.
  • Do not use nautical icons, waves, gradients, or decorative charts as filler.
  • Do not let red, green, and amber badges become the main visual identity.
  • Do not center long copy or create equal three-card feature rows.
katagami spec
# Tidal Quarry Dispatch

## Philosophy

Tidal Quarry Dispatch is a coastal operations language for scheduling stone-yard salvage crews around tide windows, weighbridge capacity, and weather holds. It treats the interface like a damp quarry dispatch board: measured slabs, survey marks, load tickets, and tide cuts create hierarchy without generic SaaS chrome.

### Values

- operational legibility under pressure
- material restraint from stone, paper, and brine
- one dominant dispatch artifact instead of module inventory
- measured asymmetry that keeps priority obvious

### Anti-Values

- generic analytics dashboards
- soft floating card stacks
- decorative nautical illustrations
- status colors masquerading as identity

### Visual Character

- Use a dominant left tide-ruler column with alternating 12px and 36px horizontal tick bands that aligns every route, hold, and crew row.
- Build surfaces as square limestone slabs with 0px container radius, 1px dark wet-edge borders, and inset 4px quarry-score lines instead of shadows.
- Create hierarchy with torn-ticket overlays: narrow off-white strips rotated no more than one degree and pinned across selected records.
- Reserve seaweed green for structural gates and active tide windows while all semantic statuses use small stamped labels inside neutral stone cells.

## Tokens

### Borders

- **Accent Width**: 4px
- **Character**: dark wet-edge outlines plus short seaweed gate bars separate active tide windows
- **Default Width**: 1px
- **Style**: solid with occasional double score line

### Colors

| Name | Value |
|------|-------|
| accent | `#B9894B` |
| background | `#EEE7D7` |
| border | `#3D4037` |
| error | `#8E3E32` |
| info | `#4E6570` |
| muted | `#6E6A5D` |
| primary | `#31594A` |
| secondary | `#77684E` |
| success | `#31594A` |
| surface | `#F8F1E1` |
| text | `#24251F` |
| warning | `#A66D2C` |

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(.2,.7,.2,1)
- **Philosophy**: interactions slide along the tide-ruler axis or notch inward; never fade as the only state change

### Radii

- **Full**: 9999px
- **Lg**: 4px
- **Md**: 2px
- **None**: 0
- **Sm**: 0

### Shadows

- **Lg**: inset 0 0 0 1px rgba(61,64,55,0.95), 10px 10px 0 rgba(49,89,74,0.14)
- **Md**: inset 0 0 0 1px rgba(61,64,55,0.9), 6px 6px 0 rgba(119,104,78,0.16)
- **Sm**: inset 0 -1px 0 rgba(36,37,31,0.18)

### Spacing

- **Base**: 8px
- **Scale**: [4,8,12,16,24,32,48,64,96]

### Surfaces

- **Bg Pattern**: low-contrast quarry grid with tide ticks every 36px on the dispatch axis
- **Card Style**: hard-edged slabs with internal score lines and small ticket overlays for selected records
- **Treatment**: matte limestone paper with sparse speckle and square slab joints

### Typography

- **Base Size**: 16px
- **Body Font**: Source Serif 4
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Azeret+Mono:wght@400;600;700&family=Bricolage+Grotesque:wght@500;700;800&family=Source+Serif+4:opsz,wght@8..60,400;8..60,600&display=swap
- **Heading Font**: Bricolage Grotesque
- **Letter Spacing**: -0.02em
- **Line Height**: 1.48
- **Mono Font**: Azeret Mono
- **Scale Ratio**: 1.28

## Rules

### Composition

One dominant dispatch board owns the screen: a tide-ruler axis on the left locks time, while the main slab grid breaks once for an oversized active berth ticket that interrupts the rows.

### Density

Moderately dense operations data with compact rows, tight code clusters, and large intentional gaps around tide changes and hold decisions.

### Hierarchy

Display headings use compressed geometric weight, narrative instructions use serif text, and operational codes use mono stamps; priority is created by position on the tide ruler before color.

### Signature Patterns

- Tide-ruler axis appears in navigation, tables, and forms as alternating tick bands that controls alignment and reveals temporal priority.
- Quarry-score slabs use square containers, inset score lines, and offset bottom-right block shadows that read as stone cuts rather than floating cards.
- Pinned ticket overlays mark selected or editable content with off-white strips, tiny staple squares, and mono load codes instead of modal-heavy workflows.
- Seaweed gate bars are short 4px structural accents on active controls, focused fields, and tide-window rows, never generic one-sided borders on rounded cards.

## Layout

### Breakpoints

mobile 375px, tablet 768px, desktop 1200px and above

### Grid

Desktop uses a 72px tide axis, 240px dispatch rail, and flexible slab board; tablet collapses the rail above the board; mobile turns tide ticks into section dividers.

### Whitespace

Use 8px inside code clusters, 24px between related slab groups, and 96px around tide-window breaks so the largest gap is at least twelve times the tightest gap.

## Guidance

### Do

- Anchor every screen to a visible tide or measurement axis.
- Use square slabs, score lines, and ticket overlays to make product hierarchy structural.
- Style every input, select, checkbox, slider, and table state with gate bars or notches.
- Keep accent use limited to seaweed gates and amber caution stamps.

### Don't

- Do not create generic card rows with soft radii or default drop shadows.
- Do not use nautical icons, waves, gradients, or decorative charts as filler.
- Do not let red, green, and amber badges become the main visual identity.
- Do not center long copy or create equal three-card feature rows.

### Accessibility

Maintain WCAG AA contrast with dark slate text on limestone surfaces and near-white text on green gates; focus states must add both a 4px gate bar and outline change.
DESIGN.md
---
version: "alpha"
name: "Tidal Quarry Dispatch"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#B9894B"
  background: "#EEE7D7"
  border: "#3D4037"
  error: "#8E3E32"
  info: "#4E6570"
  muted: "#6E6A5D"
  primary: "#31594A"
  secondary: "#77684E"
  success: "#31594A"
  surface: "#F8F1E1"
  text: "#24251F"
  warning: "#A66D2C"
typography:
  headline-lg:
    fontFamily: "Bricolage Grotesque"
    fontSize: "2.097rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Bricolage Grotesque"
    fontSize: "1.638rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "Source Serif 4"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.48
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "Azeret Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "4px"
  md: "2px"
  none: "0px"
  sm: "0px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
  step-8: "96px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "#ffffff"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  card-surface:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  input-default:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    height: "44px"
---

# Tidal Quarry Dispatch

## Overview

Tidal Quarry Dispatch is a coastal operations language for scheduling stone-yard salvage crews around tide windows, weighbridge capacity, and weather holds. It treats the interface like a damp quarry dispatch board: measured slabs, survey marks, load tickets, and tide cuts create hierarchy without generic SaaS chrome.

### Values

- operational legibility under pressure
- material restraint from stone, paper, and brine
- one dominant dispatch artifact instead of module inventory
- measured asymmetry that keeps priority obvious

### Anti-Values

- generic analytics dashboards
- soft floating card stacks
- decorative nautical illustrations
- status colors masquerading as identity

### Visual Character

- Use a dominant left tide-ruler column with alternating 12px and 36px horizontal tick bands that aligns every route, hold, and crew row.
- Build surfaces as square limestone slabs with 0px container radius, 1px dark wet-edge borders, and inset 4px quarry-score lines instead of shadows.
- Create hierarchy with torn-ticket overlays: narrow off-white strips rotated no more than one degree and pinned across selected records.
- Reserve seaweed green for structural gates and active tide windows while all semantic statuses use small stamped labels inside neutral stone cells.

## Colors

Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.

| Token | Value |
|-------|-------|
| accent | `#B9894B` |
| background | `#EEE7D7` |
| border | `#3D4037` |
| error | `#8E3E32` |
| info | `#4E6570` |
| muted | `#6E6A5D` |
| primary | `#31594A` |
| secondary | `#77684E` |
| success | `#31594A` |
| surface | `#F8F1E1` |
| text | `#24251F` |
| warning | `#A66D2C` |

## Typography

- **Headline-Lg**: Bricolage Grotesque, 2.097rem, weight 700, line-height 1.1.
- **Headline-Md**: Bricolage Grotesque, 1.638rem, weight 600, line-height 1.15.
- **Body-Md**: Source Serif 4, 16px, weight 400, line-height 1.48.
- **Label-Md**: Azeret Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
- **Step-8**: `96px`

### Breakpoints

mobile 375px, tablet 768px, desktop 1200px and above

### Grid

Desktop uses a 72px tide axis, 240px dispatch rail, and flexible slab board; tablet collapses the rail above the board; mobile turns tide ticks into section dividers.

### Whitespace

Use 8px inside code clusters, 24px between related slab groups, and 96px around tide-window breaks so the largest gap is at least twelve times the tightest gap.

## Elevation & Depth

### Shadows

- **Lg**: inset 0 0 0 1px rgba(61,64,55,0.95), 10px 10px 0 rgba(49,89,74,0.14)
- **Md**: inset 0 0 0 1px rgba(61,64,55,0.9), 6px 6px 0 rgba(119,104,78,0.16)
- **Sm**: inset 0 -1px 0 rgba(36,37,31,0.18)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `4px`
- **Md**: `2px`
- **None**: `0px`
- **Sm**: `0px`

### Surfaces

- **Bg Pattern**: low-contrast quarry grid with tide ticks every 36px on the dispatch axis
- **Card Style**: hard-edged slabs with internal score lines and small ticket overlays for selected records
- **Treatment**: matte limestone paper with sparse speckle and square slab joints

### Borders

- **Accent Width**: 4px
- **Character**: dark wet-edge outlines plus short seaweed gate bars separate active tide windows
- **Default Width**: 1px
- **Style**: solid with occasional double score line

## Components

### Composition

One dominant dispatch board owns the screen: a tide-ruler axis on the left locks time, while the main slab grid breaks once for an oversized active berth ticket that interrupts the rows.

### Density

Moderately dense operations data with compact rows, tight code clusters, and large intentional gaps around tide changes and hold decisions.

### Hierarchy

Display headings use compressed geometric weight, narrative instructions use serif text, and operational codes use mono stamps; priority is created by position on the tide ruler before color.

### Signature Patterns

- Tide-ruler axis appears in navigation, tables, and forms as alternating tick bands that controls alignment and reveals temporal priority.
- Quarry-score slabs use square containers, inset score lines, and offset bottom-right block shadows that read as stone cuts rather than floating cards.
- Pinned ticket overlays mark selected or editable content with off-white strips, tiny staple squares, and mono load codes instead of modal-heavy workflows.
- Seaweed gate bars are short 4px structural accents on active controls, focused fields, and tide-window rows, never generic one-sided borders on rounded cards.

## shadcn/ui Usage

When the target app uses shadcn/ui, copy DESIGN.md with shadcn instead of the plain DESIGN.md. It contains the same Katagami design-language source plus the shadcn/ui primitives, imports, theme variables, component recipes, and preview-shot guidance.

DESIGN.md with shadcn: `/language/en-019edc67-f19e-7110-a1ad-6c5a49e22810/DESIGN.with-shadcn.md`.

The shadcn page also exposes optional machine-readable files for automation, but the human-facing handoff is DESIGN.md with shadcn.

Install recommended primitives with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.

Use these primitives in shadcn apps:
- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Implementation rule for agents: import shadcn primitives from `@/components/ui/*`, apply the generated CSS variables first, then compose the language-specific recipes from the companion MD. Katagami remains the source of truth; shadcn names are the implementation surface.

## Do's and Don'ts

- Do Anchor every screen to a visible tide or measurement axis.
- Do Use square slabs, score lines, and ticket overlays to make product hierarchy structural.
- Do Style every input, select, checkbox, slider, and table state with gate bars or notches.
- Do Keep accent use limited to seaweed gates and amber caution stamps.
- Don't Do not create generic card rows with soft radii or default drop shadows.
- Don't Do not use nautical icons, waves, gradients, or decorative charts as filler.
- Don't Do not let red, green, and amber badges become the main visual identity.
- Don't Do not center long copy or create equal three-card feature rows.

### Accessibility

Maintain WCAG AA contrast with dark slate text on limestone surfaces and near-white text on green gates; focus states must add both a 4px gate bar and outline change.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "tidal-quarry-dispatch",
  "type": "registry:theme",
  "title": "Tidal Quarry Dispatch shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#EEE7D7",
      "foreground": "#24251F",
      "card": "#F8F1E1",
      "card-foreground": "#24251F",
      "popover": "#F8F1E1",
      "popover-foreground": "#24251F",
      "primary": "#31594A",
      "primary-foreground": "#ffffff",
      "secondary": "#77684E",
      "secondary-foreground": "#ffffff",
      "muted": "#6E6A5D",
      "muted-foreground": "#24251F",
      "accent": "#B9894B",
      "accent-foreground": "#ffffff",
      "destructive": "#8E3E32",
      "border": "#3D4037",
      "input": "#3D4037",
      "ring": "#B9894B",
      "chart-1": "#31594A",
      "chart-2": "#77684E",
      "chart-3": "#B9894B",
      "chart-4": "#31594A",
      "chart-5": "#A66D2C",
      "sidebar": "#F8F1E1",
      "sidebar-foreground": "#24251F",
      "sidebar-primary": "#31594A",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#4E6570",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#3D4037",
      "sidebar-ring": "#B9894B",
      "radius": "2px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#31594A",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#B9894B",
      "accent-foreground": "#ffffff",
      "destructive": "#8E3E32",
      "border": "#303642",
      "input": "#303642",
      "ring": "#B9894B",
      "chart-1": "#31594A",
      "chart-2": "#77684E",
      "chart-3": "#B9894B",
      "chart-4": "#31594A",
      "chart-5": "#A66D2C",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#31594A",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#B9894B",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#B9894B",
      "radius": "2px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edc67-f19e-7110-a1ad-6c5a49e22810",
    "slug": "tidal-quarry-dispatch",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
```
in the wild

embodiments

Design Language Preview

Tidal Quarry Dispatch

Color Palette

primary
secondary
accent
background
surface
text
muted
border
error
success
warning
info

Typography

h1

Heading One

h2

Heading Two

h3

Heading Three

h4

Heading Four

body

Body text demonstrates the reading experience. Good typography is invisible — it lets the content speak without drawing attention to the letterforms themselves.

caption

Caption text for supplementary information and metadata.

code
const theme = applyTokens(designLanguage);
render(<App theme={theme} />);

Buttons

Form Controls

Navigation

tabs
Overview content area with contextual information about the design language.
segmented control
dropdown menu

Feedback & Status

badges
NewDefaultActivePendingErrorOutline
alerts
Info: A new version is available.
Success: Changes saved successfully.
Warning: Storage is almost full.
Error: Failed to process request.
progress
66% complete
tooltip
avatar
AKJDML

Containers & Overlays

card

Card Title

Cards group related content and actions. This example shows a basic content card with a title and description.

accordion

Design tokens are the atomic values of a design system — colors, spacing, typography, and other values stored as key-value pairs.

dialog
separator

Data Display

table
NameStatusCategoryScore
Neo BrutalismPublishedMaximalist94
Aero GlassDraftSpatial87
Signal UIReviewEnterprise91
stat cards
Languages
42
+12%
Elements
3,150
+8%
Usage
18.4k
+23%
DESIGN.md

at a glance

Palette

Typography

headline-lgBricolage Grotesque · 34px · 700

The quick brown fox jumps

headline-mdBricolage Grotesque · 26px · 600

The quick brown fox jumps

body-mdSource Serif 4 · 16px · 400

The quick brown fox jumps

label-mdAzeret Mono · 12px · 600

The quick brown fox jumps

Components

New
Card title

Components rendered with this language’s tokens — colors, type, and rounded corners as specified.

Spacing

  • base8px
  • xs4px
  • sm8px
  • md12px
  • lg16px
  • xl24px
  • 2xl32px
  • 3xl48px
  • 4xl64px
  • step-896px

Shape

full9999px
lg4px
md2px
none0px
sm0px
shadcn/ui

implementation kit

needs agent-authored kitcompatibility fallback
shadcn compatibility only
The generated theme variables are available, but the polished shadcn component recipes and shots have not been authored by the Katagami agent yet.
fallbackprimitives render
Compatibility proof
Local shadcn-style primitives accept the generated theme variables.
primaryaccentsurfacemutedwarningerror
table rhythm
buttonok
cardok
inputok
recommendedcompatibility fallback

DESIGN.md with shadcn

Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.

advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #EEE7D7;
  --foreground: #24251F;
  --card: #F8F1E1;
  --card-foreground: #24251F;
  --popover: #F8F1E1;
  --popover-foreground: #24251F;
  --primary: #31594A;
  --primary-foreground: #ffffff;
  --secondary: #77684E;
  --secondary-foreground: #ffffff;
  --muted: #6E6A5D;
  --muted-foreground: #24251F;
  --accent: #B9894B;
  --accent-foreground: #ffffff;
  --destructive: #8E3E32;
  --border: #3D4037;
  --input: #3D4037;
  --ring: #B9894B;
  --chart-1: #31594A;
  --chart-2: #77684E;
  --chart-3: #B9894B;
  --chart-4: #31594A;
  --chart-5: #A66D2C;
  --sidebar: #F8F1E1;
  --sidebar-foreground: #24251F;
  --sidebar-primary: #31594A;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #4E6570;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #3D4037;
  --sidebar-ring: #B9894B;
  --radius: 2px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #31594A;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #B9894B;
  --accent-foreground: #ffffff;
  --destructive: #8E3E32;
  --border: #303642;
  --input: #303642;
  --ring: #B9894B;
  --chart-1: #31594A;
  --chart-2: #77684E;
  --chart-3: #B9894B;
  --chart-4: #31594A;
  --chart-5: #A66D2C;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #31594A;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #B9894B;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #B9894B;
  --radius: 2px;
}
tsx starter
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
  Card,
  CardContent,
  CardDescription,
  CardFooter,
  CardHeader,
  CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";

export function TidalQuarryDispatchShadcnKit() {
  return (
    <section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
      <div className="flex items-start justify-between gap-4">
        <div>
          <Badge variant="outline">shadcn/ui</Badge>
          <h2 className="mt-3 text-2xl font-semibold tracking-tight">Tidal Quarry Dispatch</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

      <Tabs defaultValue="components">
        <TabsList>
          <TabsTrigger value="components">Components</TabsTrigger>
          <TabsTrigger value="states">States</TabsTrigger>
          <TabsTrigger value="export">Export</TabsTrigger>
        </TabsList>
      </Tabs>

      <Card>
        <CardHeader>
          <CardTitle>Component recipe</CardTitle>
          <CardDescription>
            Replace this starter content with the agent-authored product scene
            from components.md and preview-shots.json.
          </CardDescription>
        </CardHeader>
        <CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
          <Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
          <Button variant="secondary">Preview state</Button>
        </CardContent>
        <CardFooter className="justify-between">
          <Badge>Ready</Badge>
          <Button variant="outline">Copy recipe</Button>
        </CardFooter>
      </Card>
    </section>
  );
}
theme JSONcompatibility fallback
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "tidal-quarry-dispatch",
  "type": "registry:theme",
  "title": "Tidal Quarry Dispatch shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#EEE7D7",
      "foreground": "#24251F",
      "card": "#F8F1E1",
      "card-foreground": "#24251F",
      "popover": "#F8F1E1",
      "popover-foreground": "#24251F",
      "primary": "#31594A",
      "primary-foreground": "#ffffff",
      "secondary": "#77684E",
      "secondary-foreground": "#ffffff",
      "muted": "#6E6A5D",
      "muted-foreground": "#24251F",
      "accent": "#B9894B",
      "accent-foreground": "#ffffff",
      "destructive": "#8E3E32",
      "border": "#3D4037",
      "input": "#3D4037",
      "ring": "#B9894B",
      "chart-1": "#31594A",
      "chart-2": "#77684E",
      "chart-3": "#B9894B",
      "chart-4": "#31594A",
      "chart-5": "#A66D2C",
      "sidebar": "#F8F1E1",
      "sidebar-foreground": "#24251F",
      "sidebar-primary": "#31594A",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#4E6570",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#3D4037",
      "sidebar-ring": "#B9894B",
      "radius": "2px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#31594A",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#B9894B",
      "accent-foreground": "#ffffff",
      "destructive": "#8E3E32",
      "border": "#303642",
      "input": "#303642",
      "ring": "#B9894B",
      "chart-1": "#31594A",
      "chart-2": "#77684E",
      "chart-3": "#B9894B",
      "chart-4": "#31594A",
      "chart-5": "#A66D2C",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#31594A",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#B9894B",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#B9894B",
      "radius": "2px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019edc67-f19e-7110-a1ad-6c5a49e22810",
    "slug": "tidal-quarry-dispatch",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "base_size",
        "body_font",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
component recipescompatibility fallback
# Tidal Quarry Dispatch shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019edc67-f19e-7110-a1ad-6c5a49e22810`
Slug: `tidal-quarry-dispatch`

## Intent

Tidal Quarry Dispatch is a coastal operations language for scheduling stone-yard salvage crews around tide windows, weighbridge capacity, and weather holds. It treats the interface like a damp quarry dispatch board: measured slabs, survey marks, load tickets, and tide cuts create hierarchy without generic SaaS chrome.

## Required primitives

- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Install with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.

## Token cues

Colors:

{
  "accent": "#B9894B",
  "background": "#EEE7D7",
  "border": "#3D4037",
  "error": "#8E3E32",
  "info": "#4E6570",
  "muted": "#6E6A5D",
  "primary": "#31594A",
  "secondary": "#77684E",
  "success": "#31594A",
  "surface": "#F8F1E1",
  "text": "#24251F",
  "warning": "#A66D2C"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Source Serif 4",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Azeret+Mono:wght@400;600;700&family=Bricolage+Grotesque:wght@500;700;800&family=Source+Serif+4:opsz,wght@8..60,400;8..60,600&display=swap",
  "heading_font": "Bricolage Grotesque",
  "letter_spacing": "-0.02em",
  "line_height": 1.48,
  "mono_font": "Azeret Mono",
  "scale_ratio": 1.28
}

## Visual character to preserve

- Use a dominant left tide-ruler column with alternating 12px and 36px horizontal tick bands that aligns every route, hold, and crew row.
- Build surfaces as square limestone slabs with 0px container radius, 1px dark wet-edge borders, and inset 4px quarry-score lines instead of shadows.
- Create hierarchy with torn-ticket overlays: narrow off-white strips rotated no more than one degree and pinned across selected records.
- Reserve seaweed green for structural gates and active tide windows while all semantic statuses use small stamped labels inside neutral stone cells.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "stickerBadges": true,
  "motion": "lift-rotate",
  "density": "balanced",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.

### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.

### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.

### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.

### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.

## Preview shots

- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/tidal-quarry-dispatch/registry-theme.json` variables, then use these recipes for composition and state design.
- Preserve Katagami token names as source metadata; shadcn semantic names are only the export surface.
- Do: Anchor every screen to a visible tide or measurement axis.; Use square slabs, score lines, and ticket overlays to make product hierarchy structural.; Style every input, select, checkbox, slider, and table state with gate bars or notches.; Keep accent use limited to seaweed gates and amber caution stamps.
- Do not: Do not create generic card rows with soft radii or default drop shadows.; Do not use nautical icons, waves, gradients, or decorative charts as filler.; Do not let red, green, and amber badges become the main visual identity.; Do not center long copy or create equal three-card feature rows.

## Copy-paste component example

This generated starter proves the import shape. Production Katagami agents should replace it with a language-specific product composition.

```tsx
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
  Card,
  CardContent,
  CardDescription,
  CardFooter,
  CardHeader,
  CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";

export function TidalQuarryDispatchShadcnKit() {
  return (
    <section className="grid gap-4 rounded-[var(--radius)] border bg-background p-4 text-foreground">
      <div className="flex items-start justify-between gap-4">
        <div>
          <Badge variant="outline">shadcn/ui</Badge>
          <h2 className="mt-3 text-2xl font-semibold tracking-tight">Tidal Quarry Dispatch</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

      <Tabs defaultValue="components">
        <TabsList>
          <TabsTrigger value="components">Components</TabsTrigger>
          <TabsTrigger value="states">States</TabsTrigger>
          <TabsTrigger value="export">Export</TabsTrigger>
        </TabsList>
      </Tabs>

      <Card>
        <CardHeader>
          <CardTitle>Component recipe</CardTitle>
          <CardDescription>
            Replace this starter content with the agent-authored product scene
            from components.md and preview-shots.json.
          </CardDescription>
        </CardHeader>
        <CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
          <Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
          <Button variant="secondary">Preview state</Button>
        </CardContent>
        <CardFooter className="justify-between">
          <Badge>Ready</Badge>
          <Button variant="outline">Copy recipe</Button>
        </CardFooter>
      </Card>
    </section>
  );
}
```

## Layout notes

{
  "breakpoints": "mobile 375px, tablet 768px, desktop 1200px and above",
  "grid": "Desktop uses a 72px tide axis, 240px dispatch rail, and flexible slab board; tablet collapses the rail above the board; mobile turns tide ticks into section dividers.",
  "whitespace": "Use 8px inside code clusters, 24px between related slab groups, and 96px around tide-window breaks so the largest gap is at least twelve times the tightest gap."
}
preview shotscompatibility fallback
{
  "artifact": "katagami:shadcn-preview-shots",
  "version": "preview-shots-v1",
  "generator": "katagami-ui-compatibility-projection",
  "generatedBy": "katagami-ui-projection",
  "requiresVisualProfile": true,
  "schema": "katagami:shadcn-preview-shots/renderable-v1",
  "renderable": true,
  "language": {
    "id": "en-019edc67-f19e-7110-a1ad-6c5a49e22810",
    "name": "Tidal Quarry Dispatch",
    "slug": "tidal-quarry-dispatch"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "Use a dominant left tide-ruler column with alternating 12px and 36px horizontal tick bands that aligns every route, hold, and crew row.",
    "Build surfaces as square limestone slabs with 0px container radius, 1px dark wet-edge borders, and inset 4px quarry-score lines instead of shadows.",
    "Create hierarchy with torn-ticket overlays: narrow off-white strips rotated no more than one degree and pinned across selected records.",
    "Reserve seaweed green for structural gates and active tide windows while all semantic statuses use small stamped labels inside neutral stone cells."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": true,
    "grain": false,
    "stickerBadges": true,
    "motion": "lift-rotate",
    "density": "balanced",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "Tidal Quarry Dispatch launch room",
        "description": "A product team workspace where navigation, filters, metrics, and dense rows carry the language's visible structure.",
        "primaryAction": "Apply theme",
        "secondaryAction": "Review states",
        "stats": [
          {
            "label": "components",
            "value": "16",
            "tone": "accent"
          },
          {
            "label": "states",
            "value": "ready"
          },
          {
            "label": "density",
            "value": "balanced",
            "tone": "warning"
          }
        ],
        "rows": [
          {
            "label": "Primary flow",
            "value": "mapped",
            "status": "active"
          },
          {
            "label": "Token coverage",
            "value": "semantic",
            "status": "synced"
          },
          {
            "label": "Responsive proof",
            "value": "queued",
            "status": "review"
          }
        ],
        "statuses": [
          "Active",
          "Synced",
          "Draft"
        ]
      }
    },
    {
      "id": "detail-editor",
      "title": "Detail editor",
      "viewport": "tablet",
      "primitives": [
        "button",
        "card",
        "input",
        "textarea",
        "select",
        "checkbox",
        "switch",
        "slider",
        "dialog",
        "sheet"
      ],
      "composition": "A focused editing flow with form fields, validation, confirmation, and a contextual side panel.",
      "mustShow": [
        "focus ring",
        "error or destructive state",
        "dialog or sheet treatment",
        "written guidance content"
      ],
      "avoid": [
        "unstyled browser controls",
        "floating cards inside cards",
        "missing labels"
      ],
      "scene": {
        "eyebrow": "editing flow",
        "headline": "Language recipe editor",
        "description": "A focused form proving labels, validation, toggles, panel rhythm, and action hierarchy.",
        "primaryAction": "Save recipe",
        "secondaryAction": "Open sheet",
        "fields": [
          {
            "label": "Component family",
            "value": "Narrative cards"
          },
          {
            "label": "State treatment",
            "value": "Visible focus + validation"
          },
          {
            "label": "Motion",
            "value": "Small lift, no opacity-only fade"
          }
        ],
        "statuses": [
          "Focus",
          "Invalid",
          "Confirmed"
        ]
      }
    },
    {
      "id": "data-operations",
      "title": "Data operations",
      "viewport": "mobile",
      "primitives": [
        "button",
        "tabs",
        "badge",
        "dropdown-menu",
        "table",
        "tooltip",
        "separator"
      ],
      "composition": "A compact operational view proving row rhythm, stacked actions, menu states, badges, and empty/destructive states.",
      "mustShow": [
        "responsive reflow",
        "dense row styling",
        "menu affordance",
        "status badge system"
      ],
      "avoid": [
        "desktop-only tables",
        "text overflow",
        "default shadcn spacing without Katagami character"
      ],
      "scene": {
        "eyebrow": "operations",
        "headline": "Compact review queue",
        "description": "A narrow viewport scene with rows, menus, tooltips, badges, and destructive affordances.",
        "primaryAction": "Resolve",
        "secondaryAction": "Filter",
        "rows": [
          {
            "label": "Button hierarchy",
            "value": "approved",
            "status": "ok"
          },
          {
            "label": "Table rhythm",
            "value": "needs pass",
            "status": "watch"
          },
          {
            "label": "Empty state",
            "value": "designed",
            "status": "done"
          }
        ],
        "statuses": [
          "Queued",
          "Blocked",
          "Done"
        ]
      }
    }
  ],
  "componentRecipes": [
    {
      "primitive": "button",
      "intent": "Prove action hierarchy, focus, disabled, and destructive states."
    },
    {
      "primitive": "card",
      "intent": "Carry the language surface, border, elevation, and density rules."
    },
    {
      "primitive": "input",
      "intent": "Show labels, focus rings, validation, and spacing rhythm."
    },
    {
      "primitive": "textarea",
      "intent": "Show longer guidance, validation copy, and writing density."
    },
    {
      "primitive": "select",
      "intent": "Show filtering, selection contrast, and menu trigger styling."
    },
    {
      "primitive": "dialog",
      "intent": "Show centered decision states and overlay treatment."
    },
    {
      "primitive": "sheet",
      "intent": "Show contextual side panels and responsive editing."
    },
    {
      "primitive": "tabs",
      "intent": "Show navigational structure and active/inactive contrast."
    },
    {
      "primitive": "badge",
      "intent": "Show compact status vocabulary and semantic colors."
    },
    {
      "primitive": "separator",
      "intent": "Show section rhythm without generic gray dividers."
    },
    {
      "primitive": "checkbox",
      "intent": "Show binary selection with visible focus and checked states."
    },
    {
      "primitive": "switch",
      "intent": "Show settings toggles and on/off contrast."
    },
    {
      "primitive": "slider",
      "intent": "Show numeric adjustment with track/thumb styling."
    },
    {
      "primitive": "tooltip",
      "intent": "Show concise explanation styling above compact controls."
    },
    {
      "primitive": "dropdown-menu",
      "intent": "Show action menus, destructive items, and grouped choices."
    },
    {
      "primitive": "table",
      "intent": "Show dense operational data, separators, row states, and responsive behavior."
    }
  ],
  "qualityRules": {
    "do": [
      "Anchor every screen to a visible tide or measurement axis.",
      "Use square slabs, score lines, and ticket overlays to make product hierarchy structural.",
      "Style every input, select, checkbox, slider, and table state with gate bars or notches.",
      "Keep accent use limited to seaweed gates and amber caution stamps."
    ],
    "dont": [
      "Do not create generic card rows with soft radii or default drop shadows.",
      "Do not use nautical icons, waves, gradients, or decorative charts as filler.",
      "Do not let red, green, and amber badges become the main visual identity.",
      "Do not center long copy or create equal three-card feature rows."
    ]
  }
}