# Task AR.2 - Epic & Technical Design

Status: Completed

## UI / UX Design Governance

All future workspace, dashboard, calendar, timeline, activity, customer, opportunity, quotation, manager, and executive UI design work must use the `ui-ux-pro-max` skill as part of the design process.

Before proposing or implementing any UI, the agent must review:

- `layout.md`
- `docs/standards/ui-ux-rules.md`
- `docs/standards/architecture-rules.md`
- existing shadcn/ui usage patterns
- existing dashboard layout conventions
- existing CRM page/detail/table/form patterns

### Design Rules

- Preserve existing shadcn/ui foundation.
- Prefer extension over visual redesign.
- Follow existing layout rhythm unless the blueprint explicitly requires a new workspace pattern.
- Do not introduce a disconnected design system.
- New workspace UI must align with ALLA OS role-based workspace philosophy.
- Calendar, My Day, Manager Workspace, Customer Workspace, Timeline, and Activity surfaces must be designed as operational workspaces, not generic CRUD pages.
- Every UI proposal must include:
  - page purpose
  - primary user role
  - layout structure
  - key actions
  - empty state
  - loading state
  - permission-aware visibility
  - responsive behavior
  - relationship to existing CRM navigation

### Required Design Inputs

Use:

- `ui-ux-pro-max` for UX quality, interaction flow, visual hierarchy, and enterprise usability
- `layout.md` for layout structure and page composition rules
- `ui-ux-rules.md` for ALLA OS UI standards
- existing shadcn/ui components as the implementation baseline

### Frozen Rule

No future workspace implementation may start with code first.

Every new workspace or major UI surface must first produce a UI/UX design note that references:

- Business Constitution
- AR.1 Architecture Transition Plan
- `layout.md`
- `ui-ux-rules.md`
- `ui-ux-pro-max`