iconography
Skill0 starsChanged 3 days agoMITView on GitHub
Use consistent, recognizable icons with accessible labels, predictable sizing, and verified licensing.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- shashidharbabu/rocketride-design-skillstheir own version, first seen Nov 15, 2026
- toribryan/design-skillstheir own version, first seen Oct 25, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- toribryan/design-skills★ 1same name
- shashidharbabu/rocketride-design-skills★ 0same 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
- 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-designSkill
- visual-regressionSkill
- website-architectureSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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 10
Use when choosing, adding, or standardizing interface icons.
- Distinctive: line 14
Do not use icons to replace clear labels for unfamiliar or high-impact actions.
- Distinctive: line 24
Check whether text, an existing icon, or a native control already communicates the action.
- Distinctive: line 29
Keep decorative icons hidden from assistive technology.
- Distinctive: line 31
Verify license and avoid bundling restricted assets.
- Distinctive: line 37
Do not mix icon families without a clear design reason.
- Distinctive: line 52
Check semantic name, keyboard target, visual consistency, state contrast, license, and whether a text label is needed.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Iconography
When to use
Use when choosing, adding, or standardizing interface icons.
When not to use
Do not use icons to replace clear labels for unfamiliar or high-impact actions. Do not use emoji as production interface controls.
Inputs and assumptions
Inspect the existing icon library, stroke/fill style, sizing grid, intended meaning, accessibility label, and license.
Workflow
- Check whether text, an existing icon, or a native control already communicates the action.
- Choose a recognizable icon from one consistent family.
- Pair ambiguous icons with visible text; give icon-only controls an accessible name and adequate target size.
- Keep decorative icons hidden from assistive technology.
- Align stroke, optical size, baseline, and state color with the system.
- Verify license and avoid bundling restricted assets.
Decision rules
- The accessible name describes the action, not the artwork.
- A disabled or destructive action must not rely on icon color alone.
- Do not mix icon families without a clear design reason.
Example
An icon-only “Delete project” control should expose that exact accessible name and open a confirmation that identifies the project.
Common failures
- Unlabeled icon buttons and ambiguous glyphs.
- Emoji whose appearance varies by platform.
- Inconsistent stroke weights and undocumented copies of icon assets.
Validation
Check semantic name, keyboard target, visual consistency, state contrast, license, and whether a text label is needed.
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.