tasteforge-video

Topics in the source

• TasteForge Video
• When to Use
• Local Deterministic Operations vs Provider Generation
• Canonical Implementation
• Chaining the Creative Skills
• Workflow
• Applying Real Footage Without Repeated Sources
• File-Driven Multimodal Contract

For the complete standalone creative pipeline, use taste-distillation then taste-application. Those ECC skills ship their Python scripts directly: measure references, generate or pass through existing takes, grade, cut, composite, verify, and hand off to Blender and Resolve. No separate video repository is required for that flow. This skill documents ECC's packaged offline engine and its strict evidence contract. TasteForge turns "make it feel like this reference" into a repeatable, inspectable workflow: interview taste, distill it into a structured style pack, validate the pack, apply its measured cadence and look to local media, and export an editable timeline. The canonical implementation is the tasteforge package shipped inside ECC at skills/taste-application/scripts/tasteforge/. Ito-Markets/ito-video is an example project that consumes the packaged ECC engine. The user asks to interview for video taste before any footage is made ("ask me about the look", "interview me about aesthetic direction"). The user wants to distill an aesthetic into structured constraints — a reusable style pack rather than vibes ("turn these references into a pack"). The user wants to validate a style

This is an excerpt. Refer to the complete source and its current requirements.