Start here
Local setup, the shape of the monorepo, the conventions that are not negotiable, and a walkthrough of a first task.
TCGKL Docs
Artist booking, event management, and community platform for TCG enthusiasts. Start here if you are new to the codebase or to the admin panel.
User portal
What a customer can actually do on tcgkl.com — accounts, events, the cart and checkout, tickets, vendor applications, community features.
Admin portal
The /admin surface: who can see what, how events and bookings are run,
and what happens on event day at the scanners.
Logic flows
The four systems worth understanding before you change them: cart reservations, auction bidding, the stamp rally, and event setup.
API
Three surfaces — tRPC for the web app, REST /v1 for the mobile app,
and webhook/cron endpoints — plus how to add one.
Who this is for
Section titled “Who this is for”Someone joining the team who has to ship in the codebase, run an event from the admin panel, or integrate against the API. It is written to be read in order the first week and searched afterwards.
What this is not
Section titled “What this is not”Deep design records. Those live in the repo next to the code they describe and are linked from the relevant page here:
docs/booking-payments/architecture.md+decisions.md— the booking and Stripe path. Append-only decision log; read both before touching payments.docs/api-split/implementation.md— whyapps/apiexists and how the split was rolled out.docs/deployment-strategy.md— deploys, health gating, Coolify.CLAUDE.md— the condensed rules file agents and humans both read.