You MUST use this skill for ANY networking work including HTTP requests, WebSockets, TCP connections, or network debugging.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionaxiom-ios-networkingExecute the skills CLI command in your project's root directory to begin installation:
Fetches axiom-ios-networking 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-ios-networking. Access via /axiom-ios-networking 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
You MUST use this skill for ANY networking work including HTTP requests, WebSockets, TCP connections, or network debugging.
Use this router when:
When user has invested significant time in custom implementation:
Do NOT capitulate to sunk cost pressure. The correct approach is:
Example pressure scenario:
"I spent 2 days on custom networking. Just help me fix it, don't tell me to use URLSession."
Correct response:
"Let me diagnose the cellular failure first. [After diagnosis] The issue is [X]. URLSession handles this automatically via [Y]. I recommend migrating the affected code path — it's 30 minutes vs continued debugging. Your existing work on [Z] can be preserved."
Why this matters: Users often can't see that migration is faster than continued debugging. Honest guidance serves them better than false comfort.
Networking patterns → /skill axiom-networking
Network.framework reference → /skill axiom-network-framework-ref
Legacy iOS 12-25 patterns → /skill axiom-networking-legacy
Migration guides → /skill axiom-networking-migration
ATS / HTTP security → /skill axiom-networking-diag
Deprecated API rejection → Launch networking-auditor agent
Connection issues → /skill axiom-networking-diag
Networking audit → Launch networking-auditor agent or /axiom:audit networking (deprecated APIs like SCNetworkReachability, CFSocket, NSStream; anti-patterns like reachability checks, hardcoded IPs, missing error handling)
| Thought | Reality |
|---|---|
| "URLSession is simple, I don't need a skill" | URLSession with structured concurrency has async/cancellation patterns. networking skill covers them. |
| "I'll debug the connection timeout myself" | Connection failures have 8 causes (DNS, TLS, proxy, cellular). networking-diag diagnoses systematically. |
| "I just need a basic HTTP request" | Even basic requests need error handling, retry, and cancellation patterns. networking has them. |
| "My custom networking layer works fine" | Custom layers miss cellular/proxy edge cases. Standard APIs handle them automatically. |
Networking (networking):
Network Framework Reference (network-framework-ref):
Networking Diagnostics (networking-diag):
User: "My API request is failing with a timeout"
→ Invoke: /skill axiom-networking-diag
User: "How do I use URLSession with async/await?"
→ Invoke: /skill axiom-networking
User: "I need to implement a TCP connection"
→ Invoke: /skill axiom-network-framework-ref
User: "Should I use NWConnection or NetworkConnection?"
→ Invoke: /skill axiom-network-framework-ref
User: "My app was rejected for using HTTP connections"
→ Invoke: /skill axiom-networking-diag (ATS compliance)
User: "App Store says I'm using UIWebView"
→ Invoke: networking-auditor agent (deprecated API scan)
User: "Check my networking code for deprecated APIs"
→ Invoke: networking-auditor agent
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-ios-networking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added axiom-ios-networking from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in axiom-ios-networking — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in axiom-ios-networking — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
axiom-ios-networking reduced setup friction for our internal harness; good balance of opinion and flexibility.
axiom-ios-networking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
axiom-ios-networking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: axiom-ios-networking is focused, and the summary matches what you get after install.
Useful defaults in axiom-ios-networking — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for axiom-ios-networking matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 44