Typesetter is a Claude skill that converts any topic, conversation, or file into a single-file HTML document with a fixed reading design, triggered via `/paper` or `/typeset`.

Stars

24

7-day growth

No data

Forks

0

Open issues

0

License

No data

Last updated

2026-07-06

AI repository intelligence
FR-AI / ANALYSIS

Why it is worth attention

It enforces a disciplined, thesis-first writing process and a curated component library to produce clean, readable documents without external dependencies or JavaScript.

Who it is for

  • Claude Code users who want to generate polished reading documents from raw content
  • Technical writers and knowledge workers seeking a structured alternative to markdown
  • Developers who need to turn planning sessions or rough notes into shareable guides
  • Anyone who finds raw markdown daunting and prefers a designed, fixed-layout HTML output

Use cases

  • Turn a messy planning conversation into a readable document with `/paper this plan`
  • Explain a complex concept like 'how transformers attend to context' with a thesis-first structure
  • Convert a rough markdown file into a polished guide with a clear reading hierarchy
  • Compare a small set of options (2-4) using the card component for side-by-side presentation

Strengths

  • Single-file HTML output with no external requests, readable down to 360px
  • Fixed design system (warm paper, serif body, accent hues) that never changes per invocation
  • Enforced quality checks: one thesis panel, proper escaping, untouched CSS except accent hues
  • Component library (thesis, cards, numbered flow, rows, snippets, etc.) that maps structure to meaning

Considerations

  • Only produces static reading documents — no interaction, state, or JavaScript
  • Requires Claude Code environment and proper installation as a skill
  • Fixed design may not be customizable beyond accent hue adjustments

README quick start

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:

  1. A topic. /paper why vector databases exist. Claude researches or draws on its own knowledge, then typesets the explanation.
  2. Conversation content. /paper this plan, or "make what we just discussed readable". Typesets whatever we already worked out.
  3. 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:

  1. 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.
  2. 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.
  3. 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

Description

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

Related repositories

Similar projects matched by category, topics, and programming language.

ddosi
Featured
ddosi GitHub avatar

PacketLens

PacketLens is a pure front-end, offline pcap analysis tool that runs entirely in the browser, supporting deep protocol decoding, HTTPS decryption, and million-packet instant loading without any backend.

HTML
19
ViffyGwaanl
Featured
ViffyGwaanl GitHub avatar

kimi-k3-learn

An interactive learning system that turns the 47-page Kimi K3 technical report into a single offline HTML file with running algorithms, 3D visualizations, spaced repetition quizzes, and a smart highlighting QA tool.

AI & Machine Learning
15
iamtechartist
Featured
iamtechartist GitHub avatar

human-cell-visualizer

An interactive 3D visualization of three human cell types using Three.js, WebGL particles, and custom GLSL shaders, allowing users to rotate, zoom, morph, and explore annotated structures.

Design & Creative
13