openpress-create-pages

name

openpress-create-pages

description

Use when the user wants to create, draft, scaffold, or add a page-based OpenPress artifact such as a report, proposal, whitepaper, paper, book, teaching note, handbook, or long-form document. This skill owns fresh workspace bootstrap for pages, adding a pages Press to an existing Workspace, page-based Press Tree generation, first-pass theme intake, page components, hierarchy, prose structure, captions, factual boundaries, learner-facing document rules, and portable language skill routing.

OpenPress Create Pages

openpress-create-pages owns artifact creation. The openpress skill owns CLI lifecycle: build, render, PDF, image, deploy, doctor, upgrade.

Boundary

Owner	Scope
openpress-create-pages	Create or add page-based artifacts: structure, prose rules, theme, components.
openpress-create-slide	Slide decks.
openpress	CLI lifecycle.
openpress-deploy	Public deploy after explicit user confirmation.
openpress-apply-comments	Pending @openpress-comment markers.

---

Setup

1. Environment check:

node -v && npm -v && npx -v

Node ≥ 20 required. If missing or outdated, stop and ask the user to install Node.js LTS.

2. Detect workspace branch:

find press -mindepth 2 -maxdepth 2 -name press.tsx -print -quit 2>/dev/null | grep -q . && echo EXISTING || echo FRESH

3a. Fresh workspace:

Use npm create @open-press <target> -- --type slides only to create the package-based workspace shell when the user is starting from an empty folder. After dependencies and skills are installed, replace the generated slides Press with a pages Press owned by this skill. Do not use a force flag.

3b. Existing workspace:

Read press/*/press.tsx to identify existing slugs, geometries, componentsDir, and mediaDir. Create a new press/<slug>/ folder. Do not touch sibling Press folders unless the user asks.

---

Intake

Gather before writing files:

• Artifact type: report / proposal / whitepaper / paper / book / teaching note / handbook / other
• Audience
• Primary language
• Title
• Page geometry:
  • report, proposal, whitepaper, paper, book, teaching note, handbook → a4
  • custom: ask for width and height in CSS absolute units
• Theme inputs: primary ink, accent, font roles, Chinese/English font configuration, optional reference aesthetic
  • body:正文、表格、caption、註解
  • serif:書名、章節標題、正式敘事
  • mono:code、路徑、資料欄位
  • display:封面大標，可選
  • Prefer self-hosted Latin fonts plus local CJK fallbacks; bundle licensed CJK subsets only when identical Chinese glyphs are required across machines.
• Known source material and confirmed facts

Do not ask for subtitle, organization, author, version, or footer as Press metadata — those are rendered text in cover/page components.

---

Hierarchy and Writing Rules

Decide structure before drafting prose.

Heading levels:

• #: whole document title only; cover identity, not normal content files
• ##: formal chapter/document unit; enters formal TOC
• ###: major topic group; enters formal TOC
• ####: concrete algorithm, operation, theorem, variant, worked procedure, or local reference item; normally stays out of formal TOC

Rules:

• Preserve confirmed facts.
• Mark missing facts as [TODO: ...], [FIX: ...], or [DRAFT: ...].
• Use <TableCaption>...</TableCaption> before captioned tables.
• Do not hand-maintain figure/table numbers.
• Public content belongs in registered MDX sources. Internal planning belongs in press/design.md, memory/, or skills.
• For teaching notes, course handouts, worksheets, study guides, or tutorials, write to the learner: compare nearby concepts, show state-changing procedures step by step, add short practice checks only when useful, and place answers after the learner has had a chance to attempt.
• For programming teaching material, introduce the data shape before long code, break helper functions apart before the complete version, keep identifiers consistent across prose/tables/diagrams/code, and include expected output or final state when it helps verification.

Use open-press search to locate content before editing:

# 找哪個章節提到某個關鍵字，回傳 page id + 行號
open-press search . "<query>" --json

# 含 components / theme / design.md 一起搜
open-press search . "<query>" --scope all --json

Portable skill triggers:

Content	Load
Traditional Chinese professional content	chinese-ai-writing-polish

Resolve conflicts in this order: explicit user instruction → workspace memory/design.md → document brief → this skill's structural decisions → portable language skill rules.

---

Verify

Draft marker scan before build:

# 確認沒有未完成標記殘留
open-press search . "[TODO:" --scope all --json
open-press search . "[DRAFT:" --scope all --json
open-press search . "[FIX:" --scope all --json

Fresh or structural edit:

npm run build

When PDF readiness matters:

npm run openpress:pdf

Report: Press slug, title, geometry, source root, theme paths written, next editable paths, verification result.

---

When to Read References

• Press Tree & folder layout: read references/press-tree.md — canonical folder structure, Press Tree TSX example, path resolution rules.
• Theme & page components: read references/theme.md — paths to write, theme rules, CSS constraints.

---

Do Not

• Do not use npm create @open-press or open-press create as an upgrade or migration tool.
• Do not edit generated output.
• Do not publish.
• Do not write unsupported facts.