docs(prompting): frame.md is the design spec, drop design.md references

This commit is contained in:
Vance Ingalls
2026-07-29 18:45:30 -07:00
parent 5a05182226
commit 4260f12b01
+2 -2
View File
@@ -9,12 +9,12 @@ Everything so far was one scene at a time. This level is about videos as systems
## Point at a spec, don't describe a vibe
HyperFrames projects can carry a design spec — `frame.md` (video-first) or `design.md` — whose frontmatter tokens are the machine-readable brand: exact hex values, font families, weight relationships, and the brand's Do's and Don'ts. When one exists, name it:
HyperFrames projects can carry a design spec — `frame.md` — whose frontmatter tokens are the machine-readable brand: exact hex values, font families, weight relationships, and the brand's Do's and Don'ts. When one exists, name it:
> Use the palette and type from `frame.md`. Build a 15-second feature announcement.
- ❌ `make it feel on-brand and premium`
- ✅ `pull colors and fonts from design.md; premium means generous spacing and one restrained accent`
- ✅ `pull colors and fonts from frame.md; premium means generous spacing and one restrained accent`
The engine rationale: `on-brand` is a mood the agent guesses at. A spec's frontmatter is normative — the agent quotes the hex and font family verbatim instead of approximating, and reads the prose sections for intent. If your brand lives somewhere else (a PDF brand guide, a screenshot, pasted hex codes), attach it — attachments and pasted tokens are read more reliably than a described impression.