Functional UI Prototype

Goal

Produce a browser-based, fully interactive prototype that is indistinguishable in behavior from a feature backed by a real server. The prototype must use localStorage as its persistence layer, simulate realistic network latency on every data operation, and meet the same quality bar as production code in both visual fidelity and code standards.

Constraints

No Backend Changes

Do not create, modify, or extend any backend code, API route, server endpoint, serverless function, database migration, or server-side configuration. The prototype must be entirely self-contained in the frontend.

Production-Grade Quality

A prototype is not an excuse for lower quality. Apply the same standards the project enforces for production code:

• Visual quality must match the project's existing UI.
• Code quality must pass the project's linting, formatting, and type-checking rules.
• Component structure, naming, file organization, and styling must follow the project's established conventions.