mirror of
https://github.com/hanzoai/frames.git
synced 2026-09-24 00:08:03 +00:00
zooqueen
62bbc7766c
Every SKILL.md already declared the new name — name: frames, frames-cli, frames-core, and so on — but the directories were never moved, so the tree carried frames-* in content and hyperframes-* on disk. Everything that resolves a skill by path missed: the core-skill list, the plugin marketplace pin, and the docs the CLI reads at runtime. Eight tests failed on main because the files they open do not exist. The directories now match what the files say they are, and the guide the claude-design contract reads takes the name that contract already used.
1.4 KiB
1.4 KiB
Design Adherence
Post-authoring verification that the composition follows the design spec. Run it after building, before serving the preview.
If a design spec (frame.md / design.md) exists, read the HTML and check:
- Colors — every hex value in the composition appears in the spec's palette section (however the user labeled it: Colors, Palette, Theme, etc.). Flag any invented colors.
- Typography — font families and weights match the spec's type spec. No substitutions.
- Corners — border-radius values match the declared corner style, if specified.
- Spacing — padding and gap values fall within the declared density range, if specified.
- Depth — shadow usage matches the declared depth level, if specified (flat = none, subtle = light, layered = glows).
- Avoidance rules — if the spec has a section listing things to avoid (commonly "What NOT to Do", "Don'ts", "Anti-patterns", or "Do's and Don'ts"), verify none are present.
Report violations as a checklist. Fix each one before serving.
If no design spec exists (house-style-only path), verify:
- Palette consistency — the same bg, fg, and accent colors are used across all scenes. No per-scene color invention.
- No lazy defaults — check the composition against
house-style.md's "Lazy Defaults to Question" list. If any appear, they must be a deliberate choice for the content, not a default.