# Track Spec: Dashboard UI/UX Polish & Functional Refinement (Phase 2)

**Track ID**: `dashboard_polish_v2_20260312`
**Status**: Approved
**Persona**: PO (Vision), Dev (Architecture), QA (Validation)

## 1. Goal
Perform a comprehensive visual and functional sweep of all dashboard pages (excluding the sidebar and header). The goal is to elevate the "Visual Perception" using minimalist `uncodixfy` principles while adding dynamic, interactive feedback and resolving functional friction in areas like the Blackboard task management.

## 2. Requirements

### 2.1 Visual Perception (Minimalist & Dynamic)
- **Aesthetics**: Adhere to `uncodixfy` Minimalist (Porcelain) standards: clean whitespace, high-quality typography, and subtle hierarchy.
- **Interactivity**: 
    - Implement smooth hover states for all interactive elements (rows, buttons, cards).
    - Add micro-animations for state changes (e.g., loading spinners, success checkmarks).
    - Use `shadcn/ui` primitives consistently with standardized 8-10px border radii.
- **Dynamic Feedback**: Enhance feedback during data mutations (toast notifications, optimistic UI updates where applicable).

### 2.2 Functional Refinement (Blackboard Tasks)
- **Drag & Drop**: Smoothen the "grab and move" experience for Blackboard tasks.
    - Improve ghost/preview elements during drag.
    - Add haptic visual feedback (shadow change, scale shift) when grabbing.
    - Ensure drop animations are fluid and predictable.
- **Small Friction Points**: Audit and fix minor UX "papercuts" (e.g., focus management, missing tooltips, alignment issues).

### 2.3 Structural Constraints
- **Ignore**: The Sidebar and Header are out of scope for this track.
- **Pages**: Every page under `app/(private)/dashboard/**/*` must be audited.

## 3. Technical Constraints
- **UI -> Repository**: Forbidden. UI components MUST never import from `lib/db/repositories`. Use Server Actions from `actions/`.
- **Validation**: Use **Zod** for all client-side and action-side validation.
- **Testing**: 100% test coverage is required for all new or modified logic. Verify responsive layouts for all audited pages.
- **No Ambiguity Clause**: Implementers MUST provide line numbers and code snippets for all proposed changes. No speculative inference allowed.

## 4. Resource Budgets
- **Latency**: Critical actions (save/delete) should respond in < 200ms (optimistic UI preferred).
- **Bundle Size**: Minimize external library additions; prefer built-in `shadcn` and `lucide-react`.

## 5. Acceptance Criteria
- [ ] All pages audited and updated to new visual standards.
- [ ] Blackboard task dragging is "smooth" and visually responsive.
- [ ] Zero `pnpm build` or `tsc` errors.
- [ ] 100% test pass rate with coverage maintained.