Setup
If ~/austria/ doesn't exist or is empty, read setup.md and start naturally.
When to Use
User is planning an Austria trip and needs practical guidance beyond generic inspiration: entry rules, region choice, rail vs car tradeoffs, mountain timing, city sequencing, food and culture context, and on-the-ground execution.
Architecture
Memory lives in ~/austria/. See memory-template.md for structure.
CODEBLOCK0
Quick Reference
Use this map to choose the right decision module before building the route.
| Topic | File |
|---|
| Entry, Border, and Money | |
| Tourist entry, visa, Schengen logic, IDs |
entry-and-documents.md |
| Customs, cash, food restrictions, border habits |
customs-and-border.md |
| Budget framing and hidden costs |
budget-and-costs.md |
| Cards, cash, tipping, tax-free basics |
tipping-and-payments.md |
|
Planning Backbone | |
| Region selection and route architecture |
regions.md |
| Sample itineraries for 4-14 days |
itineraries.md |
| Accommodation strategy by trip style |
accommodation.md |
|
Transport and Outdoors | |
| Rail, buses, airport links, route timing |
transport-domestic.md |
| Driving, vignette, winter equipment, mountain roads |
road-trips-and-driving.md |
| Alpine, lake, hiking, hut, and cable-car logic |
alps-lakes-and-outdoors.md |
| Winter sports, Christmas markets, thermal rhythm |
winter-ski-and-christmas.md |
| Border hops and nearby add-ons |
border-hops-and-day-trips.md |
|
Regions and Cities | |
| Vienna playbook |
vienna.md |
| Salzburg and Salzkammergut playbook |
salzburg-and-salzburgerland.md |
| Innsbruck and Tyrol playbook |
innsbruck-and-tyrol.md |
| Graz and Styria playbook |
graz-and-styria.md |
| Carinthia and lake districts playbook |
carinthia-and-lakes.md |
| Danube, Linz, and Wachau playbook |
danube-linz-and-wachau.md |
|
Lifestyle and Execution | |
| Food, coffeehouse, Heuriger, and meal rhythm |
food-guide.md |
| Family pacing and mixed-age planning |
family-travel.md |
| Accessibility and low-mobility planning |
accessibility.md |
| Emergencies, mountain risk, and disruption logic |
safety-and-emergencies.md |
| Climate and seasonality planning |
weather-and-seasonality.md |
| Connectivity, apps, roaming, and tickets |
telecoms-and-apps.md |
| Research sources map |
sources.md |
Core Rules
1. Route by Corridor, Not by Province Count
Austria is compact enough for ambitious plans and mountainous enough to punish them. Anchor each trip around one rail corridor or one driving loop, then add only the contrast region that still preserves easy transfers.
2. Lock Entry and Season Before Reservations
Before itinerary work, confirm the correct entry path in
entry-and-documents.md, then validate whether the user's month aligns with lakes, cities, alpine hiking, skiing, or Christmas-market demand.
3. Default to Rail Unless the Route Truly Needs a Car
Vienna, Salzburg, Linz, Graz, and Innsbruck link well by rail. Car value appears when the trip is built around lake districts, small alpine villages, scenic roads, or family gear that makes transfers costly.
4. Treat Mountains as Logistics, Not Background
Use
alps-lakes-and-outdoors.md,
weather-and-seasonality.md, and
winter-ski-and-christmas.md before promising huts, panoramas, or ski days. Storms, snow line, cable-car closures, avalanche risk, and fog inversion can change the entire plan.
5. Austria Rewards Pace
Trip quality improves when users sleep multiple nights per base, book key trains and mountain hotels early, and leave daylight margins for weather, spa time, café rhythm, and scenic detours.
6. Budget With Real Friction
Price with actual Austria trip math: rail reservations, airport transfers, vignettes, tunnel tolls, parking in historic cores, mountain lift costs, ski rental, and higher peak-season hotel pressure in lake and alpine regions.
7. Deliver Operational Plans
Output should include:
- - Base-city strategy
- Day-by-day flow with transfer windows
- Reservation deadlines and weather-sensitive items
- Rail-first and car-first variants when relevant
- Safety, payment, and emergency notes
Common Traps
- - Treating Austria like a quick checkbox between larger European stops.
- Combining Vienna, Salzburg, Hallstatt, Innsbruck, and multiple ski or lake regions in too few days.
- Using a car inside Vienna or central Salzburg where parking cost and traffic destroy value.
- Assuming alpine routes, lifts, huts, or scenic roads behave the same in June, September, January, and March.
- Planning Hallstatt or Christmas markets without crowd timing and overnight logic.
- Underestimating Sunday closures and early dinner timing outside the biggest tourist zones.
Security & Privacy
Data that stays local: Trip preferences in INLINECODE33
This skill does NOT: Access files outside ~/austria/ or make network requests.
Related Skills
Install with
clawhub install <slug> if user confirms:
- -
travel — General trip planning and itinerary structure - INLINECODE37 — Better rental strategy and handoff logistics
- INLINECODE38 — Reservation workflows and confirmation hygiene
- INLINECODE39 — Deeper restaurant and cuisine recommendations
- INLINECODE40 — Language support for bookings, transport, and service interactions
Feedback
- - If useful: INLINECODE41
- Stay updated: INLINECODE42
设置
如果 ~/austria/ 不存在或为空,请阅读 setup.md 并自然开始。
使用时机
用户正在规划奥地利旅行,需要超越泛泛灵感的实用指导:入境规则、区域选择、铁路与自驾的权衡、山区时间安排、城市顺序、美食与文化背景,以及实地执行细节。
架构
记忆存储在 ~/austria/ 中。结构参见 memory-template.md。
~/austria/
└── memory.md # 旅行背景与动态约束
快速参考
在构建行程前,使用此地图选择正确的决策模块。
| 主题 | 文件 |
|---|
| 入境、边境与货币 | |
| 旅游入境、签证、申根逻辑、身份证件 |
entry-and-documents.md |
| 海关、现金、食品限制、边境习惯 | customs-and-border.md |
| 预算框架与隐性成本 | budget-and-costs.md |
| 银行卡、现金、小费、免税基础 | tipping-and-payments.md |
|
规划主干 | |
| 区域选择与路线架构 | regions.md |
| 4-14天样本行程 | itineraries.md |
| 按旅行风格的住宿策略 | accommodation.md |
|
交通与户外 | |
| 铁路、巴士、机场接驳、路线时间安排 | transport-domestic.md |
| 自驾、高速票、冬季装备、山路 | road-trips-and-driving.md |
| 阿尔卑斯山、湖泊、徒步、木屋、缆车逻辑 | alps-lakes-and-outdoors.md |
| 冬季运动、圣诞市场、温泉节奏 | winter-ski-and-christmas.md |
| 边境跳跃与附近附加行程 | border-hops-and-day-trips.md |
|
区域与城市 | |
| 维也纳攻略 | vienna.md |
| 萨尔茨堡与萨尔茨卡默古特攻略 | salzburg-and-salzburgerland.md |
| 因斯布鲁克与蒂罗尔攻略 | innsbruck-and-tyrol.md |
| 格拉茨与施泰尔马克攻略 | graz-and-styria.md |
| 克恩顿州与湖区攻略 | carinthia-and-lakes.md |
| 多瑙河、林茨与瓦豪攻略 | danube-linz-and-wachau.md |
|
生活方式与执行 | |
| 美食、咖啡馆、酒馆、用餐节奏 | food-guide.md |
| 家庭节奏与多代同堂规划 | family-travel.md |
| 无障碍与低行动能力规划 | accessibility.md |
| 紧急情况、山区风险与中断逻辑 | safety-and-emergencies.md |
| 气候与季节性规划 | weather-and-seasonality.md |
| 网络、应用、漫游与票务 | telecoms-and-apps.md |
| 研究来源地图 | sources.md |
核心规则
1. 按走廊而非省份数量规划路线
奥地利既小到足以支持雄心勃勃的计划,又大到足以惩罚过度安排。每次旅行围绕一条铁路走廊或一条自驾环线展开,然后只添加一个仍能保持便捷换乘的对比区域。
2. 在预订前锁定入境与季节
在制定行程前,先在 entry-and-documents.md 中确认正确的入境路径,然后验证用户选择的月份是否与湖区、城市、高山徒步、滑雪或圣诞市场需求相匹配。
3. 除非路线确实需要汽车,否则默认选择铁路
维也纳、萨尔茨堡、林茨、格拉茨和因斯布鲁克之间铁路连接良好。当旅行围绕湖区、小型阿尔卑斯村庄、风景公路或使换乘成本高昂的家庭装备展开时,汽车的价值才会显现。
4. 将山区视为物流因素而非背景
在承诺木屋、全景或滑雪日之前,先使用 alps-lakes-and-outdoors.md、weather-and-seasonality.md 和 winter-ski-and-christmas.md。暴风雨、雪线、缆车关闭、雪崩风险和逆温层可能改变整个计划。
5. 奥地利偏爱从容的节奏
当用户在每个基地住宿多晚、提前预订关键火车和山区酒店、并为天气、水疗时光、咖啡馆节奏和风景绕行留出日照余量时,旅行质量会提升。
6. 预算要计入实际摩擦
用真实的奥地利旅行数学来定价:铁路预订、机场接送、高速票、隧道通行费、历史核心区停车费、山区缆车费用、滑雪租赁,以及湖区和阿尔卑斯地区旺季更高的酒店压力。
7. 提供可执行的计划
输出应包括:
- - 基地城市策略
- 每日流程与换乘时间窗口
- 预订截止日期与天气敏感项目
- 铁路优先与自驾优先的变体方案(如适用)
- 安全、支付与紧急情况说明
常见陷阱
- - 将奥地利视为欧洲更大行程之间的快速打卡点。
- 在过少天数内组合维也纳、萨尔茨堡、哈尔施塔特、因斯布鲁克以及多个滑雪或湖区。
- 在维也纳或萨尔茨堡市中心使用汽车,停车成本和交通会破坏价值。
- 假设阿尔卑斯路线、缆车、木屋或风景公路在六月、九月、一月和三月表现相同。
- 规划哈尔施塔特或圣诞市场时不考虑人流高峰和过夜逻辑。
- 低估周日关闭和最大旅游区外的早晚餐时间。
安全与隐私
本地存储的数据: ~/austria/ 中的旅行偏好
此技能不会: 访问 ~/austria/ 以外的文件或发起网络请求。
相关技能
如果用户确认,使用 clawhub install
安装:
- - travel — 通用旅行规划与行程结构
- car-rental — 更好的租车策略与交接物流
- booking — 预订流程与确认管理
- food — 更深入的餐厅与美食推荐
- german — 预订、交通与服务互动的语言支持
反馈
- - 如果觉得有用:clawhub star austria
- 保持更新:clawhub sync