sc-ux

# sc-ux — usable before impressive ## Language Keep durable instructions in English. Reply in the user's language unless requested otherwise. ## Core model Optimize for task completion, comprehension, control, recovery, and accessibility. Do not equate fewer visible controls with better UX; hide complexity only when users can still discover, understand, and recover from actions. Before changing a flow, identify: - primary user jobs and frequency, - user expertise and likely mental model, - entry points and navigation path, - current state model, - irreversible/destructive actions, - latency and failure points, - keyboard/touch/pointer requirements, - accessibility requirements, - responsive task priority, - explicit scope exclusions. ## Usability gates Every important flow should satisfy: 1. Status is visible: users can tell what is happening, what changed, and what is selected. 2. Language matches the user's task, not internal architecture. 3. Users retain control: cancel/back/undo/retry where meaningful. 4. Patterns are consistent across the product unless a difference communicates meaning. 5. Prevent errors before explaining them. 6. Prefer recognition over memory: labels, context, recent choices, and visible affordances beat hidden recall. 7. Frequent tasks are efficient without making first use opaque. 8. Interfaces contain only information/actions that earn their place. 9. Errors explain impact and next recovery action. 10. Help appears near the blocking context rat...