axiom-sf-symbols-ref▌
charleswiltgen/axiom · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Use when:
SF Symbols — API Reference
When to Use This Skill
Use when:
- You need exact API signatures for rendering modes or symbol effects
- You need UIKit/AppKit equivalents for SwiftUI symbol APIs
- You need to check platform availability for a specific effect
- You need configuration options (weight, scale, variable values)
- You need to create custom symbols with proper template structure
Related Skills
- Use
axiom-sf-symbolsfor decision trees, anti-patterns, troubleshooting, and when to use which effect - Use
axiom-swiftui-animation-reffor general SwiftUI animation (non-symbol)
Part 1: Symbol Display
SwiftUI
// Basic display
Image(systemName: "star.fill")
// With Label (icon + text)
Label("Favorites", systemImage: "star.fill")
// Font sizing — symbol scales with text
Image(systemName: "star.fill")
.font(.title)
// Image scale — relative sizing without changing font
Image(systemName: "star.fill")
.imageScale(.large) // .small, .medium, .large
// Explicit point size
Image(systemName: "star.fill")
.font(.system(size: 24))
// Weight — matches SF Pro font weights
Image(systemName: "star.fill")
.fontWeight(.bold) // .ultraLight through .black
// Symbol variant — programmatic .fill, .circle, .square, .slash
Image(systemName: "person")
.symbolVariant(.circle.fill) // Renders person.circle.fill
// Variable value — 0.0 to 1.0, controls symbol fill level
Image(systemName: "speaker.wave.3.fill", variableValue: 0.5)
UIKit
// Basic display
let image = UIImage(systemName: "star.fill")
imageView.image = image
// Configuration — point size and weight
let config = UIImage.SymbolConfiguration(pointSize: 24, weight: .bold)
let image = UIImage(systemName: "star.fill", withConfiguration: config)
// Configuration — text style (scales with Dynamic Type)
let config = UIImage.SymbolConfiguration(textStyle: .title1)
let image = UIImage(systemName: "star.fill", withConfiguration: config)
// Configuration — scale
let config = UIImage.SymbolConfiguration(scale: .large) // .small, .medium, .large
// Combine configurations
let sizeConfig = UIImage.SymbolConfiguration(pointSize: 24, weight: .bold, scale: .large)
// Variable value
let image = UIImage(systemName: "speaker.wave.3.fill", variableValue: 0.5)
AppKit
// Basic display
let image = NSImage(systemSymbolName: "star.fill", accessibilityDescription: "Favorite")
// Configuration
let config = NSImage.SymbolConfiguration(pointSize: 24, weight: .bold)
let configured = image?.withSymbolConfiguration(config)
Part 2: Rendering Modes
SwiftUI
// Monochrome (default)
Image(systemName: "cloud.rain.fill")
.foregroundStyle(.blue)
// Hierarchical — depth from single color
Image(systemName: "cloud.rain.fill")
.symbolRenderingMode(.hierarchical)
.foregroundStyle(.blue)
// Palette — explicit color per layer
Image(systemName: "cloud.rain.fill")
.symbolRenderingMode(.palette)
.foregroundStyle(.white, .blue)
// For 3-layer symbols:
.foregroundStyle(.red, .white, .blue)
// Multicolor — Apple's curated colors
Image(systemName: "cloud.rain.fill")
.symbolRenderingMode(.multicolor)
// Preferred rendering mode — uses symbol's preferred mode
// Falls back gracefully if the symbol doesn't support it
Image(systemName: "cloud.rain.fill")
.symbolRenderingMode(.monochrome) // explicit monochrome
SymbolRenderingMode Enum
| Value | Description |
|---|---|
.monochrome |
Single color for all layers (default) |
.hierarchical |
Single color with automatic opacity per layer |
.palette |
Explicit color per layer via .foregroundStyle() |
.multicolor |
Apple's fixed curated colors |
UIKit
// Hierarchical
let config = UIImage.SymbolConfiguration(hierarchicalColor: .systemBlue)
imageView.preferredSymbolConfiguration = config
// Palette
let config = UIImage.SymbolConfiguration(paletteColors: [.white, .systemBlue])
imageView.preferredSymbolConfiguration = config
// Multicolor
let config = UIImage.SymbolConfiguration.preferringMulticolor()
imageView.preferredSymbolConfiguration = config
// Monochrome — just set tintColor
imageView.tintColor = .systemBlue
Combining Configurations (UIKit)
let sizeConfig = UIImage.SymbolConfiguration(pointSize: 24, weight: .bold)
let colorConfig = UIImage.SymbolConfiguration(paletteColors: [.white, .blue, .gray])
let combined = sizeConfig.applying(colorConfig)
imageView.preferredSymbolConfiguration = combined
Part 3: Symbol Effects — Complete API
Effect Protocol Hierarchy
All symbol effects conform to SymbolEffect. Sub-protocols define behavior:
| Protocol | Trigger | Modifier | Loop |
|---|---|---|---|
DiscreteSymbolEffect |
value: (Equatable) |
.symbolEffect(_:options:value:) |
No |
IndefiniteSymbolEffect |
isActive: (Bool) |
.symbolEffect(_:options:isActive:) |
Yes |
TransitionSymbolEffect |
View lifecycle | .transition(.symbolEffect(_:)) |
No |
ContentTransitionSymbolEffect |
Symbol change | .contentTransition(.symbolEffect(_:)) |
No |
Remove All Effects (SwiftUI)
// StripHow to use axiom-sf-symbols-ref on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add axiom-sf-symbols-ref
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches axiom-sf-symbols-ref from GitHub repository charleswiltgen/axiom and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate axiom-sf-symbols-ref. Access the skill through slash commands (e.g., /axiom-sf-symbols-ref) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★38 reviews- ★★★★★Noah Garcia· Dec 28, 2024
axiom-sf-symbols-ref fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Shikha Mishra· Dec 8, 2024
We added axiom-sf-symbols-ref from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Ganesh Mohane· Dec 4, 2024
axiom-sf-symbols-ref is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Zara Garcia· Dec 4, 2024
I recommend axiom-sf-symbols-ref for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Sakshi Patil· Nov 23, 2024
Keeps context tight: axiom-sf-symbols-ref is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Daniel Patel· Nov 23, 2024
axiom-sf-symbols-ref fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Hassan Garcia· Nov 19, 2024
I recommend axiom-sf-symbols-ref for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Chaitanya Patil· Oct 14, 2024
axiom-sf-symbols-ref has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Daniel Brown· Oct 14, 2024
Registry listing for axiom-sf-symbols-ref matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Arya Desai· Oct 10, 2024
axiom-sf-symbols-ref reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 38