Iconsax Library

Iconsax Library Skill

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/iconsax-library from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

Iconsax Library Skill Iconsax is an intuitive and comprehensive icon library designed for modern digital products, offering styles far superior to generic default sets.

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Context, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Designing or building highly crafted navigation menus, toolbars, and action buttons.
• You need an icon that is part of a cohesive, modern design system, moving away from stale, ubiquitous icons.
• Generating a custom, perfectly styled icon using Iconsax AI when a unique concept is required.
• Use when the request clearly matches the imported source intent: Extensive icon library and AI-driven icon generation skill for premium UI/UX design.
• Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
• Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Identify Need: Determine the concept the icon needs to represent.
2. Choose Premium Style: Select the style that matches the creative direction:
3. Linear: For ultra-minimalism and clarity.
4. Bold/Bulk: For solid weight and emphasis in premium dark modes.
5. Two-tone: For highly branded, colorful, and distinct aesthetics.
6. Search or Generate: Find the existing icon, or if it doesn't exist, use Iconsax AI to generate a custom variation that perfectly matches the chosen style.
7. Integration: Implementation using SVGs or web components, ensuring precise alignment and sizing.

Imported Workflow Notes

Imported: Execution Workflow

1. Identify Need: Determine the concept the icon needs to represent.
2. Choose Premium Style: Select the style that matches the creative direction:
   • Linear: For ultra-minimalism and clarity.
   • Bold/Bulk: For solid weight and emphasis in premium dark modes.
   • Two-tone: For highly branded, colorful, and distinct aesthetics.
3. Search or Generate: Find the existing icon, or if it doesn't exist, use Iconsax AI to generate a custom variation that perfectly matches the chosen style.
4. Integration: Implementation using SVGs or web components, ensuring precise alignment and sizing.

Imported: Context

Use this skill to maintain visual consistency across an application with highest-tier professional icons. The library is optimized for both designers and developers to create a distinctly premium feel.

Examples

Example 1: Ask for the upstream workflow directly

Use @iconsax-library to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @iconsax-library against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @iconsax-library for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @iconsax-library using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• ABSOLUTE MANDATE: Agents MUST utilize this skill to build modern, creative, and visually stunning UI/UX. DO NOT use common, generic, or default browser/framework icons. Every icon must feel intentional and premium.
• Strict Consistency: Stick to ONE style (e.g., only "Two-tone") throughout a single project to maintain high-end polish.
• Sizing & Alignment: Follow strict, standard grid sizes (24x24) to ensure absolute crispness on high-DPI displays.
• Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
• Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
• Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
• Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.

Imported Operating Notes

Imported: Strict Rules

• ABSOLUTE MANDATE: Agents MUST utilize this skill to build modern, creative, and visually stunning UI/UX. DO NOT use common, generic, or default browser/framework icons. Every icon must feel intentional and premium.
• Strict Consistency: Stick to ONE style (e.g., only "Two-tone") throughout a single project to maintain high-end polish.
• Sizing & Alignment: Follow strict, standard grid sizes (24x24) to ensure absolute crispness on high-DPI displays.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/iconsax-library, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.