Таски готовы

.specify/templates/ux-reference-template.md

@@ -39,15 +39,23 @@ $ command --flag value
 *   **Key Elements**:
     *   **[Button Name]**: Primary action. Color: Blue.
     *   **[Input Field]**: Placeholder text: "Enter your name...". Validation: Real-time.
+*   **Contract Mapping**:
+    *   **`@UX_STATE`**: Enumerate the explicit UI states that must appear later in `contracts/modules.md`
+    *   **`@UX_FEEDBACK`**: Define visible system reactions for success, validation, and failure
+    *   **`@UX_RECOVERY`**: Define what the user can do after failure or degraded state
+    *   **`@UX_REACTIVITY`**: Note expected Svelte rune bindings with `$state`, `$derived`, `$effect`, `$props`
 *   **States**:
-    *   **Default**: Clean state, waiting for input.
+    *   **Idle/Default**: Clean state, waiting for input.
     *   **Loading**: Skeleton loader replaces content area.
-    *   **Success**: Toast notification appears top-right: "Saved!" (Green).
+    *   **Success**: Toast notification appears top-right and state is recoverable without reload.
+    *   **Error/Degraded**: Visible failure state with explicit recovery path.
 
 ## 4. The "Error" Experience
 
 **Philosophy**: Don't just report the error; guide the user to the fix.
 
+**Semantic Requirement**: Every documented failure path here should map to `@UX_RECOVERY` and, where relevant, `@UX_FEEDBACK` in the generated component contracts.
+
 ### Scenario A: [Common Error, e.g. Invalid Input]
 
 *   **User Action**: Enters "123" in a text-only field.