Axiom Networking
Ship reliable HTTP, WebSocket, and Network.framework connections in Swift/iOS apps and debug timeouts, TLS, and App Store ATS issues.
Overview
Axiom Networking is an agent skill most often used in Build (also Ship, Operate) that enforces disciplined URLSession, Network.framework, and socket implementation plus targeted diagnostics for Apple networking work.
Install
npx skills add https://github.com/charleswiltgen/axiom --skill axiom-networkingWhat is this skill?
- Mandatory discipline for URLSession, Network.framework, NWConnection, and WebSocket work on Apple platforms
- Structured concurrency patterns and anti-pattern guardrails via networking-discipline reference docs
- iOS 26+ NetworkConnection API plus legacy NWConnection (iOS 12–18) reference paths
- Diagnostics for timeouts, TLS failures, dropped connections, and production network crises
- ATS, HTTP, and App Store rejection guidance tied to networking-diag workflows
- Covers NetworkConnection (iOS 26+) and NWConnection legacy (iOS 12–18) reference tracks
- Quick-reference table maps symptoms to discipline, framework-ref, diag, and legacy docs
Adoption & trust: 514 installs on skills.sh; 956 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You are implementing or debugging iOS network code and keep hitting deprecated APIs, flaky connections, TLS errors, or App Store ATS rejections without a consistent playbook.
Who is it for?
Solo builders shipping Swift/iOS or macOS apps who want agent-enforced networking rules across HTTP, WebSockets, and Network.framework.
Skip if: Teams building only server-side Node or Python APIs with no Apple client, or projects that need a one-off curl command without ongoing iOS networking discipline.
When should I use this skill?
Implementing or debugging ANY network connection, API call, or socket including URLSession, Network.framework, and connection diagnostics.
What do I get? / Deliverables
Your agent follows Axiom’s networking references to implement connections correctly, migrate off deprecated APIs, and diagnose drops and TLS failures with a repeatable crisis path.
- Corrected networking implementation aligned with Axiom discipline docs
- Diagnostic steps and fixes for timeouts, TLS, and connection stability
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Networking implementation is core product work during Build, so integrations is the canonical shelf for URLSession and Network.framework work. The skill centers on wiring and fixing client-side API and socket integrations—not app UI or release automation alone.
Where it fits
Wire a new REST client with URLSession structured concurrency without reintroducing deprecated completion-handler patterns.
Resolve ATS or cleartext HTTP issues before App Store submission using networking-diag guidance.
Triage production connection timeouts and TLS handshake failures with the crisis diagnosis reference path.
How it compares
Use instead of ad-hoc Stack Overflow snippets when you need opinionated Apple networking discipline and diagnostics, not a generic HTTP client cheat sheet.
Common Questions / FAQ
Who is axiom-networking for?
Indie and solo developers building or maintaining Apple-platform apps who rely on agents to write or debug URLSession, Network.framework, and socket code.
When should I use axiom-networking?
During Build integrations for new API clients; during Ship when fixing ATS or HTTP policies; during Operate when diagnosing production timeouts, TLS failures, or connection drops.
Is axiom-networking safe to install?
Review the Security Audits panel on this Prism page and the MIT-licensed skill sources before enabling it in your agent workflow.
SKILL.md
READMESKILL.md - Axiom Networking
# Networking **You MUST use this skill for ANY networking work including HTTP requests, WebSockets, TCP connections, or network debugging.** ## Quick Reference | Symptom / Task | Reference | |----------------|-----------| | URLSession with structured concurrency | See `skills/networking-discipline.md` | | Network.framework anti-patterns | See `skills/networking-discipline.md` | | Deprecated API migration | See `skills/networking-discipline.md` | | Pressure scenarios (reachability, sockets) | See `skills/networking-discipline.md` | | NetworkConnection (iOS 26+) API reference | See `skills/network-framework-ref.md` | | NWConnection (iOS 12-18) API reference | See `skills/network-framework-ref.md` | | TLV framing, Coder protocol | See `skills/network-framework-ref.md` | | NetworkListener, NetworkBrowser, Wi-Fi Aware | See `skills/network-framework-ref.md` | | Connection timeouts, TLS failures | See `skills/networking-diag.md` | | Data not arriving, connection drops | See `skills/networking-diag.md` | | ATS / HTTP / App Store rejection | See `skills/networking-diag.md` | | Production crisis diagnosis | See `skills/networking-diag.md` | | NWConnection patterns (iOS 12-18) | See `skills/networking-legacy.md` | | UDP batch, NWListener, NWBrowser | See `skills/networking-legacy.md` | | BSD sockets → NWConnection migration | See `skills/networking-migration.md` | | NWConnection → NetworkConnection migration | See `skills/networking-migration.md` | | URLSession StreamTask → NetworkConnection | See `skills/networking-migration.md` | ## Decision Tree ```dot digraph networking { start [label="Networking task" shape=ellipse]; what [label="What do you need?" shape=diamond]; start -> what; what -> "skills/networking-discipline.md" [label="implement patterns,\nanti-patterns,\npressure scenarios"]; what -> "skills/network-framework-ref.md" [label="API reference\n(iOS 26+ or 12-18)"]; what -> "skills/networking-diag.md" [label="debug connection\nfailures"]; what -> "skills/networking-legacy.md" [label="iOS 12-18\nNWConnection patterns"]; what -> "skills/networking-migration.md" [label="migrate from\nsockets/URLSession"]; } ``` 1. URLSession with structured concurrency? → `skills/networking-discipline.md` 2. Network.framework / NetworkConnection (iOS 26+)? → `skills/network-framework-ref.md` 3. NWConnection (iOS 12-18)? → `skills/networking-legacy.md` 4. Migrating from sockets/URLSession? → `skills/networking-migration.md` 5. Connection issues / debugging? → `skills/networking-diag.md` 6. ATS / HTTP / App Store rejection for networking? → `skills/networking-diag.md` + networking-auditor 7. Certificate pinning, signing API requests, encrypting payloads? → `/skill axiom-security` 8. UIWebView or deprecated API rejection? → networking-auditor (Agent) 9. Want deprecated API / anti-pattern scan? → networking-auditor (Agent) #### Platform-specific networking - watchOS low-level-networking limits (TN3135) → See axiom-watchos (skills/background-and-networking.md) ## 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 ## Critical Patterns **Networking** (`skills/networking-discipline.md`): - URLSession with structured concurrency - 8 red-flag anti-patterns (SCNetworkReachability, blocking sockets, hardcoded IPs) - Decision tree for choosing TCP/UDP/TLS patterns - NetworkConnection pattern