Build your own Etsy.

# Build an original app inspired by Etsy

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 maker marketplace called Makershelf, inspired by Etsy. Approved makers create small shops, sell original physical items with variations and personalization, and track made-to-order fulfillment. Begin with one seller per checkout, one currency, and test orders without live payments.

## Design
Use an original image-led catalog, maker shop pages, product options, personalization preview, and a clear order summary. Make production lead time, selected variation, seller identity, and shipping assumptions visible before ordering. Give small sellers a practical dashboard.

## Features
1. Shops and listings: create seller-owned shop profiles and draft/published listings with original images, categories, materials, production lead times, and explicit item availability.

2. Variations and personalization: configure a bounded set of variation combinations with SKU/price/stock and required optional text fields. Validate character limits and freeze selected text/options in the order snapshot.

3. Discovery: search published items, filter category/price, favorite listings/shops, and browse one maker’s catalog. Do not use scraped Etsy inventory or fabricate seller ratings.

4. Test checkout: enforce one seller per cart, calculate totals on the server, reserve ready-made stock or an explicitly limited production slot, and create an idempotent no-payment order with a promised fulfillment window.

5. Maker workflow: accept, produce, dispatch, cancel, and record customer-requested changes through a versioned order history. Allow only completed-order reviews and protect customer contact details from other shops.

## Tech stack
Use PHP/Laravel, PostgreSQL, a TypeScript storefront, and object storage for licensed listing images. Use transactions for stock or production-capacity reservations, integer minor-unit prices, and server-side seller/order permissions. Keep test checkout distinct from real charge collection.

## Data & behavior
Shop; ShopRole; Listing; Variation; SKU; PersonalizationField; Favorite; Cart; CapacitySlot; Reservation; Order {shopId, state, promisedBy}; OrderLine {listingSnapshot, options, personalization}; OrderChange; FulfillmentEvent; Review. Do not rewrite agreed order details when a listing changes.

Acceptance checks and scope:
Test missing personalization, a sold-out variation, production-slot races, duplicate checkout, changing options after order creation, seller access, and review eligibility. Exclude Etsy content import, live payments/payouts, cross-border tax calculation, shipping-carrier APIs, and digital-download DRM.

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