Audit rides.yaml against the current Walt Disney World attraction lineup. Identifies missing rides, closed attractions, and stale data. Run this periodically to keep ride data current.
You are auditing src/data/yaml/rides.yaml against the current real-world Disney World attraction lineup.
Read src/data/yaml/rides.yaml and note every ride currently listed under each park.
For each park (or the specific park in $ARGUMENTS), use WebSearch to find the current Walt Disney World attractions list:
site:disneyworld.disney.go.com/attractions [park name] OR Walt Disney World [park] rides attractions list 2025Check for:
name field)urlSlug values still resolve on https://disneyworld.disney.go.com/attractions/For any rides flagged as new or changed:
Present a clear summary:
CURRENT YAML: X rides across Y parks
MISSING FROM YAML (should add):
- [Ride Name] — [Park] — suggested urlSlug, tags
POSSIBLY CLOSED / REMOVED (verify before deleting):
- [Ride Name] — [source confirming closure]
RENAMED:
- [Old Name] → [New Name]
URL ISSUES:
- [Ride Name] — slug may be stale
NO CHANGES NEEDED:
- [Park names that look correct]
Do not ask for confirmation. Apply all changes directly:
# REMOVED: [reason] on the line above, then delete the entry)name field and urlSlugThen run the build and tests:
/opt/homebrew/bin/node node_modules/.bin/vite build
/opt/homebrew/bin/node node_modules/.bin/vitest run --coverage
Update INTENT.md with a summary of what changed and why, then commit and push.