Skip to content

docs: product-first README rewrite with live screenshot - #2

Merged
HazzJC merged 1 commit into
mainfrom
readme/product-focused-rewrite
Sep 14, 2026
Merged

HazzJC merged 1 commit into
mainfrom
readme/product-focused-rewrite

Conversation

@HazzJC

@HazzJC HazzJC commented Sep 14, 2026

Copy link
Copy Markdown
Owner

Summary

Part of a broader GitHub profile improvement pass (task H02a). This repo's README led with a long feature list rather than a clear statement of the problem it solves, so this PR rewrites it to front-load, in order:

  1. A one-sentence problem statement and who it's for
  2. A screenshot of the live app (captured fresh from the deployed site, saved to docs/screenshot.png)
  3. The live demo link
  4. The product decisions behind the architecture (why guests don't need accounts, why Pick does, host-only cookie auth, shared game metadata, graceful degradation without third-party API keys)
  5. A brief, accurate architecture/solution summary matching the actual code (Next.js App Router + TypeScript + Prisma/PostgreSQL, src/lib/match-scoring.ts, etc.)
  6. Honest quality evidence: 163 passing Vitest tests across 50 files, a GitHub Actions CI workflow (.github/workflows/quality.yml) that runs test/lint/build on every PR and push to main, and an explicit note that there's no end-to-end/browser test suite yet
  7. Setup/local dev instructions — verified by running npm install and npm test fresh from a clean clone (163/163 passing)
  8. Current limitations and project status (single-maintainer side project, no PlayStation library API, Discord reminder cadence limits on the Vercel Hobby plan, etc.)
  9. Attribution/data provenance (IGDB, Steam Web API, IsThereAnyDeal) and current licensing status — the repo has no LICENSE file, which is stated plainly rather than assuming or inventing a license; a separate licensing pass will address that.

No other repo settings were touched (visibility, topics, pins, account settings are out of scope for this change).

Test plan

  • Cloned the repo fresh and ran npm install + npm test — 163/163 tests passed
  • Reviewed .github/workflows/quality.yml to confirm CI runs test/lint/build
  • Visited the live deployment and walked through the "Plan a night" flow to confirm the README's description matches actual behavior
  • Captured the embedded screenshot directly from the live deployment
  • npm run build against a real Postgres database was not re-verified in this pass (no database was provisioned for this change) — CI already covers this on every push

🤖 Generated with Claude Code

Part of a GitHub profile improvement pass (task H02a). The previous README
led with feature lists rather than a clear problem statement, so this
rewrite front-loads: what problem the app solves and for whom, a screenshot
and live demo link, the product decisions behind the architecture, an
honest account of test/CI coverage (163 passing Vitest tests, no e2e yet),
verified local setup steps, current limitations, and data provenance/
licensing status (no LICENSE file yet — left for a separate pass).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@vercel

vercel Bot commented Sep 14, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
what-should-we-play Ready Ready Preview Sep 14, 2026 12:00pm UTC

@HazzJC
HazzJC merged commit 5c2f35f into main Sep 14, 2026
3 checks passed

This branch was successfully deployed

1 active deployment
Preview — b847d6aa Deployed Sep 14, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant