silver-app

As a user I want to be able to use backend APIs for creating, reading, updating, and deleting tasks. Implement FastAPI endpoints: POST /tasks, GET /tasks, GET /tasks/{id}, PUT /tasks/{id}, DELETE /tasks/{id}. Each task supports fields: title, description, category, due_date (IST/DD-MM-YYYY), priority, is_completed. Require JWT auth on all endpoints. Include Alembic migration for the tasks table.

As a user I want to be able to use a frontend task form page that matches the designed Task Form (v2) page exactly. Implement the task creation/editing form based on the existing JSX design. Fields: Task Title, Description (optional), Category pill-selector with custom 'Other' input, Due Date with IST locale and DD/MM/YYYY format, Priority toggle (Low/Medium/High), Completion Status switch. Inline error messages in #FF6F61. Cancel navigates back to Dashboard; Save submits the task.

As a user I want to be able to use a frontend dashboard page that matches the designed Dashboard (v2) page exactly. Implement the main task dashboard based on the existing JSX design. Features: floating task card grid layout, filter bar (by due date, category, completion status), a '+' FAB button to add new tasks, empty state illustration. Navigates to Task Form for add/edit and reflects task completion inline.

As a user I want to be able to use a frontend landing page that matches the designed Landing (v2) page exactly. Implement the landing/home page based on the existing JSX design. The page should present the silver-app value proposition, provide navigation to Login and Signup, and reflect the floating card signature design concept. Follows from the theme/design system task.

As a user I want to be able to use a frontend login page that matches the designed Login (v2) page exactly. Implement the sign-in page based on the existing JSX design. Includes email/password fields, inline validation, error handling, and redirect to Dashboard on successful authentication. Links to Signup page.

As a user I want to be able to use a frontend signup page that matches the designed Signup (v2) page exactly. Implement the account registration page based on the existing JSX design. Includes form fields for name, email, password, inline validation with #FF6F61 error messages, and navigation to the Login page on success. Locale defaults: IST timezone, DD/MM/YYYY.

As a user I want to be able to use a frontend task card component that matches the designed Task Card (v2) exactly. Implement the reusable floating task card based on the existing JSX design. Features: hover elevation animation, completion flip/fade animation with confetti, drag-and-drop reorder support, edit action linking to Task Form, delete action with confirmation, completion toggle with #7ED321 accent. Used inside the Dashboard page.

As a user I want to be able to use backend APIs for filtering and sorting tasks by due date, category, or completion status. Extend the GET /tasks endpoint with query parameters: filter_by_category, filter_by_status (completed/pending), sort_by (due_date, category, completion_status). Return paginated results. Ensure IST timezone handling for due_date comparisons.

As a user I want to be able to use the frontend login and signup pages connected to the real backend auth APIs. Wire the Login and Signup pages to POST /auth/login and POST /auth/register. Store JWT token in secure storage. Handle API errors with inline #FF6F61 messages. Redirect to Dashboard on successful auth. Implement protected route guard for Dashboard and Task Form pages.

As a user I want to be able to use the frontend dashboard connected to real task data from the backend. Wire Dashboard and Task Card components to GET /tasks (with filter/sort params), DELETE /tasks/{id}, and PATCH completion status. Implement optimistic UI updates for completion toggle and delete. Handle loading and empty states.

As a user I want to be able to use the task form page to create and edit tasks via the backend API. Wire the Task Form page to POST /tasks (create mode) and PUT /tasks/{id} (edit mode). Pre-populate fields in edit mode from GET /tasks/{id}. Handle validation errors returned from API inline. On success, navigate back to Dashboard.