step3-content-blueprint

Populate Step 3 canon JSON files with cross-file coherence for characters, locations, and cinematography.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/Perfectz/AIMVDashboard --skill step3-content-blueprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: step3-content-blueprint
Source: https://github.com/Perfectz/AIMVDashboard/tree/main/skills/step3-content-blueprint
Command: npx skills add https://github.com/Perfectz/AIMVDashboard --skill step3-content-blueprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams to complete and lock the Step 3 content bible for AIMVDashboard by populating canonical JSON files (characters.json, locations.json, visual_style.json, cinematography.json, shot_list.json) and ensuring cross-file coherence.

Core Features & Use Cases

  • Create production-ready canon artifacts that anchor characters, locations, style, and cinematography across all downstream prompts and generations.
  • Validate cross-file references, enforce required fields, and maintain ID coherence between shots, characters, and locations.
  • Use case: When asked to complete or validate Step 3 page tabs, generate a consistent bible that downstream prompts rely on.

Quick Start

Populate all Step 3 canon JSON files for a target project and validate cross-file coherence against Step 1-2 context.

Frequently Asked Questions about step3-content-blueprint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a production-ready story bible with consistent canon JSON files?

Generate a production-ready story bible by populating canonical JSON files for characters, locations, visual style, cinematography, and shot list, ensuring cross-file coherence and ID validation across all artifacts.

What is cross-file coherence in cinematography and visual style JSON generation?

Cross-file coherence in JSON generation validates references and enforces required fields, ensuring character IDs, locations, visual style, and cinematography constraints remain strictly aligned across the project bible.

How to validate shot list references against characters and locations JSON?

Validate shot list references by checking ID coherence between shot entries and the characters.json and locations.json files, enforcing required fields to maintain strict cross-file alignment.

Does this canon JSON generation enforce critical constraints for cinematography and visual style?

Yes, canon JSON generation enforces critical constraints specifically within the cinematography.json and visual_style.json files, delivering API-ready outputs that align timing with downstream analysis sections.

Can I use this to populate all Step 3 canon JSON files for an AIMVDashboard project?

Yes, you can populate all Step 3 canon JSON files for an AIMVDashboard project, validating cross-file references against Step 1-2 context to produce a locked, production-ready bible.

When do I need to lock a story bible and generate canonical JSON artifacts?

Lock a story bible and generate canonical JSON artifacts when downstream prompts and generations require anchored characters, locations, style, and cinematography data to maintain strict production coherence.