asset-continuity-management
Asset continuity management
Use this skill to keep generated-media projects reproducible, reviewable, and visually/aurally consistent across many assets, revisions, tools, and deliverables. Treat continuity as a production control system: every asset gets an ID, every change becomes an event, every derivative points back to its sources, and every continuity-critical choice is captured before more generation compounds the mistake.
This skill is provider-independent. Do not assume any particular generator exposes seeds, request IDs, input hashes, content credentials, prompt logs, or model versions. Capture them when available; explicitly record unknown, not_provided, or not_applicable when they are not.
Core rule
Never manage continuity by memory, filenames alone, or chat history alone. Maintain a project-local continuity package with three living records:
asset_manifest: one row/object per file or generated unit.source_reference_ledger: one row/object per source, reference, prompt, seed, model/tool context, approval, and rights/usage constraint.continuity_bible: canonical descriptions and locked references for characters, products, locations, wardrobe, brand, voice, music, captions, and recurring design motifs.
If the host pipeline already has artifact schemas, map these records into the native schemas rather than inventing parallel files. If no schema exists, use structured JSON, YAML, CSV, or tables that can be diffed and reviewed.
What to record first
Before generating or editing media, create the minimum continuity control plane: