# TTCS RailForge — Cloudflare + GitHub launch prompt

Use this prompt with a coding agent that has access to the GitHub repository and Cloudflare account.

```text
You are launching TTCS RailForge, a static one-page train card battler.

Repository and source of truth
- Work only in the existing GitHub repository.
- Inspect the repository before editing; preserve the existing build system and content unless the task explicitly requires a change.
- Do not invent credentials, payment URLs, train facts, deployment IDs, or environment variables.
- If a required value is missing, stop and report the exact value needed.

Product requirements
- Keep the title: TTCS RailForge.
- TTCS means “Train Type & Class Standard,” a fictional in-world certification for identity, era, and clearly labeled gameplay balance.
- Keep the historical reference window ending in 2002.
- Keep the $97 price, but do not claim checkout is live until a verified payment URL is supplied.
- Preserve the big central BATTLE button and the playable card selection/filter interactions.
- Preserve the real demo-deck download and its stat disclaimer.

Verification before deployment
1. Read package.json, the README, and any repository-specific instructions.
2. Run the project’s documented install/build checks using the existing package manager.
3. Validate every local asset path, including the header PNG, JSON download, and launch prompt.
4. Confirm the page renders with no blocking console or runtime errors.
5. Confirm the source cards are presented as a curated roster, not an exhaustive list.
6. Check that any factual train/date claim has a source link or is removed; never fill gaps from memory.
7. Check responsive layout at desktop and mobile widths.
8. Run git diff and review the exact files changed.

Cloudflare deployment
- Deploy the built static output to Cloudflare Pages or the project’s configured Cloudflare static host.
- Use the repository’s configured project and production branch; do not create a second project unless explicitly instructed.
- Do not change DNS or access settings without explicit approval.
- After deployment, inspect the deployment status and open the production URL.
- Report the production URL, commit SHA, build command, and any missing configuration.

Payments
- Before enabling the purchase button, set a verified checkout URL in the site’s documented configuration.
- Never use example.com, a guessed Stripe link, or a fake success state.
```