Prototype feature

Build the feature as real UI with local data. Preserve component and action boundaries so prototype-to-contract can replace mocks with fragments and mutations later.

Read

• Read the existing app shell, routes, shared components, design tokens, data conventions, and state patterns.
• Fit the app. Ask before introducing a new dependency, design convention, route pattern, or state model.

Build

• Build only the requested workflow. Do not invent extra product surface.
• Keep data local. Do not add backend calls, schema files, generated GraphQL artifacts, or async loading simulation.
• Make the prototype clickable with local state. Use the repo's existing frontend stack and conventions.

Data

• Model data as product-domain entities with stable ids, nested relationships, good names, and computed fields when useful.
• Seed enough realistic records to cover every reachable state needed to review the workflow.