Why

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 every format: warm parchment canvas, a single ink-blue accent, serif for authority, sans for utility, editorial whitespace tuned for print.

Part of a trilogy: Kaku (書く) writes code, Waza (技) drills habits, Kami (紙) delivers documents.

See it

One-Pager · 中文 Tesla 公司介绍 · 单页

Slides · English Agent keynote, 6 slides

Resume · English Founder CV, 2 pages

Portfolio · 中文 Kaku 项目作品集 · 6 页

Usage

Claude Code

npx skills add tw93/kami -a claude-code -g -y

Codex

npx skills add tw93/kami -a codex -g -y

Generic agents (opencode, pi, and other tools that read from ~/.agents/)

npx skills add tw93/kami -a '*' -g -y

Claude Desktop

Download from Releases, open Customize > Skills > "+" > Create skill, upload the ZIP.

The skill auto-triggers when you describe what you need, no slash command required.

make a one-pager for my startup / build me a resume / write me a recommendation letter / design a slide deck for my talk / turn this into a polished white paper / make a portfolio showcasing my projects / 帮我排版一份白皮书 / 帮我做一份作品集 / 生成一份项目方案

Design

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. Three inline SVG diagram types (architecture, flowchart, quadrant) are included. 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 at 400, headings at 500. Avoid synthetic bold
Line-height	Tight titles 1.1-1.3, dense body 1.4-1.45, reading body 1.5-1.55. Never 1.6+
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 / design.en.md. Cheatsheet: CHEATSHEET.md / CHEATSHEET.en.md.

Background

I invest in US equities and regularly ask AI to generate analysis reports. The output always looked like a default Google Doc: bland, inconsistent, forgettable. I can't stand ugly documents, especially when every report comes out looking different from the last one. So I kept tweaking the typography, colors, and spacing until I had something I actually wanted to read.

Then I was invited to present a talk based on my article "The Agent You Don't Know: Principles, Architecture, and Engineering Practice" and needed a slide deck that matched the same standard. That round pushed the system further, adding inline SVG diagrams, a consistent warm palette, and tighter editorial rhythm. Eventually it was doing enough that I pulled it into its own package. That became kami: one visual language I like, applied to everything I ship.

Support

• 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 🥩.

License

MIT License. Feel free to use kami and contribute.