Build your own Linear.

# Build an original app inspired by Linear

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 issue and project tracker called Orbit, inspired by Linear. It is for a small software team planning work and tracking progress. The main journey is creating an issue, assigning it to a project and owner, and moving it through a clear workflow.

## Design
Use a focused, dense-but-legible interface with a narrow workspace sidebar, a list or board in the main area, and an issue detail panel. Use slate surfaces, subtle separators, crisp type, and one violet accent. Include status symbols, priority indicators, a command palette, and accessible keyboard shortcuts. Give the app its own identity.

## Features
1. Issues: create and edit a title, Markdown description, status, priority, assignee, labels, project, and due date. Generate a stable human-readable issue key. Support archive and restore.

2. Views: switch between a filterable issue list and a board grouped by status. Move issues with a status menu or drag-and-drop. Combine filters for project, assignee, label, and priority.

3. Projects: create a project with a description and target date, view related issues, and derive completion progress from actual issue statuses.

4. Cycles: create a date-bounded cycle and assign issues to it. Show completed versus remaining work and carry unfinished issues into another cycle with confirmation.

5. Fast navigation: search issue keys, titles, and descriptions; provide a command palette for navigation and issue creation. A chronological activity log records meaningful issue changes.

## 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
Workspace {id, name}; Member {id, workspaceId, displayName}; Project {id, workspaceId, name, description, targetDate}; Issue {id, key, workspaceId, projectId, cycleId, title, description, status, priority, assigneeId, labels, dueDate, archivedAt}; Cycle {id, workspaceId, name, startsAt, endsAt}; Activity {id, issueId, actorId, action, createdAt}. Use a real authenticated backend for shared team data; scope every query and mutation to workspace membership.

Acceptance checks and scope:
Verify create → assign → move → complete → reload; combine filters and search; archive and restore; derive project progress; and move unfinished cycle work without duplication. If a backend cannot be configured, provide a clearly labeled local demo and document the shared-workspace setup. Leave code-host integrations, billing, and advanced reporting outside the MVP.

## 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.