docs: initialize project
This commit is contained in:
63
.planning/PROJECT.md
Normal file
63
.planning/PROJECT.md
Normal file
@@ -0,0 +1,63 @@
|
||||
# GearBox
|
||||
|
||||
## What This Is
|
||||
|
||||
A web-based gear management and purchase planning app. Users can catalog their gear collections (bikepacking, sim racing, or any hobby), track details like weight, price, and source, and use planning threads to research and compare new purchases against their existing setup. Built as a single-user app with a clean, minimalist interface.
|
||||
|
||||
## Core Value
|
||||
|
||||
Make it effortless to manage gear and plan new purchases — see how a potential buy affects your total setup weight and cost before committing.
|
||||
|
||||
## Requirements
|
||||
|
||||
### Validated
|
||||
|
||||
<!-- Shipped and confirmed valuable. -->
|
||||
|
||||
(None yet — ship to validate)
|
||||
|
||||
### Active
|
||||
|
||||
<!-- Current scope. Building toward these. -->
|
||||
|
||||
- [ ] Gear collection with items including weight, price, purchase source, category, photos, product links, and notes
|
||||
- [ ] Planning threads for researching purchases — add candidate products, compare side-by-side
|
||||
- [ ] See how candidates affect overall setup (total weight/cost impact)
|
||||
- [ ] Named setups (e.g. "Summer Bikepacking") composed from collection items with total weight/cost
|
||||
- [ ] Thread resolution — pick a winner, it moves to your collection, thread closes
|
||||
- [ ] Status tracking on thread items (researching → ordered → arrived)
|
||||
- [ ] Priority/ranking within threads to mark favorites
|
||||
- [ ] Dashboard home page with cards linking to collection, threads, and setups
|
||||
|
||||
### Out of Scope
|
||||
|
||||
- Authentication / multi-user — single user for v1, no login needed
|
||||
- Custom comparison parameters — future enhancement, not v1
|
||||
- Mobile app — web-first
|
||||
- Social/sharing features — may add later
|
||||
|
||||
## Context
|
||||
|
||||
- Primary use case is bikepacking gear, but the data model should be generic enough for any hobby/collection type
|
||||
- Replaces a spreadsheet-based workflow for tracking gear and planning purchases
|
||||
- Single user, no auth — simplest possible setup
|
||||
- User prefers Bun over npm as package manager/runtime
|
||||
|
||||
## Constraints
|
||||
|
||||
- **Runtime**: Bun — used as package manager and runtime
|
||||
- **Design**: Light, airy, minimalist — white/light backgrounds, lots of whitespace, no visual clutter
|
||||
- **Navigation**: Dashboard-based home page, not sidebar or top-nav tabs
|
||||
- **Scope**: No auth, single user for v1
|
||||
|
||||
## Key Decisions
|
||||
|
||||
| Decision | Rationale | Outcome |
|
||||
|----------|-----------|---------|
|
||||
| No auth for v1 | Single user, simplicity first | — Pending |
|
||||
| Generic data model | Support any hobby, not just bikepacking | — Pending |
|
||||
| Dashboard navigation | Clean entry point, not persistent nav | — Pending |
|
||||
| Bun runtime | User preference | — Pending |
|
||||
|
||||
---
|
||||
*Last updated: 2026-03-14 after initialization*
|
||||
Reference in New Issue
Block a user