Sweden

Setup

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

When to Use

User is planning a Sweden trip and needs operational guidance beyond generic Nordic advice: Schengen entry checks, Stockholm versus west coast versus Lapland routing, rail-flight-car tradeoffs, season fit, budget reality, and on-the-ground execution.

Architecture

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

~/sweden/
└── memory.md     # Trip context, constraints, booking status, and route decisions

Quick Reference

Core Rules

1. Route by Corridor, Not by Flag Count

For short trips, choose one main Sweden corridor: Stockholm and archipelago, west coast, south via Skane, central lake country, or Lapland. Sweden looks simple on a map but quality drops fast when every region becomes a stop.

2. Ask for Month Before Naming a Route

The correct Sweden plan changes radically by month. Daylight, snow cover, ferry frequency, archipelago service, aurora chances, swimming weather, and road safety all depend on season.

3. Confirm Schengen Math Before Locking Plans

Use entry-and-documents.md first for passport validity, Schengen day counting, EES rollout context, and whether the user is mixing Sweden with Denmark, Norway, Finland, or the Baltics.

4. Always Offer Two Transport Models

For any multi-stop trip, provide at least two viable patterns:

• Rail and ferry heavy: lower winter driving risk, more timetable dependence
• Flight or self-drive heavy: more reach, higher transfer or weather friction

5. Budget with Sweden Reality

Do not price from hotel headlines alone. Include airport transfer costs, rail supplements, island ferries, car parking, winter gear, restaurant alcohol, and shoulder-season opening patterns.

6. Protect the User from Nordic Overreach

Flag bad combinations early:

• Stockholm, Gothenburg, Gotland, and Lapland in one week
• Lapland winter trips without darkness or cold tolerance
• Summer archipelago or Midsummer travel booked too late
• Cross-border south-Sweden plans that ignore passport or ID checks

7. Deliver Operational Plans

Output should include:

• Best base or base pair
• Day-by-day flow with realistic transfer windows
• Booking deadlines or low-inventory warnings
• Weather backup and downgrade options
• Safety notes for cold, ferries, and remote areas

Common Traps

• Treating Sweden as a compact city-break country where south, center, and far north fit naturally into one short itinerary.
• Assuming Schengen admin is trivial because the first arrival point is not Sweden.
• Choosing a rental car before checking whether rail plus one strategic base solves the trip better.
• Planning Lapland around aurora certainty instead of darkness, forecast, and backup activities.
• Ignoring ferry or island timetables in the archipelago and on Gotland.
• Underestimating how much alcohol, dining, and airport transfers move the real budget.
• Booking scenic summer trips without checking that some services are sharply seasonal.

Security & Privacy

Data that stays local: Trip preferences in ~/sweden/

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

Related Skills

Install with clawhub install <slug> if user confirms:

• travel — General trip planning and itinerary structure
• europe — Broader Schengen and multi-country Europe planning
• booking — Reservation workflows and total-cost booking hygiene
• food — Deeper restaurant and cuisine planning
• english — Language support for bookings and practical interactions

Feedback

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