editorial-monograph

Editorial Monograph

A document style for Serious long-form— A derivation of Japanese minimalism + IBM Carbon hairline style, suited to product proposals, white papers, research reports, specification documents, and other occasions requiring A4 print, clear chapter structure, and long-form reading.

This is a starter-bearing skill: it ships SKILL rules plus a runnable starter/ document workspace (React/MDX entry, theme, design doc, sample chapters). Use openpress to initialize the OpenPress runtime workspace; this skill owns the editorial starter files and design rules.

Visual Signature

Type: serif chapter openers (Noto Serif TC / Source Han Serif TC) + sans body (IBM Plex Sans / PingFang TC)
Lines: 1px hairline + dotted underline for links; no box-shadow / gradient
Color: black, white, and gray as the main palette + three-color status accents (warn / success / info) + chart palette (gold / coral / dark)
Layout: fixed A4 layout, full-page chapter openers, TOC with page numbers but no footer, optional chapter mini cover, automatic figure / table numbering
Chapter numbering: default 01 / 02 / 2.1（pagination + CSS ::before); can change to 一、二、（一） or Chapter 1 / §1.1, tokens and selectors are in the starter's theme/base/typography.css and design.md sections on Typography Scale / Chapter & Section Numbering

Suitable For

product proposal / business plan
whitepaper / spec / requirements doc
academic monograph / long-form research report
editorial-format business report

Not Suitable For

slide deck (no bundled starter; when customizing dimensions, change config.page, do not treat the A4 starter as a slide deck and force-change tokens)
poster / one-pager
marketing landing page

Related Starters

claude-document — warmer paper, Claude-like rhythm. Choose it when the document is closer to a working brief / spec / note than a formal monograph.

Apply To A Workspace

Use openpress to initialize a target workspace, then copy or adapt this skill's starter/press tree into the workspace. Then:

Fill title / subtitle / organization on the <Press> props inside press/<slug>/press.tsx. Merge starter/package.openpress.json into the workspace package.json's "openpress" field for deploy / pdf settings.
Ask openpress to choose the validation/export/render commands needed to confirm the workspace is healthy.
Use openpress for the source-boundary decision; typical editable source areas are press/<slug>/chapters/**/*.mdx for content, press/<slug>/press.tsx for cover/TOC/back-cover, and press/<slug>/theme/tokens.css or press/shared/theme/tokens.css for visual tokens.

Page content rules (hierarchy, table captions, figure numbering, factual boundaries) live in openpress-create-pages; this skill does not redefine them.

Do / Don't

Do:

to change brand color: change tokens.css in --openpress-chart-gold or add --openpress-brand-accent
to change fonts: change --openpress-font-serif / --openpress-font-body 's font stack; when cross-mobile / iPad stability is needed, also update theme/fonts.css to load webfonts, do not rely only on local(...)
to add a new page kind (divider / appendix-cover): in theme/page-surfaces/ add CSS; existing chapter-opener can serve as a book/teaching-material chapter mini cover
to change numbering style (一、二、 or §1.1): change theme/base/typography.css 's ::before content, with @counter-style
to change page size (B5 / Letter / slides): change press/<slug>/press.tsx within <Press page="..."> 's prop;tokens.css retains only theme defaults and visual tokens

Don't:

do not change inline emphasis color to arbitrary swatches (breaks the semantic system); new status swatches must first add --openpress-status-* tokens before use
do not put theme/base/typography.css 's CSS for a single chart / specimen inside (that is press/<slug>/components/<name>/ 's responsibility)
do not shrink the font size too much for dense content; A4 body text should not be smaller than 9.5pt
do not change hairlines to solid lines of 2px or more; this starter's character relies on thin lines

In-depth design rules

editorial-monograph does not maintain a separate reference/ document—all specifications are written in starter/press/design.md and, after being copied to the workspace along with the starter, become that project's design document:

Section 1 Style goals and use cases — goals / applicable scenarios / role definitions
Section 2 Tokens — typography / color / spacing / page geometry / inline emphasis / chapter & section numbering
Section 3 Components — page surfaces / text components / tables / figures / charts
Section 4 CSS responsibilities

After the agent applies the skill, this file becomes that project's press/design.md content; later, if the user wants to customize it, they can directly edit design.md without going back to edit the skill.