d6347264f1
Sweep across the planning docs so a future session opening any of them sees the same picture of where the slice actually landed and which docs to load before touching a given phase. BUILD_SEQUENCE.md: - Reworded status header from "slice has shipped" to honest framing: scaffolded through Day 6, architectural pieces proven, reviewer surface and hero-image rendering not demo-ready. - Added "How to use this document" explaining the reference-docs block pattern. - Added "What V1 inherits from the slice" inventory mapping shipped work onto Phases 1-3 (foundation), 5 (TypeSystem), 8 (orchestration), 11 (render), 12 (review), 13 (export). Plus "What V1 replaces." - Added "Slice gaps" subsection enumerating the two items that block Phase 12 from inheriting the review page as-is. - Added Reference docs blocks to every phase (1-14), priority-ordered. - Wired ANIMATION_V1.md forward-pointers specifically into Phase 6 (asset selection consults unionBoundingBox), Phase 7 (crop tool must respect required_source_size), Phase 8 (Assemble agent emits AnimationTimeline referencing preset names only), Phase 11 (GSAP via s0.2mdn.net CDN, SplitType bundled, force-prefers-reduced-motion), Phase 13 (G1-G12 supersede general gates for animation checks). - Added validator additions in Phase 8: animation preset whitelist, duration cap, loop cap. - Added Document index at the bottom listing every referenced doc. PHASE_1_BRIEF.md: - Added superseded banner pointing to VERTICAL_SLICE.md and BUILD_SEQUENCE.md Phase 2. Notes that the architectural pieces this brief was designed to land did land; the reviewer-surface gaps are documented in SLICE_DEVIATIONS.md sections 12-13. SLICE_DEVIATIONS.md: - Added section 12: hero-image rendering on Konva unverified across the four IAB sizes. Earlier rounds shipped with broken placeholder URLs; the Unsplash swap fixed the URL but not the full pipeline (load-gating the GSAP timeline, CORS, per-size crop/fit, parity vs. Playwright PNG). V1 reversal: dedicated Konva image-pipeline pass before Phase 12 inherits the review UI. - Added section 13: the review page is a developer scaffold. Empty, loading, and error states, drawer affordance, export feedback, and information hierarchy are not designed. V1 reversal: Phase 12 starts from a design pass over the existing data shape, not from the slice's page shell. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| apps/web | ||
| feeds | ||
| infra/fonts | ||
| packages | ||
| patches | ||
| scripts | ||
| .env.example | ||
| .gitignore | ||
| .nvmrc | ||
| ANIMATION_V1.md | ||
| ANIMATION_V1_DESIGN_DECISIONS.md | ||
| ANIMATION_V1_RESEARCH.md | ||
| ANTI_PATTERNS.md | ||
| ARCHITECTURE.md | ||
| Avoiding UX Failure FIRST.md | ||
| BUILD_SEQUENCE.md | ||
| CLAUDE.md | ||
| EXECUTIVE_SUMMARY.md | ||
| FRUSTRATION_LIST.md | ||
| INTERACTION_STANDARDS.md | ||
| package.json | ||
| PHASE_1_BRIEF.md | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| PROJECT_STRUCTURE.md | ||
| README.md | ||
| RESEARCH.md | ||
| RESOLVED_FEED.md | ||
| SLICE_DEVIATIONS.md | ||
| tsconfig.base.json | ||
| turbo.json | ||
| UX_ACCEPTANCE_CRITERIA.md | ||
| VERTICAL_SLICE.md | ||
Banner Studio — Claude Code Briefing Bundle
This bundle contains everything needed to begin building the agentic HTML5 banner production platform with Claude Code, plus an executive summary for non-engineering audiences.
What's in here
For Claude Code (drop these in the project root):
CLAUDE.md— Read on every session. Locked decisions, conventions, what not to do. The operational source of truth.PROJECT_STRUCTURE.md— Monorepo layout, package by package, file by file. Use as the scaffolding target.PHASE_1_BRIEF.md— Step-by-step prompts for the first week of work. Foundation phase, no UI yet.BUILD_SEQUENCE.md— All 14 phases with exit criteria. Expand each phase into Claude Code prompts as you reach it.ARCHITECTURE.md— The full architecture spec (the document you authored). Source of truth for data shapes, algorithms, and rationale.RESEARCH.md— Research backing the locked decisions. Reference for the "why" behind stack and pattern choices.
For leadership and stakeholder decks:
EXECUTIVE_SUMMARY.md— Plain-prose briefing. The PPT source document. Sections map naturally to slides.
How to start
-
Create the project repo. Copy
CLAUDE.md,PROJECT_STRUCTURE.md,PHASE_1_BRIEF.md,BUILD_SEQUENCE.md,ARCHITECTURE.md, andRESEARCH.mdinto the root. -
Open Claude Code in that directory.
-
First prompt:
Read
CLAUDE.md, thenPHASE_1_BRIEF.md. We are at Step 1.1. Begin. -
Work through Phase 1 step by step. Do not skip the unit tests on the layout engine. Do not skip Step 1.9 (the type-safety proof) — it confirms the contract chain works before you build anything substantial on top of it.
-
At Phase 1 exit, tag
v0.1.0-foundationand start Phase 2.
A note on the documents
CLAUDE.md is intentionally opinionated. It states what is locked, what is forbidden, and where to look for the why. This is the right shape for a Claude Code briefing — it tells the model what decisions have already been made so it doesn't waste context re-deriving them, and it tells it where to look when a deeper question comes up.
PHASE_1_BRIEF.md is the only phase with literal prompts pre-written. As you complete Phase 1 and start Phase 2, expand that phase's summary in BUILD_SEQUENCE.md into a similar step-by-step brief. The first phase needed prompts because zero-state is the hardest moment; later phases can lean on the patterns established in Phase 1.
EXECUTIVE_SUMMARY.md is written to be read by people who will never touch the code. It's the document that gets adapted into a 10-slide deck or a one-pager for a stakeholder conversation. Sections are sized to map to slides without further editing.