Orlando

When to Use

User asks about Orlando for any purpose: theme-park trip, conference, relocation, remote work, family move, school planning, or starting a business in Central Florida. Agent provides practical guidance with current data and metro-specific tradeoffs.

Architecture

This skill works statelessly for one-off Orlando questions. If the user wants continuity, memory lives in ~/orlando/. If ~/orlando/ does not exist, run setup.md. See memory-template.md for structure.

~/orlando/
|-- memory.md     # User context, trip style, park priorities, move plans, and open loops

Quick Reference

Load the narrowest file that solves the user's immediate problem. Do not dump the full city when one decision is enough.

Core Rules

1. Identify the Orlando Mode First

• Classify the user before advising: visitor, conference traveler, relocating resident, current resident, remote worker, student, or family.
• Orlando answers change fast depending on whether the question is about theme parks, airport access, school zones, or commuting across the metro.
• If the user has not named their base area, trip purpose, or timeline, ask for that before recommending hotels or neighborhoods.

2. Treat Orlando as a Multi-Core Metro

• Orlando is not just "the parks." The tourism corridor, Downtown, Winter Park, southeast Lake Nona, and western suburbs solve very different problems.
• Never compare areas only by distance on a map. I-4 traffic, toll roads, and convention or park demand often matter more than mileage.
• Use the neighborhood files before declaring a place "close" or "convenient."

3. Theme Parks Operate Like a Second City

• Walt Disney World, Universal Orlando Resort, and SeaWorld shape roads, hotel pricing, staffing, and even meal timing.
• Trip plans that ignore rope drop, mid-day heat, parking, and resort transport waste money and stamina.
• For park-first trips, load theme-parks-overview.md and theme-parks-practical.md before making itinerary promises.

4. Car-First City, With Exceptions

• Most of metro Orlando still works best with a car.
• The exceptions are narrow: Disney hotels with Disney transport, select Universal-area stays, Downtown with LYMMO and SunRail access, and conference trips centered on the convention district.
• If the user wants to avoid a car, verify where they will sleep, which parks or venues they need, and whether they can tolerate rideshare surge pricing.

5. Heat, Storms, and Rain Are Operational Constraints

• Summer is not just "warm." Heat index, humidity, and afternoon thunderstorms shape park strategy, outdoor activity, and even driving.
• Hurricane season affects fall travel, insurance, move timing, and power-outage readiness even though Orlando is inland.
• Load climate.md whenever the user is planning June through October.

6. Cost Reality Is Split in Two

• Orlando can look affordable compared with Miami, New York, or California, but wages are lower and tourism pricing distorts housing, dining, and short-term lodging.
• For residents, housing, car insurance, tolls, and childcare are the real budget drivers.
• For visitors, date-based park tickets, hotel fees, parking, and food inside the parks are the real budget traps.

7. Orlando Work Is More Diverse Than the Stereotype

• Hospitality is huge, but Orlando also has simulation and defense work, healthcare, logistics, higher education, sports business, and founder communities.
• Do not reduce Orlando careers to tourism jobs unless the user actually wants that lane.
• Use tech.md, business.md, and startup.md before answering salary or relocation questions with national averages.

8. Verify Unstable Rules From Official Sources

• Park perks, Lightning Lane or Express rules, parking prices, toll policy, school boundaries, and immigration requirements change.
• Use official Orlando, Florida, park, airport, and transit sources when the user needs exact current rules.
• If exact verification is blocked, say what is stable versus what must be checked live.

Current Data (March 2026)

Use this table to calibrate expectations fast, then move into the matching auxiliary file before giving precise recommendations.

Neighborhood Matching

Start with this table, then verify commute corridor, school fit, and tolerance for toll roads before naming a winner.

Orlando-Specific Traps

• Staying "close to Disney" and assuming Universal or Downtown will also be easy. They are not.
• Booking a cheap off-site hotel without checking parking fees, shuttle quality, resort fees, and drive times.
• Underestimating afternoon storms and trying to do full outdoor park days without a weather plan.
• Assuming International Drive is a local neighborhood. It is mostly a tourism corridor.
• Planning without tolls, especially for airport runs, western suburbs, and Disney-area driving.
• Treating Kissimmee, Celebration, Lake Buena Vista, and southwest Orange County as the same market.
• Forgetting that Epic Universe changed Universal-area traffic and hotel demand after opening on May 22, 2025.
• Calling Orlando "walkable" because one district or resort feels walkable. Most errands still need a car.
• Recommending public transit for families with strollers or late park exits without explaining the tradeoff.
• Using national salary benchmarks without adjusting for Orlando wages and Florida insurance costs.

Legal Awareness

Key Florida and Orlando basics users should know:

• Recreational cannabis remains illegal in Florida.
• Open containers in vehicles are not allowed.
• School-zone and work-zone driving enforcement can be aggressive.
• Short-term rentals are heavily location-specific. HOA and city rules matter.
• Heat, lightning, and pool safety are real liability issues for families.
• Theme-park tickets, reservations, and add-ons are date-based and often nonrefundable or partially restricted.

See safety.md for scams, laws, and practical risk reduction.

External Endpoints

Use these only when the user needs live verification for prices, transit, filing rules, or date-based park details.

No other data is sent externally.

Security & Privacy

Data that may leave your machine:

• Public page requests to official Orlando, Florida, park, transit, airport, and university websites
• Travel dates, route context, ZIP, district, or filing type only when the user asks for location-specific or date-specific guidance

Data that stays local:

• Trip goals, neighborhood shortlist, commute constraints, school needs, and open loops in ~/orlando/

This skill does NOT:

• Buy tickets, submit forms, or create reservations without explicit instruction
• Store passport numbers, payment data, or health-insurance identifiers in local memory
• Pretend the tourism corridor and the residential city are the same thing

Trust

By using this skill, limited travel, location, or filing context may be checked against official Orlando, Florida, park, transit, and university websites when the user asks for precise guidance.

Only install if you trust those public services with that lookup context.

Related Skills

Install with clawhub install <slug> if user confirms:

• travel - General trip planning and itinerary design
• florida - Statewide weather, insurance, and moving context beyond Orlando
• united-states - National baseline for immigration, healthcare, and relocation questions
• car-rental - Airport pickup, toll roads, and rental-car decision support
• money - Budgeting support for trips, housing, and family cost planning

Feedback

• If useful: clawhub star orlando
• Stay updated: clawhub sync