66 lines
3.2 KiB
Markdown
66 lines
3.2 KiB
Markdown
# Video Workbench Case Pattern Library
|
|
|
|
This directory is the local case-pattern library for Codex execution work in Video Workbench.
|
|
|
|
It is extracted from old GPT case files only at the level of structure, granularity, page or storyboard method, speaker-note style, visual asset layering, and review dimensions. It is not a prompt library and not a copy of the old GPT knowledge base.
|
|
|
|
## Source Basis
|
|
|
|
The first two patterns were localized from:
|
|
|
|
- `knowledge-vault/prompts/GPT/强哥的策划导演/30_CASE_典型视频分镜案例.md`
|
|
- `knowledge-vault/prompts/GPT/强哥的策划导演/31_CASE_典型培训AI_PPT案例.md`
|
|
|
|
Those source files remain historical GPT assets in Knowledge Vault. Video Workbench uses the extracted patterns below as Codex-side local execution guidance.
|
|
|
|
## Cases
|
|
|
|
| case | use when | local output focus |
|
|
| --- | --- | --- |
|
|
| [science-video-page-style-case.md](science-video-page-style-case.md) | Turning a deep article, model point, or public-facing concern into a PPT-style science video | Shot/page granularity, narration pacing, visual metaphor, review criteria |
|
|
| [training-ai-ppt-case.md](training-ai-ppt-case.md) | Turning AI education, method training, product enablement, or workshop content into a teachable slide deck | Teaching unit design, speaker notes, interaction, editable slide structure |
|
|
|
|
## Local Use
|
|
|
|
Use these cases after GPT V2 stage 0-5 planning has been accepted into a project `intake/` directory. Codex then converts the accepted planning into:
|
|
|
|
- `project.md` for project map and current focus;
|
|
- `execution-plan.md` for execution strategy, batch, round, and next decision;
|
|
- `visual-system/visual-system.md` for visual-system materialization and review;
|
|
- `slides/slides.md` and `slides/sNN/` for page or shot execution facts and assets.
|
|
|
|
## What To Extract
|
|
|
|
Extract these parts from old or future real cases:
|
|
|
|
- medium branch and audience;
|
|
- logic-to-page or logic-to-shot decomposition;
|
|
- page or shot function;
|
|
- one-unit-one-purpose granularity;
|
|
- editable page text vs visual asset vs narration or speaker notes;
|
|
- visual-system anchors and reusable motifs;
|
|
- review dimensions and acceptance criteria;
|
|
- batch/iteration advice.
|
|
|
|
## What Not To Inherit
|
|
|
|
Do not inherit these legacy assumptions:
|
|
|
|
- GPT outputs final image prompts.
|
|
- GPT outputs Codex JSON execution packages.
|
|
- GPT specifies local output paths, task lists, or generation parameters.
|
|
- the old assumption that every image prompt must forbid readable text.
|
|
- old source filenames or schemas become current Video Workbench contracts.
|
|
|
|
For current Video Workbench, text placement is an execution decision. Body copy is usually rendered in the editable PPT or video page layer; image-generated labels, formulas, diagrams, or text are allowed only when the execution plan and review criteria explicitly require that layer.
|
|
|
|
## Review Dimensions
|
|
|
|
When adding a new case pattern, check:
|
|
|
|
- Does the pattern state which medium branch it serves?
|
|
- Does it describe unit granularity without copying a full old case?
|
|
- Does it separate source logic, page or shot copy, visual assets, and narration/speaker notes?
|
|
- Does it provide review criteria that Codex can apply during small-batch iteration?
|
|
- Does it avoid old Prompt, JSON, path, and global text-rendering rules?
|