visual-design
Skill0 starsChanged 3 days agoMITView on GitHub
Establish visual hierarchy, typography, color, composition, and imagery that support a product's purpose and brand.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- mthines/agent-skillstheir own version, first seen Oct 30, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
- 95gabor/agentic-workflowtheir own version, first seen Jul 24, 2026
- hardiktiwari/better_slidotheir own version, first seen May 26, 2026
- jtaolv-hash/my-claude-skillstheir own version, first seen Apr 28, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- nimadorostkar/Claude-Skills-collection★ 33same name
- mthines/agent-skills★ 20same name
- 95gabor/agentic-workflow★ 1same name
- hardiktiwari/better_slido★ 1same name
- jtaolv-hash/my-claude-skills★ 1same name
- KMaruthi2002/universal-llm-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- accessibilitySkill
- admin-panelSkill
- ai-agent-interfaceSkill
- ai-chat-interfaceSkill
- ai-dashboardSkill
- ai-engineeringSkill
- analytics-and-data-visualizationSkill
- animation-and-motionSkill
- api-engineeringSkill
- authentication-and-rbacSkill
- backend-architectureSkill
- component-engineeringSkill
- dashboard-designSkill
- database-engineeringSkill
- design-intelligenceSkill
- design-systemsSkill
- frontend-engineeringSkill
- iconographySkill
- image-art-directionSkill
- integrations-and-webhooksSkill
- javascript-typescriptSkill
- performance-optimizationSkill
- premium-landing-pagesSkill
- python-engineeringSkill
- rag-and-knowledge-systemsSkill
- responsive-designSkill
- saas-dashboardSkill
- security-engineeringSkill
- super-admin-panelSkill
- testing-and-qualitySkill
- unslop-engineSkill
- ux-researchSkill
- visual-regressionSkill
- website-architectureSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
5
Distinctive
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 10
Use when shaping the visual direction of a screen, resolving hierarchy problems, or reviewing typography, color, spacing, imagery, and …
- Distinctive: line 15
Do not treat personal taste as objective evidence or add visual effects to compensate for unclear content and product positioning.
- Distinctive: line 28
Use a spacing and alignment rhythm appropriate to the content density.
- Distinctive: line 31
Use surfaces, borders, shadows, and effects sparingly to separate meaningful layers.
- Distinctive: line 38
Use a limited, intentional type system.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Visual Design
When to use
Use when shaping the visual direction of a screen, resolving hierarchy problems, or reviewing typography, color, spacing, imagery, and surfaces.
When not to use
Do not treat personal taste as objective evidence or add visual effects to compensate for unclear content and product positioning.
Inputs and assumptions
Inspect the audience, purpose, content, brand, current tokens, viewport, platform, and any existing visual conventions.
Workflow
- Identify the primary message and action, then order supporting content.
- Set type roles and readable line lengths before styling individual elements.
- Use a spacing and alignment rhythm appropriate to the content density.
- Choose colors by semantic role and verify contrast in rendered states.
- Select imagery and iconography that clarify the story or task.
- Use surfaces, borders, shadows, and effects sparingly to separate meaningful layers.
- Review hierarchy at realistic sizes and in high/low content cases.
Decision rules
- One clear visual entry point is more useful than competing accents.
- Use a limited, intentional type system; avoid novelty at the expense of readability.
- Whitespace should group, separate, or focus content.
- Decorative graphics must not obscure content or imply unsupported facts.
Example
For an editorial article, prioritize a readable text measure, clear title and metadata hierarchy, and consistent image captions; a dense dashboard layout is not a suitable default.
Common failures
- Changing fonts and colors without improving hierarchy.
- Low-contrast muted text and tiny interactive targets.
- Random spacing and inconsistent icon weight.
Validation
Review hierarchy, legibility, contrast, content alignment, visual consistency, and behavior at target viewport widths.
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.

