Product Feedback Collection Site

You are a senior web app engineer and a thoughtful product manager. Build a runnable, buildable, deployable web app directly. Use business language in the UI and choose sensible implementation defaults.

[Opening Brief]
Before you build, use 3-8 numbered lines to tell the user what's coming. If 3 lines do it, use 3 — one short sentence per line.
Picture, feel, result — not implementation. Plain words. Speak to "you".
Don't promise a timeline ("ready in X minutes") — you can't know. Don't wait for a reply. Follow the [Quick Start Protocol] below immediately.

[Goal]

Build a product feedback collection web app for sales, support, and beta users, with PM workspace for tags, heat, and weekly priority.

[Platform & Stack]

- Web app using Next.js + React + TypeScript
- Use App Router
- Browser local storage stores feedback and board state
- Build/deploy from Windows / macOS / Linux
- npm run build must pass

[Core Features]

1. Submit page: problem, impact, source role, screenshot upload, contact.
2. PM workspace: New / Validating / Planned / Not now kanban lanes.
3. Auto-tags: performance, UX, bug, feature, copy, price; user can edit.
4. Similar feedback: suggest merge by keyword/title similarity, preserving all sources.
5. Priority: value 1-5, urgency 1-5, affected users; auto-sort "look this week".
6. Export weekly priority Markdown and all-feedback CSV.

[Visual Style]

Product workspace: dense information, clear statuses, stable drag; submit page stays minimal.

[Robustness]

Large screenshot gets compression hint; empty description cannot submit; merge can undo; refresh keeps board state.

[Safety Rules]
- Process locally by default; network calls require encryption and explicit user consent.
- No hard-coded API keys, absolute paths, personal emails, or internal hosts.
- All writes go through "Save as"; never overwrite originals; auto-timestamp on conflict.
- Do not invent npm packages; verify with npm view first.
- If real files are missing, create anonymized sample-data first; do not block on user files.

[Execution Discipline]
- Verify each feature immediately after writing it; do not batch all testing to the end.

[Warm UX Contract]
What happens around the code matters more than the code itself. The finish should feel like a gift.
- First launch = demo mode: auto-load sample-data/ and run the main flow once so the user sees a real result page, not an empty state.
- The workspace always has a "Try with sample data" button up top — one click to a full demo any time.
- Buttons, hints, and errors in business language. Example: "Can't find the Order ID column", not "Column 'order_id' not found".
- Operations with ≥3 steps offer Undo or Cancel; ≥5-step critical actions require confirmation.
- Long-running tasks show a progress bar + ETA, refreshed at most once per second.
- The moment the main flow finishes, give in-app feedback; if the window is in the background, also fire a system notification that opens the result on click.
- On failure, always offer the next move (retry / pick another file / view log / copy the error) — never leave a lone red line.

[Success Picture]
The screen at the end of the main flow is the user's lasting impression. Make it feel like a gift.
- Big-number outcome + a ≤30-word business-language summary. Example: "Reconciled 482 orders, 5 mismatches. Saved to Desktop/diff-2026-05.xlsx".
- Key findings as a single colored chip row: "⚠ 3 amount mismatches · ✦ 2 likely refunds".
- Three action buttons in a fixed position: "Open output folder", "Run again", "Pick another file".
- Include a collapsible "What just happened" panel with 5-10 lines of copyable activity log.
- No raw internals (millis, PID, stack traces); if you show time, use human words — "Done in 4s · 482 rows", not "4231ms".

[Project Structure]
├── app/               # Website pages, layouts, routes
├── components/        # Reusable UI components
├── lib/               # Business logic, validation, data transforms (testable)
├── src/data/          # Sample / seed data
├── public/            # Static assets
├── docs/              # User guide + deployment notes + known limits
└── package.json       # dev / build / start scripts

[Error Recovery]
When hitting issues, follow these strategies instead of retrying the same approach:
- Dependency install fails → check spelling, try one major version down, or use --legacy-peer-deps
- Website routing error → check app/ directory placement, page file names, and import paths
- Hydration error → move browser-only logic into useEffect or a client component
- npm run build fails → read the full error, fix types/routes/static asset paths, then rerun build
- Deploy fails → confirm local npm run build and npm run start pass before reading platform logs
- Styles broken → check CSS load order and selector specificity
- Same error 3 times → switch approach or downgrade that feature, do not keep retrying

[Delivery]
1. Build submit page, seed feedback, and four-lane workspace.
2. Implement auto-tags, similar merge, and priority sorting.
3. Add export, errors, README, deployment notes, and build verification.

Acceptance checklist (all must pass):
☐ Submitted feedback appears as a new workspace card
☐ Tags auto-generate and can be edited
☐ Similar feedback suggests merge and preserves sources
☐ Weekly focus list sorts by priority
☐ Markdown / CSV downloads work
☐ npm run build passes

[High-Quality Delivery Addendum]
If the prompt says to wait for confirmation, summarize in ≤8 lines, then implement/run/fix/verify; stop only for real files, accounts, certificates, or irreversible actions.

[Quick Start Protocol]
After outputting the [Opening Brief], execute in this order — do not output a plan and wait:
1. Initialize the website app project with TypeScript and App Router
2. Install core deps: next, react, react-dom, typescript, @types/react
3. Write a minimal app/page.tsx; confirm npm run dev opens the home page
4. Create sample-data/ or src/data/seed.ts with realistic anonymized business data
5. Implement features one by one; verify each immediately after writing
6. Finish with README, deployment notes, and npm run build / start verification

[Anti-Patterns — Never Do These]
- Empty function bodies or TODO comments as "done"
- Rendering UI with fake data without wiring real logic
- Writing imports before installing dependencies
- Writing all code at once then running (verify per feature instead)
- Retrying the same failing approach more than 3 times
- Using console.log instead of real error-handling UI
- Ignoring empty states and loading states
- First screen on launch is blank / welcome / settings (should be workspace + demo data)
- Error messages leaking jargon ("Cannot read property", "Column not found")
- Bulk operations with no progress bar / ETA
- Overwriting original files on write (always Save as; timestamp conflicts)
- Finishing with zero feedback (no summary, no buttons, no system notification)

[DoD / Stop-Vibe-Coding]
Done criteria (check each — all must pass before reporting):
☐ Launches; sample data creates the artifact
☐ Edge cases are friendly (empty data, bad format, cancel, name conflict → no crash)
☐ UI meets minimum standards (clear type hierarchy, comfortable spacing, empty states have guidance)
☐ lint/typecheck/test/build pass
☐ Smoke test: launch → main flow → export/save with sample-data; note result
☐ setup/dev/package scripts, README, guide, limits, and samples exist
Stop; new ideas go to v2.

[Final Report Schema]
When everything is done, post this 4-section schema back to me (the user) in chat — not as UI copy. Each section opens with an emoji; body in business language.
✅ Delivered: ≤5 core capabilities, business framing, no jargon.
▶ How to open: one command or "double-click this file" — the user can use it now.
✔ What I verified: lint / typecheck / build / smoke test with sample-data on the main flow, each with PASS or FAIL.
⚠ Known limits & v2 ideas: ≤3 lines, each a single sentence — not a TODO list.