sfsymbol-generatorGenerate an Xcode SF Symbol asset catalog .symbolset from an SVG. Use when you need to add a custom SF Symbol (build-time) by creating the symbolset folder, Contents.json, and SVG file.
Install via ClawdBot CLI:
clawdbot install svkozak/sfsymbol-generatorGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Potentially destructive shell commands in tool definitions
exec(Audited Apr 17, 2026 · audit v1.0
Generated Mar 20, 2026
Mobile app developers need to incorporate custom brand icons that match the SF Symbols aesthetic for consistency. This skill automates the creation of .symbolset assets from brand SVGs, ensuring proper scaling and alignment within the iOS interface. It is used during build-time to add logos or unique icons without manual asset preparation.
Design teams creating SwiftUI prototypes require additional icons beyond the standard SF Symbols library. This tool allows designers to quickly convert custom SVG designs into usable symbols, maintaining design system integrity. It supports rapid iteration by generating assets directly into Xcode projects.
Large organizations developing internal iOS apps need tailored icons for specific workflows or branding. This skill facilitates the generation of custom symbols from existing SVG assets, ensuring compliance with SF Symbols guidelines. It streamlines asset management for teams maintaining multiple app variants.
Educators and students learning iOS development can use this skill to practice integrating custom icons into SwiftUI projects. It simplifies the process of converting simple SVG drawings into functional symbols, reducing the learning curve for asset catalog management. This supports hands-on projects in coding bootcamps or university courses.
Offer a basic version for free to attract individual developers, with premium features like batch processing, advanced template customization, or cloud storage for SVG assets. Revenue is generated through subscription plans for teams or enterprises needing enhanced functionality and support.
Partner with design tools like Figma or Sketch to provide a seamless export plugin that directly generates .symbolset files from designs. Revenue comes from licensing fees per user or platform integration deals, targeting professional designers and agencies.
Provide tailored solutions for large clients needing complex icon sets or integration into existing CI/CD pipelines. Revenue is generated through project-based fees or retainer contracts, focusing on enterprises with specific branding or compliance requirements.
💬 Integration Tip
Ensure SVG files have a viewBox and use path-based shapes for compatibility. Set the SFSYMBOL_ASSETS_DIR environment variable to customize asset catalog locations in Xcode projects.
Scored Apr 19, 2026
Best practices and example-driven guidance for building SwiftUI views and components. Use when creating or refactoring SwiftUI UI, designing tab architecture with TabView, composing screens, or needing component-specific patterns and examples.
Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.
Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.
Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.
Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.
Build performant cross-platform apps with Flutter widgets, state management, and platform integration.