storyboard-prompt-orchestration

Generates structured storyboard scripts and style-locked image prompts from product concepts.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/thorsenk/skills --skill storyboard-prompt-orchestration-thorsenk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: storyboard-prompt-orchestration
Source: https://github.com/thorsenk/skills/tree/main/skills/storyboard-prompt-orchestration
Command: npx skills add https://github.com/thorsenk/skills --skill storyboard-prompt-orchestration-thorsenk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a messy product idea into a usable image-generation prompt usually skips the design-thinking step, producing generic centered compositions with no interaction logic or annotations. This Skill enforces a mandatory pipeline—context scoping, storyboard script, locked visual style, then final prompts—so every output is grounded in structured zones covering interface, interaction, brand, and annotations. ## Core Features & Use Cases - Mandatory storyboard script: Emits a markdown storyboard with metadata, zones A–E (interface, interaction, brand, annotations, spatial), key notes, constraints, and open questions before any prompt is written. - Six locked style contracts: Selects one of six style_output_mode values (rough notebook storyboard, editorial systems illustration, industrial concept sketch, blueprint UX schematic, product keynote concept board, whiteboard strategy map) with explicit drift-avoidance rules and a disclosed hybrid protocol. - Controlled rerun menu: Offers a single post-run menu (R0–R5) for restyling, panel-count changes, storyboard revision, fresh context, or prompt-only export. - Use Case: A designer asks for a concept storyboard for an AI research workspace; the Skill produces a four-panel storyboard script with zone-mapped content, locks style A, and outputs generation-ready prompts with colored-pencil semantics and anti-polish constraints. ## Quick Start Use the storyboard-prompt-orchestration skill to turn my product idea for a smart home control kiosk into a storyboard script and generation-ready prompts.

Frequently Asked Questions about storyboard-prompt-orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a storyboard script from a product idea?▼

Provide your concept and the Skill scopes the context, then emits a markdown storyboard with metadata, zones for interface, interaction, brand, and annotations, plus key notes and open questions. It defaults to four panels and storyboard-plus-prompt output unless you specify otherwise.

What visual styles are available for concept storyboards?▼

Six locked style_output_mode contracts exist: rough notebook storyboard, editorial systems illustration, industrial concept sketch, blueprint UX schematic, product keynote concept board, and whiteboard strategy map. Each has binding visual language and drift-avoidance rules defined in reference.md.

Can I mix two storyboard styles in one run?▼

Hybrids are allowed only with explicit disclosure: you must name the hybrid, declare one dominant base style, and list the concrete borrowed traits from other styles. Silent mixing of visual language across modes is prohibited.

Does the storyboard skill generate images directly?▼

It generates images only when an image tool is available in the host and you explicitly ask for a render after storyboard approval. Otherwise it outputs generation-ready prompts for an external image generator, and prompt-only requests never invoke a renderer.

When should I not use storyboard prompt orchestration?▼

Avoid it for polished final comps, production wireframes, logo-only exploration, photorealistic hero shots, or unstructured one-shot image requests without a storyboard phase. It is designed for early-stage ideation artifacts, not final deliverables.