Argentina

Setup

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

When to Use

User is planning an Argentina trip and needs practical guidance beyond generic inspiration: entry rules, money and payments, region choice, flight and road logic, park access, safety, and day-to-day execution.

Architecture

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

~/argentina/
└── memory.md     # Trip context and evolving constraints

Quick Reference

Use this map to jump into the right decision module before building the route.

Core Rules

1. Route by Macro-Region, Not by Map Fantasy

For short trips, pick one anchor cluster and one contrast region at most. Argentina is long enough that "just add Iguazu or Patagonia" can destroy the experience.

2. Lock Entry and Money Before Non-Refundables

Before buying flights, confirm the correct entry path, the length of stay, border-hop implications, and the payment strategy for cards, cash, and park tickets.

3. Ask for Month First

Argentina changes dramatically by season. Patagonia, Iguazu, Mendoza, and the northwest should never be planned with one generic weather assumption.

4. Treat Patagonia as Multiple Trips

Lake District, South Patagonia, and Ushuaia are different products with different transport and weather logic. Do not merge them casually.

5. Always Offer Two Transport Models

For each route, give at least two practical options with tradeoffs:

• Flight-heavy: faster, fewer overnight transfers, more airport friction
• Road/bus-heavy: slower, more scenery, more fatigue and weather sensitivity

6. Budget with Friction, Not Headlines

Argentina trip quality often depends more on transfer costs, excursion timing, airport changes, and card/cash execution than on the hotel sticker price.

7. Deliver Action Plans

Output should include:

• Base-city strategy
• Day-by-day flow with transfer buffers
• Booking deadlines or low-inventory warnings
• Weather fallback or alternate plan
• Safety, payment, and emergency notes

Common Traps

• Buenos Aires + Mendoza + Iguazu + Patagonia in one short trip.
• Assuming Patagonia is one interchangeable region.
• Planning with old exchange-rate blog posts instead of current official references.
• Ignoring cross-border implications when adding the Brazilian side of Iguazu or Chile crossings.
• Using overnight buses or same-day airport changes without buffer.
• Choosing accommodation by nightly rate only and losing hours to transfers.
• Treating national park access as fully spontaneous in peak season.

Security & Privacy

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

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

Related Skills

Install with clawhub install \x3Cslug> if user confirms:

• travel — General trip planning and itinerary structure
• car-rental — Better rental strategy and handoff logistics
• booking — Reservation workflows and confirmation hygiene
• food — Deeper restaurant and cuisine recommendations
• spanish — Language support for bookings, transport, and service interactions

Feedback

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