Kami紙
Good content deserves good paper. Kami is a layout design system for the AI era, making documents clear, readable, and memorable.
00 · See it
Output Samples
Give Claude the brief: one-pagers, long docs, letters, portfolios, resumes, slides all become polished layouts from one small, reliable rule set. The same brief also travels to image renderers, with the copy-paste prompt and sample outputs in the README.
Landing Pages
Built with Kami
The same landing-page template applied to three different products. One constraint set, three distinct purposes.
01 · Usage
Install & Invoke
Tell Claude what you need, for example "build me a resume", "make a one-pager for my startup", or "design a slide deck for my talk". The skill auto-triggers, no slash command needed.
# Claude Code, Codex, Cursor, and other agents npx skills add tw93/kami -a claude-code codex cursor -g -y # Claude Code plugin (v2.1.142+) /plugin marketplace add tw93/kami /plugin install kami@kami # Codex plugin codex plugin marketplace add tw93/kami codex plugin add kami@kami # Claude Desktop Download kami.zip, then upload it in Customize > Skills > "+" > Create skill
02 · Manifesto
Design Principles
Warm parchment canvas, ink blue as the sole accent, serif carries hierarchy, while hard shadows and flashy palettes recede. This system is built for printed matter: stable, clear, and composed. Parchment is the default; an opt-in white-paper variant prints any document on a white background while keeping the warmth in cards and tables.
- 1
Page background is parchment
#f5f4ed, never pure white - 2
Accent color is ink blue
#1B365Donly; no second chromatic hue - 3
All grays are warm, yellow-brown undertone; no cool blue-grays
- 4
One serif family carries headlines and body; add a distinct sans only for real UI chrome
- 5
Serif body at 400, headings at 500. Avoid synthetic bold
- 6
Three line-height bands: tight titles 1.1-1.3 / dense 1.4-1.45 / reading 1.5-1.55
- 7
Tag backgrounds must be solid hex; no rgba, WeasyPrint double-rectangle bug
- 8
Keep surfaces flat by default; reserve a whisper shadow for real floating elements
03 · Color
Warm Restraint
One accent + warm neutrals + zero cool colors. Ink blue covers no more than 5% of any page. Beyond that is clutter, not restraint.
Canvas
Parchment
Page background, the emotional foundation
#F5F4EDIvory
Cards / elevated surfaces
#FAF9F5Warm Sand
Button default / interactive surfaces
#E8E6DCDeep Dark
Dark theme page base, not pure black
#141413Brand
Ink Blue
Primary color · CTA · labels · section overline
#1B365DInk Light
Links on dark surfaces · lighter variant
#2D5A8ADark Surface
Dark theme container · warm charcoal
#30302EError
Error state, deep warm red
#B53333Warm Neutrals
Near Black
#141413Dark Warm
#3D3D3AOlive
#504e49Stone
#6b6a64Tag Tints
Use one of two registered solid tints. #EEF2F7 recedes; #E4ECF5 is the default. Solid hex avoids WeasyPrint's double-rectangle rendering bug.
Quiet
#EEF2F7Default
#E4ECF504 · Typography
Type System
One serif family carries hierarchy and body; mono is reserved for code and technical labels.
Aa
Serif · Headlines + Body
Charter / TsangerJinKai02
Used for headlines, body text, pull quotes, and numeric emphasis. English uses Charter, Chinese uses TsangerJinKai02.
</>
Mono · Code
JetBrains Mono
Code blocks, version numbers, hex values, tabular figures.
Scale (print pt; screen px = pt x 1.33)
clear, stable, poised
weight 500
line 1.10
weight 500
line 1.20
weight 500
line 1.25
weight 500
line 1.30
weight 400
line 1.55
weight 400
line 1.45
weight 600
line 1.35
05 · Spacing & Shape
Rhythm & Form
Base unit: 4pt. Denser layouts get smaller margins; more formal documents get larger ones.
| Scale | Value | Use | |
|---|---|---|---|
| xs | 2-3 pt | Inline elements | |
| sm | 4-5 pt | Tag padding · tight layout | |
| md | 8-10 pt | Component internals | |
| lg | 16-20 pt | Between components · card padding | |
| xl | 24-32 pt | Section title margins | |
| 2xl | 40-60 pt | Between major sections | |
| 3xl | 80-120 pt | Between long-doc chapters |
Radii
Depth
Flat is the default. Use whitespace, one quiet fill, or one neutral hairline. Reserve a whisper shadow for a real screenshot, popover, or other surface that actually floats.
06 · Components
Atomic Modules
A small fixed set, kept only where it solves a concrete document problem.
Buttons
fill + border · no shadow · 8px radius
Tags, two levels
solid hex · receded or default
Quote
olive text + italic · no side rule
A thousand no's for every yes, prefer clarity over decoration.
Metric
serif number + sans label · tabular-nums
Section Title
serif 500 · 15pt · size-led hierarchy, no decoration
Plain List
spacing carries rhythm · no marker
- Warm parchment, never pure white
- Ink blue accent, no second color
- Serif carries authority
Code Block
ivory bg + 4pt radius, no border
// warmth from restraint, not from color canvas = parchment; accent = ink_blue palette = warm_neutrals − cool_grays document = serif × hierarchy + generous_space beauty = constraints × intention ÷ noise
Quiet Card
one ivory fill + 8px radius · no border or shadow
Tesla Company Profile · One-Pager
Single A4 page · 4 metric cards + 3 body sections + timeline
07 · Diagrams
Inline Charts
Eighteen inline SVG diagram types covering architecture, process, and data chart scenarios. Tell Claude which type you need and it embeds directly into the document, colors and fonts following the Kami design language.
System components and connections, one focal node
Decision branches, yes/no paths, focal on success
Quarterly revenue comparison, gradient or single color
Revenue structure breakdown, supports 3–6 segments
08 · Decision Lookup
Quick Reference
When in doubt about what to use, consult this table. If it's not here, go back to first principles.
| Task | How |
|---|---|
| Large headline | serif 500, size by hierarchy, line-height 1.10-1.30 |
| Reading body | serif 400, 9.5-10 pt, line-height 1.55 |
| Emphasize a number | color: var(--brand), not bold |
| Separate two sections | Whitespace first; one 0.5pt neutral full-width hairline only when the boundary must be explicit |
| Quote someone | Olive text + italic or indentation; no side rule |
| Show code | Ivory bg + 4pt radius + mono font, no border |
| Primary vs secondary | Primary: brand fill + ivory text; Secondary: warm-sand + charcoal |
| Mark a special card | Use a stronger label or one quiet fill; do not add an accent edge |
| Begin a section | Serif 500 · 15pt · size-led hierarchy, no decoration needed |
| Document cover | Single page, Display size + right-aligned author/date + generous whitespace |
| Show key figures | Baseline row, transparent, no container + serif number, ink blue + sans label |
09 · Anti-Patterns
What to Avoid
Exceptions are allowed, but the reason should be explicit.
Page canvas
NeverPure white #ffffff or cool gray #f3f4f6 as page background. It makes the page feel brittle and weakens the warm parchment character.
InsteadAlways #f5f4ed parchment, with @page background set to the same color to avoid white edges when printing.
Tag tints
Neverrgba(27,54,93,0.18) for tags. WeasyPrint renders padding and glyph areas at different opacity, creating double rectangles.
InsteadUse the registered default tag token #E4ECF5. The rendering stays clean and the color remains stable.
Synthetic bold
NeverHeadlines at font-weight: 600 or heavier synthetic bold. It blurs strokes and degrades typographic quality.
InsteadBody 400, headings 500 (real W05). For more presence, use size, spacing, or ink-blue text, never synthetic bold.
Shadows
NeverHard drop shadow 0 2px 8px rgba(0,0,0,0.3). Visually heavy and likely to print as dark blobs.
InsteadKeep the surface flat. Use whitespace, one quiet fill, or a neutral hairline; reserve a whisper shadow for real floating UI or screenshots.
10 · Background
Design Origins
I like investing in US equities and ask Claude to write research reports all the time. Every output landed in the same default-doc look: gray, flat, a different layout each session. The structure was hard to scan, the formatting felt dated, and nothing about the page made me want to keep reading. So I started fixing the typography, the palette, the spacing, one rule at a time, until the report became a page I actually enjoyed.
Later I needed to present "The Agent You Don't Know: Principles, Architecture and Engineering Practice." I already had the document and didn't want to build slides from scratch, so I used Claude Design to lay it out in my own style, tweaked it round after round, and eventually got it to a place I was happy with. That process added inline SVG charts, a unified warm palette, and a tighter editorial rhythm. It kept growing until it covered every document I regularly ship, so I kept abstracting the process, and it became kami: one quiet design system I can hand to any agent and trust the output.
11 · Questions
FAQ
- What is Kami?
- Kami is a constraint-based design system that gives AI-generated documents a consistent editorial language through one accent color, serif-led hierarchy, and a warm parchment canvas, and can also guide image renderers such as Claude Design or GPT Canvas.
- What can it produce?
- Kami includes eight document templates, a multilingual landing-page system, and 18 inline SVG diagram types. Documents export to PDF or PNG, and slides also have an editable PPTX path.
- Can Kami match my brand?
- Yes, share your brand colors, fonts, and layout preferences or provide a brand profile, and your brief will override Kami's defaults.
- What languages does it support?
- Kami supports English, Chinese, Japanese, and Korean with Charter, TsangerJinKai02, YuMincho, and Source Han Serif K respectively, plus per-language tuning for spacing, line height, and type size, while Japanese and Korean remain best-effort CJK paths with visual QA before delivery.






