Indigo Turquoise Pixel Data Product Language
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.
specification
philosophy
tokens
borders4 items
- accent width
- 2px
- character
- committed single-geometry hairlines with turquoise focus outlines and tiny inset pixel nodes rather than uneven or chipped edges
- default width
- 1px
- style
- solid
colors12 items
motion3 items
- duration
- 180ms
- easing
- cubic-bezier(0.2, 0.8, 0.2, 1)
- philosophy
- micro-interactions step through two or three pixel states, then settle into soft product motion; no arcade blinking or excessive neon pulses
radii5 items
- full
- 9999px
- lg
- 18px
- md
- 12px
- none
- 0
- sm
- 8px
shadows3 items
- lg
- 0 28px 70px rgba(16,24,40,0.14)
- md
- 0 14px 34px rgba(43,47,174,0.10)
- sm
- 0 1px 2px rgba(16,24,40,0.06)
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
surfaces3 items
- bg pattern
- none by default; occasional single-row pixel register strips may appear inside components to express sequence status
- card style
- large rounded white panels with single neutral hairline borders, inner cyan focus glints only when active, and no decorative side stripes
- treatment
- clean white and mist-neutral planes with no dotted or square-grid background; depth comes from hairlines, inset cyan glows, and measured shadows
typography8 items
- base size
- 16px
- body font
- Inter
- google fonts url
- https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&family=Space+Grotesk:wght@500;600;700&family=Handjet:wght@500;600;700&display=swap
- heading font
- Space Grotesk
- letter spacing
- -0.02em
- line height
- 1.5
- mono font
- Handjet
- scale ratio
- 1.25
rules
Use spacious product-shell layouts with a white hero workspace, indigo navigation capsules, and turquoise sequence connectors embedded within task flows rather than generic dashboard chart walls.
Balanced product density: roomy outer whitespace, compact data modules, and scannable rows with 12-16px gaps so pixel detail reads as precision rather than clutter.
Headlines use Space Grotesk weight and size contrast; operational metadata uses Handjet in short uppercase bursts; important state is communicated by placement, label, and pixel register count before color.
layout
mobile 375px, tablet 768px, desktop 1200px, wide 1440px
Asymmetric product workspace: 12-column desktop with a 280px context column and fluid main canvas; tablet collapses to two stacked zones; mobile becomes a single-column task rail.
Outer whitespace is generous and neutral; internal rhythm uses 8px increments with 24px panel padding and compact 8px pixel-register gaps.
guidance
- Use indigo for depth/selection, turquoise for active data edges, and lime only for verified or newly changed micro-states.
- Keep pixel type to labels, counters, badges, and code-like annotations; use Inter for body text and Space Grotesk for premium headings.
- Make pixel motifs functional: sequence, status, focus, loading, version, freshness, and verification.
- Default to clean white/neutral surfaces with no dotted texture and never square-grid backgrounds.
- Do not use decorative side rails, left stripes, chipped corners, uneven borders, or arbitrary mixed radii.
- Do not turn the system into retro arcade, Minecraft/block overload, terminal hacker UI, or neon cyberpunk.
- Do not use generic dashboard chart panels as the main proof; prefer workflow, data operations, and product state scenes.
- Do not add rainbow sprawl or warm accent colors outside true error and warning semantics.
katagami spec
# Indigo Turquoise Pixel Data Product Language ## Philosophy A premium product UI language where white Apple-like surfaces are organized by indigo depth, turquoise live-data edges, and tiny lime verification pixels. Pixel forms act as registers, sequence marks, counters, and focus states rather than nostalgic game decoration. ### Values - Cool-electric color discipline with indigo and turquoise as the primary relationship - Pixel motifs that encode status, order, and precision instead of ornament - Readable premium typography with pixel-influenced accents only at labels and numerals - Calm white/neutral product surfaces that make data states feel exact and trustworthy ### Anti-Values - No square-grid backgrounds, default dotted textures, arcade skins, or terminal hacker clichés - No side rails/card stripes, chipped corners, uneven borders, or color garnish detached from meaning - No rainbow palette or unrelated warm accents except semantic warning/error states ### Visual Character - White and near-white surfaces use broad 18px rounded rectangles, one-pixel neutral hairlines, and soft downward shadows to preserve an Apple-like product feel. - Indigo appears as compressed header capsules, selected text, and deep inline data wells while turquoise is reserved for live borders, focus rings, and connected sequence paths. - Tiny 3px and 6px square pixel registers sit inside badges, progress steps, counters, and button state indicators, never as a repeated background grid. - Pixel-influenced typography is limited to uppercase labels, short code annotations, badge counters, and display numerals while body copy stays in a polished geometric sans. - Lime/yellow-green is used only for verified, ready, or newly changed states as small luminous squares, ticks, and numeric deltas against the cool indigo-cyan system. ## Tokens ### Borders - **Accent Width**: 2px - **Character**: committed single-geometry hairlines with turquoise focus outlines and tiny inset pixel nodes rather than uneven or chipped edges - **Default Width**: 1px - **Style**: solid ### Colors | Name | Value | |------|-------| | accent | `#C8FF2E` | | background | `#F7F9FC` | | border | `#D8E1EC` | | error | `#D92D20` | | info | `#0BA5EC` | | muted | `#667085` | | primary | `#2B2FAE` | | secondary | `#00B8D9` | | success | `#12B76A` | | surface | `#FFFFFF` | | text | `#101828` | | warning | `#F79009` | ### Motion - **Duration**: 180ms - **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1) - **Philosophy**: micro-interactions step through two or three pixel states, then settle into soft product motion; no arcade blinking or excessive neon pulses ### Radii - **Full**: 9999px - **Lg**: 18px - **Md**: 12px - **None**: 0 - **Sm**: 8px ### Shadows - **Lg**: 0 28px 70px rgba(16,24,40,0.14) - **Md**: 0 14px 34px rgba(43,47,174,0.10) - **Sm**: 0 1px 2px rgba(16,24,40,0.06) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Bg Pattern**: none by default; occasional single-row pixel register strips may appear inside components to express sequence status - **Card Style**: large rounded white panels with single neutral hairline borders, inner cyan focus glints only when active, and no decorative side stripes - **Treatment**: clean white and mist-neutral planes with no dotted or square-grid background; depth comes from hairlines, inset cyan glows, and measured shadows ### Typography - **Base Size**: 16px - **Body Font**: Inter - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&family=Space+Grotesk:wght@500;600;700&family=Handjet:wght@500;600;700&display=swap - **Heading Font**: Space Grotesk - **Letter Spacing**: -0.02em - **Line Height**: 1.5 - **Mono Font**: Handjet - **Scale Ratio**: 1.25 ## Rules ### Composition Use spacious product-shell layouts with a white hero workspace, indigo navigation capsules, and turquoise sequence connectors embedded within task flows rather than generic dashboard chart walls. ### Density Balanced product density: roomy outer whitespace, compact data modules, and scannable rows with 12-16px gaps so pixel detail reads as precision rather than clutter. ### Hierarchy Headlines use Space Grotesk weight and size contrast; operational metadata uses Handjet in short uppercase bursts; important state is communicated by placement, label, and pixel register count before color. ### Signature Patterns - Pixel register strips: short inline runs of 3px or 6px squares inside badges, toggles, and rows communicate stage, freshness, or verification without becoming a background grid. - Turquoise live edge: active inputs, selected tabs, and draggable modules use a 2px cyan outline plus a tiny corner pixel node instead of side rails or colored stripes. - Indigo data wells: high-priority summaries use rounded indigo capsules with white text, Handjet numerals, and lime verification pixels for ready states. - Sequence bead connectors: multi-step product flows connect modules with slim cyan lines and isolated square beads, avoiding chart-like dashboard tropes. - Pixel numerals as accents: counters and deltas use Handjet with generous tracking while all body and explanatory text remains Inter for premium readability. ## Layout ### Breakpoints mobile 375px, tablet 768px, desktop 1200px, wide 1440px ### Grid Asymmetric product workspace: 12-column desktop with a 280px context column and fluid main canvas; tablet collapses to two stacked zones; mobile becomes a single-column task rail. ### Whitespace Outer whitespace is generous and neutral; internal rhythm uses 8px increments with 24px panel padding and compact 8px pixel-register gaps. ## Guidance ### Do - Use indigo for depth/selection, turquoise for active data edges, and lime only for verified or newly changed micro-states. - Keep pixel type to labels, counters, badges, and code-like annotations; use Inter for body text and Space Grotesk for premium headings. - Make pixel motifs functional: sequence, status, focus, loading, version, freshness, and verification. - Default to clean white/neutral surfaces with no dotted texture and never square-grid backgrounds. ### Don't - Do not use decorative side rails, left stripes, chipped corners, uneven borders, or arbitrary mixed radii. - Do not turn the system into retro arcade, Minecraft/block overload, terminal hacker UI, or neon cyberpunk. - Do not use generic dashboard chart panels as the main proof; prefer workflow, data operations, and product state scenes. - Do not add rainbow sprawl or warm accent colors outside true error and warning semantics.
DESIGN.md
---
version: "alpha"
name: "Indigo Turquoise Pixel Data Product Language"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
accent: "#C8FF2E"
background: "#F7F9FC"
border: "#D8E1EC"
error: "#D92D20"
info: "#0BA5EC"
muted: "#667085"
primary: "#2B2FAE"
secondary: "#00B8D9"
success: "#12B76A"
surface: "#FFFFFF"
text: "#101828"
warning: "#F79009"
typography:
headline-lg:
fontFamily: "Space Grotesk"
fontSize: "1.953rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.02em"
headline-md:
fontFamily: "Space Grotesk"
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: "Handjet"
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"
---
# Indigo Turquoise Pixel Data Product Language
## Overview
A premium product UI language where white Apple-like surfaces are organized by indigo depth, turquoise live-data edges, and tiny lime verification pixels. Pixel forms act as registers, sequence marks, counters, and focus states rather than nostalgic game decoration.
### Values
- Cool-electric color discipline with indigo and turquoise as the primary relationship
- Pixel motifs that encode status, order, and precision instead of ornament
- Readable premium typography with pixel-influenced accents only at labels and numerals
- Calm white/neutral product surfaces that make data states feel exact and trustworthy
### Anti-Values
- No square-grid backgrounds, default dotted textures, arcade skins, or terminal hacker clichés
- No side rails/card stripes, chipped corners, uneven borders, or color garnish detached from meaning
- No rainbow palette or unrelated warm accents except semantic warning/error states
### Visual Character
- White and near-white surfaces use broad 18px rounded rectangles, one-pixel neutral hairlines, and soft downward shadows to preserve an Apple-like product feel.
- Indigo appears as compressed header capsules, selected text, and deep inline data wells while turquoise is reserved for live borders, focus rings, and connected sequence paths.
- Tiny 3px and 6px square pixel registers sit inside badges, progress steps, counters, and button state indicators, never as a repeated background grid.
- Pixel-influenced typography is limited to uppercase labels, short code annotations, badge counters, and display numerals while body copy stays in a polished geometric sans.
- Lime/yellow-green is used only for verified, ready, or newly changed states as small luminous squares, ticks, and numeric deltas against the cool indigo-cyan system.
## 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 | `#C8FF2E` |
| background | `#F7F9FC` |
| border | `#D8E1EC` |
| error | `#D92D20` |
| info | `#0BA5EC` |
| muted | `#667085` |
| primary | `#2B2FAE` |
| secondary | `#00B8D9` |
| success | `#12B76A` |
| surface | `#FFFFFF` |
| text | `#101828` |
| warning | `#F79009` |
## Typography
- **Headline-Lg**: Space Grotesk, 1.953rem, weight 700, line-height 1.1.
- **Headline-Md**: Space Grotesk, 1.563rem, weight 600, line-height 1.15.
- **Body-Md**: Inter, 16px, weight 400, line-height 1.5.
- **Label-Md**: Handjet, 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, tablet 768px, desktop 1200px, wide 1440px
### Grid
Asymmetric product workspace: 12-column desktop with a 280px context column and fluid main canvas; tablet collapses to two stacked zones; mobile becomes a single-column task rail.
### Whitespace
Outer whitespace is generous and neutral; internal rhythm uses 8px increments with 24px panel padding and compact 8px pixel-register gaps.
## Elevation & Depth
### Shadows
- **Lg**: 0 28px 70px rgba(16,24,40,0.14)
- **Md**: 0 14px 34px rgba(43,47,174,0.10)
- **Sm**: 0 1px 2px rgba(16,24,40,0.06)
## Shapes
### Rounded
- **Full**: `9999px`
- **Lg**: `18px`
- **Md**: `12px`
- **None**: `0px`
- **Sm**: `8px`
### Surfaces
- **Bg Pattern**: none by default; occasional single-row pixel register strips may appear inside components to express sequence status
- **Card Style**: large rounded white panels with single neutral hairline borders, inner cyan focus glints only when active, and no decorative side stripes
- **Treatment**: clean white and mist-neutral planes with no dotted or square-grid background; depth comes from hairlines, inset cyan glows, and measured shadows
### Borders
- **Accent Width**: 2px
- **Character**: committed single-geometry hairlines with turquoise focus outlines and tiny inset pixel nodes rather than uneven or chipped edges
- **Default Width**: 1px
- **Style**: solid
## Components
### Composition
Use spacious product-shell layouts with a white hero workspace, indigo navigation capsules, and turquoise sequence connectors embedded within task flows rather than generic dashboard chart walls.
### Density
Balanced product density: roomy outer whitespace, compact data modules, and scannable rows with 12-16px gaps so pixel detail reads as precision rather than clutter.
### Hierarchy
Headlines use Space Grotesk weight and size contrast; operational metadata uses Handjet in short uppercase bursts; important state is communicated by placement, label, and pixel register count before color.
### Signature Patterns
- Pixel register strips: short inline runs of 3px or 6px squares inside badges, toggles, and rows communicate stage, freshness, or verification without becoming a background grid.
- Turquoise live edge: active inputs, selected tabs, and draggable modules use a 2px cyan outline plus a tiny corner pixel node instead of side rails or colored stripes.
- Indigo data wells: high-priority summaries use rounded indigo capsules with white text, Handjet numerals, and lime verification pixels for ready states.
- Sequence bead connectors: multi-step product flows connect modules with slim cyan lines and isolated square beads, avoiding chart-like dashboard tropes.
- Pixel numerals as accents: counters and deltas use Handjet with generous tracking while all body and explanatory text remains Inter for premium readability.
## 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-019e4bf6-d397-7a11-ac6b-49798ba839ed/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 indigo for depth/selection, turquoise for active data edges, and lime only for verified or newly changed micro-states.
- Do Keep pixel type to labels, counters, badges, and code-like annotations; use Inter for body text and Space Grotesk for premium headings.
- Do Make pixel motifs functional: sequence, status, focus, loading, version, freshness, and verification.
- Do Default to clean white/neutral surfaces with no dotted texture and never square-grid backgrounds.
- Don't Do not use decorative side rails, left stripes, chipped corners, uneven borders, or arbitrary mixed radii.
- Don't Do not turn the system into retro arcade, Minecraft/block overload, terminal hacker UI, or neon cyberpunk.
- Don't Do not use generic dashboard chart panels as the main proof; prefer workflow, data operations, and product state scenes.
- Don't Do not add rainbow sprawl or warm accent colors outside true error and warning semantics.
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "indigo-turquoise-pixel-data-product-language",
"type": "registry:theme",
"title": "Indigo Turquoise Pixel Data Product Language shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#F7F9FC",
"foreground": "#101828",
"card": "#FFFFFF",
"card-foreground": "#101828",
"popover": "#FFFFFF",
"popover-foreground": "#101828",
"primary": "#2B2FAE",
"primary-foreground": "#ffffff",
"secondary": "#00B8D9",
"secondary-foreground": "#ffffff",
"muted": "#667085",
"muted-foreground": "#101828",
"accent": "#C8FF2E",
"accent-foreground": "#111111",
"destructive": "#D92D20",
"border": "#D8E1EC",
"input": "#D8E1EC",
"ring": "#C8FF2E",
"chart-1": "#2B2FAE",
"chart-2": "#00B8D9",
"chart-3": "#C8FF2E",
"chart-4": "#12B76A",
"chart-5": "#F79009",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#101828",
"sidebar-primary": "#2B2FAE",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#0BA5EC",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#D8E1EC",
"sidebar-ring": "#C8FF2E",
"radius": "12px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#2B2FAE",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#C8FF2E",
"accent-foreground": "#111111",
"destructive": "#D92D20",
"border": "#303642",
"input": "#303642",
"ring": "#C8FF2E",
"chart-1": "#2B2FAE",
"chart-2": "#00B8D9",
"chart-3": "#C8FF2E",
"chart-4": "#12B76A",
"chart-5": "#F79009",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#2B2FAE",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#C8FF2E",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#C8FF2E",
"radius": "12px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019e4bf6-d397-7a11-ac6b-49798ba839ed",
"slug": "indigo-turquoise-pixel-data-product-language",
"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"
]
}
}
}
```embodiments
at a glance
Typography
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
Components
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
implementation kit
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
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #F7F9FC;
--foreground: #101828;
--card: #FFFFFF;
--card-foreground: #101828;
--popover: #FFFFFF;
--popover-foreground: #101828;
--primary: #2B2FAE;
--primary-foreground: #ffffff;
--secondary: #00B8D9;
--secondary-foreground: #ffffff;
--muted: #667085;
--muted-foreground: #101828;
--accent: #C8FF2E;
--accent-foreground: #111111;
--destructive: #D92D20;
--border: #D8E1EC;
--input: #D8E1EC;
--ring: #C8FF2E;
--chart-1: #2B2FAE;
--chart-2: #00B8D9;
--chart-3: #C8FF2E;
--chart-4: #12B76A;
--chart-5: #F79009;
--sidebar: #FFFFFF;
--sidebar-foreground: #101828;
--sidebar-primary: #2B2FAE;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #0BA5EC;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #D8E1EC;
--sidebar-ring: #C8FF2E;
--radius: 12px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #2B2FAE;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #C8FF2E;
--accent-foreground: #111111;
--destructive: #D92D20;
--border: #303642;
--input: #303642;
--ring: #C8FF2E;
--chart-1: #2B2FAE;
--chart-2: #00B8D9;
--chart-3: #C8FF2E;
--chart-4: #12B76A;
--chart-5: #F79009;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #2B2FAE;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #C8FF2E;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #C8FF2E;
--radius: 12px;
}
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 IndigoTurquoisePixelDataProductLanguageShadcnKit() {
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">Indigo Turquoise Pixel Data Product Language</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>
);
}
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"cssVars": {
"dark": {
"accent": "#C8FF2E",
"accent-foreground": "#111111",
"background": "#0f1115",
"border": "#303642",
"card": "#181b22",
"card-foreground": "#f8fafc",
"chart-1": "#2B2FAE",
"chart-2": "#00B8D9",
"chart-3": "#C8FF2E",
"chart-4": "#12B76A",
"chart-5": "#F79009",
"destructive": "#D92D20",
"foreground": "#f8fafc",
"input": "#303642",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#2B2FAE",
"primary-foreground": "#ffffff",
"radius": "12px",
"ring": "#C8FF2E",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"sidebar": "#181b22",
"sidebar-accent": "#C8FF2E",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#2B2FAE",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#C8FF2E"
},
"light": {
"accent": "#C8FF2E",
"accent-foreground": "#111111",
"background": "#F7F9FC",
"border": "#D8E1EC",
"card": "#FFFFFF",
"card-foreground": "#101828",
"chart-1": "#2B2FAE",
"chart-2": "#00B8D9",
"chart-3": "#C8FF2E",
"chart-4": "#12B76A",
"chart-5": "#F79009",
"destructive": "#D92D20",
"foreground": "#101828",
"input": "#D8E1EC",
"muted": "#667085",
"muted-foreground": "#101828",
"popover": "#FFFFFF",
"popover-foreground": "#101828",
"primary": "#2B2FAE",
"primary-foreground": "#ffffff",
"radius": "12px",
"ring": "#C8FF2E",
"secondary": "#00B8D9",
"secondary-foreground": "#ffffff",
"sidebar": "#FFFFFF",
"sidebar-accent": "#0BA5EC",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#D8E1EC",
"sidebar-foreground": "#101828",
"sidebar-primary": "#2B2FAE",
"sidebar-primary-foreground": "#ffffff",
"sidebar-ring": "#C8FF2E"
},
"theme": {}
},
"meta": {
"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",
"languageId": "en-019e4bf6-d397-7a11-ac6b-49798ba839ed",
"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"
]
},
"slug": "indigo-turquoise-pixel-data-product-language",
"source": "katagami"
},
"name": "indigo-turquoise-pixel-data-product-language",
"title": "Indigo Turquoise Pixel Data Product Language shadcn Theme",
"type": "registry:theme"
}
# Indigo Turquoise Pixel Data Product Language shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019e4bf6-d397-7a11-ac6b-49798ba839ed`
Slug: `indigo-turquoise-pixel-data-product-language`
## Intent
A premium product UI language where white Apple-like surfaces are organized by indigo depth, turquoise live-data edges, and tiny lime verification pixels. Pixel forms act as registers, sequence marks, counters, and focus states rather than nostalgic game decoration.
## 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": "#C8FF2E",
"background": "#F7F9FC",
"border": "#D8E1EC",
"error": "#D92D20",
"info": "#0BA5EC",
"muted": "#667085",
"primary": "#2B2FAE",
"secondary": "#00B8D9",
"success": "#12B76A",
"surface": "#FFFFFF",
"text": "#101828",
"warning": "#F79009"
}
Typography:
{
"base_size": "16px",
"body_font": "Inter",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700;800&family=Space+Grotesk:wght@500;600;700&family=Handjet:wght@500;600;700&display=swap",
"heading_font": "Space Grotesk",
"letter_spacing": "-0.02em",
"line_height": 1.5,
"mono_font": "Handjet",
"scale_ratio": 1.25
}
## Visual character to preserve
- White and near-white surfaces use broad 18px rounded rectangles, one-pixel neutral hairlines, and soft downward shadows to preserve an Apple-like product feel.
- Indigo appears as compressed header capsules, selected text, and deep inline data wells while turquoise is reserved for live borders, focus rings, and connected sequence paths.
- Tiny 3px and 6px square pixel registers sit inside badges, progress steps, counters, and button state indicators, never as a repeated background grid.
- Pixel-influenced typography is limited to uppercase labels, short code annotations, badge counters, and display numerals while body copy stays in a polished geometric sans.
- Lime/yellow-green is used only for verified, ready, or newly changed states as small luminous squares, ticks, and numeric deltas against the cool indigo-cyan system.
## ShadSync visual profile
{
"family": "system",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": false,
"stickerBadges": true,
"motion": "still",
"density": "balanced",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
}
## Signature component recipes
### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.
### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.
### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.
### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.
### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.
## Preview shots
- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.
## Implementation contract
- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/indigo-turquoise-pixel-data-product-language/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 indigo for depth/selection, turquoise for active data edges, and lime only for verified or newly changed micro-states.; Keep pixel type to labels, counters, badges, and code-like annotations; use Inter for body text and Space Grotesk for premium headings.; Make pixel motifs functional: sequence, status, focus, loading, version, freshness, and verification.; Default to clean white/neutral surfaces with no dotted texture and never square-grid backgrounds.
- Do not: Do not use decorative side rails, left stripes, chipped corners, uneven borders, or arbitrary mixed radii.; Do not turn the system into retro arcade, Minecraft/block overload, terminal hacker UI, or neon cyberpunk.; Do not use generic dashboard chart panels as the main proof; prefer workflow, data operations, and product state scenes.; Do not add rainbow sprawl or warm accent colors outside true error and warning semantics.
## 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 IndigoTurquoisePixelDataProductLanguageShadcnKit() {
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">Indigo Turquoise Pixel Data Product Language</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
```
## Layout notes
{
"breakpoints": "mobile 375px, tablet 768px, desktop 1200px, wide 1440px",
"grid": "Asymmetric product workspace: 12-column desktop with a 280px context column and fluid main canvas; tablet collapses to two stacked zones; mobile becomes a single-column task rail.",
"whitespace": "Outer whitespace is generous and neutral; internal rhythm uses 8px increments with 24px panel padding and compact 8px pixel-register gaps."
}
{
"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-019e4bf6-d397-7a11-ac6b-49798ba839ed",
"name": "Indigo Turquoise Pixel Data Product Language",
"slug": "indigo-turquoise-pixel-data-product-language"
},
"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": [
"White and near-white surfaces use broad 18px rounded rectangles, one-pixel neutral hairlines, and soft downward shadows to preserve an Apple-like product feel.",
"Indigo appears as compressed header capsules, selected text, and deep inline data wells while turquoise is reserved for live borders, focus rings, and connected sequence paths.",
"Tiny 3px and 6px square pixel registers sit inside badges, progress steps, counters, and button state indicators, never as a repeated background grid.",
"Pixel-influenced typography is limited to uppercase labels, short code annotations, badge counters, and display numerals while body copy stays in a polished geometric sans.",
"Lime/yellow-green is used only for verified, ready, or newly changed states as small luminous squares, ticks, and numeric deltas against the cool indigo-cyan system."
],
"visualProfile": {
"family": "system",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": false,
"stickerBadges": true,
"motion": "still",
"density": "balanced",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
},
"shots": [
{
"id": "application-shell",
"title": "Application shell",
"viewport": "desktop",
"primitives": [
"button",
"card",
"input",
"select",
"tabs",
"badge",
"separator",
"table"
],
"composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
"mustShow": [
"primary and secondary actions",
"card hierarchy",
"filterable state",
"table or list density"
],
"avoid": [
"component inventory walls",
"placeholder-only content",
"generic rounded SaaS chrome"
],
"scene": {
"eyebrow": "workspace spread",
"headline": "Indigo Turquoise Pixel Data Product Language 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 indigo for depth/selection, turquoise for active data edges, and lime only for verified or newly changed micro-states.",
"Keep pixel type to labels, counters, badges, and code-like annotations; use Inter for body text and Space Grotesk for premium headings.",
"Make pixel motifs functional: sequence, status, focus, loading, version, freshness, and verification.",
"Default to clean white/neutral surfaces with no dotted texture and never square-grid backgrounds."
],
"dont": [
"Do not use decorative side rails, left stripes, chipped corners, uneven borders, or arbitrary mixed radii.",
"Do not turn the system into retro arcade, Minecraft/block overload, terminal hacker UI, or neon cyberpunk.",
"Do not use generic dashboard chart panels as the main proof; prefer workflow, data operations, and product state scenes.",
"Do not add rainbow sprawl or warm accent colors outside true error and warning semantics."
]
}
}