* docs(skills): prefer frame.md over design.md for video specs
Skills now look for a design spec in precedence order frame.md →
design.md → DESIGN.md when reading. frame.md is the preferred spec for
video/hyperframes projects (same format as design.md) and wins if more
than one exists.
Read-path mentions updated across SKILL.md, house-style.md,
prompt-expansion.md, video-composition.md, and dynamic-techniques.md.
Creation flows (design picker, visual-styles) still output design.md;
website-to-video skill untouched.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* docs(skills): resolve frame.md/design.md consistency gaps from review
Address partial-migration contradictions flagged in review:
- video-composition.md: abstract the section header and intro line
(line 3, "## The Design Spec Is Brand, Not Layout") so a reader does
not hit design.md-only language before the abstracted body
- SKILL.md references index: "the design spec as brand not layout"
(line 472), "generating a design spec" (line 480), and the Step 1
conceptual aside (line 37)
- Note frame.md is always lowercase (no FRAME.md fallback) in the
precedence note; switch prompt-expansion prerequisite to the same
frame.md -> design.md -> DESIGN.md arrow notation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>