# A broadsheet design system breakdown

> Eight broadsheet-style slides break down a design-system document: source notes, a thesis, six workflow stages, rules, banned patterns and a keep-or-skip comparison. Built with slides-grab, a slide harness for Claude Code and Codex.

- Kind: Slides
- Live deck: https://blog.nomadamas.org/slides-grab/presentations/claude-design-system/viewer.html
- Page: https://meetreference.com/v/newspaper-style-breakdown-design-prompt/
- Ready-to-use agent handoff: https://meetreference.com/v/newspaper-style-breakdown-design-prompt/agent.txt
- Authorship: AI-made, per the source
- Made with: Not stated
- Model: not stated
- Built with: not stated
- Skills or plugins: slides-grab
- Style: Decks; broadsheet, editorial, serif, monochrome, cream, ruled grid, typographic
- Slides: 8
- Preview: a flip-through of inspected screenshots; open the live work to experience its motion and interactions.
- Shared by NomaDamas in GitHub, Apr 27, 2026: https://github.com/NomaDamas/slides-grab/tree/main/showcase/presentations/claude-design-system
- Prompt fidelity: Unavailable in this entry. The recreation brief is written by Reference.

## Before you start

Guidance from Reference, separate from the creator's instructions.

1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present.
2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized.
3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed.
4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting.
5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use.

Requirements reported by the source: slides-grab (npm) with Claude Code or Codex.

## Recreating this deck

This is a visual reference. No original creator prompt is available. The following brief was written by Reference after inspecting the work.

Establish a publication identity using a dark masthead, small tracked section labels, page numbers, and thin rules on warm ivory. Create sequence rhythm by alternating oversized statements with ruled columns, a numbered process grid, and a side-by-side comparison while keeping the same typographic hierarchy. For a new subject, replace the analysis with its own thesis, stages, contrasts, and closing principles; adjust column widths and line breaks to avoid cramped bilingual wrapping.

1. Open the live work or source and inspect the frame images below.
2. Adapt its layout, hierarchy, palette, and interaction patterns to the user's own content and brand.
3. Compare the result against the reference. Use your own assets and credit the original creator.

## What it looks like

Written by Reference from the captured walkthrough frames, not by the creator.

A restrained newspaper-inspired breakdown of a design prompt, presented in Korean with a formal editorial tone.

- Color: Warm ivory and pale gray backgrounds, near-black text and rules, with subtle muted gray accents.
- Type: Bold serif display headlines paired with clean sans-serif Korean text and small monospaced labels.
- Framing: Strong page headers, fine horizontal rules, numbered sections, and carefully aligned text panels create a precise editorial layout.
- Structure: The sequence moves from a title page into the prompt and thesis, then develops workflow principles, a checklist, keep-versus-skip guidance, and a closing set of design rules.

Storyboard of the slides: https://meetreference.com/media/newspaper-style-breakdown-design-prompt/storyboard.webp

- Slide 1: https://meetreference.com/media/newspaper-style-breakdown-design-prompt/f1.webp
- Slide 2: https://meetreference.com/media/newspaper-style-breakdown-design-prompt/f2.webp
- Slide 3: https://meetreference.com/media/newspaper-style-breakdown-design-prompt/f3.webp
- Slide 4: https://meetreference.com/media/newspaper-style-breakdown-design-prompt/f4.webp
- Slide 5: https://meetreference.com/media/newspaper-style-breakdown-design-prompt/f5.webp
- Slide 6: https://meetreference.com/media/newspaper-style-breakdown-design-prompt/f6.webp
- Slide 7: https://meetreference.com/media/newspaper-style-breakdown-design-prompt/f7.webp
- Slide 8: https://meetreference.com/media/newspaper-style-breakdown-design-prompt/f8.webp

## How it was made, per the creator

- Notes: Deck from the slides-grab showcase gallery (https://nomadamas.github.io/slides-grab/): "a static gallery of presentations built with slides-grab", the "harness + editor + linter for generating slides in Claude Code / Codex". Each slide is its own HTML file plus a viewer and PDF.

## Links

- View deck: https://blog.nomadamas.org/slides-grab/presentations/claude-design-system/viewer.html
- Original post: https://github.com/NomaDamas/slides-grab/tree/main/showcase/presentations/claude-design-system