axiom-swiftui

Use when building, fixing, or improving ANY SwiftUI UI — views, navigation, layout, animations, performance, architecture, gestures, debugging, iOS 26 features.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an efficient, well-structured SwiftUI router with strong conciseness and clear navigation. Its main limitation is that actionable detail lives entirely in referenced files that are not present in this skill's bundle, so a reader cannot verify or execute the referenced guidance from the bundle alone.

Suggestions

Add a brief inline note or manifest confirming which `skills/*.md` references are part of this bundle versus external suites, since no `references/` directory is present to verify them.

For the highest-traffic symptoms (e.g. "view not updating"), include one or two concrete inline steps before deferring to `skills/debugging.md` so the body is actionable without an external file read.

Add explicit verification guidance for the automated-scan workflows (e.g. how to confirm an auditor ran cleanly) to lift workflow_clarity toward 5.

Dimension	Reasoning	Score
Conciseness	A lean router body with no concept explanations or padding — symptom-to-reference tables, a decision tree, and short routing notes, every token earning its place and assuming Claude's competence.	5 / 5
Actionability	Provides concrete, executable routing (named agents, `/axiom:audit` commands, specific `skills/*.md` paths) but the body itself defers all actual instructions to referenced files rather than giving copy-paste-ready steps, leaving minor gaps.	4 / 5
Workflow Clarity	Clear sequencing via the decision tree, quick-reference table, and a conflict-resolution priority order; as a non-destructive router it needs no validation checkpoints, but the routing flow has minor gaps versus a fully explicit checklist.	4 / 5
Progressive Disclosure	Well-organized overview with clearly signaled, one-level-deep references (`skills/*.md`) and easy navigation, but the referenced paths live outside this skill's bundle (no `references/`/`scripts/`/`assets/` directories present) so the references cannot be verified against an actual bundle structure, keeping it just below 5.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a strong, explicit trigger with comprehensive SwiftUI domain coverage and a clear "Use when..." clause. It could nudge specificity to 5 by replacing the generic verbs "building/fixing/improving" with more concrete actions.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ("views, navigation, layout, animations, performance, architecture, gestures, debugging, iOS 26 features") but the actions are broad verbs ("building, fixing, or improving") rather than fully concrete operations, leaving minor coverage gaps versus a 5.	4 / 5
Completeness	Explicitly answers both what ("building, fixing, or improving ANY SwiftUI UI" plus enumerated areas) and when ("Use when...") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Strong natural keywords ("SwiftUI", "navigation", "layout", "animations", "gestures", "debugging", "iOS 26") a user would say, but it lacks a few synonyms or file-type variations that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear SwiftUI niche with distinct, well-bounded triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: CharlesWiltgen/Axiom
Path: .claude-plugin/plugins/axiom/skills/axiom-swiftui/SKILL.md
Commit: dd33347

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.