القائمة
Use when reviewing user-facing Aming Claw flows against the bundled ue_audit.v1 contract, especially ordinary non-technical builder flows where request and state visibility matter.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Single Aming Claw skill entrypoint. Use this first for Aming Claw governance, backlog, graph, runtime, worker, QA, dashboard, MCP, install/start/bootstrap, or dogfood work; prefer the MCP onboard_route_guide tool before choosing a role or successor contract.
Public demo for Backlog Duplicate: a new requirement overlaps existing backlog work, and the observer asks whether to merge, supersede, or keep it separate. Use when a user asks to run, preview, or collect duplicate backlog evidence with the current Claude Code or Codex observer session.
Public demo for Docs Drift: a feature changes but documentation is stale, and the drift state is surfaced before a second doc fix. Use when a user asks to run, preview, or collect evidence for docs drift with the current Claude Code or Codex observer session.
Public HN challenge entrypoint for Aming Claw. Use when a user asks to run, preview, present, or collect evidence for the multi-agent challenge: one observer coordinates multiple commit-bound workers, records a failed or interrupted worker, replays it from the same contract lineage, reconciles the target graph, and writes an audit self-review.
HN demo case for the fear that code changes leave docs, tests, and config stale after implementation. Guides evidence collection for Asset Inbox, binding state, Baseline and Possible drift, Review Queue, impact scope, and review boundaries.
HN demo case for the fear that AI does not understand project structure and duplicates work. Guides evidence collection for graph-first discovery, backlog contract, target file fence, and acceptance criteria before implementation.
| name | aming-claw-ue-review |
| description | Use when reviewing user-facing Aming Claw flows against the bundled ue_audit.v1 contract, especially ordinary non-technical builder flows where request and state visibility matter. |
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.