---
name: review-kiduna-studio
description: Review a Kiduna Studio concept, mockup, or prototype for focus, clarity, Realm intelligence, trustworthy action, progressive disclosure, taxonomy fidelity, visual character, and capability coverage. Use after each short design pass to decide what to keep, cut, change, and test next before advancing to broader scenes or engineering handoff.
---

# Review Kiduna Studio

Read [review-scorecard.md](references/review-scorecard.md). Review the artifact at the actual target viewport and, if interactive, exercise its primary and exceptional paths.

## 1. Verify evidence and scope

- Identify the artifact and version reviewed.
- State which user, Realm, Focus, journey, and capabilities it intends to prove.
- Separate inherited requirements, proposals, contradictions, and missing evidence.

## 2. Review in the correct order

Evaluate:

1. dominant focus and information hierarchy;
2. outcome clarity and conversational usefulness;
3. Realm intelligence and Stance;
4. Element recognition and lifecycle;
5. progressive disclosure and context movement;
6. authority, privacy, trust, gates, Records, and recovery;
7. visual, spatial, motion, and tonal coherence;
8. taxonomy fidelity and capability evidence.

Do not let polish compensate for a failed interaction model.

## 3. Score and diagnose

Score each criterion 0–2 using the reference. Cite observable evidence. Name the root cause rather than listing only symptoms. Flag any automatic-fail condition.

## 4. Conclude decisively

Return four lists:

- **Keep** — behavior or qualities that should become constraints.
- **Cut** — elements adding weight without improving outcome or trust.
- **Change** — the smallest high-leverage revisions.
- **Test next** — one bounded experiment with a single learning objective.

Also provide the scorecard, open decisions, capability evidence changes, and a clear gate recommendation: advance, revise, or stop and resolve evidence.

Do not prescribe technical implementation unless requested.
