axiom audit networking

Engineering Community

Skill notes

Tool Use Is Mandatory

Run every Glob, Grep, and Read this prompt lists. Do not reason from training data instead of scanning. Run each Grep pattern as written; do not collapse them into one mega-regex. Run the Read verifications each section calls for. "Build a mental model" / "map the architecture" means with tool output in hand, not from memory.

Files to Exclude

Skip: *Tests.swift, *Previews.swift, */Pods/*, */Carthage/*, */.build/*, */DerivedData/*, */scratch/*, */docs/*, */.claude/*, */.claude-plugin/*

Step 3: Map Connection Lifecycle

Read 2-3 key networking files to understand: How connections are created and stored Whether state handlers are implemented (ready, waiting, failed) Whether connections are cancelled/cleaned up Whether network transitions are handled (viability, better path)

Output

Write a brief Networking Architecture Map (5-10 lines) summarizing: Primary networking approach (URLSession, NWConnection, NetworkConnection, legacy) Protocol types in use (HTTP, TCP/TLS, UDP, WebSocket) Connection lifecycle pattern (state handling, cleanup, transition support) Legacy API presence (any deprecated APIs found)

Phase 2: Detect Known Anti-Patterns

Run all 10 existing detection patterns. For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@CharlesWiltgen · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Map Networking Architecture

Phase 1: Map Networking Architecture

02
Step 1: Identify Networking Frameworks

Step 1: Identify Networking Frameworks

03
Step 2: Identify Protocol Types

Step 2: Identify Protocol Types

04
Step 3: Map Connection Lifecycle

Read 2-3 key networking files to understand: How connections are created and stored Whether state handlers are implemented (ready, waiting, failed) Whether connections are cancelled/cleaned up Whether network transitions are handled (viability, better path)

05
Phase 2: Detect Known Anti-Patterns

Run all 10 existing detection patterns. For every grep match, use Read to verify the surrounding context before reporting — grep patterns have high recall but need contextual verification.

06
Phase 3: Reason About Networking Completeness

Using the Networking Architecture Map from Phase 1 and your domain knowledge, check for what's *missing* — not just what's wrong. Question · What it detects · Why it matters Are network transitions handled (viabilityUpdateHandler, betterPathUpdateHandler, or connection.states)? · Missing transition support · 40% of connection failures happen during WiFi-to-cellular transitions — users walking between rooms or buildings

07
Phase 4: Cross-Reference Findings

Bump severity for these combinations: Finding A · + Finding B · = Compound · Severity SCNetworkReachability · Reachability before connect · Double legacy: deprecated API used for deprecated pattern · CRITICAL Blocking socket calls · On main thread (no dispatch) · Guaranteed ANR crash + App Store rejection · CRITICAL Missing [weak self] · Multiple completion handlers on same connection · Compound retain cycles, connection never deallocates · HIGH

08
Phase 5: Networking Health Score

Scoring: MODERN: 0 deprecated APIs, 0 CRITICAL anti-patterns, >80% transition coverage, 100% TLS for sensitive data NEEDS MIGRATION: <=2 deprecated APIs with migration comments, no CRITICAL anti-patterns, some transition gaps LEGACY: >2 deprecated APIs, OR any CRITICAL anti-patterns, OR blocking sockets, OR missing TLS for sensitive data

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.