Marketing Foundation
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.
Understand customer needs, compare competitors and plan a community around real member value.
Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.
Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.
Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.
Translate a scene into shots, camera setups, assets and continuity notes.
--- name: shotlist-and-visual-breakdown description: "Convert scripts, scene outlines, or treatments into shot lists, camera setups, production beats, continuity notes, asset requirements, and prompt-ready visual breakdowns." --- # shotlist-and-visual-breakdown ## When to use - The user asks for a shot list, scene breakdown, storyboard plan, camera plan, production beat map, or asset list. - The user provides script pages or a scene outline and wants image/video prompt inputs. - The user needs continuity notes for characters, locations, props, wardrobe, blocking, or screen direction. ## When not to use - The user is still exploring the story premise and has no scene yet. - The user only wants model-specific syntax conversion. - The user wants a full production budget or call sheet. ## Required inputs - Scene text or outline - Runtime/clip duration target - Visual style or genre - Continuity bible if available ## Optional inputs - Target model limits - Aspect ratio - Location/asset constraints - Need for image prompts, video prompts, or both ## Workflow 1. Break the scene into story beats and visual beats. 2. For each beat, assign shot purpose: geography, emotion, reveal, action, detail, transition, or continuity insert. 3. Select shot scale, angle, lens feel, camera movement, lighting state, blocking, and production design anchors. 4. Respect duration math: one clear action per short shot unless the target model supports multi-shot or extension workflows. 5. Create continuity notes: eye lines, screen direction, wardrobe, prop state, weather, time of day, and emotional state. 6. Create an asset list for characters, locations, props, costumes, reference images, sound cues, and keyframes. 7. Prepare handoff rows for image and video prompting. ## Decision logic - If identity consistency matters, request or generate reference sheet prompts before video prompts. - If the scene has complex motion, split into simpler shots rather than one overloaded prompt. - If the target model supports first/last frames, mark shots that need keyframes. - If dialogue is present, check line length against clip duration. ## Output formats - Shot list table - Camera setup list - Scene breakdown - Asset list - Continuity notes - Image/video prompt handoff ## Quality checks - Every shot has a purpose and a single dominant subject/action. - Camera movement is motivated by story or emotion. - Shot order preserves geography and screen direction. - Asset needs are explicit enough to generate references. - Prompts can be created without re-reading the full script. ## Anti-patterns - Shot lists that merely restate the script - Multiple camera moves in one short AI-video prompt - Ignoring prop or wardrobe state changes - Using style words without visual execution details - Cutting away before a story beat has visual consequence ## Exit criteria - The scene is decomposed into shot rows and asset requirements ready for image/video prompting or production packaging. ## Supporting files Read only the supporting file needed for the active task: - `references/shotlist_schema.md` - `references/camera_plan.md` - `references/production_breakdown.md` - `templates/shot_list.md` - `templates/scene_breakdown.md` - `templates/asset_list.md`
Translate a scene into shots, camera setups, assets and continuity notes.
The complete original workflow, with source attribution and the limitations below.
Confirm the task, check actual dependencies, then apply the relevant original instructions within authorized scope.
Script/outline, runtime, style and available continuity references.
Published after an obvious-danger screen under the user-requested policy, not a functional test. Supporting files required conditionally by the original are not supplied: references/shotlist_schema.md, references/camera_plan.md, references/production_breakdown.md, templates/shot_list.md, templates/scene_breakdown.md, templates/asset_list.md. Related model-adaptation/continuity handoffs must be available for the actual task; loading this source does not load them. No media generation, model-capability verification or code execution was performed. Treat named-model parameters as unknown until checked and use authorized references/assets.
Use Shotlist and Visual Breakdown for [TASK]. Ask for missing inputs: Script/outline, runtime, style and available continuity references. Check the declared dependencies and limitations before execution. Return the original output structure with known facts, assumptions and unresolved requirements separated.
Claiming that unavailable source dependencies are bundled or that generated outputs, integrations or model behavior have been tested. Actual media generation without a separately available authorized tool.
M11 added German routing, task inputs and explicit source-package limitations; the original author remains separate from M11 curation. Published after an obvious-danger screen under the user-requested policy, not a functional test. Supporting files required conditionally by the original are not supplied: references/shotlist_schema.md, references/camera_plan.md, references/production_breakdown.md, templates/shot_list.md, templates/scene_breakdown.md, templates/asset_list.md. Related model-adaptation/continuity handoffs must be available for the actual task; loading this source does not load them. No media generation, model-capability verification or code execution was performed. Treat named-model parameters as unknown until checked and use authorized references/assets.
MIT License Copyright (c) 2026 0xhughs Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copy the text below, then paste it into your chat.