web-visual-direction
Skill2 starsChanged 4 months agoMITView on GitHub
Define a distinctive, implementable visual direction for websites and web apps. Use when an agent must establish or repair art direction, typography, color, composition, imagery, density, motion, or the first-screen impression before substantial frontend implementation.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- llms.txtllms.txt
- agentic-site-buildingSkill
- conversion-accessibility-polishSkill
- landing-page-craftSkill
- production-web-architectureSkill
- product-motion-designSkill
- responsive-ui-qaSkill
- technical-seo-discoverySkill
- web-design-systemSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Verify the direction at mobile and desktop widths.
- Distinctive: line 28
Prefer a memorable structural idea over decorative effects.
- Distinctive: line 30
Use typography with a reason.
- Distinctive: line 31
Use cards for meaningful grouping, not as the default container for every sentence.
- Distinctive: line 32
Treat gradients, glass, grain, glow, and oversized type as tools, not proof of design quality.
- Distinctive: line 33
Keep motion purposeful and respect reduced-motion preferences.
- Distinctive: line 34
Do not fabricate brand assets, customer logos, metrics, or product screenshots.
- Distinctive: line 49
Read references/site-archetypes.md when the product type should materially change the direction.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Web Visual Direction
Turn an ambiguous brief into one coherent visual system. Make choices that fit the product and can survive implementation; do not produce a mood-board-shaped list of adjectives.
Workflow
- Inspect the product brief and existing code, brand assets, screenshots, content, component library, and constraints. Preserve intentional brand equity.
- State the audience, their immediate task, and the feeling the interface should create in one sentence each.
- Choose one visual thesis with a useful tension, such as "editorial authority with operational speed." Explain why it fits.
- Select two or three relevant references. Extract principles - rhythm, contrast, framing, density - not surface decoration or copyrighted layouts.
- Decide the composition before styling details:
- identify the first viewport's focal point;
- define the grid, content width, density, and section rhythm;
- decide what intentionally breaks the grid, if anything.
- Define implementation-ready rules for typography, color, surfaces, borders, imagery, icons, and motion.
- Express the direction as a small token set and component implications. Reuse the project's existing styling system.
- Implement one representative viewport or component when implementation is in scope.
- Verify the direction at mobile and desktop widths. Remove choices that weaken comprehension, hierarchy, performance, or accessibility.
Decision Rules
- Lead with the real product, work, place, person, object, or outcome.
- Prefer a memorable structural idea over decorative effects.
- Match density to the job: operational interfaces are compact; narrative brand pages can breathe.
- Use typography with a reason. Do not ban or choose a font only because it is fashionable.
- Use cards for meaningful grouping, not as the default container for every sentence.
- Treat gradients, glass, grain, glow, and oversized type as tools, not proof of design quality.
- Keep motion purposeful and respect reduced-motion preferences.
- Do not fabricate brand assets, customer logos, metrics, or product screenshots.
Delivery Contract
Return or implement:
- Visual thesis - one sentence.
- Reference principles - what to borrow and what to avoid.
- Direction spec - composition, type, palette, surfaces, imagery, icons, and motion.
- Token sketch - named values or mappings compatible with the codebase.
- Responsive intent - what changes at narrow and wide widths.
- Proof - screenshot or inspected viewport when browser access exists.
Reference
Read references/site-archetypes.md when the product type should materially change the direction.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

