为什么值得关注

它强制实施先写论点的写作流程和精选的组件库，无需外部依赖或 JavaScript，就能生成清晰、可读的文档。

适合谁使用

希望从原始内容生成精美阅读文档的 Claude Code 用户
寻求 Markdown 替代方案的技术写作者和知识工作者
需要将规划会议或粗略笔记转化为可分享指南的开发者
觉得原始 Markdown 难以阅读、偏爱固定布局 HTML 输出的人

典型使用场景

将混乱的规划对话转化为可读文档：`/paper this plan`
使用论点优先结构解释复杂概念，例如“transformers 如何关注上下文”
将粗略的 Markdown 文件转换为具有清晰阅读层级的精美指南
使用卡片组件并排比较少量选项（2-4 个）

项目优势

单一 HTML 文件输出，无外部请求，可在 360px 宽度下正常阅读
固定设计系统（暖纸色、衬线字体、强调色），每次调用不变
强制质量检查：仅有一个论点面板、正确转义、CSS 除强调色外保持不变
组件库（论点、卡片、编号流程、行、代码片段等）将结构映射到含义

使用前须知

仅生成静态阅读文档——无交互、状态或 JavaScript
需要 Claude Code 环境并正确安装为技能
固定设计除调整强调色外无法自定义

README 快速开始

Typesetter

A Claude skill that turns any topic, conversation, or file into a single-file HTML document in one fixed reading design. Trigger it with /paper or /typeset.

Demo

See it in action: example output

Why

I find raw markdown daunting to read. Long explanations, plans, and guides sit better in a designed document than in a wall of # and -. I don't want to hand-design a new layout every time either, so the skill fixes one design system once and reuses it for every document after.

This is a reading document, not an app. No JavaScript, no controls, no state. If I want interaction, that's /aha or /crack, not this.

What

The skill accepts three kinds of input:

A topic. /paper why vector databases exist. Claude researches or draws on its own knowledge, then typesets the explanation.
Conversation content. /paper this plan, or "make what we just discussed readable". Typesets whatever we already worked out.
A file. Upload a markdown or text file. Claude reads it, restructures it for reading, typesets it.

If I invoke it bare with nothing to point at, it asks one question: what should the document teach, and who is it for.

Output is one .html file, saved and shared through present_files. No external requests, readable down to 360px.

How

The design is fixed in assets/template.html. The CSS never changes per invocation. Warm paper background, dark ink, a serif body for reading, monospace for labels and code, a blueprint teal and workshop amber accent pair. The one knob I can turn: ask for a different accent mood and it adjusts the three --accent-* hues, nothing else.

The process before writing anything:

Find the thesis first. Every document carries exactly one thesis panel, the single most important idea, stated in two sentences. If Claude can't state it that tight, it hasn't understood the content yet.
Outline as sections. One idea per section. Six to eight sections for a full document, fewer for a short one. Ordered as a reader's journey: the problem, the cast, the mechanics, the practice, the close.
Map content shape to component, not the other way around. This is the rule that matters most: structure must encode something true. A numbered flow claims "this is a sequence." Cards claim "these are p

项目描述

Claude Code skill that turns any topic, conversation, or file into a single-file, beautifully typeset HTML document - trigger with /paper

typesetter