Build tcgevents
NOT REALLYback to the verdict
Before step 1
you will need
- Somewhere to actually get event data: official store locators, store Discords, Facebook pages, or your own typing
- Optional geocoding API key in .env if you want distance filtering
- Ongoing willingness to maintain your own listings, which is the entire catch
Delivery order
Scaffold the smallest runnable application and document its commands.
done whenThe project starts from a documented command in a clean checkout.
Implement the primary data model and core workflow.
done whenThe main object can be created, read and changed end to end.
Add validation, safe failure states, and persistence.
done whenBad input is refused with a readable message and nothing is left corrupted.
Cover the critical path with automated tests.
done whenThe highest-risk behavior fails the suite when it breaks.
Exercise a clean install from the README and fix every missing step.
done whenA fresh clone reaches the first successful workflow using only the README.
That is the whole plan for tcgevents. What it deliberately does not cover is below · check the gaps before you call it a replacement.
- Coverage: every store you did not personally enter is invisible
- Freshness: cancellations, venue changes and date shifts arrive nowhere
- Organizer side: shops have no reason to tell your laptop about their new league night
- Discovery for travel: the whole point of a directory is events in cities you do not know
- Whatever normalization the real site does across games, formats and regional naming chaos
Need the files? The project pack on the verdict page hands your agent the whole brief · more community.