Naser Mansour
0f9d12c3cf
Adds docs/tasks/ (16 epics + 102 stories converted to task/subtask files with statuses.md as the new status source of truth) and docs/ux-design.md (retrospective design-system reference), and points CLAUDE.md at them. docs/prd.md and docs/architecture.md are kept as BMAD wrote them; the legacy docs/stories/, docs/epics/, docs/qa/gates/ and .bmad-core/ stay in place as historical/traceability records, superseded but not deleted. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
id, title, status, date, parent
| id | title | status | date | parent |
|---|---|---|---|---|
| 9-5 | 9-5 Component Styling - Forms | QA Review | 2026-09-27 | 9 |
Description
As a user, I want consistent, accessible form styling, So that data entry is intuitive and error states are clear. Full implementation history: docs/stories/story-9.5-component-styling-forms.md
Acceptance Criteria
- Border: Charcoal Gray (
border-charcoal/30) - Focus: Gold border with subtle ring (
focus:border-gold focus:ring-gold/20) - Border-radius: 6px (
rounded-md) - Padding: 12px 16px (
px-4 py-3) - Same styling as inputs
- Minimum height: 120px (
min-h-[120px]) - Custom styled using Flux UI (not native browser)
- Consistent border/focus styling with inputs
- Custom styled with gold accent when checked
- Clear visual distinction between checked/unchecked states
- SemiBold weight (
font-semibold) - Required indicator (*) in danger color
- Red border (
border-danger) - Error message displayed below field
- Error ring on focus (
focus:ring-danger/20) - Labels align to the right in RTL mode
- Input text direction follows locale
- Error messages align correctly
- Padding swaps appropriately (use
ps-4 pe-4instead ofpx-4if needed)