back to gallery
design language·white-lapis-product-notebook-shell

White Lapis Product Notebook Shell

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
A premium white product interface language where the product object and measured decisions sit in a calm paper shell; lapis blue appears only as a decisive control and spatial reference color, while pale butter is reserved for quiet annotation marks.
values
product-first calmcolor as decision evidencepaper-like spaciousnessmeasured optical precision
anti-values
×rainbow accent systems×generic dashboard density×decorative rails or stripes×global dotted backgrounds
tokens
borders4 items
accent width
1px
character
Pale gray hairlines for structure; lapis borders appear only on focused or selected controls, never as decorative side accents.
default width
1px
style
solid
colors12 items
accent
#1F4EA8
background
#FFFFFF
border
#E6E7EA
error
#8F3A35
info
#1F4EA8
muted
#73777F
primary
#1F4EA8
secondary
#FFF3B8
success
#3F6F55
surface
#FAFAF7
text
#17181B
warning
#B18B2C
motion3 items
duration
180ms
easing
cubic-bezier(0.2, 0.8, 0.2, 1)
philosophy
Small state confirmations: controls brighten, lapis focus rings resolve, and product annotations fade in without bounce or spectacle.
radii5 items
full
9999px
lg
18px
md
12px
none
0
sm
8px
shadows3 items
lg
0 34px 90px rgba(31,78,168,0.12)
md
0 18px 60px rgba(23,24,27,0.08)
sm
0 1px 2px rgba(23,24,27,0.05)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
bg pattern
Global background is clean white; dotted notebook texture is isolated to one quiet annotation panel using low-opacity radial points.
card style
Flat rounded rectangles with 1px pale-gray borders, soft white fill, rare inset separators, and no colored stripes or rails.
treatment
Quiet white and warm paper planes with subtle inset borders; one secondary annotation surface may use a tiny lapis-gray point field.
typography8 items
base size
16px
body font
Instrument Sans
google fonts url
https://fonts.googleapis.com/css2?family=Instrument+Sans:wght@400;500;600;700&family=IBM+Plex+Mono:wght@400;500;600&display=swap
heading font
Instrument Sans
letter spacing
-0.018em
line height
1.48
mono font
IBM Plex Mono
scale ratio
1.2
rules
composition
Start with a spacious white product stage, then place controls as quiet instruments around the object; avoid dashboard module grids and decorative color framing.
density

Medium-low density with generous vertical rhythm, compact controls, and information grouped in measured clusters rather than broad analytics panels.

hierarchy

Let product imagery, large black type, and restrained lapis active states define priority; secondary notes sit in pale paper panels with muted mono metadata.

signature patterns
One secondary annotation card uses a low-opacity radial point-field background clipped inside a rounded paper panel, never across the page.Lapis selection appears as small filled pills, fine focus rings, and vector-like measurement paths that connect UI values to the product stage.Pale butter annotation highlights sit behind short text fragments or note chips with transparent fill and no saturated yellow blocks.Product cards use inset top metadata rows and bottom measurement shelves separated by hairlines, preserving a premium hardware-spec feel.Interactive elements use white fill, pale borders, and lapis text or ring changes on state instead of colored button stripes or multi-hue badges.
layout
breakpoints

Mobile 375px stacks product, annotation, and controls; tablet 768px uses two balanced columns; desktop 1200px+ uses a 1.45fr/0.75fr shell.

grid

Asymmetric product shell: a wide product stage paired with a narrow instrumentation column, collapsing to stacked cards on smaller screens.

whitespace

Whitespace is a primary material: keep 24-64px breathing room around product stages and allow empty white areas to remain unfilled.

guidance
do
  • Use lapis only when a control is active, selected, focused, or directly tied to a measured product feature.
  • Keep the global canvas white or warm paper with hairline gray boundaries and large quiet intervals.
  • Place the dotted notebook texture in one secondary annotation area at very low contrast.
  • Use pale butter as an annotation highlight behind text snippets or small note chips.
avoid
  • Do not create a rainbow palette, colored side rails, card stripes, button stripes, or confetti accents.
  • Do not use square grid backgrounds or make the dotted point texture a global page motif.
  • Do not turn the embodiment into a generic SaaS dashboard or swatch catalog.
  • Do not add extra vivid accent colors; use opacity, tint, shade, and hierarchy instead.
katagami spec
# White Lapis Product Notebook Shell

## Philosophy

A premium white product interface language where the product object and measured decisions sit in a calm paper shell; lapis blue appears only as a decisive control and spatial reference color, while pale butter is reserved for quiet annotation marks.

### Values

- product-first calm
- color as decision evidence
- paper-like spaciousness
- measured optical precision

### Anti-Values

- rainbow accent systems
- generic dashboard density
- decorative rails or stripes
- global dotted backgrounds

### Visual Character

- Use a white-to-paper background with large unbroken negative space, hairline pale-gray dividers, and no global texture except one isolated point-field annotation panel.
- Build hierarchy with low, flat product plinths, inset measurement cards, and single-pixel ink borders rather than heavy shadows or colored card accents.
- Apply lapis blue only to active controls, selected measurement paths, numeric deltas, and focus states so color reads as product evidence rather than decoration.
- Reserve pale butter for translucent text highlights and small note chips inside annotation contexts, never for primary buttons or broad surfaces.
- Use compact rounded geometry with one committed radius family, precise type spacing, and calm opacity layers to create depth without adding more hues.

## Tokens

### Borders

- **Accent Width**: 1px
- **Character**: Pale gray hairlines for structure; lapis borders appear only on focused or selected controls, never as decorative side accents.
- **Default Width**: 1px
- **Style**: solid

### Colors

| Name | Value |
|------|-------|
| accent | `#1F4EA8` |
| background | `#FFFFFF` |
| border | `#E6E7EA` |
| error | `#8F3A35` |
| info | `#1F4EA8` |
| muted | `#73777F` |
| primary | `#1F4EA8` |
| secondary | `#FFF3B8` |
| success | `#3F6F55` |
| surface | `#FAFAF7` |
| text | `#17181B` |
| warning | `#B18B2C` |

### Motion

- **Duration**: 180ms
- **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1)
- **Philosophy**: Small state confirmations: controls brighten, lapis focus rings resolve, and product annotations fade in without bounce or spectacle.

### Radii

- **Full**: 9999px
- **Lg**: 18px
- **Md**: 12px
- **None**: 0
- **Sm**: 8px

### Shadows

- **Lg**: 0 34px 90px rgba(31,78,168,0.12)
- **Md**: 0 18px 60px rgba(23,24,27,0.08)
- **Sm**: 0 1px 2px rgba(23,24,27,0.05)

### Spacing

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

### Surfaces

- **Bg Pattern**: Global background is clean white; dotted notebook texture is isolated to one quiet annotation panel using low-opacity radial points.
- **Card Style**: Flat rounded rectangles with 1px pale-gray borders, soft white fill, rare inset separators, and no colored stripes or rails.
- **Treatment**: Quiet white and warm paper planes with subtle inset borders; one secondary annotation surface may use a tiny lapis-gray point field.

### Typography

- **Base Size**: 16px
- **Body Font**: Instrument Sans
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Instrument+Sans:wght@400;500;600;700&family=IBM+Plex+Mono:wght@400;500;600&display=swap
- **Heading Font**: Instrument Sans
- **Letter Spacing**: -0.018em
- **Line Height**: 1.48
- **Mono Font**: IBM Plex Mono
- **Scale Ratio**: 1.2

## Rules

### Composition

Start with a spacious white product stage, then place controls as quiet instruments around the object; avoid dashboard module grids and decorative color framing.

### Density

Medium-low density with generous vertical rhythm, compact controls, and information grouped in measured clusters rather than broad analytics panels.

### Hierarchy

Let product imagery, large black type, and restrained lapis active states define priority; secondary notes sit in pale paper panels with muted mono metadata.

### Signature Patterns

- One secondary annotation card uses a low-opacity radial point-field background clipped inside a rounded paper panel, never across the page.
- Lapis selection appears as small filled pills, fine focus rings, and vector-like measurement paths that connect UI values to the product stage.
- Pale butter annotation highlights sit behind short text fragments or note chips with transparent fill and no saturated yellow blocks.
- Product cards use inset top metadata rows and bottom measurement shelves separated by hairlines, preserving a premium hardware-spec feel.
- Interactive elements use white fill, pale borders, and lapis text or ring changes on state instead of colored button stripes or multi-hue badges.

## Layout

### Breakpoints

Mobile 375px stacks product, annotation, and controls; tablet 768px uses two balanced columns; desktop 1200px+ uses a 1.45fr/0.75fr shell.

### Grid

Asymmetric product shell: a wide product stage paired with a narrow instrumentation column, collapsing to stacked cards on smaller screens.

### Whitespace

Whitespace is a primary material: keep 24-64px breathing room around product stages and allow empty white areas to remain unfilled.

## Guidance

### Do

- Use lapis only when a control is active, selected, focused, or directly tied to a measured product feature.
- Keep the global canvas white or warm paper with hairline gray boundaries and large quiet intervals.
- Place the dotted notebook texture in one secondary annotation area at very low contrast.
- Use pale butter as an annotation highlight behind text snippets or small note chips.

### Don't

- Do not create a rainbow palette, colored side rails, card stripes, button stripes, or confetti accents.
- Do not use square grid backgrounds or make the dotted point texture a global page motif.
- Do not turn the embodiment into a generic SaaS dashboard or swatch catalog.
- Do not add extra vivid accent colors; use opacity, tint, shade, and hierarchy instead.
DESIGN.md
---
version: "alpha"
name: "White Lapis Product Notebook Shell"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#1F4EA8"
  background: "#FFFFFF"
  border: "#E6E7EA"
  error: "#8F3A35"
  info: "#1F4EA8"
  muted: "#73777F"
  primary: "#1F4EA8"
  secondary: "#FFF3B8"
  success: "#3F6F55"
  surface: "#FAFAF7"
  text: "#17181B"
  warning: "#B18B2C"
typography:
  headline-lg:
    fontFamily: "Instrument Sans"
    fontSize: "1.728rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.018em"
  headline-md:
    fontFamily: "Instrument Sans"
    fontSize: "1.44rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.018em"
  body-md:
    fontFamily: "Instrument Sans"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.48
    letterSpacing: "-0.018em"
  label-md:
    fontFamily: "IBM Plex Mono"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "18px"
  md: "12px"
  none: "0px"
  sm: "8px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
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"
---

# White Lapis Product Notebook Shell

## Overview

A premium white product interface language where the product object and measured decisions sit in a calm paper shell; lapis blue appears only as a decisive control and spatial reference color, while pale butter is reserved for quiet annotation marks.

### Values

- product-first calm
- color as decision evidence
- paper-like spaciousness
- measured optical precision

### Anti-Values

- rainbow accent systems
- generic dashboard density
- decorative rails or stripes
- global dotted backgrounds

### Visual Character

- Use a white-to-paper background with large unbroken negative space, hairline pale-gray dividers, and no global texture except one isolated point-field annotation panel.
- Build hierarchy with low, flat product plinths, inset measurement cards, and single-pixel ink borders rather than heavy shadows or colored card accents.
- Apply lapis blue only to active controls, selected measurement paths, numeric deltas, and focus states so color reads as product evidence rather than decoration.
- Reserve pale butter for translucent text highlights and small note chips inside annotation contexts, never for primary buttons or broad surfaces.
- Use compact rounded geometry with one committed radius family, precise type spacing, and calm opacity layers to create depth without adding more hues.

## 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 | `#1F4EA8` |
| background | `#FFFFFF` |
| border | `#E6E7EA` |
| error | `#8F3A35` |
| info | `#1F4EA8` |
| muted | `#73777F` |
| primary | `#1F4EA8` |
| secondary | `#FFF3B8` |
| success | `#3F6F55` |
| surface | `#FAFAF7` |
| text | `#17181B` |
| warning | `#B18B2C` |

## Typography

- **Headline-Lg**: Instrument Sans, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Instrument Sans, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: Instrument Sans, 16px, weight 400, line-height 1.48.
- **Label-Md**: IBM Plex 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`

### Breakpoints

Mobile 375px stacks product, annotation, and controls; tablet 768px uses two balanced columns; desktop 1200px+ uses a 1.45fr/0.75fr shell.

### Grid

Asymmetric product shell: a wide product stage paired with a narrow instrumentation column, collapsing to stacked cards on smaller screens.

### Whitespace

Whitespace is a primary material: keep 24-64px breathing room around product stages and allow empty white areas to remain unfilled.

## Elevation & Depth

### Shadows

- **Lg**: 0 34px 90px rgba(31,78,168,0.12)
- **Md**: 0 18px 60px rgba(23,24,27,0.08)
- **Sm**: 0 1px 2px rgba(23,24,27,0.05)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `18px`
- **Md**: `12px`
- **None**: `0px`
- **Sm**: `8px`

### Surfaces

- **Bg Pattern**: Global background is clean white; dotted notebook texture is isolated to one quiet annotation panel using low-opacity radial points.
- **Card Style**: Flat rounded rectangles with 1px pale-gray borders, soft white fill, rare inset separators, and no colored stripes or rails.
- **Treatment**: Quiet white and warm paper planes with subtle inset borders; one secondary annotation surface may use a tiny lapis-gray point field.

### Borders

- **Accent Width**: 1px
- **Character**: Pale gray hairlines for structure; lapis borders appear only on focused or selected controls, never as decorative side accents.
- **Default Width**: 1px
- **Style**: solid

## Components

### Composition

Start with a spacious white product stage, then place controls as quiet instruments around the object; avoid dashboard module grids and decorative color framing.

### Density

Medium-low density with generous vertical rhythm, compact controls, and information grouped in measured clusters rather than broad analytics panels.

### Hierarchy

Let product imagery, large black type, and restrained lapis active states define priority; secondary notes sit in pale paper panels with muted mono metadata.

### Signature Patterns

- One secondary annotation card uses a low-opacity radial point-field background clipped inside a rounded paper panel, never across the page.
- Lapis selection appears as small filled pills, fine focus rings, and vector-like measurement paths that connect UI values to the product stage.
- Pale butter annotation highlights sit behind short text fragments or note chips with transparent fill and no saturated yellow blocks.
- Product cards use inset top metadata rows and bottom measurement shelves separated by hairlines, preserving a premium hardware-spec feel.
- Interactive elements use white fill, pale borders, and lapis text or ring changes on state instead of colored button stripes or multi-hue badges.

## 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-019e4646-e508-7ef2-9d6e-ac3edeb2a53f/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 Use lapis only when a control is active, selected, focused, or directly tied to a measured product feature.
- Do Keep the global canvas white or warm paper with hairline gray boundaries and large quiet intervals.
- Do Place the dotted notebook texture in one secondary annotation area at very low contrast.
- Do Use pale butter as an annotation highlight behind text snippets or small note chips.
- Don't Do not create a rainbow palette, colored side rails, card stripes, button stripes, or confetti accents.
- Don't Do not use square grid backgrounds or make the dotted point texture a global page motif.
- Don't Do not turn the embodiment into a generic SaaS dashboard or swatch catalog.
- Don't Do not add extra vivid accent colors; use opacity, tint, shade, and hierarchy instead.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "white-lapis-product-notebook-shell",
  "type": "registry:theme",
  "title": "White Lapis Product Notebook Shell shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#FFFFFF",
      "foreground": "#17181B",
      "card": "#FAFAF7",
      "card-foreground": "#17181B",
      "popover": "#FAFAF7",
      "popover-foreground": "#17181B",
      "primary": "#1F4EA8",
      "primary-foreground": "#ffffff",
      "secondary": "#FFF3B8",
      "secondary-foreground": "#111111",
      "muted": "#73777F",
      "muted-foreground": "#17181B",
      "accent": "#1F4EA8",
      "accent-foreground": "#ffffff",
      "destructive": "#8F3A35",
      "border": "#E6E7EA",
      "input": "#E6E7EA",
      "ring": "#1F4EA8",
      "chart-1": "#1F4EA8",
      "chart-2": "#FFF3B8",
      "chart-3": "#1F4EA8",
      "chart-4": "#3F6F55",
      "chart-5": "#B18B2C",
      "sidebar": "#FAFAF7",
      "sidebar-foreground": "#17181B",
      "sidebar-primary": "#1F4EA8",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#1F4EA8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#E6E7EA",
      "sidebar-ring": "#1F4EA8",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1F4EA8",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#1F4EA8",
      "accent-foreground": "#ffffff",
      "destructive": "#8F3A35",
      "border": "#303642",
      "input": "#303642",
      "ring": "#1F4EA8",
      "chart-1": "#1F4EA8",
      "chart-2": "#FFF3B8",
      "chart-3": "#1F4EA8",
      "chart-4": "#3F6F55",
      "chart-5": "#B18B2C",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1F4EA8",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#1F4EA8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#1F4EA8",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e4646-e508-7ef2-9d6e-ac3edeb2a53f",
    "slug": "white-lapis-product-notebook-shell",
    "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

the full element showcase
embodiment · white-lapis-product-notebook-shell
DESIGN.md

at a glance

Palette

Typography

headline-lgInstrument Sans · 28px · 700

The quick brown fox jumps

headline-mdInstrument Sans · 23px · 600

The quick brown fox jumps

body-mdInstrument Sans · 16px · 400

The quick brown fox jumps

label-mdIBM Plex 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

Shape

full9999px
lg18px
md12px
none0px
sm8px
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.
primarysurfacemutedwarningerror
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: #17181B;
  --card: #FAFAF7;
  --card-foreground: #17181B;
  --popover: #FAFAF7;
  --popover-foreground: #17181B;
  --primary: #1F4EA8;
  --primary-foreground: #ffffff;
  --secondary: #FFF3B8;
  --secondary-foreground: #111111;
  --muted: #73777F;
  --muted-foreground: #17181B;
  --accent: #1F4EA8;
  --accent-foreground: #ffffff;
  --destructive: #8F3A35;
  --border: #E6E7EA;
  --input: #E6E7EA;
  --ring: #1F4EA8;
  --chart-1: #1F4EA8;
  --chart-2: #FFF3B8;
  --chart-3: #1F4EA8;
  --chart-4: #3F6F55;
  --chart-5: #B18B2C;
  --sidebar: #FAFAF7;
  --sidebar-foreground: #17181B;
  --sidebar-primary: #1F4EA8;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #1F4EA8;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #E6E7EA;
  --sidebar-ring: #1F4EA8;
  --radius: 12px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #1F4EA8;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #1F4EA8;
  --accent-foreground: #ffffff;
  --destructive: #8F3A35;
  --border: #303642;
  --input: #303642;
  --ring: #1F4EA8;
  --chart-1: #1F4EA8;
  --chart-2: #FFF3B8;
  --chart-3: #1F4EA8;
  --chart-4: #3F6F55;
  --chart-5: #B18B2C;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #1F4EA8;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #1F4EA8;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #1F4EA8;
  --radius: 12px;
}
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 WhiteLapisProductNotebookShellShadcnKit() {
  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">White Lapis Product Notebook Shell</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": "white-lapis-product-notebook-shell",
  "type": "registry:theme",
  "title": "White Lapis Product Notebook Shell shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#FFFFFF",
      "foreground": "#17181B",
      "card": "#FAFAF7",
      "card-foreground": "#17181B",
      "popover": "#FAFAF7",
      "popover-foreground": "#17181B",
      "primary": "#1F4EA8",
      "primary-foreground": "#ffffff",
      "secondary": "#FFF3B8",
      "secondary-foreground": "#111111",
      "muted": "#73777F",
      "muted-foreground": "#17181B",
      "accent": "#1F4EA8",
      "accent-foreground": "#ffffff",
      "destructive": "#8F3A35",
      "border": "#E6E7EA",
      "input": "#E6E7EA",
      "ring": "#1F4EA8",
      "chart-1": "#1F4EA8",
      "chart-2": "#FFF3B8",
      "chart-3": "#1F4EA8",
      "chart-4": "#3F6F55",
      "chart-5": "#B18B2C",
      "sidebar": "#FAFAF7",
      "sidebar-foreground": "#17181B",
      "sidebar-primary": "#1F4EA8",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#1F4EA8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#E6E7EA",
      "sidebar-ring": "#1F4EA8",
      "radius": "12px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#1F4EA8",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#1F4EA8",
      "accent-foreground": "#ffffff",
      "destructive": "#8F3A35",
      "border": "#303642",
      "input": "#303642",
      "ring": "#1F4EA8",
      "chart-1": "#1F4EA8",
      "chart-2": "#FFF3B8",
      "chart-3": "#1F4EA8",
      "chart-4": "#3F6F55",
      "chart-5": "#B18B2C",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#1F4EA8",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#1F4EA8",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#1F4EA8",
      "radius": "12px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "en-019e4646-e508-7ef2-9d6e-ac3edeb2a53f",
    "slug": "white-lapis-product-notebook-shell",
    "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
# White Lapis Product Notebook Shell shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e4646-e508-7ef2-9d6e-ac3edeb2a53f`
Slug: `white-lapis-product-notebook-shell`

## Intent

A premium white product interface language where the product object and measured decisions sit in a calm paper shell; lapis blue appears only as a decisive control and spatial reference color, while pale butter is reserved for quiet annotation marks.

## 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": "#1F4EA8",
  "background": "#FFFFFF",
  "border": "#E6E7EA",
  "error": "#8F3A35",
  "info": "#1F4EA8",
  "muted": "#73777F",
  "primary": "#1F4EA8",
  "secondary": "#FFF3B8",
  "success": "#3F6F55",
  "surface": "#FAFAF7",
  "text": "#17181B",
  "warning": "#B18B2C"
}

Typography:

{
  "base_size": "16px",
  "body_font": "Instrument Sans",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=Instrument+Sans:wght@400;500;600;700&family=IBM+Plex+Mono:wght@400;500;600&display=swap",
  "heading_font": "Instrument Sans",
  "letter_spacing": "-0.018em",
  "line_height": 1.48,
  "mono_font": "IBM Plex Mono",
  "scale_ratio": 1.2
}

## Visual character to preserve

- Use a white-to-paper background with large unbroken negative space, hairline pale-gray dividers, and no global texture except one isolated point-field annotation panel.
- Build hierarchy with low, flat product plinths, inset measurement cards, and single-pixel ink borders rather than heavy shadows or colored card accents.
- Apply lapis blue only to active controls, selected measurement paths, numeric deltas, and focus states so color reads as product evidence rather than decoration.
- Reserve pale butter for translucent text highlights and small note chips inside annotation contexts, never for primary buttons or broad surfaces.
- Use compact rounded geometry with one committed radius family, precise type spacing, and calm opacity layers to create depth without adding more hues.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "pebble",
  "border": "solid",
  "underlay": false,
  "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/white-lapis-product-notebook-shell/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: Use lapis only when a control is active, selected, focused, or directly tied to a measured product feature.; Keep the global canvas white or warm paper with hairline gray boundaries and large quiet intervals.; Place the dotted notebook texture in one secondary annotation area at very low contrast.; Use pale butter as an annotation highlight behind text snippets or small note chips.
- Do not: Do not create a rainbow palette, colored side rails, card stripes, button stripes, or confetti accents.; Do not use square grid backgrounds or make the dotted point texture a global page motif.; Do not turn the embodiment into a generic SaaS dashboard or swatch catalog.; Do not add extra vivid accent colors; use opacity, tint, shade, and hierarchy instead.

## 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 WhiteLapisProductNotebookShellShadcnKit() {
  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">White Lapis Product Notebook Shell</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 stacks product, annotation, and controls; tablet 768px uses two balanced columns; desktop 1200px+ uses a 1.45fr/0.75fr shell.",
  "grid": "Asymmetric product shell: a wide product stage paired with a narrow instrumentation column, collapsing to stacked cards on smaller screens.",
  "whitespace": "Whitespace is a primary material: keep 24-64px breathing room around product stages and allow empty white areas to remain unfilled."
}
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-019e4646-e508-7ef2-9d6e-ac3edeb2a53f",
    "name": "White Lapis Product Notebook Shell",
    "slug": "white-lapis-product-notebook-shell"
  },
  "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 white-to-paper background with large unbroken negative space, hairline pale-gray dividers, and no global texture except one isolated point-field annotation panel.",
    "Build hierarchy with low, flat product plinths, inset measurement cards, and single-pixel ink borders rather than heavy shadows or colored card accents.",
    "Apply lapis blue only to active controls, selected measurement paths, numeric deltas, and focus states so color reads as product evidence rather than decoration.",
    "Reserve pale butter for translucent text highlights and small note chips inside annotation contexts, never for primary buttons or broad surfaces.",
    "Use compact rounded geometry with one committed radius family, precise type spacing, and calm opacity layers to create depth without adding more hues."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "pebble",
    "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": "White Lapis Product Notebook Shell 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": [
      "Use lapis only when a control is active, selected, focused, or directly tied to a measured product feature.",
      "Keep the global canvas white or warm paper with hairline gray boundaries and large quiet intervals.",
      "Place the dotted notebook texture in one secondary annotation area at very low contrast.",
      "Use pale butter as an annotation highlight behind text snippets or small note chips."
    ],
    "dont": [
      "Do not create a rainbow palette, colored side rails, card stripes, button stripes, or confetti accents.",
      "Do not use square grid backgrounds or make the dotted point texture a global page motif.",
      "Do not turn the embodiment into a generic SaaS dashboard or swatch catalog.",
      "Do not add extra vivid accent colors; use opacity, tint, shade, and hierarchy instead."
    ]
  }
}
related

More like this