Doc Kami Parchment
Turn real copy into a warm parchment one-pager or letter with ink-blue accents and editorial serif typography using the Kami Parchment Open Design template.
Overview
Doc Kami Parchment is an agent skill most often used in Build (also Validate landing, Launch distribution) that formats content into warm parchment documents with ink-blue accents and editorial serif typography.
Install
npx skills add https://github.com/nexu-io/open-design --skill doc-kami-parchmentWhat is this skill?
- Fixed visual signature: parchment canvas #f5f4ed and monochrome ink-blue accent #1B365D
- Single serif family with editorial-grade typography for A4/Letter long pages
- Open Design Studio template with debounce HTML preview and sample Issue №26 one-pager
- Personal scenario prototype on desktop web surface via html-anything upstream
- Example prompt enforces real content—no lorem ipsum or placeholder images
- Palette anchors #f5f4ed canvas and #1B365D accent
- A4 / Letter long-page aspect hint
Adoption & trust: 676 installs on skills.sh; 61.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your message is ready but default markdown or generic slides make a solo builder look amateur compared to a designed editorial one-pager.
Who is it for?
Founders and indie makers publishing one-pagers, open letters, or studio issues who want a fixed parchment + ink-blue design system without rebuilding CSS each time.
Skip if: Dark-mode SaaS dashboards, multi-brand design systems that need arbitrary palettes, or teams that require Figma handoff instead of HTML documents.
When should I use this skill?
You need the Kami Parchment Document template to turn real content into warm parchment layout with monochrome ink-blue accents and one serif family.
What do I get? / Deliverables
You get an HTML-ready Kami parchment document that keeps palette, serif, and editorial rules while your real copy and data replace the sample Issue №26 structure.
- Editorial parchment HTML document
- Markdown-styled long page matching Kami signature
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Polished document deliverables are produced while you build—specs, one-pagers, and investor letters share the same Build docs shelf. Docs is canonical because the skill outputs editorial HTML/markdown documents, not app chrome or backend APIs.
Where it fits
Render a credible one-page story for a waitlist or pitch attachment using parchment styling and real metrics.
Publish an Open Design Studio-style issue page with editorial hierarchy and monospace-adjacent serif rhythm.
Ship a letter or changelog as a branded HTML document for email or static hosting.
How it compares
Use as a styled document template skill—not a generative media API and not a full component library for product UI.
Common Questions / FAQ
Who is doc-kami-parchment for?
Solo builders and small teams using Open Design who need serif, parchment-styled documents for reports, letters, and one-pagers with consistent ink-blue accents.
When should I use doc-kami-parchment?
In Validate when polishing a landing narrative; in Build for docs and release one-pagers; at Launch when distribution assets must look editorial—whenever content should match the Kami parchment signature.
Is doc-kami-parchment safe to install?
It is primarily a design template and HTML preview workflow; review the Security Audits panel on this page and avoid embedding untrusted third-party scripts in generated HTML.
SKILL.md
READMESKILL.md - Doc Kami Parchment
【模板: Kami 羊皮纸文档】 【意图】严肃排版文档: one-pager / 长报告 / 信函 / 简历 / 财报 / changelog / portfolio。Inspired by tw93/kami。强调"写得像被排过版的纸", 不是 dashboard, 不是网页。 【硬性视觉签名 — 不许改】 - **画布**: 暖羊皮纸 `#f5f4ed` (永远不用纯白 `#fff`)。次级背景 `#efeee5`。 - **墨色**: 主文字 `#1f1d18` (近黑暖灰, 不用纯黑 `#000`)。次文字 `#6b665b`。 - **唯一色彩**: 墨蓝 `#1B365D` ——所有 accent (链接、tag 描边、重点数字、引用左 rule) 只能用这一个色, 严禁多色。 - **字体**: 一种语言一种衬线, 全文不混用: - 英文: `Charter` (fallback: `Source Serif Pro`, `Iowan Old Style`) - 中文: `TsangerJinKai02 W04` (fallback: `Noto Serif SC`) - 日文: `YuMincho` (fallback: `Noto Serif JP`) - Body 400, Heading 500 (不要 700/800/900)。 - **行高**: 标题 1.1–1.3, 紧凑正文 1.4–1.45, 阅读型正文 1.5–1.55。 - **绝不**: drop-shadow / blur / 圆角 ≥ 8px / 渐变 / 霓虹色 / rgba (用 solid hex)。 - **细节**: tag 用 solid hex 背景方块 (因为 WeasyPrint 不渲染 rgba 好); 单线几何 icon; 边缘 1px hairline `#d4d1c5` rule, 长度受控不到边。 【可选文档类型 — 按用户内容判断】 - **One-Pager** — 顶 logotype (Charter italic) + 标题 + lede + 3 列要点 + 底脚 metadata。 - **Long Doc** — 封面页 (大标题 + 副标 + 作者 + 日期) → 目录 (kicker + page no.) → 章节 (folio 顶角 + section rule + body) → 注释脚注 + 文末 colophon。 - **Letter** — 抬头地址 + 日期 + 收件人 + 正文 (左对齐, 段间空 1.5em) + 署名 + 签名占位线。 - **Portfolio** — 项目 hero (大标题 + sub) + 1 张全幅图 (用 CSS 块绘制占位) + 项目描述 + 角色 / 时间 / stack 元数据 row。 - **Resume** — 顶部姓名 (大字) + tagline 一行 + contact row + 主要 section: experience (公司 / 时间 / 职位 / bullets) + skills + education。 - **Slides** — keynote 风, 页数由【用户内容】决定 (短内容 6 页起步, 长内容应更多), 每页满铺羊皮纸, 大标题 + lede + 角标 page no., 简洁到只有"被印出来"的感觉。 - **Equity Report** — 公司名 + ticker + Q × 年份 + key metrics row (revenue / margin / yoy) + body 分析 + 图表 (SVG 单色折线)。 - **Changelog** — 版本号 (Charter italic 大字) + 日期 + 改动列表 (Added / Changed / Fixed), 单 rule 分隔。 【设计准则】 - "Composed pages, not dashboards." 不要堆 KPI 卡, 不要堆 emoji 图标, 不要 hero gradient。 - "Ring or whisper only, no hard drop shadows." 阴影只能是 `0 0 0 1px #d4d1c5` 这种 hairline 描边。 - 文字层级靠**衬线对比 + 字号 + 留白**, 不靠颜色。 - 单文件 HTML, 用 Tailwind CDN; 全文中英混排时加盘古之白; 不要外链图片, 占位用 paper-tint 色块 + 1px ink 描边。