back to gallery
design language·after-school-diskette-society

After-School Diskette Society

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
After-School Diskette Society turns software into a warm clubroom diagram: cream ABS plastic, photocopied manga structure, floppy labels, blue-ballpoint corrections, and tiny terminal jokes make cybernetics feel like shared classroom maintenance rather than spectacle.
values
Treat the computer as a room object with dust, labels, seating habits, and a social memory rather than as an abstract dashboard.Make technical hierarchy legible through notebook diagrams, manga panel crops, and practical label typography instead of decorative spectacle.Keep existential cybernetic ideas small: questions in margins, boot messages, and handwritten corrections that invite reflection without ominous AI theater.Use restraint as warmth: mostly cream paper, black ink, one blue annotation channel, and red only for tiny correction marks.Favor low-stakes educational computing, shared-machine rituals, and after-school collaboration over lone-genius hacker mythology.Let analog ephemera structure the interface: taped floppy tabs, seating charts, printer-test strips, port labels, and DOS/V prompt fragments.
anti-values
×No green matrix rain, neon cyberpunk, military HUDs, chrome overload, or synthetic hacker dashboards.×No SaaS card grids, generic analytics views, or evenly repeated feature tiles masquerading as product structure.×No fan-art anime character decoration; manga influence must live in panel rhythm, crop, ink hierarchy, and instructional composition.×No vaporwave rainbow, black-green coding palette, or high-saturation futuristic glow.
tokens
borders4 items
accent width
2px
character
Black ink structural borders at high contrast; secondary separators use rgba(30,29,25,0.10) so they read like photocopy artifacts.
default width
1px
style
solid with occasional hand-drawn dashed blue annotation rules
colors12 items
accent
#2F5F9A
background
#F3EBD8
border
#1E1D19
error
#A04438
info
#3B6792
muted
#777064
primary
#2B2A26
secondary
#6F6A5E
success
#5E7453
surface
#FFF9EA
text
#24231F
warning
#B08A45
motion3 items
duration
140ms
easing
steps(2, end)
philosophy
Motion should feel like a cursor blink, a paper tab being selected, or a printer advancing one line; never glossy or cinematic.
radii5 items
full
9999px
lg
8px
md
4px
none
0
sm
2px
shadows3 items
lg
10px 12px 0 rgba(30,29,25,0.08)
md
4px 5px 0 rgba(30,29,25,0.10)
sm
0 1px 0 rgba(30,29,25,0.18)
spacing2 items
base
8px
scale
4, 8, 12, 16, 24, 32, 48, 64, 88, 112
surfaces3 items
bg pattern
Cream base with faint blue-gray grid lines at 24px intervals plus sparse printer-test ticks and tiny boot-message marks.
card style
Flat manga panels with 1px black ink borders, 2px internal register marks, minimal radius, and restrained offset paper shadows.
treatment
Warm off-white paper and beige ABS panels with subtle grain, notebook ruling, and occasional gray adhesive label overlays.
typography10 items
annotation font
Gaegu
base size
16px
body font
Zen Kaku Gothic New
display letter spacing
-0.035em
google fonts url
https://fonts.googleapis.com/css2?family=DotGothic16&family=Gaegu:wght@400;700&family=Zen+Kaku+Gothic+Antique:wght@500;700;900&family=Zen+Kaku+Gothic+New:wght@400;500;700&display=swap
heading font
Zen Kaku Gothic Antique
letter spacing
-0.02em
line height
1.55
mono font
DotGothic16
scale ratio
1.22
rules
composition
Use a clubroom diagram page rather than a dashboard: a large left manga/system panel anchors the page, side notes overlap margins, tabs sit like taped labels, and at least one printer-strip element crosses the full width to interrupt the grid. Avoid equal repeated cards; panels should vary in scale and density according to narrative function.
density
Alternate dense annotated modules with broad cream paper pauses; related controls may cluster at 4-12px while major page areas separate by 64-112px so the design feels like a studied club notebook.
hierarchy
Hierarchy comes from ink weight, panel scale, label placement, and typography roles: heavy Gothic display for page identity, neat Gothic sans for labels and body, DotGothic16 for prompts, and blue handwritten notes for meta-commentary. Red marks remain micro-alerts only.
signature patterns
Floppy-label navigation tabs use gray adhesive rectangles with clipped corners, uppercase school labels, small hole-punch dots, and a slight alternating rotation via CSS transforms.Blue-ballpoint margin annotations use Gaegu handwriting, dashed arrow pseudo-elements, circled indices, and absolute positioning that points into the nearest manga panel.Printer-test strips span across panels with repeating dot and line backgrounds, micro command text, and perforated edges made from radial-gradient CSS masks.Notebook grid underlays appear only inside selected panels through repeating-linear-gradient layers, keeping the page technical without becoming a SaaS grid.Terminal jokes are embedded as small phosphor chips with DotGothic16 text and single-line commands, never as full code waterfalls or hacker dashboards.
layout
breakpoints

mobile <= 640px, tablet 641px-980px, desktop >= 981px; annotations become inline notes on narrow screens to preserve readability.

density

Medium-high informational density, but with deliberate quiet cream margins so annotations and technical fragments feel found rather than crammed.

grid
Desktop uses a 12-column max-width 1180px page with asymmetrical 7/5 and 4/8 panel spans; tablet collapses to 6 columns; mobile becomes one column with preserved tab and annotation layering.
responsive

Keep the dominant clubroom panel first, then printer strip, seating chart, boot notes, and archive queue; never reorder into equal marketing cards.

whitespace
Outer margins are broad at 48-88px while internal label gaps are tight at 4-12px, creating the rhythm of a notebook page with crowded notes around calm diagrams.
guidance
do
  • Use cream ABS plastic, off-white paper, black manga ink, faded label gray, and one restrained blue annotation channel.
  • Name interface modules as plausible school computer-club artifacts such as seating charts, disk ledgers, cable labels, boot logs, and printer strips.
  • Make manga influence structural: panel crops, gutter rhythm, speed-line restraint, and instructional diagram hierarchy.
  • Use terminal fragments as small punchlines or status whispers, no more than one short command per chip.
  • Give one panel dominance and vary all neighboring panels by scale, density, and orientation.
  • Use red only for tiny correction ticks, wrong-disk notes, or a single overdue warning.
  • Preserve accessibility with strong body contrast, readable 16px text, and annotations that remain supplementary rather than required instructions.
avoid
  • Do not use green matrix rain, neon glows, vaporwave gradients, cyberpunk purple, or black-background hacker theatrics.
  • Do not draw anime characters or fan-art mascots; the manga reference is page architecture, not illustration fandom.
  • Do not create three equal cards in a row, generic analytics dashboards, CRM widgets, or SaaS pricing/feature grids.
  • Do not use chrome, glassmorphism, military HUD targeting marks, dense code waterfalls, or fake threat-intelligence panels.
  • Do not add decorative colors beyond blue annotations and tiny red correction marks.
  • Do not let handwritten notes become illegible decoration; every note should clarify, question, or humanize a nearby system detail.
katagami spec
# After-School Diskette Society

## Philosophy

After-School Diskette Society turns software into a warm clubroom diagram: cream ABS plastic, photocopied manga structure, floppy labels, blue-ballpoint corrections, and tiny terminal jokes make cybernetics feel like shared classroom maintenance rather than spectacle.

### Values

- Treat the computer as a room object with dust, labels, seating habits, and a social memory rather than as an abstract dashboard.
- Make technical hierarchy legible through notebook diagrams, manga panel crops, and practical label typography instead of decorative spectacle.
- Keep existential cybernetic ideas small: questions in margins, boot messages, and handwritten corrections that invite reflection without ominous AI theater.
- Use restraint as warmth: mostly cream paper, black ink, one blue annotation channel, and red only for tiny correction marks.
- Favor low-stakes educational computing, shared-machine rituals, and after-school collaboration over lone-genius hacker mythology.
- Let analog ephemera structure the interface: taped floppy tabs, seating charts, printer-test strips, port labels, and DOS/V prompt fragments.

### Anti-Values

- No green matrix rain, neon cyberpunk, military HUDs, chrome overload, or synthetic hacker dashboards.
- No SaaS card grids, generic analytics views, or evenly repeated feature tiles masquerading as product structure.
- No fan-art anime character decoration; manga influence must live in panel rhythm, crop, ink hierarchy, and instructional composition.
- No vaporwave rainbow, black-green coding palette, or high-saturation futuristic glow.

### Visual Character

- Use cream paper and warm ABS surfaces with thin black manga-panel borders, slight 1deg taped-label rotations, and inset ruled-grid underlays built from repeating-linear-gradient CSS.
- Place blue-ballpoint annotations as absolutely positioned marginal notes with arrow rules, handwritten-style text, and small circled numbers that correct or question nearby interface modules.
- Build navigation from floppy-disk label tabs: gray adhesive rectangles with clipped corners, compact uppercase labels, and tiny red correction ticks only on active or warning states.
- Embed terminal prompt fragments as quiet jokes inside panels using bitmap monospace, low-contrast phosphor-white chips, and short DOS/V commands instead of streaming code walls.
- Compose pages as asymmetrical clubroom diagram sheets: one dominant manga crop, several dense technical notes, seating-chart cells, and a full-width printer-test strip that breaks the grid.

## Tokens

### Borders

- **Accent Width**: 2px
- **Character**: Black ink structural borders at high contrast; secondary separators use rgba(30,29,25,0.10) so they read like photocopy artifacts.
- **Default Width**: 1px
- **Style**: solid with occasional hand-drawn dashed blue annotation rules

### Colors

| Name | Value |
|------|-------|
| accent | `#2F5F9A` |
| background | `#F3EBD8` |
| border | `#1E1D19` |
| error | `#A04438` |
| info | `#3B6792` |
| muted | `#777064` |
| primary | `#2B2A26` |
| secondary | `#6F6A5E` |
| success | `#5E7453` |
| surface | `#FFF9EA` |
| text | `#24231F` |
| warning | `#B08A45` |

### Motion

- **Duration**: 140ms
- **Easing**: steps(2, end)
- **Philosophy**: Motion should feel like a cursor blink, a paper tab being selected, or a printer advancing one line; never glossy or cinematic.

### Radii

- **Full**: 9999px
- **Lg**: 8px
- **Md**: 4px
- **None**: 0
- **Sm**: 2px

### Shadows

- **Lg**: 10px 12px 0 rgba(30,29,25,0.08)
- **Md**: 4px 5px 0 rgba(30,29,25,0.10)
- **Sm**: 0 1px 0 rgba(30,29,25,0.18)

### Spacing

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

### Surfaces

- **Bg Pattern**: Cream base with faint blue-gray grid lines at 24px intervals plus sparse printer-test ticks and tiny boot-message marks.
- **Card Style**: Flat manga panels with 1px black ink borders, 2px internal register marks, minimal radius, and restrained offset paper shadows.
- **Treatment**: Warm off-white paper and beige ABS panels with subtle grain, notebook ruling, and occasional gray adhesive label overlays.

### Typography

- **Annotation Font**: Gaegu
- **Base Size**: 16px
- **Body Font**: Zen Kaku Gothic New
- **Display Letter Spacing**: -0.035em
- **Google Fonts Url**: https://fonts.googleapis.com/css2?family=DotGothic16&family=Gaegu:wght@400;700&family=Zen+Kaku+Gothic+Antique:wght@500;700;900&family=Zen+Kaku+Gothic+New:wght@400;500;700&display=swap
- **Heading Font**: Zen Kaku Gothic Antique
- **Letter Spacing**: -0.02em
- **Line Height**: 1.55
- **Mono Font**: DotGothic16
- **Scale Ratio**: 1.22

## Rules

### Composition

Use a clubroom diagram page rather than a dashboard: a large left manga/system panel anchors the page, side notes overlap margins, tabs sit like taped labels, and at least one printer-strip element crosses the full width to interrupt the grid. Avoid equal repeated cards; panels should vary in scale and density according to narrative function.

### Density

Alternate dense annotated modules with broad cream paper pauses; related controls may cluster at 4-12px while major page areas separate by 64-112px so the design feels like a studied club notebook.

### Hierarchy

Hierarchy comes from ink weight, panel scale, label placement, and typography roles: heavy Gothic display for page identity, neat Gothic sans for labels and body, DotGothic16 for prompts, and blue handwritten notes for meta-commentary. Red marks remain micro-alerts only.

### Signature Patterns

- Floppy-label navigation tabs use gray adhesive rectangles with clipped corners, uppercase school labels, small hole-punch dots, and a slight alternating rotation via CSS transforms.
- Blue-ballpoint margin annotations use Gaegu handwriting, dashed arrow pseudo-elements, circled indices, and absolute positioning that points into the nearest manga panel.
- Printer-test strips span across panels with repeating dot and line backgrounds, micro command text, and perforated edges made from radial-gradient CSS masks.
- Notebook grid underlays appear only inside selected panels through repeating-linear-gradient layers, keeping the page technical without becoming a SaaS grid.
- Terminal jokes are embedded as small phosphor chips with DotGothic16 text and single-line commands, never as full code waterfalls or hacker dashboards.

## Layout

### Breakpoints

mobile <= 640px, tablet 641px-980px, desktop >= 981px; annotations become inline notes on narrow screens to preserve readability.

### Density

Medium-high informational density, but with deliberate quiet cream margins so annotations and technical fragments feel found rather than crammed.

### Grid

Desktop uses a 12-column max-width 1180px page with asymmetrical 7/5 and 4/8 panel spans; tablet collapses to 6 columns; mobile becomes one column with preserved tab and annotation layering.

### Responsive

Keep the dominant clubroom panel first, then printer strip, seating chart, boot notes, and archive queue; never reorder into equal marketing cards.

### Whitespace

Outer margins are broad at 48-88px while internal label gaps are tight at 4-12px, creating the rhythm of a notebook page with crowded notes around calm diagrams.

## Guidance

### Do

- Use cream ABS plastic, off-white paper, black manga ink, faded label gray, and one restrained blue annotation channel.
- Name interface modules as plausible school computer-club artifacts such as seating charts, disk ledgers, cable labels, boot logs, and printer strips.
- Make manga influence structural: panel crops, gutter rhythm, speed-line restraint, and instructional diagram hierarchy.
- Use terminal fragments as small punchlines or status whispers, no more than one short command per chip.
- Give one panel dominance and vary all neighboring panels by scale, density, and orientation.
- Use red only for tiny correction ticks, wrong-disk notes, or a single overdue warning.
- Preserve accessibility with strong body contrast, readable 16px text, and annotations that remain supplementary rather than required instructions.

### Don't

- Do not use green matrix rain, neon glows, vaporwave gradients, cyberpunk purple, or black-background hacker theatrics.
- Do not draw anime characters or fan-art mascots; the manga reference is page architecture, not illustration fandom.
- Do not create three equal cards in a row, generic analytics dashboards, CRM widgets, or SaaS pricing/feature grids.
- Do not use chrome, glassmorphism, military HUD targeting marks, dense code waterfalls, or fake threat-intelligence panels.
- Do not add decorative colors beyond blue annotations and tiny red correction marks.
- Do not let handwritten notes become illegible decoration; every note should clarify, question, or humanize a nearby system detail.

### Accessibility

Maintain WCAG AA contrast for all core text, keep blue notes large enough to read, avoid relying on color alone for warnings, and preserve semantic focus states with visible ink-outline treatments.

### Usage Context

Best for educational computing tools, retro-technical archives, collaborative coding clubs, personal knowledge systems, and speculative interfaces about shared machines and memory.
DESIGN.md
---
version: "alpha"
name: "After-School Diskette Society"
description: "Agent-curated design language exported from Katagami as DESIGN.md."
colors:
  accent: "#2F5F9A"
  background: "#F3EBD8"
  border: "#1E1D19"
  error: "#A04438"
  info: "#3B6792"
  muted: "#777064"
  primary: "#2B2A26"
  secondary: "#6F6A5E"
  success: "#5E7453"
  surface: "#FFF9EA"
  text: "#24231F"
  warning: "#B08A45"
typography:
  headline-lg:
    fontFamily: "Zen Kaku Gothic Antique"
    fontSize: "1.816rem"
    fontWeight: 700
    lineHeight: 1.1
    letterSpacing: "-0.02em"
  headline-md:
    fontFamily: "Zen Kaku Gothic Antique"
    fontSize: "1.488rem"
    fontWeight: 600
    lineHeight: 1.15
    letterSpacing: "-0.02em"
  body-md:
    fontFamily: "Zen Kaku Gothic New"
    fontSize: "16px"
    fontWeight: 400
    lineHeight: 1.55
    letterSpacing: "-0.02em"
  label-md:
    fontFamily: "DotGothic16"
    fontSize: "0.75rem"
    fontWeight: 600
    lineHeight: 1
    letterSpacing: "0.08em"
rounded:
  full: "9999px"
  lg: "8px"
  md: "4px"
  none: "0px"
  sm: "2px"
spacing:
  base: "8px"
  xs: "4px"
  sm: "8px"
  md: "12px"
  lg: "16px"
  xl: "24px"
  2xl: "32px"
  3xl: "48px"
  4xl: "64px"
  step-8: "88px"
  step-9: "112px"
components:
  color-reference-accent:
    backgroundColor: "{colors.accent}"
  color-reference-background:
    backgroundColor: "{colors.background}"
  color-reference-border:
    backgroundColor: "{colors.border}"
  color-reference-error:
    backgroundColor: "{colors.error}"
  color-reference-info:
    backgroundColor: "{colors.info}"
  color-reference-muted:
    backgroundColor: "{colors.muted}"
  color-reference-primary:
    backgroundColor: "{colors.primary}"
  color-reference-secondary:
    backgroundColor: "{colors.secondary}"
  color-reference-success:
    backgroundColor: "{colors.success}"
  color-reference-surface:
    backgroundColor: "{colors.surface}"
  color-reference-text:
    backgroundColor: "{colors.text}"
  color-reference-warning:
    backgroundColor: "{colors.warning}"
  button-primary:
    backgroundColor: "{colors.primary}"
    textColor: "#ffffff"
    typography: "{typography.label-md}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  card-surface:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    padding: "{spacing.md}"
  input-default:
    backgroundColor: "{colors.surface}"
    textColor: "{colors.text}"
    rounded: "{rounded.md}"
    height: "44px"
---

# After-School Diskette Society

## Overview

After-School Diskette Society turns software into a warm clubroom diagram: cream ABS plastic, photocopied manga structure, floppy labels, blue-ballpoint corrections, and tiny terminal jokes make cybernetics feel like shared classroom maintenance rather than spectacle.

### Values

- Treat the computer as a room object with dust, labels, seating habits, and a social memory rather than as an abstract dashboard.
- Make technical hierarchy legible through notebook diagrams, manga panel crops, and practical label typography instead of decorative spectacle.
- Keep existential cybernetic ideas small: questions in margins, boot messages, and handwritten corrections that invite reflection without ominous AI theater.
- Use restraint as warmth: mostly cream paper, black ink, one blue annotation channel, and red only for tiny correction marks.
- Favor low-stakes educational computing, shared-machine rituals, and after-school collaboration over lone-genius hacker mythology.
- Let analog ephemera structure the interface: taped floppy tabs, seating charts, printer-test strips, port labels, and DOS/V prompt fragments.

### Anti-Values

- No green matrix rain, neon cyberpunk, military HUDs, chrome overload, or synthetic hacker dashboards.
- No SaaS card grids, generic analytics views, or evenly repeated feature tiles masquerading as product structure.
- No fan-art anime character decoration; manga influence must live in panel rhythm, crop, ink hierarchy, and instructional composition.
- No vaporwave rainbow, black-green coding palette, or high-saturation futuristic glow.

### Visual Character

- Use cream paper and warm ABS surfaces with thin black manga-panel borders, slight 1deg taped-label rotations, and inset ruled-grid underlays built from repeating-linear-gradient CSS.
- Place blue-ballpoint annotations as absolutely positioned marginal notes with arrow rules, handwritten-style text, and small circled numbers that correct or question nearby interface modules.
- Build navigation from floppy-disk label tabs: gray adhesive rectangles with clipped corners, compact uppercase labels, and tiny red correction ticks only on active or warning states.
- Embed terminal prompt fragments as quiet jokes inside panels using bitmap monospace, low-contrast phosphor-white chips, and short DOS/V commands instead of streaming code walls.
- Compose pages as asymmetrical clubroom diagram sheets: one dominant manga crop, several dense technical notes, seating-chart cells, and a full-width printer-test strip that breaks the grid.

## Colors

Use the YAML color tokens as the normative palette. The prose below names the roles agents should preserve when generating UI.

| Token | Value |
|-------|-------|
| accent | `#2F5F9A` |
| background | `#F3EBD8` |
| border | `#1E1D19` |
| error | `#A04438` |
| info | `#3B6792` |
| muted | `#777064` |
| primary | `#2B2A26` |
| secondary | `#6F6A5E` |
| success | `#5E7453` |
| surface | `#FFF9EA` |
| text | `#24231F` |
| warning | `#B08A45` |

## Typography

- **Headline-Lg**: Zen Kaku Gothic Antique, 1.816rem, weight 700, line-height 1.1.
- **Headline-Md**: Zen Kaku Gothic Antique, 1.488rem, weight 600, line-height 1.15.
- **Body-Md**: Zen Kaku Gothic New, 16px, weight 400, line-height 1.55.
- **Label-Md**: DotGothic16, 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**: `88px`
- **Step-9**: `112px`

### Breakpoints

mobile <= 640px, tablet 641px-980px, desktop >= 981px; annotations become inline notes on narrow screens to preserve readability.

### Density

Medium-high informational density, but with deliberate quiet cream margins so annotations and technical fragments feel found rather than crammed.

### Grid

Desktop uses a 12-column max-width 1180px page with asymmetrical 7/5 and 4/8 panel spans; tablet collapses to 6 columns; mobile becomes one column with preserved tab and annotation layering.

### Responsive

Keep the dominant clubroom panel first, then printer strip, seating chart, boot notes, and archive queue; never reorder into equal marketing cards.

### Whitespace

Outer margins are broad at 48-88px while internal label gaps are tight at 4-12px, creating the rhythm of a notebook page with crowded notes around calm diagrams.

## Elevation & Depth

### Shadows

- **Lg**: 10px 12px 0 rgba(30,29,25,0.08)
- **Md**: 4px 5px 0 rgba(30,29,25,0.10)
- **Sm**: 0 1px 0 rgba(30,29,25,0.18)

## Shapes

### Rounded

- **Full**: `9999px`
- **Lg**: `8px`
- **Md**: `4px`
- **None**: `0px`
- **Sm**: `2px`

### Surfaces

- **Bg Pattern**: Cream base with faint blue-gray grid lines at 24px intervals plus sparse printer-test ticks and tiny boot-message marks.
- **Card Style**: Flat manga panels with 1px black ink borders, 2px internal register marks, minimal radius, and restrained offset paper shadows.
- **Treatment**: Warm off-white paper and beige ABS panels with subtle grain, notebook ruling, and occasional gray adhesive label overlays.

### Borders

- **Accent Width**: 2px
- **Character**: Black ink structural borders at high contrast; secondary separators use rgba(30,29,25,0.10) so they read like photocopy artifacts.
- **Default Width**: 1px
- **Style**: solid with occasional hand-drawn dashed blue annotation rules

## Components

### Composition

Use a clubroom diagram page rather than a dashboard: a large left manga/system panel anchors the page, side notes overlap margins, tabs sit like taped labels, and at least one printer-strip element crosses the full width to interrupt the grid. Avoid equal repeated cards; panels should vary in scale and density according to narrative function.

### Density

Alternate dense annotated modules with broad cream paper pauses; related controls may cluster at 4-12px while major page areas separate by 64-112px so the design feels like a studied club notebook.

### Hierarchy

Hierarchy comes from ink weight, panel scale, label placement, and typography roles: heavy Gothic display for page identity, neat Gothic sans for labels and body, DotGothic16 for prompts, and blue handwritten notes for meta-commentary. Red marks remain micro-alerts only.

### Signature Patterns

- Floppy-label navigation tabs use gray adhesive rectangles with clipped corners, uppercase school labels, small hole-punch dots, and a slight alternating rotation via CSS transforms.
- Blue-ballpoint margin annotations use Gaegu handwriting, dashed arrow pseudo-elements, circled indices, and absolute positioning that points into the nearest manga panel.
- Printer-test strips span across panels with repeating dot and line backgrounds, micro command text, and perforated edges made from radial-gradient CSS masks.
- Notebook grid underlays appear only inside selected panels through repeating-linear-gradient layers, keeping the page technical without becoming a SaaS grid.
- Terminal jokes are embedded as small phosphor chips with DotGothic16 text and single-line commands, never as full code waterfalls or hacker dashboards.

## 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/after-school-diskette-society/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 cream ABS plastic, off-white paper, black manga ink, faded label gray, and one restrained blue annotation channel.
- Do Name interface modules as plausible school computer-club artifacts such as seating charts, disk ledgers, cable labels, boot logs, and printer strips.
- Do Make manga influence structural: panel crops, gutter rhythm, speed-line restraint, and instructional diagram hierarchy.
- Do Use terminal fragments as small punchlines or status whispers, no more than one short command per chip.
- Do Give one panel dominance and vary all neighboring panels by scale, density, and orientation.
- Do Use red only for tiny correction ticks, wrong-disk notes, or a single overdue warning.
- Do Preserve accessibility with strong body contrast, readable 16px text, and annotations that remain supplementary rather than required instructions.
- Don't Do not use green matrix rain, neon glows, vaporwave gradients, cyberpunk purple, or black-background hacker theatrics.
- Don't Do not draw anime characters or fan-art mascots; the manga reference is page architecture, not illustration fandom.
- Don't Do not create three equal cards in a row, generic analytics dashboards, CRM widgets, or SaaS pricing/feature grids.
- Don't Do not use chrome, glassmorphism, military HUD targeting marks, dense code waterfalls, or fake threat-intelligence panels.
- Don't Do not add decorative colors beyond blue annotations and tiny red correction marks.
- Don't Do not let handwritten notes become illegible decoration; every note should clarify, question, or humanize a nearby system detail.

### Accessibility

Maintain WCAG AA contrast for all core text, keep blue notes large enough to read, avoid relying on color alone for warnings, and preserve semantic focus states with visible ink-outline treatments.

### Usage Context

Best for educational computing tools, retro-technical archives, collaborative coding clubs, personal knowledge systems, and speculative interfaces about shared machines and memory.
shadcn/ui theme
```json
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "name": "after-school-diskette-society",
  "type": "registry:theme",
  "title": "After-School Diskette Society shadcn Theme",
  "cssVars": {
    "theme": {},
    "light": {
      "background": "#F3EBD8",
      "foreground": "#24231F",
      "card": "#FFF9EA",
      "card-foreground": "#24231F",
      "popover": "#FFF9EA",
      "popover-foreground": "#24231F",
      "primary": "#2B2A26",
      "primary-foreground": "#ffffff",
      "secondary": "#6F6A5E",
      "secondary-foreground": "#ffffff",
      "muted": "#777064",
      "muted-foreground": "#24231F",
      "accent": "#2F5F9A",
      "accent-foreground": "#ffffff",
      "destructive": "#A04438",
      "border": "#1E1D19",
      "input": "#1E1D19",
      "ring": "#2F5F9A",
      "chart-1": "#2B2A26",
      "chart-2": "#6F6A5E",
      "chart-3": "#2F5F9A",
      "chart-4": "#5E7453",
      "chart-5": "#B08A45",
      "sidebar": "#FFF9EA",
      "sidebar-foreground": "#24231F",
      "sidebar-primary": "#2B2A26",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#3B6792",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#1E1D19",
      "sidebar-ring": "#2F5F9A",
      "radius": "4px"
    },
    "dark": {
      "background": "#0f1115",
      "foreground": "#f8fafc",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2B2A26",
      "primary-foreground": "#ffffff",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "accent": "#2F5F9A",
      "accent-foreground": "#ffffff",
      "destructive": "#A04438",
      "border": "#303642",
      "input": "#303642",
      "ring": "#2F5F9A",
      "chart-1": "#2B2A26",
      "chart-2": "#6F6A5E",
      "chart-3": "#2F5F9A",
      "chart-4": "#5E7453",
      "chart-5": "#B08A45",
      "sidebar": "#181b22",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2B2A26",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-accent": "#2F5F9A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-ring": "#2F5F9A",
      "radius": "4px"
    }
  },
  "meta": {
    "source": "katagami",
    "languageId": "after-school-diskette-society",
    "slug": "after-school-diskette-society",
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "annotation_font",
        "base_size",
        "body_font",
        "display_letter_spacing",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    }
  }
}
```
in the wild

embodiments

the full element showcase
embodiment · after-school-diskette-society
DESIGN.md

at a glance

Palette

Typography

headline-lgZen Kaku Gothic Antique · 29px · 700

The quick brown fox jumps

headline-mdZen Kaku Gothic Antique · 24px · 600

The quick brown fox jumps

body-mdZen Kaku Gothic New · 16px · 400

The quick brown fox jumps

label-mdDotGothic16 · 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
  • step-888px
  • step-9112px

Shape

full9999px
lg8px
md4px
none0px
sm2px
shadcn/ui

implementation kit

needs agent-authored kitcompatibility fallback
shadcn compatibility only
The generated theme variables are available, but the polished shadcn component recipes and shots have not been authored by the Katagami agent yet.
fallbackprimitives render
Compatibility proof
Local shadcn-style primitives accept the generated theme variables.
primaryaccentsurfacemutedwarningerror
table rhythm
buttonok
cardok
inputok
recommendedcompatibility fallback

DESIGN.md with shadcn

Copy this when the target app uses shadcn/ui. It packages the Katagami DESIGN.md context with the install list, theme variables, component recipes, preview-shot contract, and starter TSX in one Markdown companion.

advanced implementation filesoptional machine-readable theme, CSS, TSX starter, recipes, and preview contract
shadcn add
npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table
theme css
:root {
  --background: #F3EBD8;
  --foreground: #24231F;
  --card: #FFF9EA;
  --card-foreground: #24231F;
  --popover: #FFF9EA;
  --popover-foreground: #24231F;
  --primary: #2B2A26;
  --primary-foreground: #ffffff;
  --secondary: #6F6A5E;
  --secondary-foreground: #ffffff;
  --muted: #777064;
  --muted-foreground: #24231F;
  --accent: #2F5F9A;
  --accent-foreground: #ffffff;
  --destructive: #A04438;
  --border: #1E1D19;
  --input: #1E1D19;
  --ring: #2F5F9A;
  --chart-1: #2B2A26;
  --chart-2: #6F6A5E;
  --chart-3: #2F5F9A;
  --chart-4: #5E7453;
  --chart-5: #B08A45;
  --sidebar: #FFF9EA;
  --sidebar-foreground: #24231F;
  --sidebar-primary: #2B2A26;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #3B6792;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #1E1D19;
  --sidebar-ring: #2F5F9A;
  --radius: 4px;
}

.dark {
  --background: #0f1115;
  --foreground: #f8fafc;
  --card: #181b22;
  --card-foreground: #f8fafc;
  --popover: #181b22;
  --popover-foreground: #f8fafc;
  --primary: #2B2A26;
  --primary-foreground: #ffffff;
  --secondary: #252a33;
  --secondary-foreground: #f8fafc;
  --muted: #252a33;
  --muted-foreground: #a1a1aa;
  --accent: #2F5F9A;
  --accent-foreground: #ffffff;
  --destructive: #A04438;
  --border: #303642;
  --input: #303642;
  --ring: #2F5F9A;
  --chart-1: #2B2A26;
  --chart-2: #6F6A5E;
  --chart-3: #2F5F9A;
  --chart-4: #5E7453;
  --chart-5: #B08A45;
  --sidebar: #181b22;
  --sidebar-foreground: #f8fafc;
  --sidebar-primary: #2B2A26;
  --sidebar-primary-foreground: #ffffff;
  --sidebar-accent: #2F5F9A;
  --sidebar-accent-foreground: #ffffff;
  --sidebar-border: #303642;
  --sidebar-ring: #2F5F9A;
  --radius: 4px;
}
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 AfterSchoolDisketteSocietyShadcnKit() {
  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">After-School Diskette Society</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 JSONstored + verified
{
  "$schema": "https://ui.shadcn.com/schema/registry-item.json",
  "cssVars": {
    "dark": {
      "accent": "#2F5F9A",
      "accent-foreground": "#ffffff",
      "background": "#0f1115",
      "border": "#303642",
      "card": "#181b22",
      "card-foreground": "#f8fafc",
      "chart-1": "#2B2A26",
      "chart-2": "#6F6A5E",
      "chart-3": "#2F5F9A",
      "chart-4": "#5E7453",
      "chart-5": "#B08A45",
      "destructive": "#A04438",
      "foreground": "#f8fafc",
      "input": "#303642",
      "muted": "#252a33",
      "muted-foreground": "#a1a1aa",
      "popover": "#181b22",
      "popover-foreground": "#f8fafc",
      "primary": "#2B2A26",
      "primary-foreground": "#ffffff",
      "radius": "4px",
      "ring": "#2F5F9A",
      "secondary": "#252a33",
      "secondary-foreground": "#f8fafc",
      "sidebar": "#181b22",
      "sidebar-accent": "#2F5F9A",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#303642",
      "sidebar-foreground": "#f8fafc",
      "sidebar-primary": "#2B2A26",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#2F5F9A"
    },
    "light": {
      "accent": "#2F5F9A",
      "accent-foreground": "#ffffff",
      "background": "#F3EBD8",
      "border": "#1E1D19",
      "card": "#FFF9EA",
      "card-foreground": "#24231F",
      "chart-1": "#2B2A26",
      "chart-2": "#6F6A5E",
      "chart-3": "#2F5F9A",
      "chart-4": "#5E7453",
      "chart-5": "#B08A45",
      "destructive": "#A04438",
      "foreground": "#24231F",
      "input": "#1E1D19",
      "muted": "#777064",
      "muted-foreground": "#24231F",
      "popover": "#FFF9EA",
      "popover-foreground": "#24231F",
      "primary": "#2B2A26",
      "primary-foreground": "#ffffff",
      "radius": "4px",
      "ring": "#2F5F9A",
      "secondary": "#6F6A5E",
      "secondary-foreground": "#ffffff",
      "sidebar": "#FFF9EA",
      "sidebar-accent": "#3B6792",
      "sidebar-accent-foreground": "#ffffff",
      "sidebar-border": "#1E1D19",
      "sidebar-foreground": "#24231F",
      "sidebar-primary": "#2B2A26",
      "sidebar-primary-foreground": "#ffffff",
      "sidebar-ring": "#2F5F9A"
    },
    "theme": {}
  },
  "meta": {
    "componentManifest": [
      "button",
      "card",
      "input",
      "textarea",
      "select",
      "dialog",
      "sheet",
      "tabs",
      "badge",
      "separator",
      "checkbox",
      "switch",
      "slider",
      "tooltip",
      "dropdown-menu",
      "table"
    ],
    "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
    "languageId": "after-school-diskette-society",
    "nativeTokenNames": {
      "borders": [
        "accent_width",
        "character",
        "default_width",
        "style"
      ],
      "colors": [
        "accent",
        "background",
        "border",
        "error",
        "info",
        "muted",
        "primary",
        "secondary",
        "success",
        "surface",
        "text",
        "warning"
      ],
      "motion": [
        "duration",
        "easing",
        "philosophy"
      ],
      "radii": [
        "full",
        "lg",
        "md",
        "none",
        "sm"
      ],
      "shadows": [
        "lg",
        "md",
        "sm"
      ],
      "spacing": [
        "base",
        "scale"
      ],
      "surfaces": [
        "bg_pattern",
        "card_style",
        "treatment"
      ],
      "typography": [
        "annotation_font",
        "base_size",
        "body_font",
        "display_letter_spacing",
        "google_fonts_url",
        "heading_font",
        "letter_spacing",
        "line_height",
        "mono_font",
        "scale_ratio"
      ]
    },
    "slug": "after-school-diskette-society",
    "source": "katagami"
  },
  "name": "after-school-diskette-society",
  "title": "After-School Diskette Society shadcn Theme",
  "type": "registry:theme"
}
component recipescompatibility fallback
# After-School Diskette Society shadcn/ui Components

Artifact: `component-recipes-v1`
Author: `katagami-ui-projection`
Language ID: `after-school-diskette-society`
Slug: `after-school-diskette-society`

## Intent

After-School Diskette Society turns software into a warm clubroom diagram: cream ABS plastic, photocopied manga structure, floppy labels, blue-ballpoint corrections, and tiny terminal jokes make cybernetics feel like shared classroom maintenance rather than spectacle.

## Required primitives

- button
- card
- input
- textarea
- select
- dialog
- sheet
- tabs
- badge
- separator
- checkbox
- switch
- slider
- tooltip
- dropdown-menu
- table

Install with `npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table`.

## Token cues

Colors:

{
  "accent": "#2F5F9A",
  "background": "#F3EBD8",
  "border": "#1E1D19",
  "error": "#A04438",
  "info": "#3B6792",
  "muted": "#777064",
  "primary": "#2B2A26",
  "secondary": "#6F6A5E",
  "success": "#5E7453",
  "surface": "#FFF9EA",
  "text": "#24231F",
  "warning": "#B08A45"
}

Typography:

{
  "annotation_font": "Gaegu",
  "base_size": "16px",
  "body_font": "Zen Kaku Gothic New",
  "display_letter_spacing": "-0.035em",
  "google_fonts_url": "https://fonts.googleapis.com/css2?family=DotGothic16&family=Gaegu:wght@400;700&family=Zen+Kaku+Gothic+Antique:wght@500;700;900&family=Zen+Kaku+Gothic+New:wght@400;500;700&display=swap",
  "heading_font": "Zen Kaku Gothic Antique",
  "letter_spacing": "-0.02em",
  "line_height": 1.55,
  "mono_font": "DotGothic16",
  "scale_ratio": 1.22
}

## Visual character to preserve

- Use cream paper and warm ABS surfaces with thin black manga-panel borders, slight 1deg taped-label rotations, and inset ruled-grid underlays built from repeating-linear-gradient CSS.
- Place blue-ballpoint annotations as absolutely positioned marginal notes with arrow rules, handwritten-style text, and small circled numbers that correct or question nearby interface modules.
- Build navigation from floppy-disk label tabs: gray adhesive rectangles with clipped corners, compact uppercase labels, and tiny red correction ticks only on active or warning states.
- Embed terminal prompt fragments as quiet jokes inside panels using bitmap monospace, low-contrast phosphor-white chips, and short DOS/V commands instead of streaming code walls.
- Compose pages as asymmetrical clubroom diagram sheets: one dominant manga crop, several dense technical notes, seating-chart cells, and a full-width printer-test strip that breaks the grid.

## ShadSync visual profile

{
  "family": "paper-collage",
  "material": "paper",
  "contour": "default",
  "border": "dashed",
  "underlay": true,
  "grain": true,
  "stickerBadges": false,
  "motion": "still",
  "density": "dense",
  "accents": [
    "primary",
    "accent",
    "secondary",
    "muted"
  ]
}

## Signature component recipes

### Button
Use `Button` for primary, secondary, outline, and ghost actions. Primary actions must expose the language's strongest contrast pair, while secondary and ghost actions should preserve the surface treatment instead of falling back to default neutral SaaS styling.

### Card
Use `Card`, `CardHeader`, `CardContent`, `CardFooter`, and `CardAction` as the main composition frame. Cards should demonstrate the language's surface, border, hierarchy, and density rules rather than appearing as generic rounded rectangles.

### Input and Textarea
Use `Input` and `Textarea` with visible focus rings, field labels, validation states, and the language's rhythm. Forms should show real product content, not placeholder-only controls.

### Select, Tabs, and Table
Use `Select`, `Tabs`, and `Table` to prove navigation, filtering, and dense data states. The table should show row rhythm, separators, hover/focus states, and an empty or status state when the language calls for it.

### Dialog and Sheet
Use `Dialog` for centered decisions and `Sheet` for contextual editing. Both should inherit the language's spacing, border, overlay, and motion rules.

## Preview shots

- `application-shell`: dashboard or workspace shell with navigation, cards, forms, and state badges.
- `detail-editor`: focused editing flow using input, textarea, select, switch/checkbox, dialog or sheet, and action buttons.
- `data-operations`: table-heavy operational view with tabs, dropdown menu affordances, badges, and destructive/empty states.
- Each preview shot must include a renderable `scene` payload with concrete headline, description, actions, and rows/fields/stats for the UI preview.

## Implementation contract

- Start from local `ui/src/components/ui` shadcn-style primitives; do not create a second component system.
- Apply `/katagami/shadcn/after-school-diskette-society/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 cream ABS plastic, off-white paper, black manga ink, faded label gray, and one restrained blue annotation channel.; Name interface modules as plausible school computer-club artifacts such as seating charts, disk ledgers, cable labels, boot logs, and printer strips.; Make manga influence structural: panel crops, gutter rhythm, speed-line restraint, and instructional diagram hierarchy.; Use terminal fragments as small punchlines or status whispers, no more than one short command per chip.; Give one panel dominance and vary all neighboring panels by scale, density, and orientation.; Use red only for tiny correction ticks, wrong-disk notes, or a single overdue warning.; Preserve accessibility with strong body contrast, readable 16px text, and annotations that remain supplementary rather than required instructions.
- Do not: Do not use green matrix rain, neon glows, vaporwave gradients, cyberpunk purple, or black-background hacker theatrics.; Do not draw anime characters or fan-art mascots; the manga reference is page architecture, not illustration fandom.; Do not create three equal cards in a row, generic analytics dashboards, CRM widgets, or SaaS pricing/feature grids.; Do not use chrome, glassmorphism, military HUD targeting marks, dense code waterfalls, or fake threat-intelligence panels.; Do not add decorative colors beyond blue annotations and tiny red correction marks.; Do not let handwritten notes become illegible decoration; every note should clarify, question, or humanize a nearby system detail.

## 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 AfterSchoolDisketteSocietyShadcnKit() {
  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">After-School Diskette Society</h2>
          <p className="mt-1 max-w-xl text-sm text-muted-foreground">
            Use the Katagami registry theme, then compose these shadcn primitives
            with the language-specific component recipes.
          </p>
        </div>
        <Button>Apply theme</Button>
      </div>

      <Tabs defaultValue="components">
        <TabsList>
          <TabsTrigger value="components">Components</TabsTrigger>
          <TabsTrigger value="states">States</TabsTrigger>
          <TabsTrigger value="export">Export</TabsTrigger>
        </TabsList>
      </Tabs>

      <Card>
        <CardHeader>
          <CardTitle>Component recipe</CardTitle>
          <CardDescription>
            Replace this starter content with the agent-authored product scene
            from components.md and preview-shots.json.
          </CardDescription>
        </CardHeader>
        <CardContent className="grid gap-3 sm:grid-cols-[1fr_auto]">
          <Input defaultValue="Tokenized shadcn surface" aria-label="Recipe name" />
          <Button variant="secondary">Preview state</Button>
        </CardContent>
        <CardFooter className="justify-between">
          <Badge>Ready</Badge>
          <Button variant="outline">Copy recipe</Button>
        </CardFooter>
      </Card>
    </section>
  );
}
```

## Layout notes

{
  "breakpoints": "mobile <= 640px, tablet 641px-980px, desktop >= 981px; annotations become inline notes on narrow screens to preserve readability.",
  "density": "Medium-high informational density, but with deliberate quiet cream margins so annotations and technical fragments feel found rather than crammed.",
  "grid": "Desktop uses a 12-column max-width 1180px page with asymmetrical 7/5 and 4/8 panel spans; tablet collapses to 6 columns; mobile becomes one column with preserved tab and annotation layering.",
  "responsive": "Keep the dominant clubroom panel first, then printer strip, seating chart, boot notes, and archive queue; never reorder into equal marketing cards.",
  "whitespace": "Outer margins are broad at 48-88px while internal label gaps are tight at 4-12px, creating the rhythm of a notebook page with crowded notes around calm diagrams."
}
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": "after-school-diskette-society",
    "name": "After-School Diskette Society",
    "slug": "after-school-diskette-society"
  },
  "installCommand": "npx shadcn@latest add button card input textarea select dialog sheet tabs badge separator checkbox switch slider tooltip dropdown-menu table",
  "primitives": [
    "button",
    "card",
    "input",
    "textarea",
    "select",
    "dialog",
    "sheet",
    "tabs",
    "badge",
    "separator",
    "checkbox",
    "switch",
    "slider",
    "tooltip",
    "dropdown-menu",
    "table"
  ],
  "identityNotes": [
    "Use cream paper and warm ABS surfaces with thin black manga-panel borders, slight 1deg taped-label rotations, and inset ruled-grid underlays built from repeating-linear-gradient CSS.",
    "Place blue-ballpoint annotations as absolutely positioned marginal notes with arrow rules, handwritten-style text, and small circled numbers that correct or question nearby interface modules.",
    "Build navigation from floppy-disk label tabs: gray adhesive rectangles with clipped corners, compact uppercase labels, and tiny red correction ticks only on active or warning states.",
    "Embed terminal prompt fragments as quiet jokes inside panels using bitmap monospace, low-contrast phosphor-white chips, and short DOS/V commands instead of streaming code walls.",
    "Compose pages as asymmetrical clubroom diagram sheets: one dominant manga crop, several dense technical notes, seating-chart cells, and a full-width printer-test strip that breaks the grid."
  ],
  "visualProfile": {
    "family": "paper-collage",
    "material": "paper",
    "contour": "default",
    "border": "dashed",
    "underlay": true,
    "grain": true,
    "stickerBadges": false,
    "motion": "still",
    "density": "dense",
    "accents": [
      "primary",
      "accent",
      "secondary",
      "muted"
    ]
  },
  "shots": [
    {
      "id": "application-shell",
      "title": "Application shell",
      "viewport": "desktop",
      "primitives": [
        "button",
        "card",
        "input",
        "select",
        "tabs",
        "badge",
        "separator",
        "table"
      ],
      "composition": "A real product workspace with navigation, summary cards, filtering controls, and one dense content region.",
      "mustShow": [
        "primary and secondary actions",
        "card hierarchy",
        "filterable state",
        "table or list density"
      ],
      "avoid": [
        "component inventory walls",
        "placeholder-only content",
        "generic rounded SaaS chrome"
      ],
      "scene": {
        "eyebrow": "workspace spread",
        "headline": "After-School Diskette Society 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 cream ABS plastic, off-white paper, black manga ink, faded label gray, and one restrained blue annotation channel.",
      "Name interface modules as plausible school computer-club artifacts such as seating charts, disk ledgers, cable labels, boot logs, and printer strips.",
      "Make manga influence structural: panel crops, gutter rhythm, speed-line restraint, and instructional diagram hierarchy.",
      "Use terminal fragments as small punchlines or status whispers, no more than one short command per chip.",
      "Give one panel dominance and vary all neighboring panels by scale, density, and orientation.",
      "Use red only for tiny correction ticks, wrong-disk notes, or a single overdue warning.",
      "Preserve accessibility with strong body contrast, readable 16px text, and annotations that remain supplementary rather than required instructions."
    ],
    "dont": [
      "Do not use green matrix rain, neon glows, vaporwave gradients, cyberpunk purple, or black-background hacker theatrics.",
      "Do not draw anime characters or fan-art mascots; the manga reference is page architecture, not illustration fandom.",
      "Do not create three equal cards in a row, generic analytics dashboards, CRM widgets, or SaaS pricing/feature grids.",
      "Do not use chrome, glassmorphism, military HUD targeting marks, dense code waterfalls, or fake threat-intelligence panels.",
      "Do not add decorative colors beyond blue annotations and tiny red correction marks.",
      "Do not let handwritten notes become illegible decoration; every note should clarify, question, or humanize a nearby system detail."
    ]
  }
}
related

More like this