You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(examples/conceptual-design): update playbook run outputs and concepts
Playbook run artifacts from concept-living-playbook execution: updated
task definitions, design specs, and generated HTML concepts for
linear.app, notion, and random partitions.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
You are a design director creating a masterpiece UI/UX concept. Read the inputs deeply and write a creative brief that a developer will implement.
21
+
## CONSTRAINTS — Read These First
22
22
23
-
## Inputs
24
-
25
-
-`docs/design/design-brief.md` — the product spec: vibe (handbook), data model (tasks nesting up to 5 levels, modes: leaf/spawner/gateway), and example data
26
-
-`concepts/$CONVERGE_PARTITION_KEY/design-system.md` — the brand's design system. Study it deeply — understand its personality, its rhythm, its values.
23
+
These rules override everything else. The brand's design system informs colors and typography, but the FORMAT is a book — not a dashboard, not a web app.
27
24
28
-
## You must deeply understand two things:
25
+
1.**Book layout.** Single column, `max-width: 720px`, centered. Content reads top-to-bottom. No multi-column grids. No sidebar navigation.
26
+
2.**Paper surface.** Background: warm white (`#FAFAF8`). Cards: white with soft `box-shadow` (`0 1px 3px rgba(0,0,0,0.06)`). No colored card backgrounds. No hard borders.
27
+
3.**Typography does the hierarchy.** Font size and weight communicate structure — not icons, not colored containers. Specify exact px sizes and weights for every heading level.
28
+
4.**Badges for metadata.** Status, task mode, duration — small pill badges with subtle tint. Never bold colored blocks.
29
+
5.**40% whitespace.** The page must breathe. Generous margins and gaps.
30
+
6.**Shadows max `rgba(0,0,0,0.08)`.** Gentle depth, never dramatic.
31
+
7.**Muted status colors.** Sage green for pass, warm amber for running, dusty rose for failed. Never saturated.
32
+
8.**No dark mode.** Ever. The background is warm white. The text is near-black.
33
+
9.**No Inter font.** Use the brand's font or a clean alternative like Georgia or system-ui.
34
+
10.**No sticky navbars.** No fixed headers. The page scrolls like a book.
29
35
30
-
### 1. The Design System
36
+
##Your Role
31
37
32
-
Don't just extract colors and fonts. Understand the SOUL of this brand:
33
-
- What's its personality? Playful? Serious? Minimal? Dense?
34
-
- How does it handle hierarchy? What's its approach to space?
35
-
- What's its motion philosophy? Its surface treatment?
36
-
- How does it differentiate information levels?
37
-
- What makes it recognizable and distinct?
38
+
You are a design director. Read the inputs, deeply understand the brand's personality, then write a creative brief that a developer implements literally — but within the book format above.
38
39
39
-
### 2. The Product Information Hierarchy
40
+
##Inputs
40
41
41
-
The product shows a playbook — a composable tree of tasks up to 5 levels deep. Each task has:
42
-
- Title, description, body (long markdown instructions)
-`docs/design/design-brief.md` — the product spec: the book vibe, data model, example data
43
+
-`concepts/$CONVERGE_PARTITION_KEY/design-system.md` — the brand's design system
46
44
47
-
The design must present this data clearly. The hierarchy must be immediately scannable. The reader should understand the structure at a glance AND be able to drill into any level for detail.
45
+
## Understand the Brand
48
46
49
-
## Your job
47
+
Study the design system deeply — its personality, rhythm, color philosophy, typography choices. Then ADAPT those qualities to the book format:
50
48
51
-
Create a design specification that is a **masterpiece of UI/UX** — something so well-crafted it could win design awards. Think deeply about:
49
+
- Use the brand's colors for accents, links, and highlights — but keep the warm white background
50
+
- Use the brand's font for headings and body — but at the sizes specified in the constraints
51
+
- Use the brand's spacing rhythm — but within the single-column book layout
52
+
- Use the brand's surface treatment — but only as subtle card shadow variations
52
53
53
-
- How this brand would naturally present structured, nested information
54
-
- What page composition creates the right reading experience
55
-
- How to express 5 levels of nesting beautifully (indentation? progressive disclosure? split views? breadcrumbs?)
56
-
- How task types (leaf/spawner/gateway) are distinct yet cohesive
57
-
- What typography scale makes hierarchy effortless to scan
58
-
- What interactions feel native to this brand (hover, click, expand, slide, morph)
59
-
- What unique visual touches make this feel premium and specific to this brand
60
-
- How to present data (checks, outputs, status) without clutter
54
+
## What to Include
61
55
62
-
## Principles
56
+
1.**Brand interpretation** — how you read this brand and how it shapes the spec
57
+
2.**Page composition** — overall layout (single column, 720px, top to bottom)
58
+
3.**Typography scale** — exact sizes/weights for every level (must match constraint #3)
0 commit comments