Visual story direction
Skill twk0672005/sentence-to-site/skills/visual-story-direction
Use when a landing page, portfolio, product story, or editorial site lacks a clear visual premise, hierarchy, material direction, or meaningful critique target.From its SKILL.md
npx -y skills add twk0672005/sentence-to-site --skill visual-story-directionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.0 KB, 169 tokens by cl100k_base, as published. Nobody here has run it
Visual Story Direction
Before proposing libraries or effects, decide what a visitor must understand and feel in the first viewport. A visual system needs a premise, not a pile of components.
- State audience, one-sentence promise, desired first impression, and dominant contrast.
- Turn that into hierarchy, type scale/density, material, whitespace, and one interaction or motion job.
- Build or inspect a real browser view.
- Repair the single weakest visible problem before adding another feature.
Avoid generic bento layouts, decorative gradients, stock “cinematic” effects, and animation before a page has a story. A restrained page is valid when restraint supports the premise.
Use ../../references/visual-direction.md for the critique grid and ../../templates/motion-brief.md only when motion has an actual purpose.
What ships with it: 1 file
353 B alongside SKILL.md
evals/
- evals.json353 B