agentleFS
arto-apparto-app/Arto/.claude/skills/add-icon/SKILL.md

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

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. gitkraken/vscode-gitlens★ 10ksame name
    2. 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.

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
  1. Distinctive:

    Add the icon name to the JSON array (in alphabetical order)

    line 22
  2. Very specific:

    Add variant to IconName enum (use PascalCase)

    line 30
  3. Very specific:

    Add case to Display implementation

    line 31

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Choose Icon
  2. Add to icons.json
    • Edit frontend/icons.json
    • Add the icon name to the JSON array (in alphabetical order)
  3. Build Icon Sprite (Automatic)
    • Icon sprite is automatically generated when Vite builds
    • Just run just dev or cargo build
  4. Add Rust Enum Variant
    • Edit crates/arto/src/components/icon.rs
    • Add variant to IconName enum (use PascalCase)
    • Add case to Display implementation

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

FilePurposeGit Tracked
frontend/icons.jsonIcon list configuration✅ Yes
frontend/vite.config.tsIcon sprite plugin✅ Yes
frontend/public/icons/tabler-sprite.svgGenerated sprite (Vite source)❌ No
assets/frontend/icons/tabler-sprite.svgBuild 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 (buildStart hook)
  • Rust code references icons via asset!("/assets/frontend/icons/tabler-sprite.svg")
  • Icons come from @tabler/icons npm 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!() macro

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.