axiom audit spritekit

Security 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 5: Read Key Files

Read 1-2 representative scene files and any custom SKNode/SKSpriteNode subclasses to understand: Node hierarchy (camera/world/hud separation, layer organization) PhysicsCategory definitions (named constants vs magic numbers) Spawn/despawn discipline (where nodes are added in update() and where they're removed) Action closure capture ([weak self] or strong self?)

Output

Write a brief SpriteKit Map (5-10 lines) summarizing: Number of SKScene subclasses and their purpose Custom SKNode/SKSpriteNode subclasses with touch handling PhysicsCategory definitions present (named constants / magic numbers / default 0xFFFFFFFF) Node hierarchy pattern (camera + world + hud / flat / unclear)

Phase 2: Detect Known Anti-Patterns

Run all 8 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
Security
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
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
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 Scene Graph and Physics Architecture

Phase 1: Map Scene Graph and Physics Architecture

02
Step 1: Identify Scene Inventory

Step 1: Identify Scene Inventory

03
Step 2: Identify Physics Configuration

Step 2: Identify Physics Configuration

04
Step 3: Identify Node Lifecycle and Action Surface

Step 3: Identify Node Lifecycle and Action Surface

05
Step 4: Identify Asset and Debug Surface

Step 4: Identify Asset and Debug Surface

06
Step 5: Read Key Files

Read 1-2 representative scene files and any custom SKNode/SKSpriteNode subclasses to understand: Node hierarchy (camera/world/hud separation, layer organization) PhysicsCategory definitions (named constants vs magic numbers) Spawn/despawn discipline (where nodes are added in `update()` and where they're removed) Action closure capture (`[weak self]` or strong self?)

07
Phase 2: Detect Known Anti-Patterns

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

08
Phase 3: Reason About SpriteKit Completeness

Using the SpriteKit 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 Does every body that participates in contacts have explicit `contactTestBitMask`, and is `physicsWorld.contactDelegate` set on the scene? · Contact-delegate gap · Bitmasks set but delegate missing → contacts silently never fire; the bug looks like physics, not wiring

09
Phase 4: Cross-Reference Findings

Bump severity for these combinations: Finding A · + Finding B · = Compound · Severity Default bitmask (Pattern 1) · Contact delegate set + `didBegin` overridden · Phantom contacts fire constantly; gameplay logic responds to non-events · CRITICAL Strong self in `.repeatForever` (Pattern 4) · Scene transition without `removeAllActions()` · Previous scene leaks AND keeps spawning nodes invisibly into the leaked scene · CRITICAL

10
Phase 5: SpriteKit Health Score

Metric · Value Scene count · N SKScene subclasses PhysicsCategory discipline · named-constants / mixed / magic-numbers-or-default Add/remove balance · M `addChild` vs N `removeFromParent` (ratio) Action capture discipline · M of N closures use `[weak self]` (Z%)

Discussion

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