add-icon
Skill261 starsChanged 3 days agoMITView on GitHub
Add a new Tabler icon to the project. Use when adding icons to the UI.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- wei/socialifytheir own version, first seen Oct 8, 2026
- gitkraken/vscode-gitlenstheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- gitkraken/vscode-gitlens★ 10ksame name
- wei/socialify★ 2.2ksame 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 repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Add the icon name to the JSON array (in alphabetical order)
- Very specific: line 30
Add variant to IconName enum (use PascalCase)
- Very specific: line 31
Add case to Display implementation
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Add Icon Skill
This skill guides you through adding a new icon from Tabler Icons to the project.
Process
Icons are managed via icons.json and automatically built by Vite plugin.
Steps
- Choose Icon
- Browse available icons: https://tabler.io/icons
- Note the icon name (e.g.,
folder-open,info-circle)
- Add to icons.json
- Edit
frontend/icons.json - Add the icon name to the JSON array (in alphabetical order)
- Edit
- Build Icon Sprite (Automatic)
- Icon sprite is automatically generated when Vite builds
- Just run
just devorcargo build
- Add Rust Enum Variant
- Edit
crates/arto/src/components/icon.rs - Add variant to
IconNameenum (use PascalCase) - Add case to
Displayimplementation
- Edit
Example
frontend/icons.json:
[
"folder",
"folder-open",
"file"
]crates/arto/src/components/icon.rs:
pub enum IconName {
Folder,
FolderOpen,
File,
}
impl std::fmt::Display for IconName {
fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result {
match self {
IconName::Folder => write!(f, "folder"),
IconName::FolderOpen => write!(f, "folder-open"),
IconName::File => write!(f, "file"),
}
}
}File Locations
| File | Purpose | Git Tracked |
frontend/icons.json | Icon list configuration | ✅ Yes |
frontend/vite.config.ts | Icon sprite plugin | ✅ Yes |
frontend/public/icons/tabler-sprite.svg | Generated sprite (Vite source) | ❌ No |
assets/frontend/icons/tabler-sprite.svg | Build output (Dioxus asset) | ❌ No |
Important
- NEVER edit generated SVG files directly
- The
assets/frontend/directory is.gitignored as build output - Icon sprite generation is automatic via Vite plugin (
buildStarthook) - Rust code references icons via
asset!("/assets/frontend/icons/tabler-sprite.svg") - Icons come from
@tabler/iconsnpm package (outline style only)
Build Process
icons.json
↓
Vite plugin (buildStart hook)
↓
frontend/public/icons/tabler-sprite.svg
↓
Vite build
↓
assets/frontend/icons/tabler-sprite.svg
↓
Rust asset!() macroDoes 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.

