Vibecode tcgevents
track this build5 steps, step by step0%NOT REALLY · don't bother
The software here is a searchable list with a map and some filters, which an agent can produce before your coffee cools. The product is not the list, it is the fact that events are in it: store owners posting schedules, organizers keeping dates current, players trusting it enough to check it weekly. Scrape it and you own a snapshot that starts rotting the moment a shop moves its Friday night draft. Official publisher locators exist, but they are partial, rate limited, and hostile to bulk use, and the small local scene stuff never appears there at all. Build the personal tracker if you play in two cities, but do not pretend it replaces the directory.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of tcgevents. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # tcgevents indie build ## Goal Build the smallest trustworthy replacement for the core tcgevents workflow for one developer or a tiny team. ## Scope A local event tracker where you paste or manually add tournaments, then browse them by game, date and distance with calendar and ICS export. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 If those capabilities are essential, use tcgevents instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a local-first trading card game event tracker. Single Python project, no accounts, no cloud, no telemetry. Stack, non negotiable: - Python 3.11, FastAPI, Jinja2 templates, SQLite via sqlite3 stdlib - Plain server rendered HTML plus a little vanilla JS, no build step, no npm - Leaflet from a CDN for the map, OpenStreetMap tiles Data model (events): id, game (magic, pokemon, yugioh, lorcana, other), title, format, venue_name, address, city, country, lat, lon, starts_at (UTC), ends_at nullable, entry_fee nullable, url nullable, notes, source (manual or paste), created_at, updated_at. Also a settings row for home_lat, home_lon, default_radius_km. Features, in scope: 1. Add and edit events through a simple HTML form. Manual entry is the primary path, treat it as first class. 2. A "paste dump" page: textarea where I paste messy text from a store Discord or Facebook post, plus a parser that extracts candidate title, date, time and fee with regex and dateutil, then shows an editable pre-filled form. No LLM call. If parsing fails, say so and let me fill it in. 3. List view: filter by game, date range, city, and distance from home using haversine on stored lat/lon. Sort by starts_at. 4. Map view: pins for filtered events, popup with title, time, venue, link. 5. Calendar: current month grid, events per day. 6. Export: /export.ics returns a valid VCALENDAR of the current filter. Also /export.json. 7. Geocoding: optional. If GEOCODE_PROVIDER and GEOCODE_API_KEY are set in .env, geocode addresses on save; otherwise leave lat/lon null and hide distance filters gracefully. 8. Recurring events: a weekly repeat option that materializes the next 8 occurrences, each editable and cancellable individually. Out of scope, do not build: user accounts, multi tenancy, scraping any third party site, push notifications, a mobile app, anything that pretends to have nationwide coverage. Deliverables: app.py, db.py, parse.py, templates/, static/, schema.sql, .env.example, seed.py with 12 fake events across 3 cities, and a README with run instructions (uvicorn, one command). Include pytest tests for the parser and the ICS output. Timezones: store UTC, display in a TZ set in .env, default America/New_York. ## Required capabilities - 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 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of tcgevents. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # tcgevents indie build ## Goal Build the smallest trustworthy replacement for the core tcgevents workflow for one developer or a tiny team. ## Scope A local event tracker where you paste or manually add tournaments, then browse them by game, date and distance with calendar and ICS export. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 If those capabilities are essential, use tcgevents instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a local-first trading card game event tracker. Single Python project, no accounts, no cloud, no telemetry. Stack, non negotiable: - Python 3.11, FastAPI, Jinja2 templates, SQLite via sqlite3 stdlib - Plain server rendered HTML plus a little vanilla JS, no build step, no npm - Leaflet from a CDN for the map, OpenStreetMap tiles Data model (events): id, game (magic, pokemon, yugioh, lorcana, other), title, format, venue_name, address, city, country, lat, lon, starts_at (UTC), ends_at nullable, entry_fee nullable, url nullable, notes, source (manual or paste), created_at, updated_at. Also a settings row for home_lat, home_lon, default_radius_km. Features, in scope: 1. Add and edit events through a simple HTML form. Manual entry is the primary path, treat it as first class. 2. A "paste dump" page: textarea where I paste messy text from a store Discord or Facebook post, plus a parser that extracts candidate title, date, time and fee with regex and dateutil, then shows an editable pre-filled form. No LLM call. If parsing fails, say so and let me fill it in. 3. List view: filter by game, date range, city, and distance from home using haversine on stored lat/lon. Sort by starts_at. 4. Map view: pins for filtered events, popup with title, time, venue, link. 5. Calendar: current month grid, events per day. 6. Export: /export.ics returns a valid VCALENDAR of the current filter. Also /export.json. 7. Geocoding: optional. If GEOCODE_PROVIDER and GEOCODE_API_KEY are set in .env, geocode addresses on save; otherwise leave lat/lon null and hide distance filters gracefully. 8. Recurring events: a weekly repeat option that materializes the next 8 occurrences, each editable and cancellable individually. Out of scope, do not build: user accounts, multi tenancy, scraping any third party site, push notifications, a mobile app, anything that pretends to have nationwide coverage. Deliverables: app.py, db.py, parse.py, templates/, static/, schema.sql, .env.example, seed.py with 12 fake events across 3 cities, and a README with run instructions (uvicorn, one command). Include pytest tests for the parser and the ICS output. Timezones: store UTC, display in a TZ set in .env, default America/New_York. ## Required capabilities - 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 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of tcgevents. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # tcgevents product brief ## Problem The software here is a searchable list with a map and some filters, which an agent can produce before your coffee cools. The product is not the list, it is the fact that events are in it: store owners posting schedules, organizers keeping dates current, players trusting it enough to check it weekly. Scrape it and you own a snapshot that starts rotting the moment a shop moves its Friday night draft. Official publisher locators exist, but they are partial, rate limited, and hostile to bulk use, and the small local scene stuff never appears there at all. Build the personal tracker if you play in two cities, but do not pretend it replaces the directory. ## Product outcome A local event tracker where you paste or manually add tournaments, then browse them by game, date and distance with calendar and ICS export. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - 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 ## Explicit non-goals for v1 - 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 ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build a local-first trading card game event tracker. Single Python project, no accounts, no cloud, no telemetry. Stack, non negotiable: - Python 3.11, FastAPI, Jinja2 templates, SQLite via sqlite3 stdlib - Plain server rendered HTML plus a little vanilla JS, no build step, no npm - Leaflet from a CDN for the map, OpenStreetMap tiles Data model (events): id, game (magic, pokemon, yugioh, lorcana, other), title, format, venue_name, address, city, country, lat, lon, starts_at (UTC), ends_at nullable, entry_fee nullable, url nullable, notes, source (manual or paste), created_at, updated_at. Also a settings row for home_lat, home_lon, default_radius_km. Features, in scope: 1. Add and edit events through a simple HTML form. Manual entry is the primary path, treat it as first class. 2. A "paste dump" page: textarea where I paste messy text from a store Discord or Facebook post, plus a parser that extracts candidate title, date, time and fee with regex and dateutil, then shows an editable pre-filled form. No LLM call. If parsing fails, say so and let me fill it in. 3. List view: filter by game, date range, city, and distance from home using haversine on stored lat/lon. Sort by starts_at. 4. Map view: pins for filtered events, popup with title, time, venue, link. 5. Calendar: current month grid, events per day. 6. Export: /export.ics returns a valid VCALENDAR of the current filter. Also /export.json. 7. Geocoding: optional. If GEOCODE_PROVIDER and GEOCODE_API_KEY are set in .env, geocode addresses on save; otherwise leave lat/lon null and hide distance filters gracefully. 8. Recurring events: a weekly repeat option that materializes the next 8 occurrences, each editable and cancellable individually. Out of scope, do not build: user accounts, multi tenancy, scraping any third party site, push notifications, a mobile app, anything that pretends to have nationwide coverage. Deliverables: app.py, db.py, parse.py, templates/, static/, schema.sql, .env.example, seed.py with 12 fake events across 3 cities, and a README with run instructions (uvicorn, one command). Include pytest tests for the parser and the ICS output. Timezones: store UTC, display in a TZ set in .env, default America/New_York. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted tcgevents capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# tcgevents indie build ## Goal Build the smallest trustworthy replacement for the core tcgevents workflow for one developer or a tiny team. ## Scope A local event tracker where you paste or manually add tournaments, then browse them by game, date and distance with calendar and ICS export. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 If those capabilities are essential, use tcgevents instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build a local-first trading card game event tracker. Single Python project, no accounts, no cloud, no telemetry. Stack, non negotiable: - Python 3.11, FastAPI, Jinja2 templates, SQLite via sqlite3 stdlib - Plain server rendered HTML plus a little vanilla JS, no build step, no npm - Leaflet from a CDN for the map, OpenStreetMap tiles Data model (events): id, game (magic, pokemon, yugioh, lorcana, other), title, format, venue_name, address, city, country, lat, lon, starts_at (UTC), ends_at nullable, entry_fee nullable, url nullable, notes, source (manual or paste), created_at, updated_at. Also a settings row for home_lat, home_lon, default_radius_km. Features, in scope: 1. Add and edit events through a simple HTML form. Manual entry is the primary path, treat it as first class. 2. A "paste dump" page: textarea where I paste messy text from a store Discord or Facebook post, plus a parser that extracts candidate title, date, time and fee with regex and dateutil, then shows an editable pre-filled form. No LLM call. If parsing fails, say so and let me fill it in. 3. List view: filter by game, date range, city, and distance from home using haversine on stored lat/lon. Sort by starts_at. 4. Map view: pins for filtered events, popup with title, time, venue, link. 5. Calendar: current month grid, events per day. 6. Export: /export.ics returns a valid VCALENDAR of the current filter. Also /export.json. 7. Geocoding: optional. If GEOCODE_PROVIDER and GEOCODE_API_KEY are set in .env, geocode addresses on save; otherwise leave lat/lon null and hide distance filters gracefully. 8. Recurring events: a weekly repeat option that materializes the next 8 occurrences, each editable and cancellable individually. Out of scope, do not build: user accounts, multi tenancy, scraping any third party site, push notifications, a mobile app, anything that pretends to have nationwide coverage. Deliverables: app.py, db.py, parse.py, templates/, static/, schema.sql, .env.example, seed.py with 12 fake events across 3 cities, and a README with run instructions (uvicorn, one command). Include pytest tests for the parser and the ICS output. Timezones: store UTC, display in a TZ set in .env, default America/New_York. ## Required capabilities - 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 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# tcgevents product brief ## Problem The software here is a searchable list with a map and some filters, which an agent can produce before your coffee cools. The product is not the list, it is the fact that events are in it: store owners posting schedules, organizers keeping dates current, players trusting it enough to check it weekly. Scrape it and you own a snapshot that starts rotting the moment a shop moves its Friday night draft. Official publisher locators exist, but they are partial, rate limited, and hostile to bulk use, and the small local scene stuff never appears there at all. Build the personal tracker if you play in two cities, but do not pretend it replaces the directory. ## Product outcome A local event tracker where you paste or manually add tournaments, then browse them by game, date and distance with calendar and ICS export. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - 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 ## Explicit non-goals for v1 - 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 ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build a local-first trading card game event tracker. Single Python project, no accounts, no cloud, no telemetry. Stack, non negotiable: - Python 3.11, FastAPI, Jinja2 templates, SQLite via sqlite3 stdlib - Plain server rendered HTML plus a little vanilla JS, no build step, no npm - Leaflet from a CDN for the map, OpenStreetMap tiles Data model (events): id, game (magic, pokemon, yugioh, lorcana, other), title, format, venue_name, address, city, country, lat, lon, starts_at (UTC), ends_at nullable, entry_fee nullable, url nullable, notes, source (manual or paste), created_at, updated_at. Also a settings row for home_lat, home_lon, default_radius_km. Features, in scope: 1. Add and edit events through a simple HTML form. Manual entry is the primary path, treat it as first class. 2. A "paste dump" page: textarea where I paste messy text from a store Discord or Facebook post, plus a parser that extracts candidate title, date, time and fee with regex and dateutil, then shows an editable pre-filled form. No LLM call. If parsing fails, say so and let me fill it in. 3. List view: filter by game, date range, city, and distance from home using haversine on stored lat/lon. Sort by starts_at. 4. Map view: pins for filtered events, popup with title, time, venue, link. 5. Calendar: current month grid, events per day. 6. Export: /export.ics returns a valid VCALENDAR of the current filter. Also /export.json. 7. Geocoding: optional. If GEOCODE_PROVIDER and GEOCODE_API_KEY are set in .env, geocode addresses on save; otherwise leave lat/lon null and hide distance filters gracefully. 8. Recurring events: a weekly repeat option that materializes the next 8 occurrences, each editable and cancellable individually. Out of scope, do not build: user accounts, multi tenancy, scraping any third party site, push notifications, a mobile app, anything that pretends to have nationwide coverage. Deliverables: app.py, db.py, parse.py, templates/, static/, schema.sql, .env.example, seed.py with 12 fake events across 3 cities, and a README with run instructions (uvicorn, one command). Include pytest tests for the parser and the ICS output. Timezones: store UTC, display in a TZ set in .env, default America/New_York. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted tcgevents capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
Because the alternative is checking six store Facebook pages, two Discords and a publisher locator that has not been updated since the last set rotation. Anyone paying here is paying for someone else to do the tedious aggregation and keep it current, or, if they are a store, paying to be seen by players who already have the habit of checking. Neither of those is a software problem. A self hosted clone gives you the interface and none of the reason to open it.
xCoverage: every store you did not personally enter is invisible
xFreshness: cancellations, venue changes and date shifts arrive nowhere
xOrganizer side: shops have no reason to tell your laptop about their new league night
xDiscovery for travel: the whole point of a directory is events in cities you do not know
xWhatever normalization the real site does across games, formats and regional naming chaos
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced tcgevents with one prompt"
Vibecode tcgevents
Not really. tcgevents's value is not the code: The moat is every local store that already posts its schedule there and every player who already checks. See the honest breakdown above.
How much does tcgevents cost?
tcgevents's pricing is usage-based or varies by plan · No subscription anywhere. Organisers pay 6.5% of the ticket price plus 0.25 EUR per ticket sold, taken via Stripe split payment. Chargeback handling fees of 3.50 EUR and 15.00 EUR also apply..
What do I lose by replacing tcgevents?
Honestly: 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. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to tcgevents?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.