open-press

OpenPress · document tree · rendered output · v0.3.0

OpenPress turns a document tree into publishable pages.

Chapters live as MDX, design decisions live as tokens, and the same workspace renders fixed-layout A4 pages, PDF, and a public web reader. 

$ npx skills add quan0715/open-press
View live example

document tree

Click to copy · skills install under .agents/skills/, auto-detected by Claude Code, Cursor, Codex, Gemini CLI, Cline, Continue, and 50+ other AI agents.

  • Chapters map to the document table of contents
  • Theme tokens control page rhythm, type, and accent
  • MDX changes re-render into A4 pages and the web reader

Why OpenPress

Your agent edits source; OpenPress renders the document.

Document tree

Chapters are a navigable structure.

The source mirrors the table of contents: cover, chapters, appendix, assets, and config stay in predictable places.

Theme tokens

Design changes are controlled inputs.

Typography, margins, accent color, and page rhythm live in tokens instead of being scattered across one-off CSS edits.

MDX content

Content changes render into pages.

A chapter file can mix prose, figures, callouts, and tables; preview shows exactly what changed before PDF export.

Init -> author -> publish

Talk to the agent. Then inspect the page.

Copy the prompt for the stage you are in. The agent writes into the workspace; OpenPress keeps the result page-safe, reviewable, and ready to deploy.

  1. 1.

    Init the workspace

    Start from title, audience, language, and style pack. The init flow creates a real file structure instead of a blank canvas.

    Using OpenPress, help me initialize a document workspace. Ask for title, audience, language, and style pack, then create the starter project with a first outline.
  2. 2.

    Author with the agent

    Work chapter by chapter. Ask for structure, examples, captions, comparison tables, and tone changes while preview remains the source of truth.

    Use OpenPress writing and hierarchy skills. Turn the current outline into chapter 1, keep confirmed facts unchanged, and mark missing details as [TODO].
  3. 3.

    Export and deploy

    Validate the workspace, render the public reader, export the PDF, and deploy only after confirming the target Pages project.

    Use OpenPress deploy flow. Run validation, render the web reader, export the PDF, and prepare a Cloudflare Pages deploy dry run before publishing.

    openpress:validate openpress:render openpress:pdf openpress:deploy

Bring your own agent

OpenPress gives it the document rules.

openpress-writing

Audience, narrative, captions, factual boundaries. Loads portable writing skills (繁中, teaching notes) per content type.

openpress-design

Theme tokens, page surfaces, PDF-safe CSS. Tells the agent which CSS layer owns which decision.

openpress-document-hierarchy

H1/H2/H3/H4 model, TOC depth, appendix placement. Stops the agent from making every algorithm a chapter.

openpress-diagram-drawing

When a figure belongs vs a table vs prose. Diagram bodies stay semantic; explanation moves to captions.

openpress-deploy

Public-release gate. Forces confirmation naming the target Cloudflare Pages project before any deploy.

chinese-ai-writing-polish

Removes AI-like patterns from 繁體中文 professional writing. Auto-loaded when the document language is Chinese.

No project yet?

Author a document in the next minute.

One command creates the workspace; your agent takes it from there. 

$ npx @open-press/cli init my-doc --pack editorial-monograph

Available style packs: editorial-monograph (formal long-form) and claude-document (warm working notes).