Finland

Setup

If ~/finland/ doesn't exist or is empty, read setup.md and start naturally.

When to Use

User is planning a Finland trip and needs operational guidance beyond generic Nordic inspiration: Schengen entry checks, Helsinki vs Lapland route choice, rail-flight-car tradeoffs, winter or summer season fit, cost reality, and on-the-ground execution.

Architecture

Memory lives in ~/finland/. If ~/finland/ does not exist, run setup.md. See memory-template.md for structure.

~/finland/
└── memory.md     # Trip context, route logic, and evolving constraints

Quick Reference

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

Core Rules

1. Route by Season and Daylight, Not by the Map

Finland is manageable only when the month is fixed first. July city-hopping, September foliage, January aurora, and March family snow trips are different products, not interchangeable versions of the same route.

2. Confirm Entry and Border Friction Before Non-Refundables

Before locking flights, cabins, or night trains, use entry-and-documents.md and customs-and-border.md to confirm Schengen stay rules, visa pathway, passport validity, evolving EES/ETIAS requirements, and any overland border assumptions.

3. One Main Corridor Wins Most Trips

For short trips, choose one primary Finland logic:

• Helsinki and the south for city, design, food, and easy transit
• Lapland for aurora, snow, and winter activities
• Lakeland or archipelago for slower summer nature

4. Always Offer Two Transport Models

For any route beyond Helsinki, provide at least two workable patterns:

• Rail or flight heavy: lower winter-driving risk, more timetable dependence
• Self-drive or bus-heavy: more flexibility, more weather and fatigue exposure

5. Budget the Real Finland

Do not price from hotel headlines alone. Include airport transfers, sleeper-train supplements, winter clothing rental, sauna or spa costs, checked bags, cabin groceries, and restaurant or alcohol pricing.

6. Never Sell Aurora or Winter Fantasy as Guaranteed

Aurora is probability management, not certainty. Snow conditions, cloud cover, daylight hours, and school-holiday crowds change what is smart, especially in Lapland.

7. Deliver Operational Plans

Output should include:

• Best base or base pair
• Day-by-day flow with realistic transfer windows
• Booking deadlines or sellout risks
• Weather downgrade options
• Safety and emergency quick notes

Common Traps

• Treating Helsinki and Lapland as a casual add-on in a very short trip.
• Assuming winter is romantic by default without checking darkness, cold tolerance, and clothing strategy.
• Choosing a rental car before checking whether train, bus, or one guided base solves the trip better.
• Thinking summer midnight sun means infinite energy and no pacing consequences.
• Building archipelago or lake trips without checking ferry frequency and shoulder-season reductions.
• Carrying a U.S.-style tipping mindset into a mostly service-included culture.
• Promising border, visa, or EES/ETIAS details from memory instead of verifying current rules.

Security & Privacy

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

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

Related Skills

Install with clawhub install <slug> if user confirms:

• travel — General trip planning and itinerary structure
• booking — Reservation workflows and confirmation hygiene
• car-rental — Better self-drive strategy and handoff logistics
• food — Deeper restaurant and cuisine planning
• english — Language support for bookings, menus, and practical interactions

Feedback

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