Agent skill · design visual · nexu-io
kami-landing
Produce a print-grade single-page kami (紙 / 纸) document — warm parchment canvas, ink-blue accent, serif at one weight, no italic, no cool grays. The output reads like a professional white paper or studio one-pager, not an app UI. Multilingual by design (EN · zh-CN · ja). One self-contained HTML file, zero dependencies.
Why this skill is useful
Provides specific design patterns and aesthetic guidelines for creating a print-grade document that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
kami-landing Produce a single-page document in the kami (紙 / 纸) design system. The aesthetic borrows from editorial print, technical white papers, and old typewritten correspondence — the goal is good content on good paper, not modern app UI. Design system source of truth: design-systems/kami/DESIGN.md. Read it before shipping. Tokens, type rules, the "ten invariants", and forbidden colors all live there. What you get A single self-contained HTML file with: Warm parchment canvas (#f5f4ed) — never #ffffff. Single chromatic accent — ink-blue (#1B365D), used on the section number, the headline accent word, the left rule of the manifesto, and the metric values. Anywhere else, ink-blue must cover ≤ 5% of the document surface area. Serif at one weight (500) for hierarchy — Charter (EN), TsangerJinKai02 / Source Han Serif (CN), or YuMincho (JA), selected by the language parameter. No italic anywhere. Tight print rhythm — line-heights 1.10–1.55, letter-spacing per language (0 for EN, 0.35px for CN, 0.02em for JA). Numeric stacks set in font-variant-numeric: tabular-nums so metric columns and pagination digits sit cleanly aligned. Depth via 1px rings + whisper shadows (0 4px 24px rgba(0,0,0,0.05)). No hard drop shadows, no neumorphism, no backdrop-filter blurs. Tag fills as solid hex (e.g. #E4ECF5), never rgba() — print renderers double-paint alpha tags. Responsive at 1280 / 980 / 768 / 560. Page structure Workflow contract 1. Gather brand brief Use AskQuestion (or equivalent) to collect the brand brief in chunks. Don't dump the whole input list on the user; ask in two rounds: 1. Identity round — name, tagline, location, edition / version, primary URL, dominant language. 2. Content round — manifesto paragraph + signature, 3-6 metric tiles, 3-5 chapter (title + lede + body) entries. 2. Pick the language stack The language parameter controls which --serif stack is set on :root. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/kami-landing--caf8b5