Yellow Balance Deck

Explain a focus-planning concept through priorities, people, a weekly rhythm and the next decision. Yellow Balance Deck uses light typography, white/pale-gray space, sunny yellow cards and sculptural vignettes. The app/persona story is fictional: paired phone images, allocation cards and planning numbers illustrate an idea, not a working product or proof of improved focus.

What you get

  • Twelve optional compositions: hourglass vignette/title, overlapping portrait cards, protected-priorities statement/callouts, planning numerals/glass flower, asymmetric image gallery, phone pair, two-person role spread, circle-grid chapter, note question, persona/allocation card, architectural step cards and dark mosaic close. Select, reorder, combine or extend for the exact agreed count.
  • A white/pale warm-gray #f7f7f5 system with sunny yellow #ffda32 and charcoal #342928. Light tightly spaced Arial-style headlines, quiet brief body text, fine yellow underlines, small pills, subtly rounded panels and white shadow spheres keep the hierarchy airy. Preserve delicate type rather than substituting heavy display headings.
  • Thirty-four catalog assets cover hourglass/object studies, fictional portraits, architecture, abstract materials, phone concepts and a closing mosaic. Safe/coins and phone images have finance/mobile-product subject restrictions. Use each pictorial source once; a realistic phone, architectural view or persona image does not establish product functionality, actual customers or performance.
  • A generated standalone 1280×720 HTML deck with navigation, overview/thumbnails, speaker notes, editing, presentation mode and print styling. Meaningful text, step/allocation diagrams and labels stay editable. The installation supplies recipes, references, catalog and build/media helpers; its generic schema fixture is not a completed focus-planning app deck.
  • Optional checked PPTX/PDF outputs. Native text/notes and separate pictures stay editable in PowerPoint; backgrounds, SVG decoration, shadows and complex layers are rendered. PDF printing gives one 16:9 page per slide. Inspect actual exports and recipient fonts instead of promising every decorative element as a native shape.

Before you choose

Make the planning concept explicit before judging its calm appearance. Explain which priorities it surfaces, what a proposed weekly allocation means and what decision follows. Keep the phone/persona imagery illustrative and distinguish a useful proposal from claims that a product already works or improves focus.

Good fit

  • A product or planning team has a focus/weekly-rhythm concept and approved material about its intended experience.
  • A presenter needs consistent pages for priorities, roles, comparisons, allocation and next steps.
  • A creator can provide accurate source facts, a clear audience/message, language and desired count and inspect the presentation at full size.

Not for

  • Reproducing source names, logos, artwork, recognizable people or protected characters.
  • Automatic research or verification of productivity, cognitive/health effects, product adoption or unsupported performance claims.
  • A functioning planning app or an all-native-shape PowerPoint deliverable; illustrative phones and rendered decorations do not provide either.

How to use

You say/yellow-balance-deck Create a twelve-page focus-planning concept deck with sunny yellow layouts, balanced editorial compositions and original lifestyle photographs.
  1. Provide topic, audience, key messages/source facts, language and exact count including opening/closing unless agreed otherwise. If unspecified, agree length from content and duration. Separate the intended planning experience, illustrative personas/allocations and actual evidence.

  2. Plan distinct roles for priorities, rhythm, perspectives, product concept, allocation and next action. Select/extend the twelve recipes without inventing people, metrics or steps to fill compositions. Label concept personas/values and replace fictional names; phone images illustrate proposed moments rather than implemented features.

  3. Prioritize supplied pictures, then suitable catalog reuse, generation for gaps or all-new art; reuse is the fallback without a choice/tool. Log page, subject, ratio, placement, palette, prompt and result. Use each pictorial source once, with crops/rotations/recolors counting as the same asset. Functional SVG primitives may repeat and no image quota applies.

  4. Check safe/coins and mobile-app restrictions and keep portraits/architecture relevant to the story. Use original object/photo imagery rather than manufacturing variants by reusing a background. Generate at kit slot ratios through built-in tools or the FAL helper/FAL_KEY. FAL costs separately: submit once then poll/fetch, without automatic failed-task replacement. Disclose missing or unsuitable frames.

  5. Compose approved text, alt descriptions, pictures, icons, labels and data from recipes and remove unused nodes. Python 3 handles compose/build/static checks; optional media helpers use Node. Resolve unfilled-image and leftover-example reports, verify count and inline fonts/resources under 20 MB. Preserve useful image resolution and keep meaningful copy editable.

  6. Inspect every 1280×720 page over local HTTP for delicate-type contrast, whitespace, product-background seams, rounded-card proportions, photo/portrait crops, unique mosaic images, allocation labels, bounds and notes/page consistency. Check claims against sources. Exercise text/block/order/layout/color edits, notes, undo/redo, Save/reopen and presentation mode; correct and inspect failures.

  7. 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. Visual-system guidance is applied during generation, not through an editor theme picker; embedded PPTX export replaces the retired mandatory Node/Chromium export chain.

Requirements and costs

You bring
Presentation topic and audience · Key messages or source material · Desired slide count and language
Dependencies
A browser for presentation and verified print export · Node.js for local validation · A host image generation tool for fresh artwork · Chrome, Chromium or Edge plus Node.js 20 or newer — required only for PowerPoint export
Outside costs
Generating new artwork may incur a separate provider charge. The included original example can be viewed without image generation.
Publisher testing
v1.0.5 — 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