Welcome! This skill helps new users discover the most relevant Axiom skills for their situation.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionaxiom-getting-startedExecute the skills CLI command in your project's root directory to begin installation:
Fetches axiom-getting-started 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-getting-started. Access via /axiom-getting-started 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
Welcome! This skill helps new users discover the most relevant Axiom skills for their situation.
Use the AskUserQuestion tool to gather context:
Question: "What brings you to Axiom today?"
Header: "Focus"
Options:
- "Debugging an issue" → Prioritize diagnostic skills
- "Optimizing performance" → Prioritize profiling skills
- "Adding new features" → Prioritize reference skills
- "Code review / quality check" → Prioritize audit commands
- "Just exploring" → Show overview
Question: "What's your primary tech stack?"
Header: "Stack"
Options:
- "SwiftUI (iOS 16+)" → SwiftUI-focused skills
- "UIKit" → UIKit-focused skills
- "Mixed SwiftUI + UIKit" → Both
- "Starting new project" → Best practices skills
Only ask if "Debugging an issue" was selected:
Question: "Which areas are you struggling with?"
Header: "Pain Points"
Multi-select: true
Options:
- "Xcode/build issues"
- "Memory leaks"
- "UI/animation problems"
- "Database/persistence"
- "Networking"
- "Concurrency/async"
- "Accessibility"
Based on answers, recommend 3-5 skills using this matrix:
Always recommend: axiom:xcode-debugging (universal starting point)
Then add based on pain points:
SwiftUI stack:
UIKit/Mixed:
Design decisions:
iOS 26+ features:
Navigation patterns:
Integrations:
Data persistence:
Start with audit commands (quick wins):
/axiom:audit-accessibility — WCAG compliance/axiom:audit-concurrency — Swift 6 violations/axiom:audit-memory — Leak patterns/axiom:audit-core-data — Migration safety/axiom:audit-networking — Deprecated APIsThen suggest:
Show the complete skill index (see below) and explain categories.
After gathering answers, output:
## Your Recommended Skills
Based on your answers, here are the skills most relevant to you right now:
### [Icon] [Category Name]
**axiom:[skill-name]** — [One-line description]
> Try: "[Example prompt they can use immediately]"
[Repeat for 3-5 skills]
### Quick Wins
Run these audit commands to find issues automatically:
- `/axiom:audit-[name]` — [What it finds]
## What's Next
1. **Try the example prompts above** — Copy/paste to see how skills work
2. **Run an audit command** — Get immediate actionable insights
3. **Describe your problem** — I'll suggest the right skill
4. **Browse the complete index below** — Explore all 34 skills
---
[Include the Complete Skill Reference below]
Include this reference section in every response for browsing:
Environment & Build Issues
Memory & Performance
UI Debugging
Liquid Glass (Material Design)
Layout & Navigation
Frameworks
Migration Guides
/axiom:audit-accessibility — VoiceOver labels, Dynamic Type, contrast, touch targets/axiom:audit-concurrency — Swift 6 violations, unsafe tasks, missing @MainActor/axiom:audit-memory — Timer leaks, observer leaks, closure captures, delegate cycles/axiom:audit-core-data — Migration risks, thread violations, N+1 queries/axiom:audit-networking — Deprecated APIs (SCNetworkReachability, CFSocket), anti-patterns/axiom:audit-liquid-glass — Glass adoption opportunities, toolbar improvements, blur migration"My build is failing" → Start: axiom:xcode-debugging → If dependency issue: axiom:build-debugging
"App is slow" → Start: axiom:performance-profiling (decision trees) → If SwiftUI: axiom:swiftui-performance → If memory grows: axiom:memory-debugging
"Memory leak" → Start: axiom:memory-debugging → If Objective-C blocks: axiom:objc-block-retain-cycles
"SwiftUI view issues" → Start: axiom:swiftui-debugging → If performance: axiom:swiftui-performance
"Navigation problems" → Start: axiom:swiftui-nav-diag (troubleshooting) → For patterns: axiom:swiftui-nav
"Which database?" → Decision guide: axiom:sqlitedata-migration → Then: axiom:swiftdata, axiom:sqlitedata, or axiom:grdb
"iOS 26 design" → Start: axiom:liquid-glass → Complete guide: axiom:liquid-glass-ref
"Code quality check"
→ Run: /axiom:audit-accessibility, /axiom:audit-concurrency, /axiom:audit-memory
→ Fix issues with relevant skills
Axiom skills load automatically — you don't need to memorize names or commands.
Automatic triggering (most common): Just describe your problem naturally. Claude detects which skill applies and loads it.
cloud-sync-diagswift-concurrencyExplicit invocation: If you know the skill name, invoke it directly:
/skill axiom-swift-concurrency/skill axiom-liquid-glassAudit commands: Run automated scans with slash commands:
/axiom:audit-memory — scans for memory leak patterns/axiom:audit-concurrency — scans for Swift 6 violationsKey insight: You don't need to know skill names. Describe what you're working on and Axiom routes to the right skill automatically.
Total: 50 skills, 12 audit commands, covering the complete iOS development lifecycle from design to deployment
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
axiom-getting-started is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in axiom-getting-started — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
axiom-getting-started is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: axiom-getting-started is the kind of skill you can hand to a new teammate without a long onboarding doc.
axiom-getting-started fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
axiom-getting-started fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added axiom-getting-started from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: axiom-getting-started is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend axiom-getting-started for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend axiom-getting-started for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 50