axiom swift simplifier

Other 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. Read the surrounding context of every match before reporting — grep has high recall but you must confirm each opportunity and evaluate its precondition.

Files to Exclude

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

Phase 1: Scan

Gather the Swift-file universe for the requested scope: Whole project: Glob: /*.swift (minus the exclusions above). A subsystem/directory or a single file: restrict the Glob to that path. Then run the detection greps from the catalog below over that file set.

Phase 2: Verify in Context

For every grep match, Read the surrounding lines. Confirm it is a real opportunity (not a false positive) and determine which safety tag applies — this requires reading the actual code, not the grep line alone.

Phase 3: Safety / Over-Simplification Gate

This gate is what separates this auditor from a line-golf bot. Reject any candidate that: hurts clarity, merges unrelated concerns, or removes a helpful abstraction; trades readability for fewer lines; cannot meet its precondition (then either attach the precondition as a caveat or drop it). Assign each surviving finding a safety tag:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
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
Moderate
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: Scan

Gather the Swift-file universe for the requested scope: Whole project: `Glob: /*.swift` (minus the exclusions above). A subsystem/directory or a single file: restrict the Glob to that path. Then run the detection greps from the catalog below over that file set.

02
Phase 2: Verify in Context

For every grep match, Read the surrounding lines. Confirm it is a real opportunity (not a false positive) and determine which safety tag applies — this requires reading the actual code, not the grep line alone.

03
Phase 3: Safety / Over-Simplification Gate

This gate is what separates this auditor from a line-golf bot. Reject any candidate that: hurts clarity, merges unrelated concerns, or removes a helpful abstraction; trades readability for fewer lines; cannot meet its precondition (then either attach the precondition as a caveat or drop it). Assign each surviving finding a safety tag:

04
Phase 4: Report

Emit the structured report (format below).

Discussion

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