AF swiftui-view-refactor
Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.
As a process F 34/100 · Will not run — References files that are not bundled: references/mv-patterns.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/mv-patterns.md - note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 34/100
- 0Tools and files. 1 referenced file(s) missing: references/mv-patterns.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (swiftui-view-refactor) differs from the folder (timeflow-swiftui-view-refactor)
- 60Failures and branches. 2 branches
- 85Steps. 35 steps, 1 vague phrases
- 100Execution cost. Instruction body is 1450 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 308: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.