aurora-ux_skill

Overview

This skill evaluates and improves the user experience of Aurora forms, focusing on cognitive flow rather than visual layout. It helps reorder fields, validate field dependencies, and apply progressive disclosure and validation rules to reduce user friction. Use it to audit forms and produce concrete, actionable ordering and interaction changes.

How this skill works

The skill inspects form field metadata (required flag, identifiers, dependencies, readonly/calculated status) and scores each field using a decision matrix to recommend order and visibility. It flags anti-patterns, suggests grouping and expansion panels for advanced options, and outputs a checklist for UX review and implementation tips for Create/Edit/Filter modes.

When to use it

• Audit an existing Aurora form for usability problems
• Reorder fields to match user cognition and reduce backtracking
• Design Create, Edit, or Filter forms with sensible defaults and focus behavior
• Introduce progressive disclosure for advanced or optional settings
• Validate field dependencies and tab/focus order before release

Best practices

• Place required fields first within each semantic section
• Order fields from what the user already knows to what they must decide (identifiers → basics → classification → details → settings → state)
• Group related fields and place dependents next to or below their parent fields
• Use expansion panels for advanced/rare options and keep calculated fields readonly or hidden
• Apply validation on blur for critical fields and on submit for cross-field checks; show real-time feedback only where helpful

Example use cases

• Create form: set autofocus on first editable field, preload sensible defaults, hide calculated fields
• Edit form: clearly mark readonly fields, preserve original values until save, indicate unsaved changes
• Filter UI: surface most-used filters first and provide a clear reset/clear-all action
• Country/state dependency: disable state selector until country is chosen and show a hint
• Complex entity form: move identifiers and required fields to top, push audit fields and isActive to the end or hide them