Build your own Fiverr.

# Build an original app inspired by Fiverr

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 freelance service marketplace called Craftorder, inspired by Fiverr. Providers publish scoped service packages, customers submit requirements, and both parties manage a delivery/revision workflow. Start with approved providers and no real payments or escrow.

## Design
Create an original service catalog, provider profile, package comparison, requirements form, and private order workspace. Make deliverables, turnaround, revision limits, and acceptance state explicit. Avoid implying that a paid balance, escrow account, or verified provider exists without implementing it.

## Features
1. Provider services: create draft/published service listings with original examples, package prices, delivery days, and included revisions. Review provider/listing visibility through an administrator workflow.

2. Discovery and requirements: search categories, filter published services, choose a package, and complete typed requirement fields. Snapshot the package terms and requirements when the customer places a test order.

3. Order workflow: implement pending requirements, in progress, delivered, revision requested, completed, and cancelled states with explicit role permissions and transition rules.

4. Delivery and communication: exchange private order messages and bounded deliverable files, submit a versioned delivery, request an allowed revision, and retain previous versions. Protect downloads against access by other customers/providers.

5. Reviews and moderation: allow reviews only for completed orders, provide issue reports and administrator resolution notes, and show real order counts and ratings derived from stored outcomes.

## Tech stack
Use PHP/Laravel with PostgreSQL, a TypeScript frontend, and private object storage. Persist order transitions transactionally, validate upload types, and store amounts as integer minor units. A real payment/escrow system is outside the starter version; do not represent ledger rows as held funds.

## Data & behavior
User; ProviderProfile; Service; Package; RequirementDefinition; Order {packageSnapshot, state, dueAt, revisionsRemaining}; RequirementAnswer; OrderMessage; DeliveryVersion; Attachment; Review; IssueReport; ResolutionEvent. Keep package snapshots immutable and delivery access scoped to order participants.

Acceptance checks and scope:
Test requirements missing at order creation, a provider changing package terms later, revision limits, concurrent accept/revise actions, unauthorized deliverable downloads, cancelled orders, and reviews without completed work. Exclude escrow, payouts, automatic dispute judgments, imported Fiverr profiles, and live payment collection.

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