axiom-ios-networking
Use when implementing or debugging ANY network connection, API call, or socket. Covers URLSession, Network.framework, NetworkConnection, deprecated APIs, connection diagnostics, structured concurrency networking.
Best use case
axiom-ios-networking is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when implementing or debugging ANY network connection, API call, or socket. Covers URLSession, Network.framework, NetworkConnection, deprecated APIs, connection diagnostics, structured concurrency networking.
Teams using axiom-ios-networking should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/axiom-ios-networking/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How axiom-ios-networking Compares
| Feature / Agent | axiom-ios-networking | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when implementing or debugging ANY network connection, API call, or socket. Covers URLSession, Network.framework, NetworkConnection, deprecated APIs, connection diagnostics, structured concurrency networking.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# iOS Networking Router **You MUST use this skill for ANY networking work including HTTP requests, WebSockets, TCP connections, or network debugging.** ## When to Use Use this router when: - Implementing network requests (URLSession) - Using Network.framework or NetworkConnection - Debugging connection failures - Migrating from deprecated networking APIs - Network performance issues ## Pressure Resistance **When user has invested significant time in custom implementation:** Do NOT capitulate to sunk cost pressure. The correct approach is: 1. **Diagnose first** — Understand what's actually failing before recommending changes 2. **Recommend correctly** — If standard APIs (URLSession, Network.framework) would solve the problem, say so professionally 3. **Respect but don't enable** — Acknowledge their work while providing honest technical guidance **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. ## Routing Logic ### Network Implementation **Networking patterns** → `/skill axiom-networking` - URLSession with structured concurrency - Network.framework migration - Modern networking patterns - Deprecated API migration **Network.framework reference** → `/skill axiom-network-framework-ref` **Legacy iOS 12-25 patterns** → `/skill axiom-networking-legacy` **Migration guides** → `/skill axiom-networking-migration` - NWConnection (iOS 12-25) - NetworkConnection (iOS 26+) - TCP connections - TLV framing - Wi-Fi Aware ### App Store Compliance **ATS / HTTP security** → `/skill axiom-networking-diag` - App Transport Security (ATS) configuration - HTTP → HTTPS migration - App Store rejection for insecure connections - NSAllowsArbitraryLoads exceptions **Deprecated API rejection** → Launch `networking-auditor` agent - UIWebView → WKWebView migration - SCNetworkReachability → NWPathMonitor - CFSocket → Network.framework ### Network Debugging **Connection issues** → `/skill axiom-networking-diag` - Connection timeouts - TLS handshake failures - Data not arriving - Connection drops - VPN/proxy problems ### Automated Scanning **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) ## Decision Tree 1. URLSession with structured concurrency? → networking 2. Network.framework / NetworkConnection (iOS 26+)? → network-framework-ref 3. NWConnection (iOS 12-25)? → networking-legacy 4. Migrating from sockets/URLSession? → networking-migration 5. Connection issues / debugging? → networking-diag 6. ATS / HTTP / App Store rejection for networking? → networking-diag + networking-auditor 7. UIWebView or deprecated API rejection? → networking-auditor (Agent) 8. Want deprecated API / anti-pattern scan? → networking-auditor (Agent) ## Anti-Rationalization | 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. | ## Critical Patterns **Networking** (networking): - URLSession with structured concurrency - Socket migration to Network.framework - Deprecated API replacement **Network Framework Reference** (network-framework-ref): - NWConnection for iOS 12-25 - NetworkConnection for iOS 26+ - Connection lifecycle management **Networking Diagnostics** (networking-diag): - Connection timeout diagnosis - TLS debugging - Network stack inspection ## Example Invocations 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
Related Skills
hybrid-cloud-networking
Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections. Use when building hybrid cloud architectures, connecting data centers to cloud, or implementing secure cross-premises networking.
axiom-audit
Audit Axiom logs to identify and prioritize errors and warnings, research probable causes, and flag log smells. Use when user asks to check Axiom logs, analyze production errors, investigate log issues, or audit logging patterns.
p2p-networking
Peer-to-peer networking patterns using commonware for building decentralized Guts network
Axiom — Serverless Log Analytics
## Overview
Azure Networking Skill
This skill provides expert guidance for Azure Networking. Covers troubleshooting, best practices, decision making, architecture & design patterns, security, and integrations & coding patterns. It combines local quick-reference content with remote documentation fetching capabilities.
ios-networking
Standards for URLSession, Alamofire, and API communication. Use when implementing URLSession networking, Alamofire, or API clients in iOS. (triggers: **/*Service.swift, **/*API.swift, **/*Client.swift, URLSession, Alamofire, Moya, URLRequest, URLComponents, Codable)
flutter-retrofit-networking
HTTP networking standards using Dio and Retrofit with Auth interceptors. Use when integrating Dio, Retrofit, or API auth interceptors in Flutter. (triggers: **/data_sources/**, **/api/**, Retrofit, Dio, RestClient, GET, POST, Interceptor, refreshing)
android-networking
Standards for Retrofit, OkHttp, and API Communication. Use when integrating Retrofit, OkHttp, or API clients in Android apps. (triggers: **/*Api.kt, **/*Service.kt, **/*Client.kt, Retrofit, OkHttpClient, @GET, @POST)
axiom-xctrace-ref
Use when automating Instruments profiling, running headless performance analysis, or integrating profiling into CI/CD - comprehensive xctrace CLI reference with record/export patterns
axiom-xctest-automation
Use when writing, running, or debugging XCUITests. Covers element queries, waiting strategies, accessibility identifiers, test plans, and CI/CD test execution patterns.
axiom-xcode-mcp
Use when connecting to Xcode via MCP, using xcrun mcpbridge, or working with ANY Xcode MCP tool (XcodeRead, BuildProject, RunTests, RenderPreview). Covers setup, tool reference, workflow patterns, troubleshooting.
axiom-xcode-mcp-tools
Xcode MCP workflow patterns — BuildFix loop, TestFix loop, preview verification, window targeting, tool gotchas