TroveSnap design & enhancement docs
Pre–Wave-2 planning: a feature-level breakdown of the deployed surfaces, the estate-seller
pain points TroveSnap targets (and the gaps it doesn't), and prioritized enhancement
backlogs per surface. Grounded in the code audit behind the tracker's UI/UX tab
(docs/tracking/ui-readiness.json).
| Doc | What it is |
|---|---|
| estate-seller-painpoints.md | The end-to-end estate-sale flow with the biggest pain points, mapped to TroveSnap coverage (✅ core / 🟡 partial / ❌ gap). The reference for what we enhance. |
| web-feature-breakdown.md | Every web page/tab → feature-level work to take it from demo/bypassing to contract-ready, with gates + waves. The web build list. |
| ui-ux-enhancements.md | Cross-surface UX improvements, prioritized by throughput (the dominant estate-seller pain). |
| harness-enhancements.md | Desktop-harness enhancements (identity, idempotency, privacy, packaging). |
| web-enhancements.md | Web architecture + product enhancements, incl. the deliberate gaps (contracts, staffing/SOPs, lead-gen, post-sale) to capture now and build later. |
| trove-host-vision.md | The archived consumer Trove #hosts vision (live sale events, teasers/drops, gamified Host Cards) mapped to current coverage — provenance for the host event-marketing Backlog (WI-087–092, D42). |
| storybook-design-sync-prompt.md | Ready-to-paste agent prompt to stand up Storybook so /design-sync can mock our UI into claude.ai/design — repo facts verified, React-19 pins, the decoupled component tier (WI-093). |
| seller-surface-map.md | From-source map of the deployed /seller surface — the sidebar nav, every seller route, and the features on each page. |
| seller-feature-catalog.md | The full seller feature set current + planned, end to end: lead-gen, Google Business monitoring, capture/cataloging, day-of-sale observation, post-sale auction distribution, agency ops, trust layer. |
How to use: the breakdown + pain-points docs feed Wave-2+ scoping (what to wire, in what order); the three enhancement docs are living backlogs — promote items into a sprint when the core scan→list→sell loop is contract-backed. None of this changes the existing plan; it makes the surface work explicit before we build it.