You've shipped the walkthrough project. From here, the repo's docs/ folder (30 reference documents, kept in sync with the code) answers the "how do I..." questions. This page is the map.
When you need X, read Y
| You want to... | Read (in the repo) |
|---|---|
| Take real money with Stripe | docs/BILLING.md |
| Run credits-only, no Stripe ever | docs/recipes/credit-only-mode.md |
| Understand the whole architecture | docs/ARCHITECTURE.md |
| Add Google / GitHub login buttons | docs/SOCIAL_LOGIN.md |
| Send webhooks to your users | docs/EVENTS.md + docs/webhooks/ (verifier samples in Python, Node, PHP, Go) |
| Handle jobs that take minutes (transcription, generation) | docs/LONG_RUNNING_ENDPOINTS.md |
| Add scheduled/cron work | docs/SCHEDULED_TASKS.md |
| Harden security before launch | docs/SECURITY.md |
| Understand rate limits and audit logs | docs/RATE_LIMIT_AND_AUDIT.md |
| Watch errors and performance | docs/OBSERVABILITY.md |
| Deprecate an endpoint without breaking users | docs/EXTENSION_POINTS.md |
| Translate the UI (incl. RTL) | docs/I18N.md |
| Scale past your first server | docs/SCALING.md + docs/DEPLOYMENT.md |
| Pull template updates into your fork | UPGRADING.md |
Each doc states what exists in code versus what's a recipe. They're audited against the codebase file by file (28 documents, line-referenced), so when a doc says "returns 410 after sunset", the code does that.
Working with AI on this codebase
The repo ships 673 lines of CLAUDE.md: the endpoint authoring recipe, five worked endpoints to copy, an 11-row lookup table naming the module that answers each common question, and the boundary marking the fourteen framework apps an agent must not edit. Open the repo in Claude Code and it is loaded already; see Open It in Claude Code for the orientation prompt and how to tell a good answer from a bad one. The fastest builders on this template treat every endpoint as: describe it, check four things, reload.
Getting help
- Bugs in the template: open a GitHub issue on the repo.
- Questions: the LearnWithHasan community. Show what you tried; you'll get further faster.
- Updates: watch the repo on GitHub, and
git pullwhen the CHANGELOG says there's something for you.[SECURITY]entries are pull-within-a-week.
Now go build the thing you actually bought this for. One class at a time.