back to gallerydo avoid
design language·neo-kawaii-tech
Neo-Kawaii Tech
A portable design language for agents: download the markdown first, then inspect the preview, tokens, and rules as needed.
Download DESIGN.md
Portable DESIGN.md source of truth for most agents and apps.
the spec
specification
philosophy
summary
Neo-Kawaii Tech reframes advanced software as an emotionally reassuring companion product. It merges glossy consumer-tech interfaces with playful mascot energy, turning dashboards, automation tools, and device controls into cheerful spaces that feel collectible, tactile, and socially expressive rather than corporate or clinical.
values
emotional softness over sterile efficiencyvisible delight in micro-interactions and decorative framinghigh clarity through color coding and oversized labelingfriendly futurism that makes technical systems feel approachablecollectible interface moments that reward exploration
anti-values
×grim enterprise minimalism×flat monochrome austerity×hard-edged industrial severity×hidden system status×emotionless control surfaces
tokens
colors12 items
primary
#FF5FCF
secondary
#7E7BFF
accent
#7CF7D4
background
#FFF7FD
surface
#FFFFFF
text
#34234D
muted
#8B79A8
border
#E7D9FF
error
#FF6C8E
success
#33D6A6
warning
#FFB84D
info
#69B7FF
typography8 items
- heading font
- Baloo 2
- body font
- Nunito
- mono font
- JetBrains Mono
- base size
- 16px
- scale ratio
- 1.2
- line height
- 1.55
- letter spacing
- 0.01em
- google fonts url
- https://fonts.googleapis.com/css2?family=Baloo+2:wght@500;600;700;800&family=JetBrains+Mono:wght@500;700&family=Nunito:wght@400;500;600;700;800&display=swap
spacing2 items
- base
- 8px
- scale
- 4, 8, 12, 16, 24, 32, 48, 64
radii5 items
- none
- 0
- sm
- 14px
- md
- 22px
- lg
- 32px
- full
- 9999px
shadows3 items
- sm
- 0 8px 20px rgba(145, 120, 201, 0.14)
- md
- 0 18px 44px rgba(136, 102, 196, 0.18)
- lg
- 0 28px 80px rgba(126, 123, 255, 0.22)
surfaces3 items
- treatment
- glass
- card style
- milky translucent cards over candy gradients with inner highlight blooms and sticker-like shine
- bg pattern
- dots
borders4 items
- default width
- 2px
- accent width
- 4px
- style
- solid
- character
- soft luminous outline rings with toy-like sticker edges and pastel glow seams
motion3 items
- duration
- 180ms
- easing
- cubic-bezier(0.2, 0.8, 0.2, 1)
- philosophy
- snappy
rules
composition
Build scenes as layered social-tech habitats: one dominant hero control surface, a supporting conversation or activity column, and several floating utility cards orbiting around the main workflow. Modules should overlap slightly and use decorative badges to imply constant liveliness.
hierarchy
Prioritize oversized rounded headlines, thick status pills, and color-coded labels before dense data. Important controls should look collectible and tap-ready. Secondary metrics can sit inside tiny capsules or mini cards.
density
High visual density is acceptable when softened by radii, pastel grouping, and consistent sticker framing. Use many small supportive details, but keep every functional cluster clearly bounded.
signature patterns
every primary card uses a double-layer shell: a translucent gradient surface plus a 2px white outline ring and inset top highlightsection labels appear inside uppercase capsule tags with wide letter spacing and pastel backgroundsinteractive buttons use stacked shadows and slight translateY lift on hover to feel like gummy hardware controlsdecorative sparkle, heart, and orbital dot motifs are rendered with absolute-position CSS shapes behind major sectionsavatars, toggles, and stat chips are enclosed in thick sticker-like borders that separate them from the candy background
layout
grid
Use a 12-column desktop grid with a large central hero zone spanning 7 columns, a right utility rail spanning 5 columns, and nested card clusters inside each zone. Tablet collapses to 8 columns with stacked hero/supporting clusters. Mobile becomes a single-column feed of plush modules.
breakpoints
Desktop at 1280px+, tablet at 760px-1279px, mobile below 760px. Decorative background motifs should reposition rather than disappear so the atmosphere survives at all sizes.
whitespace
Whitespace is soft and cushiony rather than sparse: keep generous internal padding, moderate inter-card gaps, and small decorative overlaps that make the interface feel layered and toy-like.
guidance
- pair technical information with mascots, chips, or mood labels to keep complex systems emotionally legible
- use multiple pastel hues simultaneously, but anchor each cluster with a clear dominant color family
- style form fields and toggles as plush controls with explicit custom chrome
- apply glass blur, inner highlights, and sticker borders consistently across cards, buttons, and avatars
- design full application scenes such as device orchestration, creator commerce, or companion dashboards instead of component catalogs
- flatten the interface into generic SaaS rectangles
- use grayscale-only panels or harsh black keylines
- leave browser-default inputs, checkboxes, or selects unstyled
- treat decoration as separate from function; decorative markers should help orient the user
- swap in neutral corporate typography that removes the toy-tech character
katagami spec
# Neo-Kawaii Tech ## Philosophy Neo-Kawaii Tech reframes advanced software as an emotionally reassuring companion product. It merges glossy consumer-tech interfaces with playful mascot energy, turning dashboards, automation tools, and device controls into cheerful spaces that feel collectible, tactile, and socially expressive rather than corporate or clinical. ### Values - emotional softness over sterile efficiency - visible delight in micro-interactions and decorative framing - high clarity through color coding and oversized labeling - friendly futurism that makes technical systems feel approachable - collectible interface moments that reward exploration ### Anti-Values - grim enterprise minimalism - flat monochrome austerity - hard-edged industrial severity - hidden system status - emotionless control surfaces ### Visual Character - pill-heavy panels with oversized 24px to 36px radii and inflated silhouettes that feel plush rather than rectangular - candy-gradient surfaces layered over milky translucent cards with soft inner highlights and luminous edge strokes - floating mascot chips, starburst badges, and rounded status bubbles anchored around primary modules as decorative utility markers - thick white or lavender outline rings around cards, buttons, and avatars to create sticker-like separation from the background - dense clusters of tiny hearts, sparkles, dot grids, and orbital lines used as atmospheric scaffolding behind content areas ## Tokens ### Colors | Name | Value | |------|-------| | primary | `#FF5FCF` | | secondary | `#7E7BFF` | | accent | `#7CF7D4` | | background | `#FFF7FD` | | surface | `#FFFFFF` | | text | `#34234D` | | muted | `#8B79A8` | | border | `#E7D9FF` | | error | `#FF6C8E` | | success | `#33D6A6` | | warning | `#FFB84D` | | info | `#69B7FF` | ### Typography - **Heading Font**: Baloo 2 - **Body Font**: Nunito - **Mono Font**: JetBrains Mono - **Base Size**: 16px - **Scale Ratio**: 1.2 - **Line Height**: 1.55 - **Letter Spacing**: 0.01em - **Google Fonts Url**: https://fonts.googleapis.com/css2?family=Baloo+2:wght@500;600;700;800&family=JetBrains+Mono:wght@500;700&family=Nunito:wght@400;500;600;700;800&display=swap ### Spacing - **Base**: 8px - **Scale**: [4,8,12,16,24,32,48,64] ### Radii - **None**: 0 - **Sm**: 14px - **Md**: 22px - **Lg**: 32px - **Full**: 9999px ### Shadows - **Sm**: 0 8px 20px rgba(145, 120, 201, 0.14) - **Md**: 0 18px 44px rgba(136, 102, 196, 0.18) - **Lg**: 0 28px 80px rgba(126, 123, 255, 0.22) ### Surfaces - **Treatment**: glass - **Card Style**: milky translucent cards over candy gradients with inner highlight blooms and sticker-like shine - **Bg Pattern**: dots ### Borders - **Default Width**: 2px - **Accent Width**: 4px - **Style**: solid - **Character**: soft luminous outline rings with toy-like sticker edges and pastel glow seams ### Motion - **Duration**: 180ms - **Easing**: cubic-bezier(0.2, 0.8, 0.2, 1) - **Philosophy**: snappy ## Rules ### Composition Build scenes as layered social-tech habitats: one dominant hero control surface, a supporting conversation or activity column, and several floating utility cards orbiting around the main workflow. Modules should overlap slightly and use decorative badges to imply constant liveliness. ### Hierarchy Prioritize oversized rounded headlines, thick status pills, and color-coded labels before dense data. Important controls should look collectible and tap-ready. Secondary metrics can sit inside tiny capsules or mini cards. ### Density High visual density is acceptable when softened by radii, pastel grouping, and consistent sticker framing. Use many small supportive details, but keep every functional cluster clearly bounded. ### Signature Patterns - every primary card uses a double-layer shell: a translucent gradient surface plus a 2px white outline ring and inset top highlight - section labels appear inside uppercase capsule tags with wide letter spacing and pastel backgrounds - interactive buttons use stacked shadows and slight translateY lift on hover to feel like gummy hardware controls - decorative sparkle, heart, and orbital dot motifs are rendered with absolute-position CSS shapes behind major sections - avatars, toggles, and stat chips are enclosed in thick sticker-like borders that separate them from the candy background ## Layout ### Grid Use a 12-column desktop grid with a large central hero zone spanning 7 columns, a right utility rail spanning 5 columns, and nested card clusters inside each zone. Tablet collapses to 8 columns with stacked hero/supporting clusters. Mobile becomes a single-column feed of plush modules. ### Breakpoints Desktop at 1280px+, tablet at 760px-1279px, mobile below 760px. Decorative background motifs should reposition rather than disappear so the atmosphere survives at all sizes. ### Whitespace Whitespace is soft and cushiony rather than sparse: keep generous internal padding, moderate inter-card gaps, and small decorative overlaps that make the interface feel layered and toy-like. ## Guidance ### Do - pair technical information with mascots, chips, or mood labels to keep complex systems emotionally legible - use multiple pastel hues simultaneously, but anchor each cluster with a clear dominant color family - style form fields and toggles as plush controls with explicit custom chrome - apply glass blur, inner highlights, and sticker borders consistently across cards, buttons, and avatars - design full application scenes such as device orchestration, creator commerce, or companion dashboards instead of component catalogs ### Don't - flatten the interface into generic SaaS rectangles - use grayscale-only panels or harsh black keylines - leave browser-default inputs, checkboxes, or selects unstyled - treat decoration as separate from function; decorative markers should help orient the user - swap in neutral corporate typography that removes the toy-tech character
DESIGN.md
---
version: "alpha"
name: "Neo-Kawaii Tech"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
primary: "#FF5FCF"
secondary: "#7E7BFF"
accent: "#7CF7D4"
background: "#FFF7FD"
surface: "#FFFFFF"
text: "#34234D"
muted: "#8B79A8"
border: "#E7D9FF"
error: "#FF6C8E"
success: "#33D6A6"
warning: "#FFB84D"
info: "#69B7FF"
typography:
headline-lg:
fontFamily: "Baloo 2"
fontSize: "1.728rem"
fontWeight: 700
lineHeight: 1.1
letterSpacing: "0.01em"
headline-md:
fontFamily: "Baloo 2"
fontSize: "1.44rem"
fontWeight: 600
lineHeight: 1.15
letterSpacing: "0.01em"
body-md:
fontFamily: "Nunito"
fontSize: "16px"
fontWeight: 400
lineHeight: 1.55
letterSpacing: "0.01em"
label-md:
fontFamily: "JetBrains Mono"
fontSize: "0.75rem"
fontWeight: 600
lineHeight: 1
letterSpacing: "0.08em"
rounded:
none: "0px"
sm: "14px"
md: "22px"
lg: "32px"
full: "9999px"
spacing:
base: "8px"
xs: "4px"
sm: "8px"
md: "12px"
lg: "16px"
xl: "24px"
2xl: "32px"
3xl: "48px"
4xl: "64px"
components:
color-reference-primary:
backgroundColor: "{colors.primary}"
color-reference-secondary:
backgroundColor: "{colors.secondary}"
color-reference-accent:
backgroundColor: "{colors.accent}"
color-reference-background:
backgroundColor: "{colors.background}"
color-reference-surface:
backgroundColor: "{colors.surface}"
color-reference-text:
backgroundColor: "{colors.text}"
color-reference-muted:
backgroundColor: "{colors.muted}"
color-reference-border:
backgroundColor: "{colors.border}"
color-reference-error:
backgroundColor: "{colors.error}"
color-reference-success:
backgroundColor: "{colors.success}"
color-reference-warning:
backgroundColor: "{colors.warning}"
color-reference-info:
backgroundColor: "{colors.info}"
button-primary:
backgroundColor: "{colors.primary}"
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"
---
# Neo-Kawaii Tech
## Overview
Neo-Kawaii Tech reframes advanced software as an emotionally reassuring companion product. It merges glossy consumer-tech interfaces with playful mascot energy, turning dashboards, automation tools, and device controls into cheerful spaces that feel collectible, tactile, and socially expressive rather than corporate or clinical.
### Values
- emotional softness over sterile efficiency
- visible delight in micro-interactions and decorative framing
- high clarity through color coding and oversized labeling
- friendly futurism that makes technical systems feel approachable
- collectible interface moments that reward exploration
### Anti-Values
- grim enterprise minimalism
- flat monochrome austerity
- hard-edged industrial severity
- hidden system status
- emotionless control surfaces
### Visual Character
- pill-heavy panels with oversized 24px to 36px radii and inflated silhouettes that feel plush rather than rectangular
- candy-gradient surfaces layered over milky translucent cards with soft inner highlights and luminous edge strokes
- floating mascot chips, starburst badges, and rounded status bubbles anchored around primary modules as decorative utility markers
- thick white or lavender outline rings around cards, buttons, and avatars to create sticker-like separation from the background
- dense clusters of tiny hearts, sparkles, dot grids, and orbital lines used as atmospheric scaffolding behind content areas
## Colors
Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.
| Token | Value |
|-------|-------|
| primary | `#FF5FCF` |
| secondary | `#7E7BFF` |
| accent | `#7CF7D4` |
| background | `#FFF7FD` |
| surface | `#FFFFFF` |
| text | `#34234D` |
| muted | `#8B79A8` |
| border | `#E7D9FF` |
| error | `#FF6C8E` |
| success | `#33D6A6` |
| warning | `#FFB84D` |
| info | `#69B7FF` |
## Typography
- **Headline-Lg**: Baloo 2, 1.728rem, weight 700, line-height 1.1.
- **Headline-Md**: Baloo 2, 1.44rem, weight 600, line-height 1.15.
- **Body-Md**: Nunito, 16px, 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`
### Grid
Use a 12-column desktop grid with a large central hero zone spanning 7 columns, a right utility rail spanning 5 columns, and nested card clusters inside each zone. Tablet collapses to 8 columns with stacked hero/supporting clusters. Mobile becomes a single-column feed of plush modules.
### Breakpoints
Desktop at 1280px+, tablet at 760px-1279px, mobile below 760px. Decorative background motifs should reposition rather than disappear so the atmosphere survives at all sizes.
### Whitespace
Whitespace is soft and cushiony rather than sparse: keep generous internal padding, moderate inter-card gaps, and small decorative overlaps that make the interface feel layered and toy-like.
## Elevation & Depth
### Shadows
- **Sm**: 0 8px 20px rgba(145, 120, 201, 0.14)
- **Md**: 0 18px 44px rgba(136, 102, 196, 0.18)
- **Lg**: 0 28px 80px rgba(126, 123, 255, 0.22)
## Shapes
### Rounded
- **None**: `0px`
- **Sm**: `14px`
- **Md**: `22px`
- **Lg**: `32px`
- **Full**: `9999px`
### Surfaces
- **Treatment**: glass
- **Card Style**: milky translucent cards over candy gradients with inner highlight blooms and sticker-like shine
- **Bg Pattern**: dots
### Borders
- **Default Width**: 2px
- **Accent Width**: 4px
- **Style**: solid
- **Character**: soft luminous outline rings with toy-like sticker edges and pastel glow seams
## Components
### Composition
Build scenes as layered social-tech habitats: one dominant hero control surface, a supporting conversation or activity column, and several floating utility cards orbiting around the main workflow. Modules should overlap slightly and use decorative badges to imply constant liveliness.
### Hierarchy
Prioritize oversized rounded headlines, thick status pills, and color-coded labels before dense data. Important controls should look collectible and tap-ready. Secondary metrics can sit inside tiny capsules or mini cards.
### Density
High visual density is acceptable when softened by radii, pastel grouping, and consistent sticker framing. Use many small supportive details, but keep every functional cluster clearly bounded.
### Signature Patterns
- every primary card uses a double-layer shell: a translucent gradient surface plus a 2px white outline ring and inset top highlight
- section labels appear inside uppercase capsule tags with wide letter spacing and pastel backgrounds
- interactive buttons use stacked shadows and slight translateY lift on hover to feel like gummy hardware controls
- decorative sparkle, heart, and orbital dot motifs are rendered with absolute-position CSS shapes behind major sections
- avatars, toggles, and stat chips are enclosed in thick sticker-like borders that separate them from the candy background
## 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-019d9bb9-a318-7f31-8d99-ea55dd8b5a79/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 pair technical information with mascots, chips, or mood labels to keep complex systems emotionally legible
- Do use multiple pastel hues simultaneously, but anchor each cluster with a clear dominant color family
- Do style form fields and toggles as plush controls with explicit custom chrome
- Do apply glass blur, inner highlights, and sticker borders consistently across cards, buttons, and avatars
- Do design full application scenes such as device orchestration, creator commerce, or companion dashboards instead of component catalogs
- Don't flatten the interface into generic SaaS rectangles
- Don't use grayscale-only panels or harsh black keylines
- Don't leave browser-default inputs, checkboxes, or selects unstyled
- Don't treat decoration as separate from function; decorative markers should help orient the user
- Don't swap in neutral corporate typography that removes the toy-tech character
shadcn/ui theme
```json
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "neo-kawaii-tech",
"type": "registry:theme",
"title": "Neo-Kawaii Tech shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#FFF7FD",
"foreground": "#34234D",
"card": "#FFFFFF",
"card-foreground": "#34234D",
"popover": "#FFFFFF",
"popover-foreground": "#34234D",
"primary": "#FF5FCF",
"primary-foreground": "#ffffff",
"secondary": "#7E7BFF",
"secondary-foreground": "#ffffff",
"muted": "#8B79A8",
"muted-foreground": "#34234D",
"accent": "#7CF7D4",
"accent-foreground": "#111111",
"destructive": "#FF6C8E",
"border": "#E7D9FF",
"input": "#E7D9FF",
"ring": "#7CF7D4",
"chart-1": "#FF5FCF",
"chart-2": "#7E7BFF",
"chart-3": "#7CF7D4",
"chart-4": "#33D6A6",
"chart-5": "#FFB84D",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#34234D",
"sidebar-primary": "#FF5FCF",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#69B7FF",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#E7D9FF",
"sidebar-ring": "#7CF7D4",
"radius": "22px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#FF5FCF",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#7CF7D4",
"accent-foreground": "#111111",
"destructive": "#FF6C8E",
"border": "#303642",
"input": "#303642",
"ring": "#7CF7D4",
"chart-1": "#FF5FCF",
"chart-2": "#7E7BFF",
"chart-3": "#7CF7D4",
"chart-4": "#33D6A6",
"chart-5": "#FFB84D",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#FF5FCF",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#7CF7D4",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#7CF7D4",
"radius": "22px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019d9bb9-a318-7f31-8d99-ea55dd8b5a79",
"slug": "neo-kawaii-tech",
"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",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
],
"spacing": [
"base",
"scale"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"motion": [
"duration",
"easing",
"philosophy"
]
}
}
}
```in the wild
embodiments
the full element showcase
embodiment · neo-kawaii-tech
DESIGN.md
at a glance
Typography
headline-lgBaloo 2 · 28px · 700
The quick brown fox jumps
headline-mdBaloo 2 · 23px · 600
The quick brown fox jumps
body-mdNunito · 16px · 400
The quick brown fox jumps
label-mdJetBrains Mono · 12px · 600
The quick brown fox jumps
Components
New
Card title
Components rendered with this language’s tokens — colors, type, and rounded corners as specified.
Spacing
- base8px
- xs4px
- sm8px
- md12px
- lg16px
- xl24px
- 2xl32px
- 3xl48px
- 4xl64px
Shape
none0px
sm14px
md22px
lg32px
full9999px
shadcn/ui
implementation kit
recommendedcompatibility fallback
DESIGN.md with shadcn
Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.
advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu tabletheme css
:root {
--background: #FFF7FD;
--foreground: #34234D;
--card: #FFFFFF;
--card-foreground: #34234D;
--popover: #FFFFFF;
--popover-foreground: #34234D;
--primary: #FF5FCF;
--primary-foreground: #ffffff;
--secondary: #7E7BFF;
--secondary-foreground: #ffffff;
--muted: #8B79A8;
--muted-foreground: #34234D;
--accent: #7CF7D4;
--accent-foreground: #111111;
--destructive: #FF6C8E;
--border: #E7D9FF;
--input: #E7D9FF;
--ring: #7CF7D4;
--chart-1: #FF5FCF;
--chart-2: #7E7BFF;
--chart-3: #7CF7D4;
--chart-4: #33D6A6;
--chart-5: #FFB84D;
--sidebar: #FFFFFF;
--sidebar-foreground: #34234D;
--sidebar-primary: #FF5FCF;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #69B7FF;
--sidebar-accent-foreground: #ffffff;
--sidebar-border: #E7D9FF;
--sidebar-ring: #7CF7D4;
--radius: 22px;
}
.dark {
--background: #0f1115;
--foreground: #f8fafc;
--card: #181b22;
--card-foreground: #f8fafc;
--popover: #181b22;
--popover-foreground: #f8fafc;
--primary: #FF5FCF;
--primary-foreground: #ffffff;
--secondary: #252a33;
--secondary-foreground: #f8fafc;
--muted: #252a33;
--muted-foreground: #a1a1aa;
--accent: #7CF7D4;
--accent-foreground: #111111;
--destructive: #FF6C8E;
--border: #303642;
--input: #303642;
--ring: #7CF7D4;
--chart-1: #FF5FCF;
--chart-2: #7E7BFF;
--chart-3: #7CF7D4;
--chart-4: #33D6A6;
--chart-5: #FFB84D;
--sidebar: #181b22;
--sidebar-foreground: #f8fafc;
--sidebar-primary: #FF5FCF;
--sidebar-primary-foreground: #ffffff;
--sidebar-accent: #7CF7D4;
--sidebar-accent-foreground: #111111;
--sidebar-border: #303642;
--sidebar-ring: #7CF7D4;
--radius: 22px;
}
tsx starter
import { Badge } from "@/components/ui/badge";
import { Button } from "@/components/ui/button";
import {
Card,
CardContent,
CardDescription,
CardFooter,
CardHeader,
CardTitle,
} from "@/components/ui/card";
import { Input } from "@/components/ui/input";
import { Tabs, TabsList, TabsTrigger } from "@/components/ui/tabs";
export function NeoKawaiiTechShadcnKit() {
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">Neo-Kawaii Tech</h2>
<p className="mt-1 max-w-xl text-sm text-muted-foreground">
Use the Katagami registry theme, then compose these shadcn primitives
with the language-specific component recipes.
</p>
</div>
<Button>Apply theme</Button>
</div>
<Tabs defaultValue="components">
<TabsList>
<TabsTrigger value="components">Components</TabsTrigger>
<TabsTrigger value="states">States</TabsTrigger>
<TabsTrigger value="export">Export</TabsTrigger>
</TabsList>
</Tabs>
<Card>
<CardHeader>
<CardTitle>Component recipe</CardTitle>
<CardDescription>
Replace this starter content with the agent-authored product scene
from components.md and preview-shots.json.
</CardDescription>
</CardHeader>
<CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
<Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
<Button variant="secondary">Preview state</Button>
</CardContent>
<CardFooter className="justify-between">
<Badge>Ready</Badge>
<Button variant="outline">Copy recipe</Button>
</CardFooter>
</Card>
</section>
);
}
theme JSONcompatibility fallback
{
"$schema": "https://ui.shadcn.com/schema/registry-item.json",
"name": "neo-kawaii-tech",
"type": "registry:theme",
"title": "Neo-Kawaii Tech shadcn Theme",
"cssVars": {
"theme": {},
"light": {
"background": "#FFF7FD",
"foreground": "#34234D",
"card": "#FFFFFF",
"card-foreground": "#34234D",
"popover": "#FFFFFF",
"popover-foreground": "#34234D",
"primary": "#FF5FCF",
"primary-foreground": "#ffffff",
"secondary": "#7E7BFF",
"secondary-foreground": "#ffffff",
"muted": "#8B79A8",
"muted-foreground": "#34234D",
"accent": "#7CF7D4",
"accent-foreground": "#111111",
"destructive": "#FF6C8E",
"border": "#E7D9FF",
"input": "#E7D9FF",
"ring": "#7CF7D4",
"chart-1": "#FF5FCF",
"chart-2": "#7E7BFF",
"chart-3": "#7CF7D4",
"chart-4": "#33D6A6",
"chart-5": "#FFB84D",
"sidebar": "#FFFFFF",
"sidebar-foreground": "#34234D",
"sidebar-primary": "#FF5FCF",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#69B7FF",
"sidebar-accent-foreground": "#ffffff",
"sidebar-border": "#E7D9FF",
"sidebar-ring": "#7CF7D4",
"radius": "22px"
},
"dark": {
"background": "#0f1115",
"foreground": "#f8fafc",
"card": "#181b22",
"card-foreground": "#f8fafc",
"popover": "#181b22",
"popover-foreground": "#f8fafc",
"primary": "#FF5FCF",
"primary-foreground": "#ffffff",
"secondary": "#252a33",
"secondary-foreground": "#f8fafc",
"muted": "#252a33",
"muted-foreground": "#a1a1aa",
"accent": "#7CF7D4",
"accent-foreground": "#111111",
"destructive": "#FF6C8E",
"border": "#303642",
"input": "#303642",
"ring": "#7CF7D4",
"chart-1": "#FF5FCF",
"chart-2": "#7E7BFF",
"chart-3": "#7CF7D4",
"chart-4": "#33D6A6",
"chart-5": "#FFB84D",
"sidebar": "#181b22",
"sidebar-foreground": "#f8fafc",
"sidebar-primary": "#FF5FCF",
"sidebar-primary-foreground": "#ffffff",
"sidebar-accent": "#7CF7D4",
"sidebar-accent-foreground": "#111111",
"sidebar-border": "#303642",
"sidebar-ring": "#7CF7D4",
"radius": "22px"
}
},
"meta": {
"source": "katagami",
"languageId": "en-019d9bb9-a318-7f31-8d99-ea55dd8b5a79",
"slug": "neo-kawaii-tech",
"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",
"background",
"border",
"error",
"info",
"muted",
"primary",
"secondary",
"success",
"surface",
"text",
"warning"
],
"typography": [
"base_size",
"body_font",
"google_fonts_url",
"heading_font",
"letter_spacing",
"line_height",
"mono_font",
"scale_ratio"
],
"spacing": [
"base",
"scale"
],
"radii": [
"full",
"lg",
"md",
"none",
"sm"
],
"shadows": [
"lg",
"md",
"sm"
],
"surfaces": [
"bg_pattern",
"card_style",
"treatment"
],
"borders": [
"accent_width",
"character",
"default_width",
"style"
],
"motion": [
"duration",
"easing",
"philosophy"
]
}
}
}
component recipescompatibility fallback
# Neo-Kawaii Tech shadcn/ui Components
Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `en-019d9bb9-a318-7f31-8d99-ea55dd8b5a79`
Slug: `neo-kawaii-tech`
## Intent
Neo-Kawaii Tech reframes advanced software as an emotionally reassuring companion product. It merges glossy consumer-tech interfaces with playful mascot energy, turning dashboards, automation tools, and device controls into cheerful spaces that feel collectible, tactile, and socially expressive rather than corporate or clinical.
## 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:
{
"primary": "#FF5FCF",
"secondary": "#7E7BFF",
"accent": "#7CF7D4",
"background": "#FFF7FD",
"surface": "#FFFFFF",
"text": "#34234D",
"muted": "#8B79A8",
"border": "#E7D9FF",
"error": "#FF6C8E",
"success": "#33D6A6",
"warning": "#FFB84D",
"info": "#69B7FF"
}
Typography:
{
"heading_font": "Baloo 2",
"body_font": "Nunito",
"mono_font": "JetBrains Mono",
"base_size": "16px",
"scale_ratio": 1.2,
"line_height": 1.55,
"letter_spacing": "0.01em",
"google_fonts_url": "https://fonts.googleapis.com/css2?family=Baloo+2:wght@500;600;700;800&family=JetBrains+Mono:wght@500;700&family=Nunito:wght@400;500;600;700;800&display=swap"
}
## Visual character to preserve
- pill-heavy panels with oversized 24px to 36px radii and inflated silhouettes that feel plush rather than rectangular
- candy-gradient surfaces layered over milky translucent cards with soft inner highlights and luminous edge strokes
- floating mascot chips, starburst badges, and rounded status bubbles anchored around primary modules as decorative utility markers
- thick white or lavender outline rings around cards, buttons, and avatars to create sticker-like separation from the background
- dense clusters of tiny hearts, sparkles, dot grids, and orbital lines used as atmospheric scaffolding behind content areas
## ShadSync visual profile
{
"family": "paper-collage",
"material": "paper",
"contour": "pebble",
"border": "solid",
"underlay": true,
"grain": false,
"stickerBadges": true,
"motion": "lift",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
}
## Signature component recipes
### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.
### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.
### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.
### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.
### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.
## Preview shots
- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.
## Implementation contract
- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/neo-kawaii-tech/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: pair technical information with mascots, chips, or mood labels to keep complex systems emotionally legible; use multiple pastel hues simultaneously, but anchor each cluster with a clear dominant color family; style form fields and toggles as plush controls with explicit custom chrome; apply glass blur, inner highlights, and sticker borders consistently across cards, buttons, and avatars; design full application scenes such as device orchestration, creator commerce, or companion dashboards instead of component catalogs
- Do not: flatten the interface into generic SaaS rectangles; use grayscale-only panels or harsh black keylines; leave browser-default inputs, checkboxes, or selects unstyled; treat decoration as separate from function; decorative markers should help orient the user; swap in neutral corporate typography that removes the toy-tech character
## 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 NeoKawaiiTechShadcnKit() {
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">Neo-Kawaii Tech</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": "Use a 12-column desktop grid with a large central hero zone spanning 7 columns, a right utility rail spanning 5 columns, and nested card clusters inside each zone. Tablet collapses to 8 columns with stacked hero/supporting clusters. Mobile becomes a single-column feed of plush modules.",
"breakpoints": "Desktop at 1280px+, tablet at 760px-1279px, mobile below 760px. Decorative background motifs should reposition rather than disappear so the atmosphere survives at all sizes.",
"whitespace": "Whitespace is soft and cushiony rather than sparse: keep generous internal padding, moderate inter-card gaps, and small decorative overlaps that make the interface feel layered and toy-like."
}
preview shotscompatibility fallback
{
"artifact": "katagami:shadcn-preview-shots",
"version": "preview-shots-v1",
"generator": "katagami-ui-compatibility-projection",
"generatedBy": "katagami-ui-projection",
"requiresVisualProfile": true,
"schema": "katagami:shadcn-preview-shots/renderable-v1",
"renderable": true,
"language": {
"id": "en-019d9bb9-a318-7f31-8d99-ea55dd8b5a79",
"name": "Neo-Kawaii Tech",
"slug": "neo-kawaii-tech"
},
"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": [
"pill-heavy panels with oversized 24px to 36px radii and inflated silhouettes that feel plush rather than rectangular",
"candy-gradient surfaces layered over milky translucent cards with soft inner highlights and luminous edge strokes",
"floating mascot chips, starburst badges, and rounded status bubbles anchored around primary modules as decorative utility markers",
"thick white or lavender outline rings around cards, buttons, and avatars to create sticker-like separation from the background",
"dense clusters of tiny hearts, sparkles, dot grids, and orbital lines used as atmospheric scaffolding behind content areas"
],
"visualProfile": {
"family": "paper-collage",
"material": "paper",
"contour": "pebble",
"border": "solid",
"underlay": true,
"grain": false,
"stickerBadges": true,
"motion": "lift",
"density": "dense",
"accents": [
"primary",
"accent",
"secondary",
"muted"
]
},
"shots": [
{
"id": "application-shell",
"title": "Application shell",
"viewport": "desktop",
"primitives": [
"button",
"card",
"input",
"select",
"tabs",
"badge",
"separator",
"table"
],
"composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
"mustShow": [
"primary and secondary actions",
"card hierarchy",
"filterable state",
"table or list density"
],
"avoid": [
"component inventory walls",
"placeholder-only content",
"generic rounded SaaS chrome"
],
"scene": {
"eyebrow": "workspace spread",
"headline": "Neo-Kawaii Tech 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": [
"pair technical information with mascots, chips, or mood labels to keep complex systems emotionally legible",
"use multiple pastel hues simultaneously, but anchor each cluster with a clear dominant color family",
"style form fields and toggles as plush controls with explicit custom chrome",
"apply glass blur, inner highlights, and sticker borders consistently across cards, buttons, and avatars",
"design full application scenes such as device orchestration, creator commerce, or companion dashboards instead of component catalogs"
],
"dont": [
"flatten the interface into generic SaaS rectangles",
"use grayscale-only panels or harsh black keylines",
"leave browser-default inputs, checkboxes, or selects unstyled",
"treat decoration as separate from function; decorative markers should help orient the user",
"swap in neutral corporate typography that removes the toy-tech character"
]
}
}
related
More like this
Kawaii Organizershares kawaii-stickers · tokyo-signage · bright-popKawaii Watercolor Packagingshares kawaii-stickers · tokyo-signage · bright-popMemphis Postmodern Graphics UIshares kawaii-stickers · tokyo-signage · bright-popShibuya Sign-Density Popshares kawaii-stickers · tokyo-signage · bright-popSuperflat Pop Graphicsshares kawaii-stickers · tokyo-signage · bright-popTokyo Indie Zine Illustrationshares kawaii-stickers · tokyo-signage · bright-pop