# Specification: Admin Dashboard UI States Audit (`audit_ui_states_20260314`)

## Overview
This track involves a comprehensive audit of the **Jomblo Admin Dashboard** to ensure robust handling of various UI/UX states (Loading, Success, Empty, Error, Partial, Secondary). The goal is to identify and resolve gaps in the current implementation, ensuring a premium, "haptic" experience as defined in our `uncodixfy` design principles.

## Functional Requirements
- **Loading States**: Audit all data-heavy dashboard pages (Orders, Catalog, Customers, Settings) for consistent use of **Skeleton Screens** during initial data fetching and page transitions.
- **Empty States**: Verify that every list and table has a context-aware **Empty State** design (e.g., "No orders found," with a call-to-action to create one).
- **Error States**: Ensure all API interactions (fetching and mutations) handle failures gracefully using an **Automatic Retry** strategy where possible, followed by a clear, non-intrusive error notification or inline error state.
- **Partial States**: Identify scenarios where some data (e.g., dashboard widgets) might load successfully while others fail, ensuring the UI remains functional and informative.
- **Secondary States**: Audit non-primary states like `disabled`, `readonly`, and `hover` across all form elements and action buttons in the dashboard.

## Non-Functional Requirements
- **Performance**: Transition from loading to content states must feel "snappy." Target latency for state transitions is **< 200ms**.
- **Aesthetic Consistency**: All state designs must align with our existing `uncodixfy` patterns: `0.5rem` border radius, professional shadows, and restrained hover effects.
- **Accessibility**: All states (especially Loading and Error) must be screen-reader friendly and maintain high color contrast.

## Acceptance Criteria
- [ ] Comprehensive audit report generated for the Admin Dashboard (Orders, Customers, Catalog, Settings).
- [ ] Skeleton screens implemented or updated for all primary dashboard lists.
- [ ] Context-aware empty states added to all empty lists/tables.
- [ ] Automatic retry logic verified for all dashboard data fetching via `useAction` or similar hooks.
- [ ] Zero build or linting errors in the final implementation.
- [ ] 100% test coverage for all new or modified state-handling logic.

## Out of Scope
- Public storefront pages (Product Catalog, Cart, Checkout).
- Major visual redesign of existing dashboard components (unless required for state handling).

## Implementer Mandate
- **No Ambiguity Clause**: Implementers MUST provide line numbers and code snippets for all proposed changes in the implementation plan. No speculative inference allowed.