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.
Track recurring characters, locations, props and changing scene state.
--- name: character-location-prop-bible description: "Create and maintain continuity bibles for characters, locations, props, costumes, color palettes, style rules, reference assets, and cross-shot visual anchors." --- # character-location-prop-bible ## When to use - The user needs consistency across images, shots, scenes, or models. - The user asks for a character bible, location bible, prop list, wardrobe continuity, style bible, or continuity checklist. - The project is moving from idea/script into repeatable image/video generation. ## When not to use - The user only wants one disposable prompt with no continuity need. - The task is pure model parameter research. - The user asks for story structure without visual asset continuity. ## Required inputs - Project title or scene - Existing descriptions or outputs - Characters/locations/props/costumes to track - Target visual style ## Optional inputs - Reference images - Shot list - Model-specific requirements - Palette or genre anchors - Version history ## Workflow 1. Create stable IDs for characters, locations, props, costumes, and style rules. 2. Record immutable anchors: identity, silhouette, proportions, palette, materials, prop condition, location geography, and lighting baseline. 3. Separate mutable state: emotion, wardrobe changes, damage, weather, time of day, prop position, and story-state changes. 4. Create golden-image reference prompt entries for clean sheets before dramatic variants. 5. After each generated output or script change, update only the changed fields and preserve a changelog note. 6. Prepare a continuity packet for prompting: minimal anchors for each shot plus exclusions for drift-prone details. ## Decision logic - If a detail must never change, place it in immutable anchors. - If a detail changes by scene, place it in state timeline. - If two sources conflict, prefer the latest user-approved bible entry and log the conflict. - If model transfer causes drift, route to model-adaptation and use reference-image workflows where supported. ## Output formats - Character profile - Location profile - Prop profile - Costume profile - Visual style bible - Continuity checklist - Reference asset index - Golden image plan - State timeline ## Quality checks - Every recurring asset has an ID and stable anchor fields. - Mutable state is tied to scene/shot numbers. - Prompt anchors are concise enough to reuse. - Style rules distinguish creative intent from execution details. - Conflicts are logged instead of silently resolved. ## Anti-patterns - Changing character descriptions between prompts - Mixing immutable identity with temporary emotion - Overlong bible entries that agents cannot practically reuse - Ignoring prop state after action beats - Relying on text-only consistency when references are available. ## Exit criteria - A concise continuity packet exists for downstream screenplay, shot list, image prompts, video prompts, and model exports. ## Supporting files Read only the supporting file needed for the active task: - `references/continuity_system.md` - `references/visual_bible_system.md` - `references/identity_anchors.md` - `references/golden_image_workflow.md` - `templates/character_profile.md` - `templates/location_profile.md` - `templates/continuity_checklist.md`
Track recurring characters, locations, props and changing scene state.
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.
Project descriptions, existing approved references and assets to track.
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/continuity_system.md, references/visual_bible_system.md, references/identity_anchors.md, references/golden_image_workflow.md, templates/character_profile.md, templates/location_profile.md, templates/continuity_checklist.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 Visual Continuity Bible for [TASK]. Ask for missing inputs: Project descriptions, existing approved references and assets to track. 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/continuity_system.md, references/visual_bible_system.md, references/identity_anchors.md, references/golden_image_workflow.md, templates/character_profile.md, templates/location_profile.md, templates/continuity_checklist.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.