claude-document

Claude Document

An open-press starter skill for Claude-like working documents: warm paper, generous fixed pages, deep blue-gray headings, serif display titles, structured tables, concise figures, and calm editorial rhythm.

This is a local starter. It is not an Anthropic brand package and should not imply official Claude or Anthropic affiliation.

Visual Signature

• Surface: A4 fixed pages with a warm paper texture and subtle vertical rhythm.
• Type: serif display headings, sans body text, monospace code.
• Color: deep blue-gray ink, muted blue labels, warm hairlines, restrained block backgrounds.
• Content components: tables, figure captions, code blocks when needed, optional full-page chapter openers.
• Pagination: fixed page ratio; overflow is a content/component problem, not a reason to let pages grow.

Suitable For

• polished working notes;
• product briefs, specs, and research summaries;
• learning material and internal documentation;
• public documents that need a calm, Claude-like editorial surface.

Not Suitable For

• marketing landing pages;
• slide decks or 16:9 talks (use a dedicated external skill, or declare a custom config.page);
• dashboards or interactive app documentation.

Related Starters

• editorial-monograph — hairline-driven, more formal long-form (whitepapers, monographs, academic-leaning). Choose it when the document is heavier and needs IBM-Carbon-style restraint instead of warm Claude tone.

Apply To A Workspace

Use openpress to initialize the OpenPress runtime workspace. Then copy or adapt this skill's starter/press tree into the target workspace. This skill defines the visual scope and starter content; openpress owns the command surface and validation workflow.

After applying, use openpress for source-boundary and command decisions. Typical editable source areas are:

• press/<slug>/press.tsx — <Press> JSX with cover, TOC shell, back cover, metadata;
• press/<slug>/chapters/**/*.mdx — content;
• press/<slug>/theme/tokens.css or press/shared/theme/tokens.css — color, typography, spacing, and page geometry variables;
• press/design.md — public style contract that future agents follow;
• package.json "openpress" field — deploy / pdf operational settings (merge from starter/package.openpress.json).

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:

• Keep figures focused on one concept, decision, or relationship.
• Prefer semantic figures, tables, and concise prose over decorative blocks.
• Keep chapter openers optional and use them only when major sections benefit from a book-like divider.

Don't:

• Put private names, customer data, deployment secrets, or project-specific author data in the starter.
• Shrink text below readable print size to hide overflow.
• Add large decorative gradients, dark sci-fi backgrounds, or brand-heavy visual noise.

Deep Rules

The detailed rules live in starter/press/design.md. Once the starter is copied into a workspace, that file becomes the project-level design contract for both users and agents.