Present an identity as a set of usable decisions, from purpose and mark construction to color, type and physical applications. Cobalt System Deck combines cobalt chapter fields, lemon cues, warm ivory pages and black contrast sections. Geometric studies stay separate from photography, and the page count follows the brief rather than the twelve-page example.
What you get
A guideline sequence built to the agreed count, using distinct pages for purpose, mission, mark construction/meaning, colors, typography, applications and imagery where the content needs them. Twelve recipes provide an identity cover, oversized contents, dark introduction, four-point mission path, grid study, mark-meaning composition, color circles, type specimen, stationery, objects, imagery board and close; they are optional structures, not a mandatory order or limit.
A coherent visual grammar: large clean sans-serif headings, compact notes, a low-contrast geometric emblem in chapter fields, construction/clear-space studies, overlapping color circles and strong changes in page density. The example’s four open brackets around a square void remain original vector geometry, not a copied brand mark. Browser-editable text and diagrams are distinct from placed artwork.
Artwork planned for each actual page rather than a fixed quota. The kit has twelve picture slots across its example layouts and twelve local catalog images, including portraits, stationery, merchandise and material/product imagery. Topic-specific stationery/merchandise pictures are used only where relevant; library portraits and illustrations do not identify real team members or customers.
A self-contained HTML presentation with page navigation, synchronized editor thumbnails, notes, presentation mode and print/PDF styling. The package supplies recipes, references, the shared runtime, Python build/check tools and Node image helpers. Its schema fixture and fictional studio example are not a finished guideline for your organization.
Requested PPTX export with editable text/notes and separate pictures, while SVG/CSS/background decoration becomes rendered layers. PDF gives one 16:9 page per slide. A visual review must cover the actual output rather than treating the diagram’s browser editability as proof of native PowerPoint shapes.
Before you choose
Check that each guideline explains an actual decision someone could apply. A construction grid should clarify a mark, a specimen should demonstrate readable type, and an application should obey the rule it illustrates. A consistent blue field alone does not make the guide usable.
Good fit
A designer needs to explain how a visual identity works through mark rules, color, typography, physical applications and image direction.
A team is creating a civic/wayfinding communication guide or another identity presentation that needs consistent rules across varied pages, rather than a recreation of an existing protected identity.
You can supply a clear audience, approved messages and source material and want the content adapted to an agreed presentation length.
Not for
Reproducing a source artwork, existing protected identity, recognizable source person or character. The visual system and any new assets must be original or approved for use.
Automated research or certification of brand claims, customer facts or mission statements. The deck presents approved evidence rather than validating it independently.
An export in which every mark, construction line, background and decorative element is a native PowerPoint shape. Text/notes and image objects have a different export boundary.
Using fictional portraits, stationery wording or studio claims as real organizational evidence simply because they match the palette.
How to use
You say/cobalt-system-deck Create a twelve-page visual identity guide for a fictional studio, using cobalt blue, lemon accents and original stationery photographs.
Provide the topic, audience, language, purpose, approved messages/source material and requested slide count. Include identity rules and assets that may actually be used. Count opening and closing pages within the requested total unless specified otherwise; if the count is missing, agree it from the material and speaking duration instead of adopting twelve pages automatically.
Plan a role for every page, selecting, combining, reordering or extending the recipes as needed. Keep the cobalt/lemon/ivory/black rhythm and original geometric logic. Cobalt and lemon is the reference preset; Deep ocean, Forest signal and Vermilion system are generation-time alternatives. Current editor color controls are individual edits, not a preset theme switcher.
Prepare an art ledger with page, subject, aspect, placement, palette, prompt and saved result per needed image. Choose reuse, reuse-plus-generation or regenerate-all, giving approved user assets priority; default to reuse when no choice is available. List unsuitable/unfilled slots. Match the kit’s aspect ratios, including 3:4 portraits, 4:3 stationery, square objects and mixed imagery-board formats.
Use the local image catalog with the checksum-verifying Node helper and respect its topic-specific labels. Use each photographic artwork on only one page; a crop, rotation or recolor is still the same source. Functional vector marks may recur as the subject of the guide. For authorized new art, use the built-in image tool or the documented paid FAL submit/status/fetch helper; preserve a returned request ID and do not automatically resubmit failures. Provider charges or account limits may apply.
Replace sample studio copy, mark explanations, stationery wording and image descriptions with the approved subject. Keep meaningful copy and diagrams outside raster art, use consistent inline SVG reading cues and no decorative model marks. Compose via plan.json, clear example leftovers/unfilled slots and build/check with Python 3. Node is needed for the image helpers, not the core HTML assembly.
Embed final images at useful resolution, using quality-preserving WebP, and keep the HTML below the package’s 20 MB ceiling. Inspect all pages at 1280×720 for crops, unique imagery, readable type, color-area balance and actual page numbering. Do not assume a font is embedded: this kit’s content styles use system sans-serif stacks. Check native font availability separately.
Test Edit/E, notes, object changes, reordering, undo/redo, Save and reopening the saved file. Confirm thumbnails, page labels and presentation navigation match the agreed total. Export only the requested PPTX/PDF, run check-pptx.py and inspect in PowerPoint, Keynote or WPS before reporting verified output; record visual issues and any remaining image gaps.
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.6 — Claude Code / Claude Desktop / Cowork / Codex / ChatGPT
FAQ
Yes. Keep the identity-guide logic while rebuilding the page plan around your approved subject and exact requested count. The twelve example recipes are a vocabulary, not a default length or ceiling. If you have no count in mind, agree one based on content and speaking duration.
Not just to reuse the style. Twelve local library images are bundled and can be embedded after checksum verification, subject to their topic suitability. Use approved supplied pictures first and list unmatched frames. New art follows the actual page design rather than a quota and can incur provider charges or account limits; do not publish a half-filled image page as complete.
Use Edit or E in the standalone HTML to change content, pictures, order and notes, then Save the file. Named palettes apply during generation; the shared editor has no style-specific theme picker. PPTX keeps text/notes editable and photos separate, with SVG/CSS decoration rendered into layers. The current build/check path is Python 3, while Node is used by optional image helpers. Inspect the export in the target application.
The visual rules use each photographic artwork on one page only; cropping, rotating or recoloring it does not create a distinct image. Functional geometric marks and icons can repeat where the guideline is explaining them. Plan independent pictures for different page roles.
User reviews
—0 reviews
Select a star to share your experience.
No reviews yet. Ratings appear once readers share real experiences.