openpress-designlisted

# open-press Design open-press design owns the **workspace visual system**: the CSS and components that live in a user's `press/` or transitional `document/` source tree. It decides how the document looks while keeping fixed-layout, mobile, and PDF output stable. ## Responsibilities - Choose typography, color, spacing, page rhythm, covers, figures, tables, and chart treatment. - Edit source-tree `theme/`, `design.md`, and `components/` in a workspace. - Decide when dense prose should become a reusable visual component. - Keep `press/design.md` public-readable so users and agents can review the same rules. - Preserve React reader output as the public reading surface; PDF is an export artifact. ## Boundaries (by path, not by topic) | Path | Owner | | --- | --- | | `press/theme/`, `press/components/`, `press/design.md` (workspace) | **this skill** | | `press/theme/`, `press/components/`, `press/design.md` (transitional workspace) | **this skill** | | Framework runtime / workbench code | framework agents only; see `openpress` > Source Boundary | Other skills: - `openpress-create-theme` owns the `/create-theme` product entry and first-pass theme generation. - `openpress-writing` owns claims, prose, audience, and captions as language. - `openpress-diagram-drawing` owns diagram semantics; this skill owns visual skin. - `openpress-deploy` owns public release. Source paths follow `openpress` > Source Boundary. ## Hard Rules - Avoid uncontrolled overflow into headers, footers