Kami (紙, かみ) means paper: the surface where a finished idea lands. Most document design drifts into two failure modes: generic corporate gray, or gradient-heavy SaaS styling. Neither reads like something made with care.
Kami holds one design idea across six document types: one-pagers, long docs, formal letters, portfolios, resumes, and slides. Each format shares a warm parchment canvas, a single ink-blue accent, serif for authority, sans for utility, and editorial whitespace tuned for print.
Kami is a document design system for the AI era: simple enough for agents to follow, strict enough to keep every output coherent, and practical enough to turn a prompt into a presentable PDF without design cleanup.
Part of a trilogy: Kaku (書く) writes code, Waza (技) drills habits, Kami (紙) delivers documents.
One-Pager · 中文 Tesla 公司介绍 · 单页 |
Slides · English Agent keynote, 6 slides |
Resume · English Founder CV, 2 pages |
Portfolio · 中文 Kaku 项目作品集 · 6 页 |
Claude Code
npx skills add tw93/kami -a claude-code -g -yCodex
npx skills add tw93/kami -a codex -g -yGeneric agents (opencode, pi, and other tools that read from ~/.agents/; codex is included, but use -a codex if you only target Codex)
npx skills add tw93/kami -a '*' -g -yClaude Desktop
Download kami.zip, open Customize > Skills > "+" > Create skill, and upload the ZIP directly (no need to unzip).
The ZIP is intentionally lightweight: Chinese TsangerJinKai font files are loaded from local checkout first, then jsDelivr CDN, not bundled inside. If the font renders incorrectly, Claude will download it automatically on the next run.
To update: download the same ZIP URL again, click "..." on the kami skill card, choose Replace, and upload the new ZIP.
The skill auto-triggers when you describe what you need, no slash command required. It supports one-pagers, long docs, formal letters, portfolios, resumes, and slides in both Chinese and English.
make a one-pager for my startup / turn this research into a long doc / write a formal letter / make a portfolio showcasing my projects / build me a resume / design a slide deck for my talk / 帮我做一份一页纸 / 帮我排版一份长文档 / 帮我写一封正式信件 / 帮我做一份作品集 / 帮我做一份简历 / 帮我做一套演讲幻灯片
To include inline charts, mention the data and chart type in your prompt. Kami embeds bar charts, line charts, and donut charts directly into the document as SVG, no external tools needed.
add a revenue breakdown donut chart / show the quarterly delivery trend as a bar chart / draw a line chart of user growth / 加一个营收结构环形图 / 用柱状图展示季度交付量 / 画一条用户增长折线
Warm parchment canvas, ink blue as the sole accent, serif carries hierarchy, no hard shadows or flashy palettes. This is not a UI framework; it is a constraint system for printed matter. Quality documents should read as composed pages, not dashboards.
Six document types (One-Pager, Long Doc, Letter, Portfolio, Resume, Slides), each with Chinese and English variants. Twelve inline SVG diagram types are included: architecture, flowchart, quadrant, bar chart, line chart, donut chart, state machine, timeline, swimlane, tree, layer stack, and Venn. Kami picks the right variant based on the language you write in.
| Element | Rule |
|---|---|
| Canvas | #f5f4ed parchment, never pure white |
| Accent | Ink blue #1B365D only, no second chromatic hue |
| Neutrals | All warm-toned (yellow-brown undertone), no cool blue-grays |
| Serif | Body 400, headings 500. Avoid synthetic bold |
| Line-height | Tight titles 1.1-1.3, dense body 1.4-1.45, reading body 1.5-1.55 |
| Shadows | Ring or whisper only, no hard drop shadows |
| Tags | Solid hex backgrounds only. rgba() triggers a WeasyPrint double-rectangle bug |
Fonts: Chinese uses TsangerJinKai02 serif + Source Han Sans. TsangerJinKai is free for personal use, commercial use requires a license from tsanger.cn. English uses Newsreader serif + Inter sans, both OFL open source.
Full spec: design.md. Cheatsheet: CHEATSHEET.md.
I invest in US equities and often ask AI to generate analysis reports. The earliest drafts looked like default Google Docs: plain, inconsistent, and easy to forget. I did not want each document to shift style every time, so I kept refining the typography, palette, and spacing until the page became something I wanted to keep reading.
Later, I was invited to give a talk on my article "The Agent You Don't Know: Principles, Architecture, and Engineering Practice" and needed a slide deck that shared the same visual standard. That iteration pushed the system further: inline SVG diagrams, a unified warm palette, and a tighter editorial rhythm. Over time it covered the document formats I use most, so it became kami, a visual language I can reuse with confidence and send out without hesitation.
- If kami helped you, share it with friends or give it a star.
- Got ideas or bugs? Open an issue or PR.
- I have two cats, TangYuan and Coke. If you think kami delights your life, you can feed them canned food.
MIT License. Feel free to use kami and contribute.