storyboard-creation
Create visual storyboards with AI image generation via inference.sh CLI.
Works with
5
total installs
5
this week
300
GitHub stars
0
upvotes
Install Skill
Run in your terminal
5
installs
5
this week
300
stars
Installation Guide
How to use storyboard-creation on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
storyboard-creation
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches storyboard-creation from inference-sh/skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate storyboard-creation. Access via /storyboard-creation in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
Storyboard Creation
Create visual storyboards with AI image generation via inference.sh CLI.
Quick Start
Requires inference.sh CLI (
infsh). Install instructions
infsh login
# Generate a storyboard panel
infsh app run falai/flux-dev-lora --input '{
"prompt": "storyboard panel, wide establishing shot of a modern city skyline at sunset, cinematic composition, slightly desaturated colors, film still style, 16:9 aspect ratio",
"width": 1248,
"height": 832
}'
# Stitch panels into a board
infsh app run infsh/stitch-images --input '{
"images": ["panel1.png", "panel2.png", "panel3.png"],
"direction": "horizontal"
}'
Shot Types
| Abbreviation | Name | Framing | When to Use |
|---|---|---|---|
| ECU | Extreme Close-Up | Eyes only, a detail | Intense emotion, revealing detail |
| CU | Close-Up | Face fills frame | Emotion, reaction, dialogue |
| MCU | Medium Close-Up | Head and shoulders | Interviews, conversations |
| MS | Medium Shot | Waist up | General dialogue, action |
| MLS | Medium Long Shot | Knees up | Walking, casual interaction |
| LS | Long Shot | Full body | Character in environment |
| WS | Wide Shot | Environment dominant | Establishing location, scale |
| EWS | Extreme Wide Shot | Vast landscape | Epic scope, isolation, transitions |
Generating Each Shot Type
# Close-Up — emotion focus
infsh app run falai/flux-dev-lora --input '{
"prompt": "close-up shot of a woman face showing concern, soft dramatic lighting from the left, shallow depth of field, cinematic film still, slightly desaturated",
"width": 1248,
"height": 832
}'
# Medium Shot — dialogue scene
infsh app run falai/flux-dev-lora --input '{
"prompt": "medium shot of two people talking across a table in a cafe, warm afternoon light through windows, natural composition, cinematic film still, 35mm lens look",
"width": 1248,
"height": 832
}'
# Wide Shot — establishing
infsh app run falai/flux-dev-lora --input '{
"prompt": "wide establishing shot of a futuristic laboratory interior, dramatic overhead lighting, long corridor with glass walls, sci-fi atmosphere, cinematic composition, anamorphic lens style",
"width": 1248,
"height": 832
}'
Camera Angles
| Angle | Effect | When to Use |
|---|---|---|
| Eye Level | Neutral, natural | Default for most scenes |
| High Angle | Subject looks small, vulnerable | Showing weakness, overview |
| Low Angle | Subject looks powerful, dominant | Authority, heroism, threat |
| Bird's Eye | God-like overview | Maps, establishing geography |
| Worm's Eye | Extreme power, awe | Architecture, towering figures |
| Dutch Angle | Unease, disorientation | Tension, madness, action |
| Over-the-Shoulder (OTS) | Viewer positioned with character | Conversations, POV |
Camera Movement
| Movement | Description | Emotion |
|---|---|---|
| Pan | Camera rotates horizontally (on tripod) | Scanning, following, revealing |
| Tilt | Camera rotates vertically (on tripod) | Revealing height, power |
| Dolly | Camera moves toward/away from subject | Intimacy (in), distance (out) |
| Truck | Camera moves laterally | Following alongside, revealing |
| Crane/Jib | Camera moves up or down vertically | Grand reveals, transitions |
| Zoom | Lens focal length changes (camera stays) | Focus shift, dramatic emphasis |
| Steadicam/Gimbal | Smooth handheld tracking | Immersion, following action |
| Handheld | Deliberate camera shake | Urgency, documentary feel, chaos |
| Static | Camera doesn't move | Stability, observation, tension |
In storyboards, indicate movement with arrows drawn on panels.
Continuity Rules
The 180-Degree Rule
Imagine a line (axis) between two characters in conversation. The camera must stay on ONE side of that line.
Character A Character B
●─────────────────●
/ \
/ CAMERA ZONE \
/ (stay on this side) \
📷 📷 📷
Camera 1 Camera 2 Camera 3
Crossing the line confuses the viewer about spatial relationships. Only cross intentionally (with a neutral shot in between or a visible camera move).
Match on Action
When cutting between two angles of the same action, the action must continue seamlessly:
Panel A: Hand reaches for door handle (medium shot)
Panel B: Hand grabs door handle (close-up)
↑ Action continues from same point
Eyeline Match
When a character looks at something, the next shot should show what they're looking at, from their approximate point of view.
Panel A: Character looks up and to the right
Panel B: The object they see, framed from slightly below-left
Screen Direction
If a character moves left-to-right in one shot, they should continue left-to-right in the next. Reversing direction implies they turned around.
Panel Layout
Standard Formats
| Layout | Panels | Use For |
|---|---|---|
| 2x3 (6 panels) | 6 per page | Detailed scenes, dialogue |
| 3x3 (9 panels) | 9 per page | Action sequences, montages |
| 2x2 (4 panels) | 4 per page | Key moments, presentations |
| Single | 1 per page | Hero shots, critical moments |
Panel Annotation Format
Each panel should include:
┌────────────────────────────────────┐
│ SCENE 3 — SHOT 2 │ ← Scene and shot number
│ │
│ [Generated image here] │ ← Visual
│ │
├────────────────────────────────────┤
│ Shot: MS, eye level │ ← Shot type and angle
│ Movement: Slow dolly in │ ← Camera movement
│ Duration: 4 sec │ ← Estimated duration
│ Action: Sarah opens the letter │ ← What happens
│ Dialogue: "This changes everything"│ ← Any spoken lines
│ SFX: Paper rustling, clock ticking │ ← Sound effects
│ Music: Tension builds │ ← Music cue
└────────────────────────────────────┘
Storyboard Workflow
Step 1: Shot List
Before generating images, write a shot list:
SCENE 1 — OFFICE, DAY
1.1 WS - Establishing shot of office building exterior, morning
1.2 MS - Sarah walks through office, carrying coffee
1.3 CU - Sarah's face, notices something on her desk
1.4 ECU - An envelope on the desk, unfamiliar handwriting
1.5 MS - Sarah picks up envelope, opens it
1.6 CU - Sarah's eyes widen as she reads
1.7 ECU - Key phrase on the letter (insert text)
Step 2: Generate Panels
Use consistent style across all panels:
# Establish a consistent style prompt suffix
STYLE="cinematic film still, slightly desaturated, warm color grade, 35mm lens, shallow depth of field"
# Panel 1.1 — Wide establishing
infsh app run falai/flux-dev-lora --input "{
\"prompt\": \"wide shot of a modern glass office building exterior, morning golden hour light, people entering, $STYLE\",
\"width\": 1248, \"height\": 832
}" --no-wait
# Panel 1.2 — Medium shot
infsh app run falai/flux-dev-lora --input "{
\"prompt\": \"medium shot of a professional woman walking through a modern open office, carrying coffee cup, morning light through windows, $STYLE\",
\"width\": 1248, \"height\": 832
}" --no-wait
# Panel 1.3 — Close-up
infsh app run falai/flux-dev-lora --input "{
\"prompt\": \"close-up of a woman face looking down at her desk with curious expression, soft office lighting, $STYLE\",
\"width\": 1248, \"height\": 832
}" --no-wait
Step 3: Assemble Board
# Stitch panels into rows
infsh app run infsh/stitch-images --input '{
"images": ["panel_1_1.png", "panel_1_2.png", "panel_1_3.png"],
"direction": "horizontal"
}'
infsh app run infsh/stitch-images --input '{
"images": ["panel_1_4.png", "panel_1_5.png", "panel_1_6.png"],
"direction": "horizontal"
}'
# Then stitch rows vertically for full page
infsh app run infsh/stitch-images --input '{
"images": ["row1.png", "row2.png"],
"direction": "vertical"
}'
Style Consistency Tips
- Use the same style suffix across all panels (lens, color grade, lighting)
- Use FLUX LoRA if you need consistent characters across panels
- Keep the same aspect ratio for all panels
- Generate more panels than you need and select the best
- If a panel doesn't match the style, regenerate with adjusted prompt
Common Mistakes
| Mistake | Problem | Fix |
|---|---|---|
| Crossing the 180-degree line | Confuses spatial relationships | Stay on one side or use neutral shot |
| All same shot type | Visually boring, no rhythm | Vary between CU, MS, WS |
| No establishing shot | Viewer doesn't know where they are | Start scenes with WS or EWS |
| Too many shots per scene | Pacing drags | 5-8 shots per scene is typical |
| Inconsistent style between panels | Looks like different projects | Use same style prompt suffix |
| Missing annotations | Panels are ambiguous | Always note shot type, movement, action |
Related Skills
npx skills add inference-sh/skills@ai-image-generation
npx skills add inference-sh/skills@ai-video-generation
npx skills add inference-sh/skills@video-prompting-guide
npx skills add inference-sh/skills@prompt-engineering
Browse all apps: infsh app list
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Related Skills
grill-me
359mattpocock/skills
premortem
196parcadei/continuous-claude-v3
deslop
113cursor/plugins
framer-motion
96pproenca/dot-skills
write-a-prd
88mattpocock/skills
travel-planner
86ailabs-393/ai-labs-claude-skills
Reviews
- IIsabella Martinez★★★★★Dec 28, 2024
I recommend storyboard-creation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- IIshan Chawla★★★★★Dec 20, 2024
Solid pick for teams standardizing on skills: storyboard-creation is focused, and the summary matches what you get after install.
- DDhruvi Jain★★★★★Dec 12, 2024
Solid pick for teams standardizing on skills: storyboard-creation is focused, and the summary matches what you get after install.
- AAditi Sharma★★★★★Nov 19, 2024
storyboard-creation reduced setup friction for our internal harness; good balance of opinion and flexibility.
- HHenry Kapoor★★★★★Nov 15, 2024
Keeps context tight: storyboard-creation is the kind of skill you can hand to a new teammate without a long onboarding doc.
- RRahul Santra★★★★★Nov 11, 2024
storyboard-creation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- IIra Ramirez★★★★★Nov 11, 2024
We added storyboard-creation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- OOshnikdeep★★★★★Nov 3, 2024
We added storyboard-creation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- GGanesh Mohane★★★★★Oct 22, 2024
storyboard-creation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- AAmina Chawla★★★★★Oct 10, 2024
Registry listing for storyboard-creation matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 35
Discussion
Comments — not star reviews- No comments yet — start the thread.