---
name: domain-product-principles
description: Use when making UX decisions, designing new flows, or evaluating whether a feature fits the product's training tool goals.
---

- Core training loop: start roleplay → converse → evaluate → view feedback — protect this path from added friction
- Feedback must be scannable: skill scores and tips visible at a glance, no walls of text
- Simulation mode (adaptive/drill/generic) must be clearly indicated — banners or badges, not buried in settings
- Progress views surface actionable insight (weaknesses, trends) — not just raw scores
- Live coaching tips are optional and non-blocking — they must not interrupt the conversation flow
- Adaptive and drill modes have distinct UX indicators — users must always know which mode they're in
- Empty and loading states must be handled gracefully — no broken UI on a user's first session
- Evaluation results should be immediately accessible after the conversation ends — no extra navigation required
- New features must not obscure the feedback view or add steps to the common training flow
- Badges and banners clarify state — use them to communicate mode, completion, and progress milestones
- Don't add settings or configuration steps that most users will never need