Build your own Todoist.

# Build an original app inspired by Todoist

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original personal task manager called Daylight, inspired by Todoist. It is for people planning everyday work and life. The main journey is capturing a task quickly, assigning it to a project and date, and completing it from a useful daily view.

## Design
Use a calm white interface, a compact sidebar, a warm red accent, circular completion controls, and comfortable task rows. Give Today and Upcoming clear headings and useful empty states. The quick-add composer should work comfortably with the keyboard and on mobile.

## Features
1. Task capture: create tasks with title, optional description, project, section, due date, priority, and labels. Provide a quick-add dialog with explicit date controls.

2. Organization: create and rename projects and sections, reorder tasks, create one level of subtasks, and move tasks between projects. Include an Inbox for unassigned work.

3. Daily views: show Inbox, Today including overdue tasks, and Upcoming grouped by date. Filter by project, label, priority, or text search.

4. Completion and recurrence: complete, undo completion, and review completed tasks. Support daily, weekly, and monthly recurrence with an explicit next-date preview and documented month-end behavior.

5. Persistence and portability: keep task edits across reloads and export/import tasks as validated JSON. Seed a few helpful tasks only on first use.

## Tech stack
Use the existing repository and conventions if there is one. If starting from scratch, use React with TypeScript and a practical, lightweight styling approach. Pick well-maintained libraries only when they materially help. Keep components, domain logic, and data access separate. Explain your chosen stack briefly, then begin implementation.

Follow the persistence requirements in Data & behavior. Personal tools may use IndexedDB. Products with public submission, bookings, permissions, or shared messaging require an authenticated backend with server-side authorization and durable storage. Use infrastructure already available in the environment. Do not put secrets in frontend code. If external infrastructure is unavailable, build a clearly labeled local demo, provide the schema and setup instructions, and state which shared features need configuration. Do not present simulated sharing or authentication as production functionality.

## Data & behavior
Project {id, name, color, order}; Section {id, projectId, name, order}; Task {id, projectId, sectionId, parentId, title, description, dueDate, priority, labels, recurrence, completedAt, order}; Completion {id, taskId, completedAt}. Store date-only deadlines as local calendar dates, not UTC instants. Use IndexedDB and a versioned JSON schema.

Acceptance checks and scope:
Verify overdue grouping near midnight, recurrence across month ends, undo without creating duplicate recurring tasks, completion history, and task order after reload. Deleting a project requires choosing whether to archive tasks or move them to Inbox. Exclude natural-language parsing, shared projects, notifications, and integrations from the first version.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.