great now write 50-100 ai dev prompts that focus on the contracts/ui/*.jsonc files.

Think through our user experience. Fill out the routes and components.registry and pages scaffolding to be consistent modern and usable.

This is when we plan out the components to create later. Structure out the full food-delivery app.

Also i notice for example key values in forms.jsonc, can we improve the single source of truth here also? Forms in particular need access to dynamic data for example to dynamically populate a drop-down. Some of that we can worry about later. For now do the best we can.

Let’s enhance the ui/jsonc with consistent copy and content.

The app is simple really.

Universal top bar with search, navigation, user avatar.

Home page with site feed.

Site feed is mix of content.

Vendor Page with vendor art, title, description, location, order, contact, and menu

Menu Items with item art, title, description, add to card.

Order page – the actual order is handled by Stripe.

Vendor Dashboard:
– Pending orders!
– Add item
– Edit item
– Edit store details
– Order history
– Customer history
– Delivery history
– Order notification channels

Customer Dashboard:
– Order history
– Favorites
– Settings

Don’t let these .jsonc files get larger than 300 lines before breaking them out into modules.

We have 50-100 ai dev prompts to compose the app scaffolding and static content in the contracts/ui/ jsonc files.