storyboard-grid-writer
Write dense storyboard-grid prompts for short-form image or previsualization workflows. Use this when a generation controller needs a 6-9 panel grid with hook logic, visible actions, product timing, and negative constraints before image or video request architecture.
What this skill does
# Storyboard Grid Writer ## Use When - A controller needs a storyboard grid, beat panel plan, contact sheet, or panel prompt pack. - Hook logic must become visible frame-by-frame action before image or video generation. - The output should hand off to `image-generation` or `video-request-architect`. ## Do Not Use When - The final provider request is already approved. Use the runner. - Reference meaning or copy boundaries are unresolved. Use `reference-decode` or `reference-contract-builder`. - The user wants plain prose, a script only, or execution submission. ## Core Rule Common prompt should be short. Storyboard panels should be detailed. The grid must carry the narrative load. Do not hide scene logic inside vague style words. ## Required Inputs - `segmentType` - `viewerQuestion` - `openingMechanism` - `creativeFormat` - `targetFrameAspectRatio` - `mustCopyVisualGrammar` or required scene anchors - `forbiddenDrift` - `productRevealTiming` - text/UI policy If no reference exists, mark the output as no-reference and state the inferred scene anchors before writing panels. ## Grid Spec Default to 6 panels for short hooks and up to 9 panels for longer proof or motion continuity. Keep these ratios separate: - `boardLayoutRatio`: the contact-sheet or storyboard-board canvas - `targetFrameAspectRatio`: the per-panel creative output ratio, such as `9:16` or `3:4` The board layout must not silently change the generated asset ratio. ## Writing Method 1. Lock viewer question and stop-scroll job for panel 1. 2. Write structural grammar before style: camera start, closest subject, early object visibility, and native-feeling behavior. 3. Keep common prompt to reference policy, canvas rules, realism, no-text/UI, and safety boundaries. 4. Write each panel as visible events: camera position, subject placement, action, environment anchors, and one candid realism flaw when useful. 5. State product reveal timing and forbidden drift. ## Output Shape Return: - `gridSpec` - `commonPrompt` - `variantTitle` - `hookEssence` - `viewerQuestion` - `panelSequence` - `productRevealTiming` - `forbiddenDrift` - `handoffSkill` ## Preflight Checkpoint Before the final prompt, print: ```text Variant title: Viewer question: Panel 1 job: Panel 2-3 support: Panel 4-6 progression: Product reveal timing: Main drift risks: ``` ## Stop Conditions - Stop when required user intent, source evidence, or owned input artifacts are missing and guessing would change the result. - Do not create provider JSON or submit renders. - Do not let a runner infer storyboard logic from generic prompt adjectives. - If an owned CLI or script command fails, report the exact error and stop. Do not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools. ## Handoff - Image panels -> `image-generation`. - Video architecture -> `video-request-architect`. - Reference uncertainty -> `reference-decode` or `reference-contract-builder`. - Prompt risk review -> `prompt-preflight-qa`. ## Public Command Boundary - Choose the smallest matching command or workflow from the user input and run it directly. - If an owned CLI or script command fails, report the exact error and stop. Do not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools. - This public skill is instruction-driven. Produce the storyboard artifact directly from the available evidence. - Do not call private provider/runtime paths or unpublished local tools. - If the CLI returns a quote-confirmation challenge, run `postplus quote confirm --json --challenge-file <challenge.json>` and retry with the returned token.
Related in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.