From aming-claw
Reviews user-facing Aming Claw flows against the ue_audit.v1 contract for UE compliance. Use during governance review of builder flows where request visibility and state visibility are critical.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aming-claw:aming-claw-ue-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill for user-facing product surfaces that need the V1 UE audit
Use this skill for user-facing product surfaces that need the V1 UE audit contract. It is a governance review helper, not an external dependency for the contract module.
Use ue_audit.v1 from:
agent/governance/contract_templates/ue_audit.v1.json
The bundled expert source is:
aming_claw.bundled_ue_expert.v1
If an external UE skill is unavailable, continue with the bundled governance profile. Record the expert source in the audit output.
Collect:
For ordinary vibe-coding builders, assume the primary need is seeing their own requests and request states unless the product owner supplies a sharper persona.
Check:
Return machine-readable findings. Each finding includes severity, screen or flow, user impact, evidence refs, recommendation, and acceptance impact.
The gate decision must be one of:
passpass_with_followupsblockDo not auto-approve a UI from AI review alone. Do not replace product owner judgment. Do not block non-user-facing backend work by default.
npx claudepluginhub amingclawdev/aming-claw --plugin aming-clawEvaluates UI flows and screens against Nielsen's 10 usability heuristics, flags friction points, and recommends fixes. Useful for UX reviews, audits, and design critiques.
Reviews UI design drafts against approved specs, UX quality attributes, and accessibility standards before task breakdown. Blocks premature implementation and enforces design review gates.
Usability review — evaluate an existing flow or UI against usability heuristics, flag friction points, and recommend fixes. Use when asked to "review the UX", "usability audit", "what's wrong with this flow", "UX feedback", "critique this design", or "why are users dropping off here".