Typography
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
The quick brown fox jumps
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.
A mission operations cockpit: one commanding tactical canvas, diagnostic rails, and stacked subpanels that look synchronized by a central system rather than collected from a UI kit.
Large uppercase coordinates, destination names and mission statuses are the headline layer; medium metric cards are secondary structure; dense monospace telemetry strips are tertiary detail.
High information density with disciplined spacing bands and breathing room around the primary tactical display.
Every major panel is a clip-path chamfer carrying a paired two-corner luminous bracket. The tactical canvas overlays orbital arcs, a scan trace and a single collision beacon on projected glass. Status feedback is light bars, segmented badges and pulsing beacon dots. Colour routes meaning: ice=info, amber=warning, red=critical.
Desktop is a command deck: one commanding tactical canvas with a narrow diagnostic rail; the dashboard uses a 230px breathing rail (left-border active state, never a boxed pill) beside a fluid main column. Tablet collapses to a single column with the rail on top; mobile becomes a single scrolling operations feed with panel hierarchy preserved.
Generous outer gutters and padding above every title; tighter telemetry spacing inside modules, wider separation between major systems.
High, with disciplined spacing bands.
Contained content caps at 1320px and centres on ultra-wide; only the landing hero spans 100vw. Grids use minmax(0,1fr) so children shrink instead of overflowing.
apogee
Subjects are reconstructed as luminous ice-blue scan-traced wireframes on a deep carbon field, wrapped in chamfered instrument framing with corner seams, a targeting reticle, sparse amber and signal-red callouts, scanlines, and a faint radar grid with orbital arcs. Operational and cinematic, never chaotic cyberpunk.
Landing hero is full-bleed; below-hero imagery sits inside its section. Drive the hero with background-image: var(--hero-image) so the studio can swap it. End every generation prompt with 'NO text, NO letters, NO logos.'
# Azimuth ## Philosophy A cinematic mission-control design language. Luminous data planes float on deep carbon void, every container is a chamfered instrument silhouette, and colour follows a strict code: ice means information, amber means caution, red means act now. Command language reads loud and uppercase; machine telemetry stays compact and monospaced. The look is built from line, not shadow. ### Values - Read the whole console at a glance, under pressure - Luminous depth with disciplined restraint - Colour as semantic alert routing, never decoration - Surfaces that feel projected onto the hull, not drawn as soft rectangles ### Anti-Values - Playful rounded consumer-app softness - Neon overload without hierarchy - Flat generic dashboard cards - A single accent edge standing in for a real framing system ## Tokens ### Colors | Name | Value | |------|-------| | bg | `#08111B` | | bg-deep | `#040A12` | | surface | `#101C29` | | surface-2 | `#0B1622` | | text | `#E7F4FF` | | muted | `#7C97AC` | | border | `#2A4459` | | accent | `#7FD6FF` | | on-accent | `#03121C` | | amber | `#FFB45C` | | signal | `#FF5E66` | | primary | `#7FD6FF` | | secondary | `#FFB45C` | | success | `#61F0BF` | | warning | `#FFB45C` | | error | `#FF5E66` | | info | `#7FD6FF` | ### Typography - **Base Size**: 17px - **Body Font**: Exo 2 - **Heading Font**: Orbitron - **Mono Font**: IBM Plex Mono - **Heading Weight**: 800 - **Heading Transform**: uppercase - **Letter Spacing**: 0.12em - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Exo+2:wght@400;500;600;700&family=IBM+Plex+Mono:wght@400;500;600&family=Orbitron:wght@500;600;700;800&display=swap ### Radii - **None**: 0px - **Chamfer**: 18px - **Pill**: 9999px ### Shadows - **Sm**: 0 10px 24px rgba(1,8,15,.34) - **Md**: 0 18px 42px rgba(1,8,15,.46) - **Lg**: 0 26px 70px rgba(1,8,15,.58) ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Surfaces - **Treatment**: carbon-glass - **Card Style**: Chamfered carbon-glass silhouette: linear-gradient(152deg, rgba(16,28,41,.72), rgba(7,15,25,.9)) with backdrop-blur, a 1px hairline trace, and a paired two-corner luminous bracket (top-left + bottom-right ice-blue L-seams). - **Bg Pattern**: masked radar grid + orbital arcs ### Borders - **Default Width**: 1px - **Accent Width**: 2px - **Style**: solid - **Character**: Hairline ice-blue traces with a paired two-corner luminous bracket; framing comes from line work, never from a single highlight edge. ### Motion - **Duration**: 240ms - **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1) - **Philosophy**: deliberate ## Rules ### Composition A mission operations cockpit: one commanding tactical canvas, diagnostic rails, and stacked subpanels that look synchronized by a central system rather than collected from a UI kit. ### Hierarchy Large uppercase coordinates, destination names and mission statuses are the headline layer; medium metric cards are secondary structure; dense monospace telemetry strips are tertiary detail. ### Density High information density with disciplined spacing bands and breathing room around the primary tactical display. ### Signature Every major panel is a clip-path chamfer carrying a paired two-corner luminous bracket. The tactical canvas overlays orbital arcs, a scan trace and a single collision beacon on projected glass. Status feedback is light bars, segmented badges and pulsing beacon dots. Colour routes meaning: ice=info, amber=warning, red=critical. ## Layout ### Grid Desktop is a command deck: one commanding tactical canvas with a narrow diagnostic rail; the dashboard uses a 230px breathing rail (left-border active state, never a boxed pill) beside a fluid main column. Tablet collapses to a single column with the rail on top; mobile becomes a single scrolling operations feed with panel hierarchy preserved. ### Whitespace Generous outer gutters and padding above every title; tighter telemetry spacing inside modules, wider separation between major systems. ### Density High, with disciplined spacing bands. ### Responsive Contained content caps at 1320px and centres on ultra-wide; only the landing hero spans 100vw. Grids use minmax(0,1fr) so children shrink instead of overflowing. ### Breakpoints - **Deck**: 1320px - **Tablet**: 980px - **Field**: 760px - **Mobile**: 560px ## Guidance ### Do - Use dark layered surfaces with narrow luminous accents, not large flat colour fills. - Treat ice, amber and red as semantic signals tied to system meaning and urgency. - Build frames, separators and overlays from line work, with the paired two-corner bracket. - Design screens as believable diegetic mission interfaces with narrative context. ### Don't - Do not use pillowy cards, pastel gradients, or soft mobile-fintech styling. - Do not let accent glows blur text or dominate the screen more than the data. - Do not give a card a single accent edge; the bracket is always a paired framing system. - Do not hide essential hierarchy inside equally weighted panels. ### Accessibility Beam-white text (#E7F4FF) on carbon ground clears WCAG AA for body and large text. Colour routing is always paired with a label or position so meaning never depends on hue alone. Motion respects prefers-reduced-motion; the settled state renders with no JavaScript. Every form control is explicitly styled with a visible ice-blue focus ring. ## Imagery Direction ### Pairs With apogee ### Summary Subjects are reconstructed as luminous ice-blue scan-traced wireframes on a deep carbon field, wrapped in chamfered instrument framing with corner seams, a targeting reticle, sparse amber and signal-red callouts, scanlines, and a faint radar grid with orbital arcs. Operational and cinematic, never chaotic cyberpunk. ### Subjects - orbital intercept scenes - ringed planets and transit gates - spacecraft and trajectory plots - reactor and sensor schematics - tactical maps ### Usage Landing hero is full-bleed; below-hero imagery sits inside its section. Drive the hero with background-image: var(--hero-image) so the studio can swap it. End every generation prompt with 'NO text, NO letters, NO logos.'
---
version: "alpha"
name: "Azimuth"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
bg: "#08111B"
bg-deep: "#040A12"
surface: "#101C29"
surface-2: "#0B1622"
text: "#E7F4FF"
muted: "#7C97AC"
border: "#2A4459"
accent: "#7FD6FF"
on-accent: "#03121C"
amber: "#FFB45C"
signal: "#FF5E66"
primary: "#7FD6FF"
secondary: "#FFB45C"
success: "#61F0BF"
warning: "#FFB45C"
error: "#FF5E66"
info: "#7FD6FF"
typography:
headline-lg:
fontFamily: "Orbitron"
fontSize: "2.075rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "0.12em"
headline-md:
fontFamily: "Orbitron"
fontSize: "1.66rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "0.12em"
body-md:
fontFamily: "Exo 2"
fontSize: "17px"
fontWeight: 400
lineHeight: 1.5
letterSpacing: "0.12em"
label-md:
fontFamily: "IBM Plex Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
none: "0px"
chamfer: "18px"
pill: "9999px"
spacing:
base: "8px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
components:
color-reference-bg:
backgroundColor: "{colors.bg}"
color-reference-bg-deep:
backgroundColor: "{colors.bg-deep}"
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-on-accent:
backgroundColor: "{colors.on-accent}"
color-reference-amber:
backgroundColor: "{colors.amber}"
color-reference-signal:
backgroundColor: "{colors.signal}"
color-reference-primary:
backgroundColor: "{colors.primary}"
color-reference-secondary:
backgroundColor: "{colors.secondary}"
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.primary}"
textColor: "#000000"
typography: "{typography.label-md}"
rounded: "{rounded.none}"
padding: "{spacing.md}"
card-surface:
backgroundColor: "{colors.surface}"
textColor: "{colors.text}"
rounded: "{rounded.none}"
padding: "{spacing.md}"
input-default:
backgroundColor: "{colors.surface}"
textColor: "{colors.text}"
rounded: "{rounded.none}"
height: "44px"
---
# Azimuth
## Overview
A cinematic mission-control design language. Luminous data planes float on deep carbon void, every container is a chamfered instrument silhouette, and colour follows a strict code: ice means information, amber means caution, red means act now. Command language reads loud and uppercase; machine telemetry stays compact and monospaced. The look is built from line, not shadow.
### Values
- Read the whole console at a glance, under pressure
- Luminous depth with disciplined restraint
- Colour as semantic alert routing, never decoration
- Surfaces that feel projected onto the hull, not drawn as soft rectangles
### Anti-Values
- Playful rounded consumer-app softness
- Neon overload without hierarchy
- Flat generic dashboard cards
- A single accent edge standing in for a real framing 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 |
|-------|-------|
| bg | `#08111B` |
| bg-deep | `#040A12` |
| surface | `#101C29` |
| surface-2 | `#0B1622` |
| text | `#E7F4FF` |
| muted | `#7C97AC` |
| border | `#2A4459` |
| accent | `#7FD6FF` |
| on-accent | `#03121C` |
| amber | `#FFB45C` |
| signal | `#FF5E66` |
| primary | `#7FD6FF` |
| secondary | `#FFB45C` |
| success | `#61F0BF` |
| warning | `#FFB45C` |
| error | `#FF5E66` |
| info | `#7FD6FF` |
## Typography
- **Headline-Lg**: Orbitron, 2.075rem, weight 700, line-height 1.1.
- **Headline-Md**: Orbitron, 1.66rem, weight 600, line-height 1.15.
- **Body-Md**: Exo 2, 17px, weight 400, line-height 1.5.
- **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`
### Grid
Desktop is a command deck: one commanding tactical canvas with a narrow diagnostic rail; the dashboard uses a 230px breathing rail (left-border active state, never a boxed pill) beside a fluid main column. Tablet collapses to a single column with the rail on top; mobile becomes a single scrolling operations feed with panel hierarchy preserved.
### Whitespace
Generous outer gutters and padding above every title; tighter telemetry spacing inside modules, wider separation between major systems.
### Density
High, with disciplined spacing bands.
### Responsive
Contained content caps at 1320px and centres on ultra-wide; only the landing hero spans 100vw. Grids use minmax(0,1fr) so children shrink instead of overflowing.
### Breakpoints
- **Deck**: 1320px
- **Tablet**: 980px
- **Field**: 760px
- **Mobile**: 560px
## Elevation & Depth
### Shadows
- **Sm**: 0 10px 24px rgba(1,8,15,.34)
- **Md**: 0 18px 42px rgba(1,8,15,.46)
- **Lg**: 0 26px 70px rgba(1,8,15,.58)
## Shapes
### Rounded
- **None**: `0px`
- **Chamfer**: `18px`
- **Pill**: `9999px`
### Surfaces
- **Treatment**: carbon-glass
- **Card Style**: Chamfered carbon-glass silhouette: linear-gradient(152deg, rgba(16,28,41,.72), rgba(7,15,25,.9)) with backdrop-blur, a 1px hairline trace, and a paired two-corner luminous bracket (top-left + bottom-right ice-blue L-seams).
- **Bg Pattern**: masked radar grid + orbital arcs
### Borders
- **Default Width**: 1px
- **Accent Width**: 2px
- **Style**: solid
- **Character**: Hairline ice-blue traces with a paired two-corner luminous bracket; framing comes from line work, never from a single highlight edge.
## Components
### Composition
A mission operations cockpit: one commanding tactical canvas, diagnostic rails, and stacked subpanels that look synchronized by a central system rather than collected from a UI kit.
### Hierarchy
Large uppercase coordinates, destination names and mission statuses are the headline layer; medium metric cards are secondary structure; dense monospace telemetry strips are tertiary detail.
### Density
High information density with disciplined spacing bands and breathing room around the primary tactical display.
### Signature
Every major panel is a clip-path chamfer carrying a paired two-corner luminous bracket. The tactical canvas overlays orbital arcs, a scan trace and a single collision beacon on projected glass. Status feedback is light bars, segmented badges and pulsing beacon dots. Colour routes meaning: ice=info, amber=warning, red=critical.
## 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-019efa04-400b-70a2-ab22-a4eaca43f566/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 dark layered surfaces with narrow luminous accents, not large flat colour fills.
- Do Treat ice, amber and red as semantic signals tied to system meaning and urgency.
- Do Build frames, separators and overlays from line work, with the paired two-corner bracket.
- Do Design screens as believable diegetic mission interfaces with narrative context.
- Don't Do not use pillowy cards, pastel gradients, or soft mobile-fintech styling.
- Don't Do not let accent glows blur text or dominate the screen more than the data.
- Don't Do not give a card a single accent edge; the bracket is always a paired framing system.
- Don't Do not hide essential hierarchy inside equally weighted panels.
### Accessibility
Beam-white text (#E7F4FF) on carbon ground clears WCAG AA for body and large text. Colour routing is always paired with a label or position so meaning never depends on hue alone. Motion respects prefers-reduced-motion; the settled state renders with no JavaScript. Every form control is explicitly styled with a visible ice-blue focus ring.
## Imagery Direction
### Pairs With
apogee
### Summary
Subjects are reconstructed as luminous ice-blue scan-traced wireframes on a deep carbon field, wrapped in chamfered instrument framing with corner seams, a targeting reticle, sparse amber and signal-red callouts, scanlines, and a faint radar grid with orbital arcs. Operational and cinematic, never chaotic cyberpunk.
### Subjects
- orbital intercept scenes
- ringed planets and transit gates
- spacecraft and trajectory plots
- reactor and sensor schematics
- tactical maps
### Usage
Landing hero is full-bleed; below-hero imagery sits inside its section. Drive the hero with background-image: var(--hero-image) so the studio can swap it. End every generation prompt with 'NO text, NO letters, NO logos.'
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "azimuth",
"type": "registry:theme",
"title": "Azimuth shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#08111B",
"foreground": "#E7F4FF",
"card": "#101C29",
"card-foreground": "#E7F4FF",
"popover": "#101C29",
"popover-foreground": "#E7F4FF",
"primary": "#7FD6FF",
"primary-foreground": "#111111",
"secondary": "#FFB45C",
"secondary-foreground": "#111111",
"muted": "#7C97AC",
"muted-foreground": "#E7F4FF",
"accent": "#7FD6FF",
"accent-foreground": "#111111",
"destructive": "#FF5E66",
"border": "#2A4459",
"input": "#2A4459",
"ring": "#7FD6FF",
"chart-1": "#7FD6FF",
"chart-2": "#FFB45C",
"chart-3": "#7FD6FF",
"chart-4": "#61F0BF",
"chart-5": "#FFB45C",
"sidebar": "#101C29",
"sidebar-foreground": "#E7F4FF",
"sidebar-primary": "#7FD6FF",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#7FD6FF",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#2A4459",
"sidebar-ring": "#7FD6FF",
"radius": "0.625rem"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#7FD6FF",
"primary-foreground": "#111111",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#7FD6FF",
"accent-foreground": "#111111",
"destructive": "#FF5E66",
"border": "#303642",
"input": "#303642",
"ring": "#7FD6FF",
"chart-1": "#7FD6FF",
"chart-2": "#FFB45C",
"chart-3": "#7FD6FF",
"chart-4": "#61F0BF",
"chart-5": "#FFB45C",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#7FD6FF",
"sidebar-primary-foreground": "#111111",
"sidebar-accent": "#7FD6FF",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#7FD6FF",
"radius": "0.625rem"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019efa04-400b-70a2-ab22-a4eaca43f566",
"slug": "azimuth",
"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",
"amber",
"bg",
"bg-deep",
"border",
"error",
"info",
"muted",
"on-accent",
"primary",
"secondary",
"signal",
"success",
"surface",
"surface-2",
"text",
"warning"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"heading_transform",
"heading_weight",
"letter_spacing",
"mono_font"
],
"radii": [
"chamfer",
"none",
"pill"
],
"shadows": [
"lg",
"md",
"sm"
],
"spacing": [
"base",
"scale"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"borders": [
"accent_width",
"character",
"default_width",
"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
Keep Azimuthand 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: #08111B;
--foreground: #E7F4FF;
--card: #101C29;
--card-foreground: #E7F4FF;
--popover: #101C29;
--popover-foreground: #E7F4FF;
--primary: #7FD6FF;
--primary-foreground: #111111;
--secondary: #FFB45C;
--secondary-foreground: #111111;
--muted: #7C97AC;
--muted-foreground: #E7F4FF;
--accent: #7FD6FF;
--accent-foreground: #111111;
--destructive: #FF5E66;
--border: #2A4459;
--input: #2A4459;
--ring: #7FD6FF;
--chart-1: #7FD6FF;
--chart-2: #FFB45C;
--chart-3: #7FD6FF;
--chart-4: #61F0BF;
--chart-5: #FFB45C;
--sidebar: #101C29;
--sidebar-foreground: #E7F4FF;
--sidebar-primary: #7FD6FF;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #7FD6FF;
--sidebar-accent-foreground: #111111;
--sidebar-border: #2A4459;
--sidebar-ring: #7FD6FF;
--radius: 0.625rem;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #7FD6FF;
--primary-foreground: #111111;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #7FD6FF;
--accent-foreground: #111111;
--destructive: #FF5E66;
--border: #303642;
--input: #303642;
--ring: #7FD6FF;
--chart-1: #7FD6FF;
--chart-2: #FFB45C;
--chart-3: #7FD6FF;
--chart-4: #61F0BF;
--chart-5: #FFB45C;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #7FD6FF;
--sidebar-primary-foreground: #111111;
--sidebar-accent: #7FD6FF;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #7FD6FF;
--radius: 0.625rem;
}
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 AzimuthShadcnKit() {
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">Azimuth</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": "azimuth",
"type": "registry:theme",
"title": "Azimuth",
"description": "Cinematic mission-control HUD theme — luminous ice-blue data on deep carbon void, chamfered instrument framing, amber and signal-red as semantic alert routing.",
"cssVars": {
"theme": {
"font-sans": "'Exo 2', system-ui, sans-serif",
"font-mono": "'IBM Plex Mono', ui-monospace, monospace",
"font-heading": "'Orbitron', system-ui, sans-serif",
"radius": "0px"
},
"light": {
"background": "#08111B",
"foreground": "#E7F4FF",
"card": "#101C29",
"card-foreground": "#E7F4FF",
"popover": "#0B1622",
"popover-foreground": "#E7F4FF",
"primary": "#7FD6FF",
"primary-foreground": "#03121C",
"secondary": "#101C29",
"secondary-foreground": "#E7F4FF",
"muted": "#0B1622",
"muted-foreground": "#7C97AC",
"accent": "#FFB45C",
"accent-foreground": "#1C1003",
"destructive": "#FF5E66",
"destructive-foreground": "#26060A",
"border": "#2A4459",
"input": "#2A4459",
"ring": "#7FD6FF",
"chart-1": "#7FD6FF",
"chart-2": "#FFB45C",
"chart-3": "#FF5E66",
"chart-4": "#61F0BF",
"chart-5": "#4FA8D6"
},
"dark": {
"background": "#040A12",
"foreground": "#E7F4FF",
"card": "#101C29",
"card-foreground": "#E7F4FF",
"popover": "#0B1622",
"popover-foreground": "#E7F4FF",
"primary": "#7FD6FF",
"primary-foreground": "#03121C",
"secondary": "#101C29",
"secondary-foreground": "#E7F4FF",
"muted": "#0B1622",
"muted-foreground": "#7C97AC",
"accent": "#FFB45C",
"accent-foreground": "#1C1003",
"destructive": "#FF5E66",
"destructive-foreground": "#26060A",
"border": "#2A4459",
"input": "#2A4459",
"ring": "#7FD6FF",
"chart-1": "#7FD6FF",
"chart-2": "#FFB45C",
"chart-3": "#FF5E66",
"chart-4": "#61F0BF",
"chart-5": "#4FA8D6"
}
}
}
# Azimuth shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019efa04-400b-70a2-ab22-a4eaca43f566`
Slug: `azimuth`
## Intent
A cinematic mission-control design language. Luminous data planes float on deep carbon void, every container is a chamfered instrument silhouette, and colour follows a strict code: ice means information, amber means caution, red means act now. Command language reads loud and uppercase; machine telemetry stays compact and monospaced. The look is built from line, not shadow.
## 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": "#08111B",
"bg-deep": "#040A12",
"surface": "#101C29",
"surface-2": "#0B1622",
"text": "#E7F4FF",
"muted": "#7C97AC",
"border": "#2A4459",
"accent": "#7FD6FF",
"on-accent": "#03121C",
"amber": "#FFB45C",
"signal": "#FF5E66",
"primary": "#7FD6FF",
"secondary": "#FFB45C",
"success": "#61F0BF",
"warning": "#FFB45C",
"error": "#FF5E66",
"info": "#7FD6FF"
}
Typography:
{
"base_size": "17px",
"body_font": "Exo 2",
"heading_font": "Orbitron",
"mono_font": "IBM Plex Mono",
"heading_weight": "800",
"heading_transform": "uppercase",
"letter_spacing": "0.12em",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Exo+2:wght@400;500;600;700&family=IBM+Plex+Mono:wght@400;500;600&family=Orbitron:wght@500;600;700;800&display=swap"
}
## Visual character to preserve
- Make the source language's structural identity visible in every component state.
## ShadSync visual profile
{
"family": "system",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": false,
"stickerBadges": false,
"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/azimuth/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 dark layered surfaces with narrow luminous accents, not large flat colour fills.; Treat ice, amber and red as semantic signals tied to system meaning and urgency.; Build frames, separators and overlays from line work, with the paired two-corner bracket.; Design screens as believable diegetic mission interfaces with narrative context.
- Do not: Do not use pillowy cards, pastel gradients, or soft mobile-fintech styling.; Do not let accent glows blur text or dominate the screen more than the data.; Do not give a card a single accent edge; the bracket is always a paired framing system.; Do not hide essential hierarchy inside equally weighted panels.
## 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 AzimuthShadcnKit() {
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">Azimuth</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": "Desktop is a command deck: one commanding tactical canvas with a narrow diagnostic rail; the dashboard uses a 230px breathing rail (left-border active state, never a boxed pill) beside a fluid main column. Tablet collapses to a single column with the rail on top; mobile becomes a single scrolling operations feed with panel hierarchy preserved.",
"whitespace": "Generous outer gutters and padding above every title; tighter telemetry spacing inside modules, wider separation between major systems.",
"density": "High, with disciplined spacing bands.",
"responsive": "Contained content caps at 1320px and centres on ultra-wide; only the landing hero spans 100vw. Grids use minmax(0,1fr) so children shrink instead of overflowing.",
"breakpoints": {
"deck": "1320px",
"tablet": "980px",
"field": "760px",
"mobile": "560px"
}
}
{
"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-019efa04-400b-70a2-ab22-a4eaca43f566",
"name": "Azimuth",
"slug": "azimuth"
},
"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": [],
"visualProfile": {
"family": "system",
"material": "flat",
"contour": "default",
"border": "solid",
"underlay": false,
"grain": false,
"stickerBadges": false,
"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": "Azimuth 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 dark layered surfaces with narrow luminous accents, not large flat colour fills.",
"Treat ice, amber and red as semantic signals tied to system meaning and urgency.",
"Build frames, separators and overlays from line work, with the paired two-corner bracket.",
"Design screens as believable diegetic mission interfaces with narrative context."
],
"dont": [
"Do not use pillowy cards, pastel gradients, or soft mobile-fintech styling.",
"Do not let accent glows blur text or dominate the screen more than the data.",
"Do not give a card a single accent edge; the bracket is always a paired framing system.",
"Do not hide essential hierarchy inside equally weighted panels."
]
}
}