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 tone and genre into reusable camera, lighting and visual-style rules.
--- name: style-cinematography-director description: "Translate genre, tone, cinematic references, lens language, lighting, framing, blocking, texture, realism, and audience experience into reusable creative direction for scripts, shot lists, and prompts." --- # style-cinematography-director ## When to use - The user asks for cinematic style, genre look, camera language, lensing, lighting, blocking, realism, texture, visual tone, or art-direction guidance. - The user has a story but needs a visual language before shot lists or prompts. - The user wants style consistency across scenes or model outputs. ## When not to use - The user only wants model-specific parameter conversion. - The user needs screenplay dialogue rather than visual direction. - The user asks for a single still prompt and already has full visual specs. ## Required inputs - Story/scene/concept - Genre/tone/audience experience - Desired realism level - References if any ## Optional inputs - Runtime - Target platform/aspect ratio - Color palette - Continuity bible - Model/tool constraints ## Workflow 1. Translate abstract tone into visible choices: contrast, palette, lens distance, camera stability, light source, texture, blocking, and production design. 2. Select a genre grammar but avoid copying a specific protected work. 3. Define lens and framing rules that express emotional distance and power dynamics. 4. Define lighting rules with direction, quality, source, color temperature, and shadow behavior. 5. Define texture and realism rules: skin, fabric, weather, grain, imperfections, and artifact guardrails. 6. Create a compact style bible and shot-level style tags for downstream prompts. 7. Flag style choices that conflict with target model limits. ## Decision logic - If the user gives only mood words, convert them into concrete camera/light/color decisions. - If multiple references conflict, choose a dominant anchor and one accent. - If photorealism matters, prioritize physical light, lens behavior, and micro-texture over quality adjectives. - If the result is for video, include motion and blocking rules. ## Output formats - Visual direction brief - Genre/tone translation - Cinematography rules - Lighting palette - Texture/realism rules - Prompt-ready style block ## Quality checks - Every style claim maps to a visible or audible execution detail. - Camera, lighting, color, and production design reinforce the same emotional goal. - References are used as inspiration, not reproduction. - Style rules are concise enough for repeated prompting. - Conflicts with model behavior are noted. ## Anti-patterns - Generic cinematic adjectives without technical choices - Overloading prompts with many film references - One-note palettes that flatten emotional range - Style rules that fight the story purpose - Copying a living artist or exact protected image when a descriptive alternative works. ## Exit criteria - A reusable style/cinematography brief is ready for story, shot list, bible, image prompt, video prompt, or model adaptation. ## Supporting files Read only the supporting file needed for the active task: - `references/cinematic_language.md` - `references/camera_lens_movement.md` - `references/lighting_and_photorealism.md` - `references/genre_style_tone.md` - `templates/visual_style_bible.md`
Translate tone and genre into reusable camera, lighting and visual-style rules.
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.
Story or scene, desired tone/realism, references and output constraints.
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/cinematic_language.md, references/camera_lens_movement.md, references/lighting_and_photorealism.md, references/genre_style_tone.md, templates/visual_style_bible.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 Cinematography Direction for [TASK]. Ask for missing inputs: Story or scene, desired tone/realism, references and output constraints. 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/cinematic_language.md, references/camera_lens_movement.md, references/lighting_and_photorealism.md, references/genre_style_tone.md, templates/visual_style_bible.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.