Switzerland

Setup

If ~/switzerland/ does not exist or is empty, read setup.md and start naturally.

When to Use

User is planning a Switzerland trip and needs operational guidance beyond postcard advice: Schengen entry checks, CHF cost reality, rail vs car tradeoffs, scenic-train and mountain timing, region choice, and on-the-ground execution.

Architecture

Memory lives in ~/switzerland/. See memory-template.md for structure.

~/switzerland/
└── memory.md     # Trip context, routing logic, and evolving constraints

Quick Reference

Use this map to load only the Switzerland subtopic that changes the decision in front of you.

Core Rules

1. Route by Corridor, Not by Pin Count

For short trips, choose one dominant Switzerland shape: Zurich and Central Switzerland, Bernese Oberland, Lake Geneva, Valais, Graubunden, Ticino, or Basel and Jura. Scenic density is high, but hotel changes, lifts, and transfer friction still punish over-routing.

2. Ask for Month and Altitude Tolerance Before Naming the Best Region

The same Switzerland plan changes meaning in February, June, September, and December. Snow line, lake appeal, hiking access, daylight, and school-holiday demand can make a famous route smart or wasteful.

3. Default to Rail, Add a Car Only When It Clearly Improves Execution

Classic visitor routes are usually better by train and boat. Car value appears when the trip is built around rural lakes, remote valleys, low-frequency villages, or border-heavy driving loops.

4. Treat Mountains as Logistics, Not Background

Use alps-lakes-and-scenic-trains.md, winter-ski-and-snow.md, and weather-and-seasonality.md before promising panoramic days. Cloud, wind, snow, avalanche controls, and pass closures can change the whole plan.

5. Budget With Real Swiss Friction

Do not price from hotel headlines alone. Include CHF reality, resort taxes, lift tickets, seat reservations where relevant, parking, tunnel or pass detours, luggage handling, and mountain food premiums.

6. Protect the User From Border and Sunday Mistakes

Switzerland sits inside Schengen but outside the EU customs and roaming default that many travelers assume. Border shopping, tax-free steps, Sunday closures, and cross-border train or car choices need explicit handling.

7. Deliver Operational Plans

Output should include:

• Best base or base pair
• Day-by-day flow with realistic transfer windows
• Booking deadlines or low-availability warnings
• Weather downgrade options
• Safety, payment, and emergency notes

Common Traps

• Treating Switzerland like a small country that can be "done" in a few rail hops.
• Mixing Zurich, Lucerne, Jungfrau, Zermatt, St. Moritz, Lake Geneva, and Ticino into one short trip.
• Booking a car before checking whether SBB plus one local bus or boat solves the route better.
• Assuming the mountain weather shown in marketing photos is the weather the user will get.
• Building scenic-train days as if they were quick transfers instead of full-day experiences.
• Underestimating how hard peak summer and ski-season hotel pricing hits famous alpine bases.
• Assuming EU roaming, EU customs, and euro pricing rules apply automatically in Switzerland.

Security & Privacy

Data that stays local: Trip preferences, route decisions, and deadlines in ~/switzerland/

This skill does NOT: Access files outside ~/switzerland/ or make network requests.

Memory rule: Keep local trip notes only when the user is doing ongoing Switzerland planning or clearly wants continuity across sessions. For one-off answers, help without creating extra trip memory.

Related Skills

Install with clawhub install <slug> if user confirms:

• travel — General trip planning and itinerary structure
• europe — Better wider-Europe context when Switzerland is part of a longer route
• booking — Reservation workflows and confirmation hygiene
• car-rental — Better self-drive strategy and handoff logistics
• food — Deeper restaurant and cuisine planning

Feedback

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