Spectrum Brand Strategy Deck

Explain a brand strategy through the promise, audience, positioning, voice and touchpoints that should guide decisions. Spectrum Brand Strategy Deck combines cream headlines on deep ink pages with rounded spectrum-color tiles and dark-background object studies. It organizes your approved strategy and evidence; fictional retail imagery and pilot targets are not verified customer research or business outcomes.

What you get

  • Nine adaptable roles: cover, three-value promise, audience segments, positioning statement, voice comparison, touchpoints, phased roadmap, measurement targets and closing decisions. Select or extend recipes for the agreed count. The installed generic schema fixture is not a completed nine-page strategy case.
  • Embedded Bricolage Grotesque display type and Figtree body on consistently dark pages with cream text. Green/blue/orange/yellow tiles support one highlighted element per page, with equal-sized siblings and a consistent rounded radius. Authored, Teal and Clay are coordinated generation-time accent presets; photographs keep their own colors.
  • Concrete readability limits on a 1280×720 canvas: 77 px margins, a twelve-column grid, content roughly 79–634 px high, at most three blocks and about a third of the page empty. Headlines allow seven words (cover five), one supporting line eighteen and a page forty-five words excluding numbers. Body stays at least 17 px; additional audience needs, owners, dates and contact details remain in notes.
  • Four local 3D object studies cover abstract colored plinths, a blank bottle, a refill station and a tiny shopfront. Refill/shop images are topic-specific. Use each pictorial source once and do not imply these concept renders are real locations, production-ready products or measured touchpoint results. Text stays on solid pages/tiles rather than pictures.
  • A generated offline HTML deck with navigation, overview/thumbnails, speaker notes, editing, presentation mode and print styling. Recipes, references, catalog and build/media tools are installed resources. Optional checked PPTX keeps native text/notes and separate pictures, with complex charts/shapes/backgrounds rendered; PDF prints one 16:9 slide per page. No automatic publishing is included.

Before you choose

Use the deck to make choices explicit: which audience comes first, what the brand promises, how that sounds and where someone experiences it. Preserve the evidence and assumptions behind those decisions in notes; a confident tile or a realistic shop render is not proof of demand or trust.

Good fit

  • A team preparing brand positioning, audience strategy, voice guidance or touchpoint planning from approved material.
  • A reviewer who wants to correct wording, evidence, sequence and notes directly in a browser before rehearsal.
  • A presenter who needs one coherent story leading from the brand promise to choices, a roadmap and a closing ask.

Not for

  • Exact reproduction of protected templates/artwork, third-party logos, identities or source wording.
  • A guarantee that all exported PowerPoint charts, shapes and decorative elements remain native objects.
  • Automatic publishing, unapproved paid generation or automatic validation of audience research and commercial claims.

How to use

You say/spectrum-brand-strategy-deck Make a nine-slide deck for a neighborhood refill shop brand strategy.
  1. Provide topic, audience, intended decision/closing ask, approximate length, approved outline and verified figures. Supply permitted imagery and agree the actual page count. Copy defaults to English unless another language is requested. Label fictional examples/pilot targets and separate assumptions about audiences from research findings.

  2. Plan the nine roles around promise, segments, positioning, voice, touchpoints, roadmap and measurement. Adapt/split layouts rather than inventing three values or segments to fill cards. Preserve supporting needs, owners, dates and details in notes. A voice comparison should use original approved examples; a roadmap should state exit criteria rather than imply completed results.

  3. Choose Authored, Teal or Clay and retain the dark-page identity, embedded fonts and 77 px grid. Keep title ≤7 words (cover ≤5), one supporting line ≤18, up to three short items and ≤45 total words excluding numbers. Body stays ≥17 px. Use one spectrum highlight, equal-sized sibling cards, no picture/card overlap and no label/folio clutter.

  4. Prioritize supplied pictures, then suitable catalog reuse, generation for gaps or all-new art; reuse is the fallback without a choice/tool. Check refill/retail subject restrictions in the four-image catalog. Use each pictorial source once, with dark backdrops and clear material forms. Treat shop/bottle renders as illustration unless real provenance supports the claim, never as customer proof.

  5. Generate optional art at kit slot ratios through built-in tools or the current FAL helper/FAL_KEY route, subject to host limits or separate provider charges. Obtain approval for paid work, submit once then poll/fetch and record prompts/results. Disclose missing frames. Keep approved text, labels and data in editable nodes outside pictures.

  6. Compose from recipes, replace copy/alt/images/data and remove unused nodes. Python 3 handles compose/build/static checks; optional media tools use Node. Resolve unfilled-image and leftover-example reports, verify count and inline fonts/resources under 20 MB. Library downloading may need internet while building; completed delivery should load no remote assets.

  7. Inspect every page over local HTTP for dark-page contrast, title fit, tile hierarchy, photo crops/uniqueness, bounds, source-backed figures and notes/page consistency. Test text/image/order/layout/color changes, notes, undo/redo, Save/reopen and presentation mode, then rehearse. Static checks do not validate strategic choices or audience assumptions.

  8. Deliver page-view HTML with Edit/E and Save (Cmd/Ctrl+S) instructions: recovery is browser-local, Save writes portable edits. Set interface/content languages independently with framework CJK/RTL support. Export/check/inspect requested PPTX/PDF and recipient fonts separately. Named palettes guide generation, not an editor theme picker; the embedded export menu replaces retired mandatory Node/Chromium and old --fonts keep command-line guidance.

Requirements and costs

You bring
Topic, audience, and the decision or learning goal. · Approximate page count and a source outline. · Verified figures and image rights for any supplied material.
Dependencies
Modern browser — required for presentation and browser editing · Chrome, Chromium or Edge plus Node.js 20 or newer — required only for PowerPoint export · Built-in image generation in your agent (GPT Image class) — only needed to create new pictures; no separate API key · Internet access — optional, to download this Skill's picture library while building a deck
Outside costs
Decks can reuse this Skill's own picture library at no image cost: you choose up front whether to reuse it or generate every picture new. New pictures use your agent's built-in image generation tool (GPT Image class) with no separate API key, and availability follows your agent account.
Publisher testing
v1.0.3 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT

FAQ

User reviews

—0 reviews

Select a star to share your experience.

No reviews yet. Ratings appear once readers share real experiences.

Similar Skills

View all skills