This skill provides comprehensive API reference for Apple's widget and extension ecosystem:
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionaxiom-extensions-widgets-refExecute the skills CLI command in your project's root directory to begin installation:
Fetches axiom-extensions-widgets-ref from charleswiltgen/axiom and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate axiom-extensions-widgets-ref. Access via /axiom-extensions-widgets-ref in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
767
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
767
stars
This skill provides comprehensive API reference for Apple's widget and extension ecosystem:
Widgets are SwiftUI archived snapshots rendered on a timeline by the system. Extensions are sandboxed executables bundled with your app.
✅ Use this skill when:
❌ Do NOT use this skill for:
For widgets that don't require user configuration.
@main
struct MyWidget: Widget {
let kind: String = "MyWidget"
var body: some WidgetConfiguration {
StaticConfiguration(kind: kind, provider: Provider()) { entry in
MyWidgetEntryView(entry: entry)
}
.configurationDisplayName("My Widget")
.description("This widget displays...")
.supportedFamilies([.systemSmall, .systemMedium, .systemLarge])
}
}
For widgets with user configuration using App Intents.
struct MyConfigurableWidget: Widget {
let kind: String = "MyConfigurableWidget"
var body: some WidgetConfiguration {
AppIntentConfiguration(
kind: kind,
intent: SelectProjectIntent.self,
provider: Provider()
) { entry in
MyWidgetEntryView(entry: entry)
}
.configurationDisplayName("Project Status")
.description("Shows your selected project")
}
}
Migration from IntentConfiguration: iOS 16 and earlier used IntentConfiguration with SiriKit intents. Migrate to AppIntentConfiguration for iOS 17+.
For Live Activities (covered in Live Activities section).
No user configuration needed? Use StaticConfiguration. Simple static options? Use AppIntentConfiguration with WidgetConfigurationIntent. Dynamic options from app data? Use AppIntentConfiguration + EntityQuery.
Quick Reference:
systemSmall (~170×170, iOS 14+) — Single piece of info, iconsystemMedium (~360×170, iOS 14+) — Multiple data points, chartsystemLarge (~360×380, iOS 14+) — Detailed view, listsystemExtraLarge (~720×380, iOS 15+ iPad only) — Rich layouts, multiple viewsaccessoryCircular (~48×48pt) — Circular complication, icon or gaugeaccessoryRectangular (~160×72pt) — Above clock, text + iconaccessoryInline (single line) — Above date, text onlystruct MyWidget: Widget {
var body: some WidgetConfiguration {
StaticConfiguration(kind: "MyWidget", provider: Provider()) { entry in
if #available(iOSApplicationExtension 16.0, *) {
switch entry.family {
case .systemSmall:
SmallWidgetView(entry: entry)
case .systemMedium:
MediumWidgetView(entry: entry)
case .accessoryCircular:
CircularWidgetView(entry: entry)
case .accessoryRectangular:
RectangularWidgetView(entry: entry)
default:
Text("Unsupported")
}
} else {
LegacyWidgetView(entry: entry)
}
}
.supportedFamilies([
.systemSmall,
.systemMedium,
.accessoryCircular,
.accessoryRectangular
])
}
}
Provides entries that define when the system should render your widget.
struct Provider: TimelineProvider {
// Placeholder while loading
func placeholder(in context: Context) -> SimpleEntry {
SimpleEntry(date: Date(), emoji: "😀")
}
// Shown in widget gallery
func getSnapshot(in context: Context, completion: @escaping (SimpleEntry) -> ()) {
let entry = SimpleEntry(date: Date(), emoji: "📷")
completion(entry)
}
// Actual timeline
func getTimeline(in context: Context, completion: @escaping (Timeline<Entry>) -> ()) {
var entries: [SimpleEntry] = []
let currentDate = Date()
// Create entry every hour for 5 hours
for hourOffset in 0 ..< 5 {
let entryDate = Calendar.current.date(byAdding: .hour, value: hourOffset, to: currentDate)!
let entry = ✓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
Steps
- 1Install product management skill
- 2Start with user story generation for known feature
- 3Progress to competitive analysis: research 2-3 competitors
- 4Use for roadmap prioritization: apply RICE/ICE scoring
- 5Draft stakeholder communications and refine based on feedback
- 6Build template library for recurring PM tasks
- 7Share 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
Related Skills
grill-me
649mattpocock/skills
Productivitysame categorypremortem
214parcadei/continuous-claude-v3
Productivitysame categorydeslop
159cursor/plugins
Productivitysame categorytravel-planner
136ailabs-393/ai-labs-claude-skills
Productivitysame categoryframer-motion
131pproenca/dot-skills
Productivitysame categorywrite-a-prd
128mattpocock/skills
Productivitysame categoryReviews
4.7★★★★★37 reviews- HHenry Martinez★★★★★Dec 16, 2024
axiom-extensions-widgets-ref is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- CChaitanya Patil★★★★★Dec 12, 2024
axiom-extensions-widgets-ref has been reliable in day-to-day use. Documentation quality is above average for community skills.
- CCamila Dixit★★★★★Nov 15, 2024
axiom-extensions-widgets-ref has been reliable in day-to-day use. Documentation quality is above average for community skills.
- CCamila Johnson★★★★★Nov 7, 2024
Solid pick for teams standardizing on skills: axiom-extensions-widgets-ref is focused, and the summary matches what you get after install.
- CCharlotte Singh★★★★★Oct 26, 2024
We added axiom-extensions-widgets-ref from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- KKiara Torres★★★★★Oct 6, 2024
Useful defaults in axiom-extensions-widgets-ref — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- HHana Malhotra★★★★★Sep 21, 2024
axiom-extensions-widgets-ref is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- PPiyush G★★★★★Sep 5, 2024
Solid pick for teams standardizing on skills: axiom-extensions-widgets-ref is focused, and the summary matches what you get after install.
- RRen Harris★★★★★Sep 1, 2024
We added axiom-extensions-widgets-ref from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- SShikha Mishra★★★★★Aug 24, 2024
We added axiom-extensions-widgets-ref from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 37
1 / 4Discussion
Comments — not star reviews- No comments yet — start the thread.