back to gallery
design language·test-repro-name-2

Test Repro Name 2

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
Minimal Repro is a diagnostic design language for test beds, regression triage, QA dashboards, and incident reproduction flows. It reduces every product moment to the smallest truthful scene: the preconditions, the expected result, the observed result, the delta, and the next reproducible action. It is intentionally sparse, auditable, and direct. The language treats visual design as a test fixture: every border establishes containment, every label clarifies state, and every accent identifies severity or focus. It avoids decorative variety so a viewer can move from symptom to verification without interpretation overhead.
values
Smallest truthful case before broad system narrativeObservable state changes instead of implied statusAuditability through IDs, timestamps, traces, and diffsRestraint over decoration; every visible property must earn its placeFunctional contrast and explicit labels for every critical stateRepeatable spacing and composition so evidence can be comparedFast, reversible actions that never obscure the current state
anti-values
×Decorative gradients, glass, and lifestyle imagery that do not help reproduction×Generic analytics dashboards or component catalogs without a specific failing workflow×Unlabeled color-only status indicators×Soft SaaS chrome, arbitrary radius mixing, and ornamental shadows
tokens
borders4 items
default
1px solid rgba(23,26,31,0.08)
emphasis
1px solid rgba(23,26,31,0.72)
focus
2px solid #2864D8 with 2px offset
severity rail
separate flat 4px strip placed before the card content, never a rounded one-sided border
colors12 items
amber
#A86600
border_strong
rgba(23,26,31,0.72)
border_weak
rgba(23,26,31,0.08)
green
#207A3D
ink
#171A1F
muted_text
#5C6675
paper
#F7F4EE
primary_blue
#2864D8
primary_blue_dark
#174AA9
red
#A7352B
surface
#FFFFFF
well
#ECE7DD
motion3 items
base
180ms cubic-bezier(.2,0,.1,1)
fast
120ms cubic-bezier(.2,0,.1,1)
principle
state confirmation only; no decorative motion, disabled under prefers-reduced-motion
radii4 items
flat
0px
large
24px
pill
9999px
primary
16px
shadows3 items
active case
0 18px 38px rgba(23,26,31,0.08)
focus
0 0 0 2px #2864D8
none
none
spacing8 items
2xl
64px
2xs
2px
3xl
96px
lg
24px
md
16px
sm
8px
xl
40px
xs
4px
surfaces4 items
canvas
warm gridded paper background #F7F4EE
card
white panel with 8% ink border
dark log
#11151A with pale mono trace lines
well
recessed #ECE7DD inset evidence strip
typography8 items
body
letter spacing -0.02em·line height 1.56·size 16px·weight 400
body font
Inter
display
letter spacing -0.04em·line height 1.12·size clamp(36px, 5vw, 64px)·weight 700
google fonts url
https://fonts.googleapis.com/css2?family=IBM+Plex+Sans:wght@500;600;700&family=Inter:wght@400;500;600;700&family=JetBrains+Mono:wght@400;600;700&display=swap
heading
letter spacing -0.03em·line height 1.15·weight 700
heading font
IBM Plex Sans
mono
letter spacing 0.02em·line height 1.45·size 12px·text transform uppercase·weight 700
mono font
JetBrains Mono
rules
composition
Show a specific fictional diagnostic product and a concrete failing workflow, not an abstract dashboard.Use a wide reproduction lane paired with a narrower evidence rail on desktop.Create one dominant failing case module and several smaller supporting modules; never use three equal cards.Include one grid break through an oversized display heading or an inset trace well that interrupts the main rhythm.Maintain visible grouping: tight gaps inside evidence, larger gaps between workflow stages, and the largest gaps around the scene.Keep panels flat; use one subtle shadow only on the currently active reproduction case.
density
Dense where evidence is compared, spacious where the user chooses the next action. Tightest gaps may be 4px while hero and section separation reaches 64px or more, satisfying the 8:1 spacing rhythm test.
hierarchy
Display headline states the exact failing case in one sentence.Primary action uses muted blue fill; secondary actions remain white with ink border.Status chips are small mono labels with text plus dot, never color alone.Evidence values use mono text and recessed wells so data separates from prose.The failing case is visually dominant through scale and content density, not extra decoration.
signature patterns
Separate flat severity rail strip adjacent to a rounded evidence card so the rail never wraps around curved corners.Expected / Observed / Delta comparison cells with dotted dividers and mono inset values make the reproduction path instantly recognizable.Uppercase JetBrains Mono case tags combine fixture IDs, timestamps, and state labels into a compact audit layer.Dark clipped trace log strips contrast with warm paper surfaces and provide a reusable evidence texture.
layout
density

Evidence regions are compact and data-rich, while decision areas breathe. This contrast makes the language feel operational rather than uniformly templated.

grid
Desktop uses a 12-column max-width around 1380px: 8 columns for the reproduction lane and 4 for the evidence rail, with 24px gutters. Cards align to an 8px spacing system but vary between dense 4px internals and 64px scene breaks.
responsive
desktop
1200px+ split diagnostic scene with persistent evidence rail
mobile
375px single timeline with full-width actions and stacked comparison cells
tablet
768px stacked rail below reproduction lane
whitespace

Whitespace is not ornamental; it isolates the one active failing case and prevents secondary metrics from competing with the reproduction path.

guidance
accessibility
WCAG AA contrast is mandatory. Focus uses a 2px blue outline with offset. All controls are semantic HTML elements with labels and helper text. Reduced motion disables transitions. State dots include visible text labels and should have aria-labels in production.
donts
Do not build a generic SaaS analytics, CRM, or project-management dashboard.Do not use one-sided colored borders on rounded elements; use a separate square rail element.Do not mix arbitrary radii such as 3px, 6px, and 10px in final embodiments.Do not rely on color alone for severity or status.Do not use glossy gradients, floating glass, large decorative illustrations, or stock lifestyle imagery.Do not present a component catalog as the embodiment scene.Do not add shadows, accents, or extra colors merely to fill empty space.Do not use banned AI-tell fonts such as Poppins, Montserrat, DM Sans, Space Grotesk, Figtree, Outfit, or Plus Jakarta Sans.
dos
Name the product context and failure case specifically.Reduce each screen to precondition, action, observed result, and verification.Pair every semantic color with a text label, dot, icon, or rail pattern.Use custom form controls, selects, checkboxes, and focus rings; never leave browser defaults.Let negative space carry identity by removing decorative fills and gradients.Expose trace IDs, timestamps, fixture names, and copy or rerun controls.Use the separate severity rail pattern consistently for failed, passing, warning, and queued states.Keep body text at 15-16px with -0.02em tracking for precision.
usage context
Best for QA tooling, regression triage, incident reproduction, automated test review, data-quality investigations, and any workflow where a person must verify a specific state transition.
katagami spec
# Test Repro Name 2

## Philosophy

Minimal Repro is a diagnostic design language for test beds, regression triage, QA dashboards, and incident reproduction flows. It reduces every product moment to the smallest truthful scene: the preconditions, the expected result, the observed result, the delta, and the next reproducible action. It is intentionally sparse, auditable, and direct. The language treats visual design as a test fixture: every border establishes containment, every label clarifies state, and every accent identifies severity or focus. It avoids decorative variety so a viewer can move from symptom to verification without interpretation overhead.

### Values

- Smallest truthful case before broad system narrative
- Observable state changes instead of implied status
- Auditability through IDs, timestamps, traces, and diffs
- Restraint over decoration; every visible property must earn its place
- Functional contrast and explicit labels for every critical state
- Repeatable spacing and composition so evidence can be compared
- Fast, reversible actions that never obscure the current state

### Anti-Values

- Decorative gradients, glass, and lifestyle imagery that do not help reproduction
- Generic analytics dashboards or component catalogs without a specific failing workflow
- Unlabeled color-only status indicators
- Soft SaaS chrome, arbitrary radius mixing, and ornamental shadows

### Visual Character

- Flat warm-paper surfaces with near-black hairline boundaries create the feeling of a precise test fixture rather than a marketing page.
- The signature pattern is a square-edged evidence card that uses a separate severity rail strip, mono case identifier, and Expected / Observed / Delta comparison area.
- Typography separates voices clearly: IBM Plex Sans for compact headings, Inter for readable instructions, and JetBrains Mono for traceable evidence values.
- Accent color is surgical: a muted blue for action and focus, plus semantic severity marks used only in small dots, rails, and status chips.

## Tokens

### Borders

- **Default**: 1px solid rgba(23,26,31,0.08)
- **Emphasis**: 1px solid rgba(23,26,31,0.72)
- **Focus**: 2px solid #2864D8 with 2px offset
- **Severity Rail**: separate flat 4px strip placed before the card content, never a rounded one-sided border

### Colors

| Name | Value |
|------|-------|
| amber | `#A86600` |
| border_strong | `rgba(23,26,31,0.72)` |
| border_weak | `rgba(23,26,31,0.08)` |
| green | `#207A3D` |
| ink | `#171A1F` |
| muted_text | `#5C6675` |
| paper | `#F7F4EE` |
| primary_blue | `#2864D8` |
| primary_blue_dark | `#174AA9` |
| red | `#A7352B` |
| surface | `#FFFFFF` |
| well | `#ECE7DD` |

### Motion

- **Base**: 180ms cubic-bezier(.2,0,.1,1)
- **Fast**: 120ms cubic-bezier(.2,0,.1,1)
- **Principle**: state confirmation only; no decorative motion, disabled under prefers-reduced-motion

### Radii

- **Flat**: 0px
- **Large**: 24px
- **Pill**: 9999px
- **Primary**: 16px

### Shadows

- **Active Case**: 0 18px 38px rgba(23,26,31,0.08)
- **Focus**: 0 0 0 2px #2864D8
- **None**: none

### Spacing

- **2xl**: 64px
- **2xs**: 2px
- **3xl**: 96px
- **Lg**: 24px
- **Md**: 16px
- **Sm**: 8px
- **Xl**: 40px
- **Xs**: 4px

### Surfaces

- **Canvas**: warm gridded paper background #F7F4EE
- **Card**: white panel with 8% ink border
- **Dark Log**: #11151A with pale mono trace lines
- **Well**: recessed #ECE7DD inset evidence strip

### Typography

- **Body**: {"letter_spacing":"-0.02em","line_height":"1.56","size":"16px","weight":400}
- **Body Font**: Inter
- **Display**: {"letter_spacing":"-0.04em","line_height":"1.12","size":"clamp(36px, 5vw, 64px)","weight":700}
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=IBM+Plex+Sans:wght@500;600;700&family=Inter:wght@400;500;600;700&family=JetBrains+Mono:wght@400;600;700&display=swap
- **Heading**: {"letter_spacing":"-0.03em","line_height":"1.15","weight":700}
- **Heading Font**: IBM Plex Sans
- **Mono**: {"letter_spacing":"0.02em","line_height":"1.45","size":"12px","text_transform":"uppercase","weight":700}
- **Mono Font**: JetBrains Mono

## Rules

### Composition

- Show a specific fictional diagnostic product and a concrete failing workflow, not an abstract dashboard.
- Use a wide reproduction lane paired with a narrower evidence rail on desktop.
- Create one dominant failing case module and several smaller supporting modules; never use three equal cards.
- Include one grid break through an oversized display heading or an inset trace well that interrupts the main rhythm.
- Maintain visible grouping: tight gaps inside evidence, larger gaps between workflow stages, and the largest gaps around the scene.
- Keep panels flat; use one subtle shadow only on the currently active reproduction case.

### Density

Dense where evidence is compared, spacious where the user chooses the next action. Tightest gaps may be 4px while hero and section separation reaches 64px or more, satisfying the 8:1 spacing rhythm test.

### Hierarchy

- Display headline states the exact failing case in one sentence.
- Primary action uses muted blue fill; secondary actions remain white with ink border.
- Status chips are small mono labels with text plus dot, never color alone.
- Evidence values use mono text and recessed wells so data separates from prose.
- The failing case is visually dominant through scale and content density, not extra decoration.

### Signature Patterns

- Separate flat severity rail strip adjacent to a rounded evidence card so the rail never wraps around curved corners.
- Expected / Observed / Delta comparison cells with dotted dividers and mono inset values make the reproduction path instantly recognizable.
- Uppercase JetBrains Mono case tags combine fixture IDs, timestamps, and state labels into a compact audit layer.
- Dark clipped trace log strips contrast with warm paper surfaces and provide a reusable evidence texture.

## Layout

### Density

Evidence regions are compact and data-rich, while decision areas breathe. This contrast makes the language feel operational rather than uniformly templated.

### Grid

Desktop uses a 12-column max-width around 1380px: 8 columns for the reproduction lane and 4 for the evidence rail, with 24px gutters. Cards align to an 8px spacing system but vary between dense 4px internals and 64px scene breaks.

### Responsive

- **Desktop**: 1200px+ split diagnostic scene with persistent evidence rail
- **Mobile**: 375px single timeline with full-width actions and stacked comparison cells
- **Tablet**: 768px stacked rail below reproduction lane

### Whitespace

Whitespace is not ornamental; it isolates the one active failing case and prevents secondary metrics from competing with the reproduction path.

## Guidance

### Do

- Name the product context and failure case specifically.
- Reduce each screen to precondition, action, observed result, and verification.
- Pair every semantic color with a text label, dot, icon, or rail pattern.
- Use custom form controls, selects, checkboxes, and focus rings; never leave browser defaults.
- Let negative space carry identity by removing decorative fills and gradients.
- Expose trace IDs, timestamps, fixture names, and copy or rerun controls.
- Use the separate severity rail pattern consistently for failed, passing, warning, and queued states.
- Keep body text at 15-16px with -0.02em tracking for precision.

### Don't

- Do not build a generic SaaS analytics, CRM, or project-management dashboard.
- Do not use one-sided colored borders on rounded elements; use a separate square rail element.
- Do not mix arbitrary radii such as 3px, 6px, and 10px in final embodiments.
- Do not rely on color alone for severity or status.
- Do not use glossy gradients, floating glass, large decorative illustrations, or stock lifestyle imagery.
- Do not present a component catalog as the embodiment scene.
- Do not add shadows, accents, or extra colors merely to fill empty space.
- Do not use banned AI-tell fonts such as Poppins, Montserrat, DM Sans, Space Grotesk, Figtree, Outfit, or Plus Jakarta Sans.

### Accessibility

WCAG AA contrast is mandatory. Focus uses a 2px blue outline with offset. All controls are semantic HTML elements with labels and helper text. Reduced motion disables transitions. State dots include visible text labels and should have aria-labels in production.

### Usage Context

Best for QA tooling, regression triage, incident reproduction, automated test review, data-quality investigations, and any workflow where a person must verify a specific state transition.
DESIGN.md
---
version: "alpha"
name: "Test Repro Name 2"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  amber: "#A86600"
  green: "#207A3D"
  ink: "#171A1F"
  muted_text: "#5C6675"
  paper: "#F7F4EE"
  primary_blue: "#2864D8"
  primary_blue_dark: "#174AA9"
  red: "#A7352B"
  surface: "#FFFFFF"
  well: "#ECE7DD"
typography:
  headline-lg:
    fontFamily: "IBM Plex Sans"
    fontSize: "1.953rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "IBM Plex Sans"
    fontSize: "1.563rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "Inter"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "JetBrains Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  flat: "0px"
  large: "24px"
  pill: "9999px"
  primary: "16px"
spacing:
  2xl: "64px"
  2xs: "2px"
  3xl: "96px"
  lg: "24px"
  md: "16px"
  sm: "8px"
  xl: "40px"
  xs: "4px"
components:
  color-reference-amber:
    backgroundColor: "{colors.amber}"
  color-reference-green:
    backgroundColor: "{colors.green}"
  color-reference-ink:
    backgroundColor: "{colors.ink}"
  color-reference-muted_text:
    backgroundColor: "{colors.muted_text}"
  color-reference-paper:
    backgroundColor: "{colors.paper}"
  color-reference-primary_blue:
    backgroundColor: "{colors.primary_blue}"
  color-reference-primary_blue_dark:
    backgroundColor: "{colors.primary_blue_dark}"
  color-reference-red:
    backgroundColor: "{colors.red}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-well:
    backgroundColor: "{colors.well}"
---

# Test Repro Name 2

## Overview

Minimal Repro is a diagnostic design language for test beds, regression triage, QA dashboards, and incident reproduction flows. It reduces every product moment to the smallest truthful scene: the preconditions, the expected result, the observed result, the delta, and the next reproducible action. It is intentionally sparse, auditable, and direct. The language treats visual design as a test fixture: every border establishes containment, every label clarifies state, and every accent identifies severity or focus. It avoids decorative variety so a viewer can move from symptom to verification without interpretation overhead.

### Values

- Smallest truthful case before broad system narrative
- Observable state changes instead of implied status
- Auditability through IDs, timestamps, traces, and diffs
- Restraint over decoration; every visible property must earn its place
- Functional contrast and explicit labels for every critical state
- Repeatable spacing and composition so evidence can be compared
- Fast, reversible actions that never obscure the current state

### Anti-Values

- Decorative gradients, glass, and lifestyle imagery that do not help reproduction
- Generic analytics dashboards or component catalogs without a specific failing workflow
- Unlabeled color-only status indicators
- Soft SaaS chrome, arbitrary radius mixing, and ornamental shadows

### Visual Character

- Flat warm-paper surfaces with near-black hairline boundaries create the feeling of a precise test fixture rather than a marketing page.
- The signature pattern is a square-edged evidence card that uses a separate severity rail strip, mono case identifier, and Expected / Observed / Delta comparison area.
- Typography separates voices clearly: IBM Plex Sans for compact headings, Inter for readable instructions, and JetBrains Mono for traceable evidence values.
- Accent color is surgical: a muted blue for action and focus, plus semantic severity marks used only in small dots, rails, and status chips.

## Colors

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

| Token | Value |
|-------|-------|
| amber | `#A86600` |
| green | `#207A3D` |
| ink | `#171A1F` |
| muted_text | `#5C6675` |
| paper | `#F7F4EE` |
| primary_blue | `#2864D8` |
| primary_blue_dark | `#174AA9` |
| red | `#A7352B` |
| surface | `#FFFFFF` |
| well | `#ECE7DD` |

## Typography

- **Headline-Lg**: IBM Plex Sans, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: IBM Plex Sans, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Inter, 16px, weight 400, line-height 1.5.
- **Label-Md**: JetBrains Mono, 0.75rem, weight 600, line-height 1.

## Layout

### Spacing Tokens

- **2xl**: `64px`
- **2xs**: `2px`
- **3xl**: `96px`
- **Lg**: `24px`
- **Md**: `16px`
- **Sm**: `8px`
- **Xl**: `40px`
- **Xs**: `4px`

### Density

Evidence regions are compact and data-rich, while decision areas breathe. This contrast makes the language feel operational rather than uniformly templated.

### Grid

Desktop uses a 12-column max-width around 1380px: 8 columns for the reproduction lane and 4 for the evidence rail, with 24px gutters. Cards align to an 8px spacing system but vary between dense 4px internals and 64px scene breaks.

### Responsive

- **Desktop**: 1200px+ split diagnostic scene with persistent evidence rail
- **Mobile**: 375px single timeline with full-width actions and stacked comparison cells
- **Tablet**: 768px stacked rail below reproduction lane

### Whitespace

Whitespace is not ornamental; it isolates the one active failing case and prevents secondary metrics from competing with the reproduction path.

## Elevation & Depth

### Shadows

- **Active Case**: 0 18px 38px rgba(23,26,31,0.08)
- **Focus**: 0 0 0 2px #2864D8
- **None**: none

## Shapes

### Rounded

- **Flat**: `0px`
- **Large**: `24px`
- **Pill**: `9999px`
- **Primary**: `16px`

### Surfaces

- **Canvas**: warm gridded paper background #F7F4EE
- **Card**: white panel with 8% ink border
- **Dark Log**: #11151A with pale mono trace lines
- **Well**: recessed #ECE7DD inset evidence strip

### Borders

- **Default**: 1px solid rgba(23,26,31,0.08)
- **Emphasis**: 1px solid rgba(23,26,31,0.72)
- **Focus**: 2px solid #2864D8 with 2px offset
- **Severity Rail**: separate flat 4px strip placed before the card content, never a rounded one-sided border

## Components

### Composition

- Show a specific fictional diagnostic product and a concrete failing workflow, not an abstract dashboard.
- Use a wide reproduction lane paired with a narrower evidence rail on desktop.
- Create one dominant failing case module and several smaller supporting modules; never use three equal cards.
- Include one grid break through an oversized display heading or an inset trace well that interrupts the main rhythm.
- Maintain visible grouping: tight gaps inside evidence, larger gaps between workflow stages, and the largest gaps around the scene.
- Keep panels flat; use one subtle shadow only on the currently active reproduction case.

### Density

Dense where evidence is compared, spacious where the user chooses the next action. Tightest gaps may be 4px while hero and section separation reaches 64px or more, satisfying the 8:1 spacing rhythm test.

### Hierarchy

- Display headline states the exact failing case in one sentence.
- Primary action uses muted blue fill; secondary actions remain white with ink border.
- Status chips are small mono labels with text plus dot, never color alone.
- Evidence values use mono text and recessed wells so data separates from prose.
- The failing case is visually dominant through scale and content density, not extra decoration.

### Signature Patterns

- Separate flat severity rail strip adjacent to a rounded evidence card so the rail never wraps around curved corners.
- Expected / Observed / Delta comparison cells with dotted dividers and mono inset values make the reproduction path instantly recognizable.
- Uppercase JetBrains Mono case tags combine fixture IDs, timestamps, and state labels into a compact audit layer.
- Dark clipped trace log strips contrast with warm paper surfaces and provide a reusable evidence texture.

## 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-019e04f7-ddea-7c53-8067-f46868bb62cc/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 Name the product context and failure case specifically.
- Do Reduce each screen to precondition, action, observed result, and verification.
- Do Pair every semantic color with a text label, dot, icon, or rail pattern.
- Do Use custom form controls, selects, checkboxes, and focus rings; never leave browser defaults.
- Do Let negative space carry identity by removing decorative fills and gradients.
- Do Expose trace IDs, timestamps, fixture names, and copy or rerun controls.
- Do Use the separate severity rail pattern consistently for failed, passing, warning, and queued states.
- Do Keep body text at 15-16px with -0.02em tracking for precision.
- Don't Do not build a generic SaaS analytics, CRM, or project-management dashboard.
- Don't Do not use one-sided colored borders on rounded elements; use a separate square rail element.
- Don't Do not mix arbitrary radii such as 3px, 6px, and 10px in final embodiments.
- Don't Do not rely on color alone for severity or status.
- Don't Do not use glossy gradients, floating glass, large decorative illustrations, or stock lifestyle imagery.
- Don't Do not present a component catalog as the embodiment scene.
- Don't Do not add shadows, accents, or extra colors merely to fill empty space.
- Don't Do not use banned AI-tell fonts such as Poppins, Montserrat, DM Sans, Space Grotesk, Figtree, Outfit, or Plus Jakarta Sans.

### Accessibility

WCAG AA contrast is mandatory. Focus uses a 2px blue outline with offset. All controls are semantic HTML elements with labels and helper text. Reduced motion disables transitions. State dots include visible text labels and should have aria-labels in production.

### Usage Context

Best for QA tooling, regression triage, incident reproduction, automated test review, data-quality investigations, and any workflow where a person must verify a specific state transition.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "test-repro-name-2",
  "type": "registry:theme",
  "title": "Test Repro Name 2 shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#ffffff",
      "foreground": "#171A1F",
      "card": "#FFFFFF",
      "card-foreground": "#171A1F",
      "popover": "#FFFFFF",
      "popover-foreground": "#171A1F",
      "primary": "#171A1F",
      "primary-foreground": "#ffffff",
      "secondary": "#f4f4f5",
      "secondary-foreground": "#111111",
      "muted": "#f4f4f5",
      "muted-foreground": "#171A1F",
      "accent": "#171A1F",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#e4e4e7",
      "input": "#e4e4e7",
      "ring": "#171A1F",
      "chart-1": "#171A1F",
      "chart-2": "#f4f4f5",
      "chart-3": "#171A1F",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#171A1F",
      "sidebar-primary": "#171A1F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#171A1F",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#e4e4e7",
      "sidebar-ring": "#171A1F",
      "radius": "0.625rem"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#171A1F",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#171A1F",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#303642",
      "input": "#303642",
      "ring": "#171A1F",
      "chart-1": "#171A1F",
      "chart-2": "#f4f4f5",
      "chart-3": "#171A1F",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#171A1F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#171A1F",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#171A1F",
      "radius": "0.625rem"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e04f7-ddea-7c53-8067-f46868bb62cc",
    "slug": "test-repro-name-2",
    "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": [
        "default",
        "emphasis",
        "focus",
        "severity_rail"
      ],
      "colors": [
        "amber",
        "border_strong",
        "border_weak",
        "green",
        "ink",
        "muted_text",
        "paper",
        "primary_blue",
        "primary_blue_dark",
        "red",
        "surface",
        "well"
      ],
      "motion": [
        "base",
        "fast",
        "principle"
      ],
      "radii": [
        "flat",
        "large",
        "pill",
        "primary"
      ],
      "shadows": [
        "active_case",
        "focus",
        "none"
      ],
      "spacing": [
        "2xl",
        "2xs",
        "3xl",
        "lg",
        "md",
        "sm",
        "xl",
        "xs"
      ],
      "surfaces": [
        "canvas",
        "card",
        "dark_log",
        "well"
      ],
      "typography": [
        "body",
        "body_font",
        "display",
        "google_fonts_url",
        "heading",
        "heading_font",
        "mono",
        "mono_font"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · test-repro-name-2
DESIGN.md

at a glance

Palette

Typography

headline-lgIBM Plex Sans · 31px · 700

The quick brown fox jumps

headline-mdIBM Plex Sans · 25px · 600

The quick brown fox jumps

body-mdInter · 16px · 400

The quick brown fox jumps

label-mdJetBrains 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

  • 2xl64px
  • 2xs2px
  • 3xl96px
  • lg24px
  • md16px
  • sm8px
  • xl40px
  • xs4px

Shape

flat0px
large24px
pill9999px
primary16px
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: #ffffff;
  --foreground: #171A1F;
  --card: #FFFFFF;
  --card-foreground: #171A1F;
  --popover: #FFFFFF;
  --popover-foreground: #171A1F;
  --primary: #171A1F;
  --primary-foreground: #ffffff;
  --secondary: #f4f4f5;
  --secondary-foreground: #111111;
  --muted: #f4f4f5;
  --muted-foreground: #171A1F;
  --accent: #171A1F;
  --accent-foreground: #ffffff;
  --destructive: #dc2626;
  --border: #e4e4e7;
  --input: #e4e4e7;
  --ring: #171A1F;
  --chart-1: #171A1F;
  --chart-2: #f4f4f5;
  --chart-3: #171A1F;
  --chart-4: #16a34a;
  --chart-5: #d97706;
  --sidebar: #FFFFFF;
  --sidebar-foreground: #171A1F;
  --sidebar-primary: #171A1F;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #171A1F;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #e4e4e7;
  --sidebar-ring: #171A1F;
  --radius: 0.625rem;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #171A1F;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #171A1F;
  --accent-foreground: #ffffff;
  --destructive: #dc2626;
  --border: #303642;
  --input: #303642;
  --ring: #171A1F;
  --chart-1: #171A1F;
  --chart-2: #f4f4f5;
  --chart-3: #171A1F;
  --chart-4: #16a34a;
  --chart-5: #d97706;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #171A1F;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #171A1F;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #171A1F;
  --radius: 0.625rem;
}
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 TestReproName2ShadcnKit() {
  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">Test Repro Name 2</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": "test-repro-name-2",
  "type": "registry:theme",
  "title": "Test Repro Name 2 shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#ffffff",
      "foreground": "#171A1F",
      "card": "#FFFFFF",
      "card-foreground": "#171A1F",
      "popover": "#FFFFFF",
      "popover-foreground": "#171A1F",
      "primary": "#171A1F",
      "primary-foreground": "#ffffff",
      "secondary": "#f4f4f5",
      "secondary-foreground": "#111111",
      "muted": "#f4f4f5",
      "muted-foreground": "#171A1F",
      "accent": "#171A1F",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#e4e4e7",
      "input": "#e4e4e7",
      "ring": "#171A1F",
      "chart-1": "#171A1F",
      "chart-2": "#f4f4f5",
      "chart-3": "#171A1F",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#FFFFFF",
      "sidebar-foreground": "#171A1F",
      "sidebar-primary": "#171A1F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#171A1F",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#e4e4e7",
      "sidebar-ring": "#171A1F",
      "radius": "0.625rem"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#171A1F",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#171A1F",
      "accent-foreground": "#ffffff",
      "destructive": "#dc2626",
      "border": "#303642",
      "input": "#303642",
      "ring": "#171A1F",
      "chart-1": "#171A1F",
      "chart-2": "#f4f4f5",
      "chart-3": "#171A1F",
      "chart-4": "#16a34a",
      "chart-5": "#d97706",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#171A1F",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#171A1F",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#171A1F",
      "radius": "0.625rem"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e04f7-ddea-7c53-8067-f46868bb62cc",
    "slug": "test-repro-name-2",
    "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": [
        "default",
        "emphasis",
        "focus",
        "severity_rail"
      ],
      "colors": [
        "amber",
        "border_strong",
        "border_weak",
        "green",
        "ink",
        "muted_text",
        "paper",
        "primary_blue",
        "primary_blue_dark",
        "red",
        "surface",
        "well"
      ],
      "motion": [
        "base",
        "fast",
        "principle"
      ],
      "radii": [
        "flat",
        "large",
        "pill",
        "primary"
      ],
      "shadows": [
        "active_case",
        "focus",
        "none"
      ],
      "spacing": [
        "2xl",
        "2xs",
        "3xl",
        "lg",
        "md",
        "sm",
        "xl",
        "xs"
      ],
      "surfaces": [
        "canvas",
        "card",
        "dark_log",
        "well"
      ],
      "typography": [
        "body",
        "body_font",
        "display",
        "google_fonts_url",
        "heading",
        "heading_font",
        "mono",
        "mono_font"
      ]
    }
  }
}
component recipescompatibility fallback
# Test Repro Name 2 shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e04f7-ddea-7c53-8067-f46868bb62cc`
Slug: `test-repro-name-2`

## Intent

Minimal Repro is a diagnostic design language for test beds, regression triage, QA dashboards, and incident reproduction flows. It reduces every product moment to the smallest truthful scene: the preconditions, the expected result, the observed result, the delta, and the next reproducible action. It is intentionally sparse, auditable, and direct. The language treats visual design as a test fixture: every border establishes containment, every label clarifies state, and every accent identifies severity or focus. It avoids decorative variety so a viewer can move from symptom to verification without interpretation overhead.

## 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:

{
  "amber": "#A86600",
  "border_strong": "rgba(23,26,31,0.72)",
  "border_weak": "rgba(23,26,31,0.08)",
  "green": "#207A3D",
  "ink": "#171A1F",
  "muted_text": "#5C6675",
  "paper": "#F7F4EE",
  "primary_blue": "#2864D8",
  "primary_blue_dark": "#174AA9",
  "red": "#A7352B",
  "surface": "#FFFFFF",
  "well": "#ECE7DD"
}

Typography:

{
  "body": {
    "letter_spacing": "-0.02em",
    "line_height": "1.56",
    "size": "16px",
    "weight": 400
  },
  "body_font": "Inter",
  "display": {
    "letter_spacing": "-0.04em",
    "line_height": "1.12",
    "size": "clamp(36px, 5vw, 64px)",
    "weight": 700
  },
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=IBM+Plex+Sans:wght@500;600;700&family=Inter:wght@400;500;600;700&family=JetBrains+Mono:wght@400;600;700&display=swap",
  "heading": {
    "letter_spacing": "-0.03em",
    "line_height": "1.15",
    "weight": 700
  },
  "heading_font": "IBM Plex Sans",
  "mono": {
    "letter_spacing": "0.02em",
    "line_height": "1.45",
    "size": "12px",
    "text_transform": "uppercase",
    "weight": 700
  },
  "mono_font": "JetBrains Mono"
}

## Visual character to preserve

- Flat warm-paper surfaces with near-black hairline boundaries create the feeling of a precise test fixture rather than a marketing page.
- The signature pattern is a square-edged evidence card that uses a separate severity rail strip, mono case identifier, and Expected / Observed / Delta comparison area.
- Typography separates voices clearly: IBM Plex Sans for compact headings, Inter for readable instructions, and JetBrains Mono for traceable evidence values.
- Accent color is surgical: a muted blue for action and focus, plus semantic severity marks used only in small dots, rails, and status chips.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "solid",
  "underlay": true,
  "grain": true,
  "stickerBadges": true,
  "motion": "still",
  "density": "dense",
  "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/test-repro-name-2/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: follow the Katagami source guidance
- Do not: do not collapse the language into generic defaults

## 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 TestReproName2ShadcnKit() {
  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">Test Repro Name 2</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

{
  "density": "Evidence regions are compact and data-rich, while decision areas breathe. This contrast makes the language feel operational rather than uniformly templated.",
  "grid": "Desktop uses a 12-column max-width around 1380px: 8 columns for the reproduction lane and 4 for the evidence rail, with 24px gutters. Cards align to an 8px spacing system but vary between dense 4px internals and 64px scene breaks.",
  "responsive": {
    "desktop": "1200px+ split diagnostic scene with persistent evidence rail",
    "mobile": "375px single timeline with full-width actions and stacked comparison cells",
    "tablet": "768px stacked rail below reproduction lane"
  },
  "whitespace": "Whitespace is not ornamental; it isolates the one active failing case and prevents secondary metrics from competing with the reproduction path."
}
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-019e04f7-ddea-7c53-8067-f46868bb62cc",
    "name": "Test Repro Name 2",
    "slug": "test-repro-name-2"
  },
  "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": [
    "Flat warm-paper surfaces with near-black hairline boundaries create the feeling of a precise test fixture rather than a marketing page.",
    "The signature pattern is a square-edged evidence card that uses a separate severity rail strip, mono case identifier, and Expected / Observed / Delta comparison area.",
    "Typography separates voices clearly: IBM Plex Sans for compact headings, Inter for readable instructions, and JetBrains Mono for traceable evidence values.",
    "Accent color is surgical: a muted blue for action and focus, plus semantic severity marks used only in small dots, rails, and status chips."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "solid",
    "underlay": false,
    "grain": true,
    "stickerBadges": true,
    "motion": "still",
    "density": "dense",
    "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": "Test Repro Name 2 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": [],
    "dont": []
  }
}