Handoff Kit — How to get these assets designed (phased)¶
Purpose: exactly what to give Claude (or any design AI) and in what order, to produce the presentation plan assets. Follow the phases top to bottom — each phase depends on the one before.
The core principle: lock the brand foundation (Phase 0) first, then produce assets one at a time or in a tight cluster, always feeding the produced brand tokens back in so everything stays visually consistent. Never paste all 28 briefs at once — you'll get generic, inconsistent output.
What "sharing" means depending on the tool¶
- Claude Code (this repo): it already has the files. Just say which asset(s) to build and it reads the briefs itself. Best for HTML/CSS assets (reports, one-pagers, website, dashboard themes) delivered as artifacts.
- Claude.ai / Claude for design (no repo access): attach or paste the specific files listed in each phase below. Always attach the two foundation files first.
- Gamma / Figma AI / PowerPoint / Canva: best for the editable deck and document assets (decks, contracts). Give them the content file + the brand tokens from Phase 0, and ask for an editable file in their native format.
Tool-fit cheat sheet (which asset goes where):
| Asset type | Best tool | Why |
|---|---|---|
| Report/one-pager/website/dashboard theme (HTML/CSS) | Claude (artifacts) | Self-contained HTML is Claude's strength; renders exactly, easy to iterate |
| Slide decks (PA06, PA17) | Gamma or PowerPoint/Google Slides, or Claude for an HTML mockup first | You need an editable deck; Claude can produce the layout/mockup, then rebuild editable |
| Legal document templates (PA16) | Word/Google Docs with brand styling | Editable, counsel-reviewed; light typographic treatment only |
| Logo / final vector identity (part of PA00) | Dedicated logo tool or designer; Claude for SVG direction exploration | True brand mark benefits from a vector specialist |
| Architecture diagrams (PA13, PA20) | Claude (SVG/d2) or Excalidraw/diagrams.net with the brand palette | Must match the repo's d2lang output |
The universal prompt template (reuse for every asset)¶
You are designing a client-facing asset for SnowOps. You have no prior knowledge
of SnowOps, so read the attached context first.
CONTEXT (read in this order):
1. 00-business-primer.md — what SnowOps is, who it sells to, the compliance-claim rule
2. 01-brand-system.md — the visual language (OR: the finalized brand kit from Phase 0)
3. [the stage brief file for this asset]
4. [the source content file(s) named in that brief]
BUILD: [Asset ID + name, e.g. "PA08 — Discovery Audit report theme"]
Follow the brief's "Deliverable spec", "Content outline", and "Design direction"
exactly. Hard rules:
- Obey the compliance-claim rule: no "guaranteed certification"; tag any (roadmap) claim.
- Use ONLY the brand tokens (colors, fonts, the green/amber/red status trio, components).
- Deliver [format from the brief, e.g. self-contained HTML that prints cleanly to PDF].
Ask me any clarifying question before starting if the brief leaves a real choice open.
Phase 0 — Brand foundation (do this ALONE, first) 🔒¶
Why first: every other asset inherits these tokens. Skipping this = 28 inconsistent assets.
- Share:
00-business-primer.md+01-brand-system.md. - Ask for: the PA00 acceptance checklist in
01-brand-system.md§8 — logo direction, color tokens (with the locked green/amber/red trio), type scale, icon/diagram/data-viz rules, one slide master + one document master, and a one-page mini brand sheet. - Decide the ⟨DECIDE⟩ items in the brand system (final logo, exact hex, fonts) here, with Claude proposing options.
- Output you must capture: a short "brand tokens" block (hex values, font names, component specs) you will paste into every later phase. This is the single most important thing to carry forward.
- Split recommendation: use Claude to produce the tokens, templates, and SVG mark directions; take the final logo to a vector tool/designer if you want a polished mark. The tokens + templates are enough to unblock everything else.
➡️ Don't start Phase 1 until you have the brand tokens block.
Phase 1 — The wedge (win the deal) 💰 P0¶
Produce in this order. Feed the Phase-0 brand tokens into each.
| Order | Asset | Attach (besides the 2 foundation files) | Tool |
|---|---|---|---|
| 1 | PA08 Discovery Audit report theme | stages/1-land.md, apps/discovery-auditor/ render notes, Y9 sanitized-sample-audit.md |
Claude (HTML/CSS theme) |
| 2 | PA09 Sample audit | — (falls out of PA08's template with the sample data) | Claude |
| 3 | PA06 Capabilities deck | stages/1-land.md, Y8/deck-outline.md |
Gamma/Slides (or Claude HTML mockup) |
| 4 | PA04 One-pagers ×3 | stages/1-land.md, the 3 Y8/one-pager-*.md |
Claude (HTML → PDF) |
| 5 | PA01 Website/landing | stages/1-land.md, Y1-positioning-messaging.md |
Claude (artifact) |
Then as capacity allows: PA05 vertical one-pagers, PA02 LinkedIn kit, PA03 email signature, PA07 call agenda.
PA08 is the highest-value asset in the whole plan — spend real iteration time on it and get Nidhi to review the compliance mapping before it touches a client.
Phase 2 — Close (turn the audit into a signature) ✍️ P0/P1¶
Reuse PA08's visual language so the proposal feels like the audit's sequel.
| Order | Asset | Attach | Tool |
|---|---|---|---|
| 1 | PA10 Proposals ×3 | stages/2-close.md, the 3 Y6/*-proposal.template.md |
Claude/Docs (editable fields) |
| 2 | PA14 Pricing sheet | stages/2-close.md, Y2-pricing-packaging.md |
Claude — editable price fields, no baked numbers |
| 3 | PA12 Coverage matrix | stages/2-close.md, Y7-compliance-coverage-matrix.md |
Claude — Nidhi-gated |
| 4 | PA13 Reference architectures ×3 | stages/2-close.md, the 3 z/Z*.md |
Claude (SVG/d2) — Nidhi-gated |
| 5 | PA11 Findings-to-roadmap, PA15 Case study | stages/2-close.md, the named Y6/Y9 files |
Claude |
| 6 | PA16 Contract pack | stages/2-close.md, Y12-contract-pack/* |
Word/Docs — counsel-gated, don't touch wording |
Phase 3 — Deliver (smooth engagement → retention) 🛠️ P1¶
| Order | Asset | Attach | Tool |
|---|---|---|---|
| 1 | PA19 Handover docs template | stages/3-deliver.md, a sample from docs/client-guides/ |
Claude — build once, all guides inherit it |
| 2 | PA17 Kickoff deck | stages/3-deliver.md, Y11-cs-expansion.md |
Gamma/Slides |
| 3 | PA18 Onboarding/access guide | stages/3-deliver.md, apps/client-bootstrap/ |
Claude |
| 4 | PA20 Diagram theme, PA21 Runbook theme | stages/3-deliver.md + PA13/PA19 outputs |
Claude (themes on generator output) |
Phase 4 — Retain & expand (make money twice) 🔁 P0/P2¶
| Order | Asset | Attach | Tool |
|---|---|---|---|
| 1 | PA22 QBR posture report theme | stages/4-retain.md, client-guides/qbr-posture-report.md, apps/posture-report/ |
Claude (HTML theme) — P0 |
| 2 | PA24 Compliance dashboard theme | stages/4-retain.md, apps/compliance-dashboard/ |
Claude |
| 3 | PA25 Upsell one-pager | stages/4-retain.md + PA04/PA14 outputs |
Claude |
| 4 | PA26 Offboarding pack | stages/4-retain.md + PA19 template |
Claude |
| 5 | PA27 Trust center (write content first) | stages/4-retain.md + authored content |
Claude — Nidhi-gated |
| — | PA23 Client dashboard | roadmap — wait until J8 ships | Grafana |
Working rules that keep quality high¶
- One asset (or one tight cluster) per conversation. Fresh context = sharper design.
- Always carry the Phase-0 brand tokens forward. Paste them into every prompt.
- Iterate, don't one-shot. Get v1, then give specific feedback ("tighten the finding chips," "the executive grade needs to be bigger"). 2–3 rounds per hero asset.
- Gate before client use: anything with a compliance/capability claim → Nidhi; contract wording → counsel; pricing numbers → Sagar finalizes.
- Update the state tracker in
README.mdas each asset moves ⬜ → 🟦 → 🟩. - Reuse, don't reinvent: PA09←PA08, PA10←PA08 language, PA20←PA13, PA21←PA19, PA26←PA19, PA25←PA04/PA14, all posture surfaces (PA22/23/24) share one language.
The fastest path to "sellable" (if you only do a little)¶
Do just these five and you can run the whole sales motion: PA00 (brand) → PA08 (audit report) → PA06 (deck) → PA04 (one-pagers) → PA10 (proposal). Then add PA22 (QBR report) the moment you have a paying client to retain.