A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.
Portable DESIGN.md source of truth for most agents and apps.
Lead with a focal reveal inside a key-light charge frame; surround it with framed islands that read like a HUD. Keep the most important action staged with a single key-light CTA, never a button pair as default furniture.
Hierarchy comes from the key light, frame state, and reveal scale before pure text size. Supporting data is tiered through chips, segmented spark meters and mono cues. State is told by which accent glows: cyan charging, magenta priority, gold complete.
High density organised into legible islands inside one frame: one focal reveal, a few support frames, and micro-status chips and meters within them. Dark stage space is reserved for the key-light glow, not neutral whitespace.
The charge frame (key-light corner bracket), the spark meter (segmented bar with a gold fill-edge spark), and the lifted reveal (focal portrait breaking the frame under a key-light rim).
A contained max-width stage (1200-1320px) with full-bleed hero. Desktop runs multi-column frame grids; tablet drops to two columns; mobile stacks to a single dramatic scroll.
Theatrical: pockets of dark stage and key-glow around the focal frame, tight spacing inside dense data islands, generous padding above every title.
high
From ~390px to 2560px+. Single column on mobile with a wrapping nav; the full-bleed hero re-anchors so the figure stays legible behind a vertical stage-darkening; headlines shrink with clamp() and wrap, never clipping the 390px edge.
keylight-cel-anime
Bold cel-anime / screen-native digital illustration — flat saturated cels, one dramatic key light, rim-lit silhouettes, radiating speed-streaks and sparkle blooms on a near-black ground.
Landing hero is a full-bleed cel-anime key visual with the figure off-centre and open dark stage for the overlay; lifted-reveal cut-ins use tight portrait crops with a cyan key-rim.
# Limelight ## Philosophy Limelight treats the interface as a charged reveal. It stages an app the way a relay race stages its runners: every focal surface sits in a key-light charge frame, progress builds as a spark meter, and the most important content is lifted into view the moment it is ready. It keeps the cinematic drama of an anime spectacle screen and drops the gacha kitsch, metallic double-frames, and glassy violet wash. ### Values - Cinematic hierarchy led by a focal reveal, not by text size alone - Intensity encoded by light: cyan charging, magenta priority, gold complete - Progress staged as a charge-up with a spark at the fill edge - A deep cinema-stage ground that lets a few accents glow like screen light - Dense but legible HUD islands inside one frame, never stacked grey boxes ### Anti-Values - Metallic double-framed panels and jewel-corner ornament - Glassy violet star-noise surfaces and grey-bordered boxes - Boxed nav pills and floating widget chrome - Condensed sci-fi display faces and the eyebrow + two-button + stat-row hero - Flat enterprise neutrality that removes all drama ### Visual Character - Charge frames: a single key light wraps one corner of a focal surface and glows in the state accent - Spark meters: segmented charge bars that throw a gold spark at the fill edge - Lifted reveal: a cel-anime portrait breaks out past its frame under a key-light rim - Intensity-coded chips, avatar key-rims and meters that recolour cyan, magenta, or gold - A deep near-black cinema-stage ground washed by a faint cyan key-glow ## Tokens ### Colors | Name | Value | |------|-------| | bg | `#0B0A12` | | surface | `#15131F` | | surface_2 | `#1E1B2C` | | text | `#F4F1FA` | | muted | `#A39FBC` | | border | `#2A2740` | | accent | `#2BE5FF` | | accent_2 | `#FF3D8B` | | accent_3 | `#FFC24B` | | on_accent | `#06121A` | | success | `#43E6A2` | | warning | `#FFC24B` | | error | `#FF5C6E` | | info | `#2BE5FF` | ### Typography - **Base Size**: 17px - **Body Font**: Inter - **Heading Font**: Space Grotesk - **Mono Font**: JetBrains Mono - **Heading Weight**: 700 - **Heading Transform**: none - **Letter Spacing**: -0.03em - **Line Height**: 1.55 - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Space+Grotesk:wght@400;500;600;700&family=Inter:wght@400;500;600&family=JetBrains+Mono:wght@400;500;700&display=swap ### Radii - **None**: 0 - **Md**: 16px - **Lg**: 24px - **Full**: 9999px ### Shadows - **Key**: 0 24px 60px -36px rgba(0,0,0,.85) - **Lift**: 0 14px 34px -12px rgba(43,229,255,.7) - **Sm**: 0 1px 0 rgba(255,255,255,.03) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64,96] ### Surfaces - **Ground**: deep cinema-stage near-black - **Card Style**: charge frame with key-light corner bracket - **Treatment**: depth-shadow, no borders ### Borders - **Style**: none - **Character**: no decorative borders; the only edges are key-light corner brackets that encode state ### Motion - **Duration**: 300ms - **Easing**: cubic-bezier(.16,.84,.3,1) - **Philosophy**: reveals and charge-ups, settled-by-default behind an html.anim gate ## Rules ### Composition Lead with a focal reveal inside a key-light charge frame; surround it with framed islands that read like a HUD. Keep the most important action staged with a single key-light CTA, never a button pair as default furniture. ### Hierarchy Hierarchy comes from the key light, frame state, and reveal scale before pure text size. Supporting data is tiered through chips, segmented spark meters and mono cues. State is told by which accent glows: cyan charging, magenta priority, gold complete. ### Density High density organised into legible islands inside one frame: one focal reveal, a few support frames, and micro-status chips and meters within them. Dark stage space is reserved for the key-light glow, not neutral whitespace. ### Signature The charge frame (key-light corner bracket), the spark meter (segmented bar with a gold fill-edge spark), and the lifted reveal (focal portrait breaking the frame under a key-light rim). ## Layout ### Grid A contained max-width stage (1200-1320px) with full-bleed hero. Desktop runs multi-column frame grids; tablet drops to two columns; mobile stacks to a single dramatic scroll. ### Whitespace Theatrical: pockets of dark stage and key-glow around the focal frame, tight spacing inside dense data islands, generous padding above every title. ### Density high ### Responsive From ~390px to 2560px+. Single column on mobile with a wrapping nav; the full-bleed hero re-anchors so the figure stays legible behind a vertical stage-darkening; headlines shrink with clamp() and wrap, never clipping the 390px edge. ### Breakpoints - **Mobile**: 0-619px - **Tablet**: 620-1039px - **Desktop**: 1040px+ ## Guidance ### Do - Use cyan, magenta and gold as highlighters to encode charging, priority and complete - Wrap a focal surface's corner in a key-light bracket; never use a lonely single edge or a grey box - Stage progress as a spark meter with a gold spark at the fill edge - Let a cel-anime portrait break out of its frame for the reveal - Keep the ground a deep cinema-stage near-black so accents glow ### Don't - Do not use metallic double-frames, jewel corners, or glassy violet surfaces - Do not box the nav into a pill bar or float chrome as a widget - Do not open the hero with an eyebrow tag, a button pair, or a three-stat row - Do not swap a regular serif for an italic serif in the headline; use a colour-pop mark - Do not flatten panels into plain grey rectangles or remove the key-light entirely ### Accessibility Body 17px+ on the dark stage with high contrast; never encode meaning in accent colour alone (pair every accent with a label or chip text); focus rings glow in the key light; respect prefers-reduced-motion. ## Imagery Direction ### Pairs With keylight-cel-anime ### Summary Bold cel-anime / screen-native digital illustration — flat saturated cels, one dramatic key light, rim-lit silhouettes, radiating speed-streaks and sparkle blooms on a near-black ground. ### Subjects - relay runners and couriers at the moment of a reveal - night-harbor cityscapes - leaping koi - hero objects under a key light ### Usage Landing hero is a full-bleed cel-anime key visual with the figure off-centre and open dark stage for the overlay; lifted-reveal cut-ins use tight portrait crops with a cyan key-rim.
---
version: "alpha"
name: "Limelight"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
bg: "#0B0A12"
surface: "#15131F"
surface_2: "#1E1B2C"
text: "#F4F1FA"
muted: "#A39FBC"
border: "#2A2740"
accent: "#2BE5FF"
accent_2: "#FF3D8B"
accent_3: "#FFC24B"
on_accent: "#06121A"
success: "#43E6A2"
warning: "#FFC24B"
error: "#FF5C6E"
info: "#2BE5FF"
typography:
headline-lg:
fontFamily: "Space Grotesk"
fontSize: "2.075rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "-0.03em"
headline-md:
fontFamily: "Space Grotesk"
fontSize: "1.66rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "-0.03em"
body-md:
fontFamily: "Inter"
fontSize: "17px"
fontWeight: 400
lineHeight: 1.55
letterSpacing: "-0.03em"
label-md:
fontFamily: "JetBrains Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
none: "0px"
md: "16px"
lg: "24px"
full: "9999px"
spacing:
base: "8px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
step-8: "96px"
components:
color-reference-bg:
backgroundColor: "{colors.bg}"
color-reference-surface:
backgroundColor: "{colors.surface}"
color-reference-surface_2:
backgroundColor: "{colors.surface_2}"
color-reference-text:
backgroundColor: "{colors.text}"
color-reference-muted:
backgroundColor: "{colors.muted}"
color-reference-border:
backgroundColor: "{colors.border}"
color-reference-accent:
backgroundColor: "{colors.accent}"
color-reference-accent_2:
backgroundColor: "{colors.accent_2}"
color-reference-accent_3:
backgroundColor: "{colors.accent_3}"
color-reference-on_accent:
backgroundColor: "{colors.on_accent}"
color-reference-success:
backgroundColor: "{colors.success}"
color-reference-warning:
backgroundColor: "{colors.warning}"
color-reference-error:
backgroundColor: "{colors.error}"
color-reference-info:
backgroundColor: "{colors.info}"
button-primary:
backgroundColor: "{colors.accent}"
textColor: "#000000"
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"
---
# Limelight
## Overview
Limelight treats the interface as a charged reveal. It stages an app the way a relay race stages its runners: every focal surface sits in a key-light charge frame, progress builds as a spark meter, and the most important content is lifted into view the moment it is ready. It keeps the cinematic drama of an anime spectacle screen and drops the gacha kitsch, metallic double-frames, and glassy violet wash.
### Values
- Cinematic hierarchy led by a focal reveal, not by text size alone
- Intensity encoded by light: cyan charging, magenta priority, gold complete
- Progress staged as a charge-up with a spark at the fill edge
- A deep cinema-stage ground that lets a few accents glow like screen light
- Dense but legible HUD islands inside one frame, never stacked grey boxes
### Anti-Values
- Metallic double-framed panels and jewel-corner ornament
- Glassy violet star-noise surfaces and grey-bordered boxes
- Boxed nav pills and floating widget chrome
- Condensed sci-fi display faces and the eyebrow + two-button + stat-row hero
- Flat enterprise neutrality that removes all drama
### Visual Character
- Charge frames: a single key light wraps one corner of a focal surface and glows in the state accent
- Spark meters: segmented charge bars that throw a gold spark at the fill edge
- Lifted reveal: a cel-anime portrait breaks out past its frame under a key-light rim
- Intensity-coded chips, avatar key-rims and meters that recolour cyan, magenta, or gold
- A deep near-black cinema-stage ground washed by a faint cyan key-glow
## Colors
Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.
| Token | Value |
|-------|-------|
| bg | `#0B0A12` |
| surface | `#15131F` |
| surface_2 | `#1E1B2C` |
| text | `#F4F1FA` |
| muted | `#A39FBC` |
| border | `#2A2740` |
| accent | `#2BE5FF` |
| accent_2 | `#FF3D8B` |
| accent_3 | `#FFC24B` |
| on_accent | `#06121A` |
| success | `#43E6A2` |
| warning | `#FFC24B` |
| error | `#FF5C6E` |
| info | `#2BE5FF` |
## Typography
- **Headline-Lg**: Space Grotesk, 2.075rem, weight 700, line-height 1.1.
- **Headline-Md**: Space Grotesk, 1.66rem, weight 600, line-height 1.15.
- **Body-Md**: Inter, 17px, weight 400, line-height 1.55.
- **Label-Md**: JetBrains Mono, 0.75rem, weight 600, line-height 1.
## Layout
### Spacing Tokens
- **Base**: `8px`
- **Xs**: `4px`
- **Sm**: `8px`
- **Md**: `12px`
- **Lg**: `16px`
- **Xl**: `24px`
- **2xl**: `32px`
- **3xl**: `48px`
- **4xl**: `64px`
- **Step-8**: `96px`
### Grid
A contained max-width stage (1200-1320px) with full-bleed hero. Desktop runs multi-column frame grids; tablet drops to two columns; mobile stacks to a single dramatic scroll.
### Whitespace
Theatrical: pockets of dark stage and key-glow around the focal frame, tight spacing inside dense data islands, generous padding above every title.
### Density
high
### Responsive
From ~390px to 2560px+. Single column on mobile with a wrapping nav; the full-bleed hero re-anchors so the figure stays legible behind a vertical stage-darkening; headlines shrink with clamp() and wrap, never clipping the 390px edge.
### Breakpoints
- **Mobile**: 0-619px
- **Tablet**: 620-1039px
- **Desktop**: 1040px+
## Elevation & Depth
### Shadows
- **Key**: 0 24px 60px -36px rgba(0,0,0,.85)
- **Lift**: 0 14px 34px -12px rgba(43,229,255,.7)
- **Sm**: 0 1px 0 rgba(255,255,255,.03)
## Shapes
### Rounded
- **None**: `0px`
- **Md**: `16px`
- **Lg**: `24px`
- **Full**: `9999px`
### Surfaces
- **Ground**: deep cinema-stage near-black
- **Card Style**: charge frame with key-light corner bracket
- **Treatment**: depth-shadow, no borders
### Borders
- **Style**: none
- **Character**: no decorative borders; the only edges are key-light corner brackets that encode state
## Components
### Composition
Lead with a focal reveal inside a key-light charge frame; surround it with framed islands that read like a HUD. Keep the most important action staged with a single key-light CTA, never a button pair as default furniture.
### Hierarchy
Hierarchy comes from the key light, frame state, and reveal scale before pure text size. Supporting data is tiered through chips, segmented spark meters and mono cues. State is told by which accent glows: cyan charging, magenta priority, gold complete.
### Density
High density organised into legible islands inside one frame: one focal reveal, a few support frames, and micro-status chips and meters within them. Dark stage space is reserved for the key-light glow, not neutral whitespace.
### Signature
The charge frame (key-light corner bracket), the spark meter (segmented bar with a gold fill-edge spark), and the lifted reveal (focal portrait breaking the frame under a key-light rim).
## 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-019efda2-dca8-7a32-839a-2c9a95ed64a3/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 cyan, magenta and gold as highlighters to encode charging, priority and complete
- Do Wrap a focal surface's corner in a key-light bracket; never use a lonely single edge or a grey box
- Do Stage progress as a spark meter with a gold spark at the fill edge
- Do Let a cel-anime portrait break out of its frame for the reveal
- Do Keep the ground a deep cinema-stage near-black so accents glow
- Don't Do not use metallic double-frames, jewel corners, or glassy violet surfaces
- Don't Do not box the nav into a pill bar or float chrome as a widget
- Don't Do not open the hero with an eyebrow tag, a button pair, or a three-stat row
- Don't Do not swap a regular serif for an italic serif in the headline; use a colour-pop mark
- Don't Do not flatten panels into plain grey rectangles or remove the key-light entirely
### Accessibility
Body 17px+ on the dark stage with high contrast; never encode meaning in accent colour alone (pair every accent with a label or chip text); focus rings glow in the key light; respect prefers-reduced-motion.
## Imagery Direction
### Pairs With
keylight-cel-anime
### Summary
Bold cel-anime / screen-native digital illustration — flat saturated cels, one dramatic key light, rim-lit silhouettes, radiating speed-streaks and sparkle blooms on a near-black ground.
### Subjects
- relay runners and couriers at the moment of a reveal
- night-harbor cityscapes
- leaping koi
- hero objects under a key light
### Usage
Landing hero is a full-bleed cel-anime key visual with the figure off-centre and open dark stage for the overlay; lifted-reveal cut-ins use tight portrait crops with a cyan key-rim.
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "limelight",
"type": "registry:theme",
"title": "Limelight shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#0B0A12",
"foreground": "#F4F1FA",
"card": "#15131F",
"card-foreground": "#F4F1FA",
"popover": "#15131F",
"popover-foreground": "#F4F1FA",
"primary": "#F4F1FA",
"primary-foreground": "#111111",
"secondary": "#f4f4f5",
"secondary-foreground": "#111111",
"muted": "#A39FBC",
"muted-foreground": "#F4F1FA",
"accent": "#2BE5FF",
"accent-foreground": "#111111",
"destructive": "#FF5C6E",
"border": "#2A2740",
"input": "#2A2740",
"ring": "#2BE5FF",
"chart-1": "#F4F1FA",
"chart-2": "#f4f4f5",
"chart-3": "#2BE5FF",
"chart-4": "#43E6A2",
"chart-5": "#FFC24B",
"sidebar": "#15131F",
"sidebar-foreground": "#F4F1FA",
"sidebar-primary": "#F4F1FA",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#2BE5FF",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#2A2740",
"sidebar-ring": "#2BE5FF",
"radius": "16px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#F4F1FA",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#2BE5FF",
"accent-foreground": "#111111",
"destructive": "#FF5C6E",
"border": "#303642",
"input": "#303642",
"ring": "#2BE5FF",
"chart-1": "#F4F1FA",
"chart-2": "#f4f4f5",
"chart-3": "#2BE5FF",
"chart-4": "#43E6A2",
"chart-5": "#FFC24B",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#F4F1FA",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#2BE5FF",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#2BE5FF",
"radius": "16px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019efda2-dca8-7a32-839a-2c9a95ed64a3",
"slug": "limelight",
"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": {
"colors": [
"accent",
"accent_2",
"accent_3",
"bg",
"border",
"error",
"info",
"muted",
"on_accent",
"success",
"surface",
"surface_2",
"text",
"warning"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"heading_transform",
"heading_weight",
"letter_spacing",
"line_height",
"mono_font"
],
"radii": [
"full",
"lg",
"md",
"none"
],
"shadows": [
"key",
"lift",
"sm"
],
"spacing": [
"base",
"scale"
],
"surfaces": [
"card_style",
"ground",
"treatment"
],
"borders": [
"character",
"style"
],
"motion": [
"duration",
"easing",
"philosophy"
]
}
}
}
```The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
Agent-generated
produced by opus-4.8 · sourced by opus-4.8 · images by gpt-image-2
Keep Limelightand swap a palette and an art style onto it — the landing & dashboard recolor live. The Studio does the same with all three lanes free.
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.
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table:root {
--background: #0B0A12;
--foreground: #F4F1FA;
--card: #15131F;
--card-foreground: #F4F1FA;
--popover: #15131F;
--popover-foreground: #F4F1FA;
--primary: #F4F1FA;
--primary-foreground: #111111;
--secondary: #f4f4f5;
--secondary-foreground: #111111;
--muted: #A39FBC;
--muted-foreground: #F4F1FA;
--accent: #2BE5FF;
--accent-foreground: #111111;
--destructive: #FF5C6E;
--border: #2A2740;
--input: #2A2740;
--ring: #2BE5FF;
--chart-1: #F4F1FA;
--chart-2: #f4f4f5;
--chart-3: #2BE5FF;
--chart-4: #43E6A2;
--chart-5: #FFC24B;
--sidebar: #15131F;
--sidebar-foreground: #F4F1FA;
--sidebar-primary: #F4F1FA;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #2BE5FF;
--sidebar-accent-foreground: #111111;
--sidebar-border: #2A2740;
--sidebar-ring: #2BE5FF;
--radius: 16px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #F4F1FA;
--primary-foreground: #111111;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #2BE5FF;
--accent-foreground: #111111;
--destructive: #FF5C6E;
--border: #303642;
--input: #303642;
--ring: #2BE5FF;
--chart-1: #F4F1FA;
--chart-2: #f4f4f5;
--chart-3: #2BE5FF;
--chart-4: #43E6A2;
--chart-5: #FFC24B;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #F4F1FA;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #2BE5FF;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #2BE5FF;
--radius: 16px;
}
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 LimelightShadcnKit() {
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">Limelight</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",
"name": "limelight",
"type": "registry:theme",
"author": "katagami-agent",
"visualProfile": {
"material": "stage",
"surface": "panels sit on a deep cinema-stage ground; separation is depth-shadow and a key-light corner bracket, never a full border",
"borders": "none",
"radius": "large",
"elevation": "key-light: a single accent wraps one corner of a focal surface (L into the corner) and glows; deep cast shadow lifts panels off the stage",
"accent_use": "highlighter — cyan/magenta/gold mark state on corner brackets, meter fills, chips and avatar rims only, never a flat fill",
"mode": "dark"
},
"cssVars": {
"theme": {
"font-sans": "Inter, system-ui, sans-serif",
"font-display": "Space Grotesk, sans-serif",
"font-mono": "JetBrains Mono, monospace",
"radius": "24px"
},
"light": {
"background": "#0B0A12",
"foreground": "#F4F1FA",
"card": "#15131F",
"card-foreground": "#F4F1FA",
"popover": "#1E1B2C",
"popover-foreground": "#F4F1FA",
"primary": "#2BE5FF",
"primary-foreground": "#06121A",
"secondary": "#1E1B2C",
"secondary-foreground": "#F4F1FA",
"muted": "#1E1B2C",
"muted-foreground": "#A39FBC",
"accent": "#FF3D8B",
"accent-foreground": "#1b0411",
"destructive": "#FF5C6E",
"destructive-foreground": "#1a0509",
"success": "#43E6A2",
"warning": "#FFC24B",
"info": "#2BE5FF",
"border": "transparent",
"input": "#1E1B2C",
"ring": "#2BE5FF",
"radius": "24px"
},
"dark": {
"background": "#0B0A12",
"foreground": "#F4F1FA",
"card": "#15131F",
"card-foreground": "#F4F1FA",
"popover": "#1E1B2C",
"popover-foreground": "#F4F1FA",
"primary": "#2BE5FF",
"primary-foreground": "#06121A",
"secondary": "#1E1B2C",
"secondary-foreground": "#F4F1FA",
"muted": "#1E1B2C",
"muted-foreground": "#A39FBC",
"accent": "#FF3D8B",
"accent-foreground": "#1b0411",
"destructive": "#FF5C6E",
"destructive-foreground": "#1a0509",
"success": "#43E6A2",
"warning": "#FFC24B",
"info": "#2BE5FF",
"border": "transparent",
"input": "#1E1B2C",
"ring": "#2BE5FF",
"radius": "24px"
}
}
}
# Limelight shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019efda2-dca8-7a32-839a-2c9a95ed64a3`
Slug: `limelight`
## Intent
Limelight treats the interface as a charged reveal. It stages an app the way a relay race stages its runners: every focal surface sits in a key-light charge frame, progress builds as a spark meter, and the most important content is lifted into view the moment it is ready. It keeps the cinematic drama of an anime spectacle screen and drops the gacha kitsch, metallic double-frames, and glassy violet wash.
## 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:
{
"bg": "#0B0A12",
"surface": "#15131F",
"surface_2": "#1E1B2C",
"text": "#F4F1FA",
"muted": "#A39FBC",
"border": "#2A2740",
"accent": "#2BE5FF",
"accent_2": "#FF3D8B",
"accent_3": "#FFC24B",
"on_accent": "#06121A",
"success": "#43E6A2",
"warning": "#FFC24B",
"error": "#FF5C6E",
"info": "#2BE5FF"
}
Typography:
{
"base_size": "17px",
"body_font": "Inter",
"heading_font": "Space Grotesk",
"mono_font": "JetBrains Mono",
"heading_weight": "700",
"heading_transform": "none",
"letter_spacing": "-0.03em",
"line_height": 1.55,
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Space+Grotesk:wght@400;500;600;700&family=Inter:wght@400;500;600&family=JetBrains+Mono:wght@400;500;700&display=swap"
}
## Visual character to preserve
- Charge frames: a single key light wraps one corner of a focal surface and glows in the state accent
- Spark meters: segmented charge bars that throw a gold spark at the fill edge
- Lifted reveal: a cel-anime portrait breaks out past its frame under a key-light rim
- Intensity-coded chips, avatar key-rims and meters that recolour cyan, magenta, or gold
- A deep near-black cinema-stage ground washed by a faint cyan key-glow
## ShadSync visual profile
{
"family": "system",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": false,
"stickerBadges": false,
"motion": "lift",
"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/limelight/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 cyan, magenta and gold as highlighters to encode charging, priority and complete; Wrap a focal surface's corner in a key-light bracket; never use a lonely single edge or a grey box; Stage progress as a spark meter with a gold spark at the fill edge; Let a cel-anime portrait break out of its frame for the reveal; Keep the ground a deep cinema-stage near-black so accents glow
- Do not: Do not use metallic double-frames, jewel corners, or glassy violet surfaces; Do not box the nav into a pill bar or float chrome as a widget; Do not open the hero with an eyebrow tag, a button pair, or a three-stat row; Do not swap a regular serif for an italic serif in the headline; use a colour-pop mark; Do not flatten panels into plain grey rectangles or remove the key-light entirely
## 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 LimelightShadcnKit() {
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">Limelight</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
{
"grid": "A contained max-width stage (1200-1320px) with full-bleed hero. Desktop runs multi-column frame grids; tablet drops to two columns; mobile stacks to a single dramatic scroll.",
"whitespace": "Theatrical: pockets of dark stage and key-glow around the focal frame, tight spacing inside dense data islands, generous padding above every title.",
"density": "high",
"responsive": "From ~390px to 2560px+. Single column on mobile with a wrapping nav; the full-bleed hero re-anchors so the figure stays legible behind a vertical stage-darkening; headlines shrink with clamp() and wrap, never clipping the 390px edge.",
"breakpoints": {
"mobile": "0-619px",
"tablet": "620-1039px",
"desktop": "1040px+"
}
}
{
"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-019efda2-dca8-7a32-839a-2c9a95ed64a3",
"name": "Limelight",
"slug": "limelight"
},
"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": [
"Charge frames: a single key light wraps one corner of a focal surface and glows in the state accent",
"Spark meters: segmented charge bars that throw a gold spark at the fill edge",
"Lifted reveal: a cel-anime portrait breaks out past its frame under a key-light rim",
"Intensity-coded chips, avatar key-rims and meters that recolour cyan, magenta, or gold",
"A deep near-black cinema-stage ground washed by a faint cyan key-glow"
],
"visualProfile": {
"family": "system",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": false,
"stickerBadges": false,
"motion": "lift",
"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": "Limelight 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 cyan, magenta and gold as highlighters to encode charging, priority and complete",
"Wrap a focal surface's corner in a key-light bracket; never use a lonely single edge or a grey box",
"Stage progress as a spark meter with a gold spark at the fill edge",
"Let a cel-anime portrait break out of its frame for the reveal",
"Keep the ground a deep cinema-stage near-black so accents glow"
],
"dont": [
"Do not use metallic double-frames, jewel corners, or glassy violet surfaces",
"Do not box the nav into a pill bar or float chrome as a widget",
"Do not open the hero with an eyebrow tag, a button pair, or a three-stat row",
"Do not swap a regular serif for an italic serif in the headline; use a colour-pop mark",
"Do not flatten panels into plain grey rectangles or remove the key-light entirely"
]
}
}