Back to Details

k2f-travel-planner

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

K2F Travel Planner — AI-Native Aesthetic Design

K2F 旅行规划器——AI 原生美学设计

Purpose

用途

Teach agents to author travel planners in 
content_and_design.md
: trip content, information layering, and design intent so the result reads like a field guide—not a chat log or destination encyclopedia.
指导 Agent 在 
content_and_design.md
中编写旅行规划器：涵盖旅行内容、信息层级和设计意图，使成品读起来像一本随身指南，而不是聊天记录或目的地百科全书。

Built on K2F

基于 K2F 构建

This skill produces travel planners as 
.K2F
packages. Follow the k2f skill for authoring, pack/verify, and export. K2F keeps agents on trip semantics and visual rhythm while the engine handles layout and typography.
Before you build, install the core skill: 
npx skills add suzheng/k2f --skill k2f
.
此 skill 会生成 
.K2F
格式的旅行规划器软件包。编写、打包/验证和导出时，请遵循 k2f skill。K2F 让 Agent 专注于旅行语义和视觉节奏，同时由引擎处理布局和排版。
开始构建前，请安装核心 skill：
npx skills add suzheng/k2f --skill k2f
。

When to Use

使用场景

  • Turning trip constraints into a shareable planner (couple, family, or group) with days, costs, and checklists in one document.
  • Merging user notes, bookings, and research into one coherent structure.
  • Not for destination-only chat or live expense tracking unless the deliverable is still a planner blueprint.
  • 将行程约束转化为一份可分享的规划器，在同一个文档中呈现每日行程、费用和清单，适用于情侣、家庭或团体。
  • 将用户笔记、预订和研究资料整合为一套连贯的结构。
  • 不适用于仅提供目的地问答或实时费用追踪的场景，除非最终交付物仍是规划器蓝图。

Workflow

工作流

Step 1. Generate the content_and_design.md

第 1 步：生成 content_and_design.md

One blueprint: semantic blocks per planner section plus explicit design intent. Label sections so the k2f skill can map them later.
Sub-steps
  1. Trip frame — Destination(s), dates, duration, travelers, purpose, budget (total or daily), currency, pace, accommodation base(s), must-sees. Note routing (linear, loop, hub-and-spoke) and transit or jet-lag recovery days.
  2. Input audit — List confirmed bookings, dietary or accessibility needs, interests to weight, and gaps. Mark 
    NEEDS USER INPUT
    for unknown flight times, hotel address, or ticket status; do not invent opening hours, prices, or visa rules—use 
    verify before travel
    stubs.
  3. Section architecture (include / cut / merge) — Default stack (reorder when the frame demands):
    • Trip at a glance (dates, party, budget headline, base neighborhoods) → Essentials (documents, emergency, money, connectivity, key transport) → Day-by-day itinerary → Budget summary → Packing checklist → Culture & safety (compact) → Pre-trip countdown.
    • Cut long destination essays, duplicate restaurant lists, generic packing unrelated to climate/activities, and hour-by-hour filler when pace is relaxed.
    • Merge overlapping transport tips into Essentials; split multi-city trips into labeled day ranges with transit days called out explicitly.
  4. Itinerary build — Theme per day; geo-cluster stops; time blocks with duration, transit, meals, cost, booking notes. Pacing: short trips 2–3 majors/day; week-long 2 major + 1 minor plus one light day; buffers and an optional rain/tired swap every 2–3 active days.
  5. Budget reconciliation — Fixed costs (flights, lodging, insurance, visas) plus daily buckets (food, local transport, activities, misc); 10% contingency; show total, per-person, and per-day; line items must trace to itinerary activities or stated assumptions.
  6. Supporting modules — Packing grouped Documents / Clothing (climate + dress codes) / Activity gear; culture as short do/don’t and dining timing; prep timeline working backward from departure (bookings that sell out first at the top).
  7. Scan layers — Glance: where, when, how much headroom. Scan: day titles and time leaders. Detail: addresses, confirmation hints, costs—subordinate in design intent.
  8. Design intent — Tone: practical, warm, local-aware; imperative checklists for actions. Hierarchy: title and dates dominate; day + theme anchors; times and places beat prose; costs and must-book flags scannable. Density: airy overview; consistent day blocks; checkbox lists; culture as callouts. Palette: calm journal feel; one accent on day headers; strong contrast on times and bookings.
Rules & constraints
  • Truth gate: prices, hours, and requirements trace to user input or labeled stubs—not guessed from memory.
  • Pace gate: total planned hours fit the stated pace; include meals and transit in every day.
  • Budget gate: category totals reconcile with headline budget or show explicit overrun note.
  • Routing gate: minimize backtracking; high-energy days not stacked after red-eye arrival without recovery.
  • Planner boundary: if the user only wants a spreadsheet tracker, note in blueprint that this skill targets a designed planner artifact.
Common failure modes
  • Attraction list without time or geography → themed days with clustered blocks.
  • Packed schedule with no rest → pacing table and one light day per week-long trip.
  • Budget section disconnected from days → tie line items to named activities.
  • Packing encyclopedia → climate + activity-filtered checklist only.
  • Culture section as generic country essay → 5–8 actionable do/don’t plus dining timing.
  • Prep timeline after departure or missing sell-out bookings → reverse chronological from departure date.
  • Repeating the same practical tip in every day → lift once to Essentials.
Quality checklist
  • Frame: destination, dates, party, budget, pace, routing, and must-sees documented.
  • Section stack fits trip length; cuts and multi-city splits explained.
  • Each day has theme, geo-logical flow, meals, transport, costs, and booking notes or stubs.
  • Budget reconciles (or flags gap) with contingency stated.
  • Packing and prep match climate, activities, and departure date.
  • Glance layer answers where/when/how much without reading full days.
  • Design intent covers tone, hierarchy, density, checklist rhythm, and accent.
蓝图应包含按规划器章节划分的语义块，以及明确的设计意图。为各章节添加标签，以便 k2f skill 后续进行映射。
子步骤
  1. 行程框架——目的地、日期、时长、旅行者、行程目的、预算（总额或每日预算）、货币、节奏、住宿区域和必去项目。注明路线安排（线性、环线或中心辐射式），以及交通中转日或适应时差的恢复日。
  2. 输入审计——列出已确认的预订、饮食或无障碍需求、需要重点考虑的兴趣，以及信息缺口。对于未知的航班时间、酒店地址或票务状态，标记 
    NEEDS USER INPUT
    ；不要臆造营业时间、价格或签证规则，而应使用 
    verify before travel
    占位项。
  3. 章节架构（保留／删减／合并）——默认章节顺序如下，可根据行程框架重新排序：
    • 行程概览（日期、同行者、预算摘要、住宿片区）→ 旅行必备（证件、紧急信息、货币、网络、关键交通）→ 逐日行程 → 预算汇总→ 打包清单 → 文化与安全（精简版）→ 出发前倒计时。
    • 删减冗长的目的地文章、重复的餐厅列表、与气候或活动无关的通用打包清单，以及节奏宽松时逐小时填充式的内容。
    • 将重复的交通提示合并到旅行必备中；对于多城市旅行，将其拆分为带标签的日期区间，并明确标出中转日。
  4. 构建行程——每天设置一个主题；按地理位置聚类安排景点；时间块应包含时长、交通、用餐、费用和预订备注。行程节奏：短途旅行每天安排 2–3 个重点行程；为期一周的旅行每天安排 2 个重点行程和 1 个次要行程，另设 1 个轻松日；每 2–3 个高强度行程日安排缓冲时间，并提供可选的雨天／疲劳备选行程。
  5. 核对预算——固定成本包括机票、住宿、保险和签证，另加每日预算分类（餐饮、当地交通、活动和杂项）；预留 10% 应急资金；展示总预算、人均预算和每日预算；每个费用明细都必须能追溯到行程中的活动或明确说明的假设。
  6. 辅助模块——打包清单按证件／衣物（气候与着装要求）／活动装备分类；文化部分采用简短的可做／不可做清单，并说明用餐时间；准备时间线从出发日期倒推排列，最容易售罄的预订项置顶。
  7. 扫读层级——速览：地点、时间、预算余量。扫读：每日标题和时间节点。详情：地址、确认信息提示和费用，在设计意图中处于次要层级。
  8. 设计意图——基调：实用、温暖并兼顾当地特色；行动项采用祈使式清单。层级：标题和日期最突出；每日行程及主题作为锚点；时间与地点优先于长篇文字；费用和必须预订标记应便于扫读。密度：概览部分留白充足；每日内容块保持一致；使用复选框列表；文化提示采用强调框。配色：营造平静的旅行日志质感；每日标题使用单一强调色；时间和预订信息采用高对比度。
规则与约束
  • 真实性校验：价格、营业时间和相关要求必须可追溯至用户输入或带标签的占位项，不能凭记忆猜测。
  • 节奏校验：计划总时长应符合既定节奏；每天都要计入用餐和交通时间。
  • 预算校验：各类别总额应与预算摘要一致，否则必须明确标注超支说明。
  • 路线校验：尽量减少折返；红眼航班抵达后如未安排恢复时间，不应连续安排高强度行程。
  • 规划器适用边界：如果用户只想要电子表格追踪器，应在蓝图中注明，此 skill 的目标是生成经过设计的规划器成品。
常见失败模式
  • 景点清单没有时间或地理信息 → 改为按主题分日，并采用地理聚类行程块。
  • 日程过满且没有休息 → 制定节奏表，并为为期一周的旅行安排一个轻松日。
  • 预算部分与每日行程脱节 → 将费用明细关联到具名活动。
  • 打包指南写成百科全书 → 仅保留基于气候和活动筛选的清单。
  • 文化部分变成泛泛的国家介绍 → 提供 5–8 条可执行的 do/don’t 建议及用餐时间说明。
  • 准备时间线放在出发之后，或遗漏容易售罄的预订项 → 从出发日期开始按倒序排列。
  • 每天重复同一条实用提示 → 提取一次并统一放入旅行必备。
质量检查清单
  • 框架：已记录目的地、日期、同行者、预算、节奏、路线和必去项目。
  • 章节结构适合行程时长；已说明删减内容和多城市拆分方式。
  • 每天都有主题、符合地理逻辑的动线、用餐、交通、费用，以及预订备注或占位说明。
  • 预算核对一致（或标出差距），并说明应急预留。
  • 打包清单和准备工作与气候、活动及出发日期相匹配。
  • 无需阅读完整每日行程，即可从速览层了解地点、时间及预算规模。
  • 设计意图涵盖基调、层级、密度、清单节奏和强调色。

Step 2. Use the content_and_design.md and k2f skill to generate a K2F file and export to an appropriate file format.

第 2 步：使用 content_and_design.md 和 k2f skill 生成 K2F 文件并导出为适当的文件格式

Follow k2f to instantiate planner sections from the blueprint, apply roles from design intent, verify, and export (typically PDF or print-ready format).
遵循 k2f，根据蓝图实例化规划器章节，应用设计意图中定义的角色，完成验证并导出，通常为 PDF 或适合打印的格式。