patrickandClaude Sonnet 5
4a19335a1e
Replace Next.js/Supabase/Vercel stack with a self-hostable setup: Vite+React frontend, Fastify+Drizzle+PostgreSQL backend with own JWT auth, deploy via git pull + rsync + systemd (checkout/service separated, updates pulled from Gitea). Adds a reference auth route (register/login/me) as the canonical pattern for new routes. Updates all skills/rules/agents/docs to match. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BMdBJfD9TT6XUU2NqGG1PN
1.4 KiB
Product Requirements Document
Filled out by
/requirementsin Init Mode, or manually before the first/requirementsrun. Keep every section concrete enough that a stranger could read it and know what NOT to build.
Vision
2-3 sentences: what is this product, who is it for, why does it need to exist. Not a feature list — the problem it solves.
Target Users
Name the actual user type(s), not "everyone". For each: their concrete pain point today, and what they're using instead of this product.
Core Features (Roadmap)
| Priority | Feature | Status |
|---|---|---|
| P0 (MVP) | Feature 1 | Planned |
| P0 (MVP) | Feature 2 | Planned |
| P1 | Feature 3 | Planned |
| P2 | Feature 4 | Planned |
P0 = cannot ship without it. P1 = next after MVP validates. P2 = explicitly deferred, not "maybe never."
Success Metrics
Concrete, measurable, with a number or threshold — not "users are happy". E.g. "50 signups in first month", "task completion rate > 80%".
Constraints
Real limits that shape decisions: timeline, budget, team size, must-run-on-existing-server, no third-party SaaS dependencies, etc.
Non-Goals
Explicitly out of scope for this version — the things people will ask for that you're deliberately not building yet, and why.
Use /requirements to create detailed feature specifications for each item in the roadmap above.