摄影旅行规划提示词

旅行摄影师可复用模板

v4.0

---

本模板的两种使用方式：

轻量模式 —— 跳过所有标记为 [OPTIONAL] 的章节以及整个技术说明章节。填写你的风格档案和旅行详情，然后让 Claude 提供一份纯文字的调研简报和逐日行程。无需运行脚本。

完整制作模式 —— 使用所有章节。Claude 将生成一套 PowerPoint 幻灯片（通过 Node.js + pptxgenjs）、一个 Excel 工作簿（通过 Python + openpyxl）以及 Google Maps CSV 文件——全部采用颜色编码并经过质检。需要能够熟练地在命令行中运行脚本。

两种模式下：请填写每一个标记为 [FILL IN] 的章节。标记为 [EXAMPLE] 的章节展示的是填写完成后的条目示例——请用你自己的详细信息替换。标记为 [OPTIONAL] 的章节如果与你的工作流程无关，可以删除。

---

我是谁

我是一名旅行摄影师，正在规划一次[有 / 无]同伴同行的旅行。我的名字是 [FILL IN]。我使用的拍摄设备为[FILL IN — 例如：Canon EOS R5 和 Sony A7IV]。我的旅行镜头配置：[FILL IN — 例如：16-35mm 广角、24-70mm 标准、100mm 微距]。我旅行时携带[FILL IN — 例如：碳纤维旅行三脚架 / 不带三脚架 / 紧凑型 gorilla-pod]。我的携带系统是[FILL IN — 例如：带 Peak Design 扣具的胸挂，可将相机固定在肩带上 / 带内胆的摄影背包]。

[EXAMPLE]：我使用 Canon 5D Mark II 和加装 EF 转接环的 Canon EOS-R。镜头配置：16-35mm（主力镜头）、24-105mm（街拍 [EXAMPLE]：我拍摄那些经久不衰的事物——建筑、风景，以及存在于时间之外的时刻。贯穿我全部作品的主线，是那些被建造或被居住过、如今已超越其原始用途却依然矗立的事物。

技术签名： [待填写——列出你一贯采用的构图与技术选择。]

[EXAMPLE]：

• 对称或近似对称的构图，配以强烈的中心消失点
• 低角度或垂直仰拍，以夸大尺度感并消除地平线——我一直这样做
• 用单个人物作为尺度参照，而非作为主要拍摄对象
• 长曝光或慢速快门，抹平水、云和人群的动态
• 结构、工业与衰败题材用黑白；当色调本身成为主题时用彩色
• 强烈的影调对比——我冲印时偏暗
• 事物的底部、内部骨架和结构骨骼比外立面更让我感兴趣

反复出现的题材类别： [待填写——列出你一贯寻找的地点和拍摄对象类型。]

[EXAMPLE]：

• 衰败与废弃——已超越其原有用途的事物（飞机残骸、残破教堂、废弃机构）
• 有分量、有锋芒的神圣空间——不是漂亮的教堂，而是发生过事情的空间
• 古老与工业的并置（发电厂里的古代大理石、现代广场上的罗马柱）
• 地下与地底空间——地穴、隧道、现代城市之下的古老地层
• 几何结构形态——桥梁、桥墩、拱门、重复元素
• 安静而空旷的街道——我在人群到来之前拍摄
• Atlas Obscura 式的地点——不寻常的、隐秘的、被遗忘的

我一贯避免的： [待填写——列出你不希望被推荐的内容。]

[EXAMPLE]：

• 名胜景点的明信片式取景
• 摆拍的拍摄对象
• 柔和或感伤的光线
• 把拥挤的旅游景点作为主要目标
• 把市场作为计划内的停留点（但乐于偶然遇见）

---

旅伴 [OPTIONAL]

[填写或删除此部分] — 如果你与旅伴同行，请在此描述他们的兴趣，以便 Claude 能制定出对你们两人都适用的计划，而不是一个让同行者只能随行陪跑的摄影师行程。

[EXAMPLE]：我的伴侣全程与我同行。他们喜欢精品店购物、开胃酒文化、街区漫步，以及包括藏骨堂和地下墓穴在内的独特文化体验。他们对非常规地点也乐于尝试。几乎所有摄影目标都是共同体验——绝大多数拍摄时他们都在场，而不是在别处等待。唯一真正独处的时间是黎明前的拍摄时段。请把共同体验融入计划，而不是安排一条平行支线。

关于冒险与体力付出： 默认情况下，一份经过充分研究、已购票、预先排定的行程可能显得毫无风险且被动——没有任何听凭偶然的余地，没有体力消耗，没有不确定性。如果存在更辛苦、更耗费体力的抵达方式（例如徒步下到景点而不是乘船，沿步道徒步而不是开车），请把它明确地作为一个选项呈现出来，而不是默默默认选择更轻松的方案。不要只是描述更辛苦的选项——还要核查返程的后勤安排（例如，如果从山顶徒步下山，车最终停在哪里，你又如何回到取车点？）。

关于疲劳： 不要假设在多城市行程中精力是无限的。请计算黎明前拍摄、时差反应和每日步行距离的累积负荷，并在行程中没有真正内置休息上午时予以提示。拥有五个出色黎明前拍摄时段的行程，胜过拥有六个平庸时段的行程。建议在行程中段左右安排至少一个不设闹钟、完全不做计划的休息上午，而不仅仅是在抵达当天。

---

行程概况

目的地： [填写 — 例如："意大利：罗马、威尼斯、米兰"] 出发： [填写 — 例如："LAX，9月16日 下午 3:05"] 返程： [填写 — 例如："LIN（米兰利纳特机场），9月28日 上午 9:50"] 去程抵达： [填写 — 例如："FCO（罗马），9月17日 下午 2:05"] 城市与晚数： [填写 — 例如："罗马 3 晚，威尼斯 3 晚，米兰 3 晚"] 城市间交通： [填写 — 例如："Frecciarossa 高速列车，力争在下午 5 点左右抵达每座新城市，以保住上一座城市的最后一个上午"] 住宿街区： [填写，或让 Claude 根据拍摄目标和旅伴兴趣进行推荐]

我希望 CLAUDE 构建的内容

1. PowerPoint 幻灯片 [可选 — 需要 Node.js 和 pptxgenjs]

此交付物面向能够熟练运行 Node.js 脚本的用户。如果你想要更简单的输出，可将本节替换为对格式化文档或文本方案的需求。

格式： LAYOUT_WIDE（13.3 x 7.5 英寸），使用 Node.js 中的 pptxgenjs 构建。分隔页和参考页采用深海军蓝背景配金色强调文字。内容页/日程页采用米白色背景。封面和文件名中包含版本号。

幻灯片页眉或行内的徽章/标记：

• 红色徽章："★ 需提前预订" — 用于需要预先购票的地点
• 绿色徽章："★ ATLAS OBSCURA" — 用于符合这种精神的独特/隐秘地点
• 金色横幅："共同体验" — 用于有意义的共同参观
• 深红色徽章："⊘ 禁止摄影" — 仅在直接核实后使用（参见地点调研标准）
• 高处观景点卡片上的深红色徽章："⊘ 已确认关闭" — 用于已不存在或已停业的观景点

需包含的幻灯片：

• 封面（旅行标题、城市、日期、版本号）
• 旅行概览（卡片式布局，每个城市停留点一张卡片，含日期/住宿晚数/大本营）
• 摄影方案（风格概述、器材）
• 日程颜色图例
• 每个城市：
  • 城市章节分隔页（整页深色背景）
  • 光线时间表（蓝调时刻开始、日出、上午黄金时刻、傍晚黄金时刻、日落、蓝调时刻结束 — 使用 Python astral 库、精确坐标、实际旅行日期计算）
  • 大本营页（为何选择该街区、距拍摄目标的远近、附近亮点、交通）
  • 每个已确认拍摄目标的地点页：简介 / 拍摄清单（4–5 个镜头）/ 非常规视角（3–4 个角度），外加一条关键信息栏（开放时间、进入方式、费用）
  • 高处观景点页（卡片式布局，3 个观景点；标记已确认关闭的观景点；区分真正适合日落后观景的观景点与天黑前即关闭、仅适合黄金时刻的观景点）
  • 每日日程 — 将一个城市的所有天数合并到单张幻灯片上；仅当内容确实会超出幻灯片高度时才拆分为续页。不要按固定行数预先拆分。
• 时间分配饼图（按类别统计的小时数，取自实际日程数据）
• 门票与预订页（3 列：提前预订 / 当天付款 / 免费）
• 器材清单页（相机、镜头、支撑设备、携带系统、配件，以及三脚架/摄影受限场所的说明）
• Aperitivo/美食酒吧页 — 按城市列出具体具名的酒吧，仅限本地精选，附地址和描述。这些是分布在多个晚间的选择，而非单晚的酒吧串游。
• 火车/交通衔接汇总页 [OPTIONAL]
• 附录 — 拍摄示意图： 每个拍摄地点的俯视图与剖面图示意。相机位置（红点）、拍摄方向（虚线）、视野锥（点线）、推荐镜头，全部编号并与该地点的拍摄清单一一对应。每张俯视图必须包含指北针/罗盘指示。剖面图（用于展示垂直关系的，如被水淹没的地下墓室或崖壁）则不需要。

日程颜色编码（7 个类别）：

• 黎明前拍摄 / 摄影：深海军蓝背景，浅蓝色文字
• 餐前酒：深紫色背景，浅紫色文字
• 共同活动：深金色背景，浅金色文字
• 自由 / 可选：深绿色背景，浅绿色文字
• 交通 / 抵达：深灰色背景，浅灰色文字
• 休息 / 退房：中灰色背景，浅灰色文字
• 需提前预订：深红色背景，浅红色文字
• （日落/黄金时刻时段块如有需要可采用深橙色变体）

---

2. Excel 工作簿 [可选 — 需要 Python 和 openpyxl]

总表工作表 — 询问对方想要哪种格式：

• 列表格式： 按时间顺序排列的行（日期、天数、城市、时间、活动、类别、时长、备注），整个行程中每个活动占一行。
• 日历网格格式： 横向周视图 — 行程的所有天数作为列从左到右排列，两侧各有一条向下延伸的共用时间轴（例如早上 5:00–晚上 10:30，以 30 分钟为一行），每个活动渲染为一个按颜色编码的块，纵向合并跨越其所覆盖的行。交通/转场日的列使用视觉上明显不同的表头和背景色调。日出、日落、蓝调时刻和黄金时刻的行在时间轴上高亮显示（用脚注标注为按整个行程平均的近似值 — 如需精确数值请参见各城市的光线时机幻灯片）。单个工作表，涵盖所有天数，不拆分工作表。

每个城市一个工作表（无论总表选择哪种样式，均采用纵向逐日格式），另加一个图例工作表。 与日程幻灯片采用相同的颜色编码。冻结窗格，隐藏网格线，在工作表为平面列表时对表头行启用自动筛选。包含一个 Duration 列。

---

3. Google Maps CSV 文件 — 每个城市一个 [OPTIONAL]

列：Name, Description, Category, Best Time, Latitude, Longitude, Address。

关键： 使用 Python 的 csv.writer 并采用 utf-8 编码。不得使用特殊字符 — 仅限纯 ASCII，并进行明确的字符替换（例如 é→e、—→--、'→）。在收录之前先验证坐标。

类别：Shooting Location, Shared Activity, Base, High Viewpoint, Transit, Optional Day Trip, CLOSED - DO NOT USE, Atlas Obscura Optional。

文件命名规范： [destination]-trip-[year]-v[N].pptx / .xlsx / [city]-locations-v[N].csv。每次重建时都要递增版本号，并且即使只有一个文件发生更改，也要让幻灯片、工作簿和所有 CSV 文件保持相同的版本号 — 重命名/重新复制未更改的文件，使整套交付物保持同步。

---

地点调研标准

针对每个拍摄地点，提供：

1. 描述 — 它是什么、为什么在摄影上重要、最佳条件，以及在相关时与我风格档案的关联
2. 镜头清单 — 值得拍摄的 4–5 个标准镜头
3. 非常规视角 — 大多数摄影师会错过的 3–4 种角度或拍法，与上文我的风格档案相匹配
4. 关键备注 — 开放时间、进入方式、费用、交通、与其他目标的邻近程度
5. 最佳时间 — 黎明前 / 清晨 / 上午 / 下午 / 黄金时刻

摄影政策核实 — 不可妥协：

在将任何地点列为摄影目标之前，直接核实其实际的摄影政策 — 查阅官方网站，或在政策不明确或事关重大时联系场馆确认。不要基于普遍口碑或片面信息就假定“禁止摄影”或“允许摄影”。两个真实例子：一个被假定完全禁止进入的地点，在直接给场馆发邮件后，发现其实允许个人使用，只是对设备使用时段有限制；另一个地下场所尽管最初被当作拍摄目标，结果却完全禁止摄影。当场馆的书面政策是将设备（三脚架、单反相机）限制在特定时段，而不是完全禁止摄影时，应将其视为排期约束，而不是脚注。

对于每座城市，还要研究：

• 最佳落脚街区（需兼顾与拍摄目标的距离以及同行者的兴趣）
• 高空观景点——分为两类： (a) 真正的日落后/夜间观景点，会一直开放到天黑之后；以及 (b) 仅黄金时段的观景点，在天真正黑透之前就关门（许多屋顶露台就是如此——在假定某个屋顶露台适合夜间拍摄之前，先对照该城市实际的日落时间核实确切的关门时间）。确认当前的开放/关闭状态；对已确认的永久关闭要明确标注，而不是默默略过。
• 可选的一日游（3–4 个选项，需同时契合你的审美和同行者的兴趣）
• 真正符合你风格的 Atlas Obscura 地点——仔细筛选，并非所有条目都合格
• 具体的开胃酒/小吃酒吧：只选本地人光顾的，不面向游客，附上名称、地址以及值得前往的理由
• 自驾或无需驾照的租赁选项（船只、小型车辆），前提是它们比固定班次的渡轮/旅行团能提供更多构图控制——直接核实价格和通行安排，不要从聚合的博客内容中推断 [OPTIONAL]

研究与核实要求：

• 核实所有地点确实存在后再纳入——对任何不确定的地点进行网络搜索
• 确认当前的通行状态——在推荐任何观景点或景点之前，先搜索是否有关闭信息
• **星期几：**始终用 Python datetime 针对实际出行年份计算。绝不猜测。
• **光线时间：**始终用 Python astral 库，基于精确的城市坐标和出行日期计算。绝不估算。
• **票价和预订窗口：**搜索当前价格——不要依赖训练数据
• 不要产生幻觉——如果对某个事实不确定，就去搜索或如实说明。如果被直接问到“你为什么对 X 产生了幻觉”，要坦率承认，而不是找借口开脱。
• 当新信息与先前的研究相矛盾时（例如，场馆的官方邮件回复），要在同一轮次中将更正同步到所有受影响的交付物——行程表、地点幻灯片、预订幻灯片、Excel 备注、CSV——而不仅仅是在对话中。

---

ATLAS OBSCURA 筛选方法

严格依据你的风格档案来筛选 Atlas Obscura 的推荐条目。以下内容可作为判断哪些通常合适、哪些不合适的参考：

高度契合：

• 地下或地底空间（墓穴、隧道、古老地层）
• 废弃或衰败的空间（旧机构旧址、工业废墟）——收录前须核实其当前的安全状况与合法进入情况；凡需要擅自闯入的地点，无论摄影吸引力多高一律舍弃
• 人骨教堂与藏骨堂
• 隐蔽的建筑异象（小巷深处的螺旋楼梯、公园里的炼金术士之门）
• 已跨入诡异领域的神圣空间

契合度低——不要推荐：

• 缺乏强视觉潜力的猎奇博物馆
• 历史上有意思但摄影上不吸引人的地点
• 任何需要非法或不安全进入方式的地点——若进入情况不确定，应标注待研究，而不是直接推荐

---

APERITIVO/餐饮调研标准

针对每座城市，调研 3–4 家具体的本地酒吧或餐厅。要求：

• 客群以本地人为主，而非面向游客
• 给出具体店名和街道地址
• 用一句话说明它值得一去的理由
• 标注任何重要的歇业信息（星期几、一天中的时段）
• 优先选择靠近拍摄地点的场所，这样同一地点可以在清晨（拍摄）和傍晚（aperitivo）各去一次——可行时这是很强的搭配
• 将这些作为贯穿整个旅程各晚的备选清单呈现，而不是某一晚的行程——除非对方明确表示想要每晚连逛酒吧，否则不要暗示如此安排

---

规划流程

按以下顺序执行：

1. 若未提供，先询问旅行日期、城市和交通方式
2. 在做任何其他事情之前，先用 Python 核实星期几
3. 用 Python astral 计算所有拍摄日的光线时机
4. 调研并提出拍摄地点——按我的风格档案筛选——在搭建行程前请求确认
5. 调研并提出每座城市的落脚街区——请求确认
6. 调研每座城市的 Atlas Obscura 条目——提出时附上对契合度的诚实评估
7. 调研每座城市具体的本地餐饮场所
8. 调研每座城市的高处观景点，按日落后可进入与仅黄金时段可进入分类
9. 确定需要提前预订的项目及预订窗口期
10. 搭建日程——黎明前拍摄、共同体验、餐饮/aperitivo、自由时间，以及至少一个真正不安排任何计划的休息上午
11. 在呈现前审计已搭建的日程：（a）其中是否包含任何真实的体力付出或不计划的时间，还是一切都靠买票入场、被动接受？（b）黎明前拍摄加步行的累计负荷是否还留有真正享受旅程的余地，还是疲劳会在旅程过半时不断叠加？
12. 一次性完成所有交付物：PowerPoint、Excel、CSV 文件
13. 交付前对幻灯片做质检：先用 soffice 转换为 PDF，再用 pdftoppm -jpeg -r 120，逐页查看图片 批量处理更改，仅在明确要求时才重建。 在动任何文件之前，先确认所有更改。将请求的更改保存在一个持续维护的列表中，最后一次性全部重建，而不是每项更改后都单独重建。

---

技术说明 [可选 — 仅在使用 PowerPoint、Excel 或 CSV 交付物时相关]

pptxgenjs:

• 绝不将 lambda 作为位置参数 y 传给辅助函数 — 应使用内联的 s.addText() 并显式指定坐标
• 始终为项目符号列表文本框添加 valign: "top"
• 每个项目符号数组的最后一项都必须显式包含 options: { bullet: true }
• 十六进制颜色值中绝不使用 # — 传入时不带井号
• 构建内容长度不一的卡片网格时，不要假设各行高度一致 — 要么根据条目数量测量/估算每张卡片的高度，要么为每列使用独立追踪的累计 y 偏移量，以免较高的卡片与下一行重叠
• 每次重建后都要进行 QA：soffice --headless --convert-to pdf，然后 pdftoppm -jpeg -r 120，交付前先检查

openpyxl:

• 所有单元格填充都使用 PatternFill("solid")
• 在可滚动数据区域的左上角冻结窗格（如果使用带有标题行和日期列轴的日历网格 Master，此位置会随之偏移）
• 在所有工作表上设置 showGridLines = False
• 当工作表是扁平列表时，在标题行上启用自动筛选；日历网格 Master 不需要自动筛选
• 对于日历网格布局：在合并单元格之前，先解决一天内时间块的重叠问题（按开始时间排序，将一个时间块的结束时间截断到下一个时间块的开始时间）；具名/近似的时间段标签没有确切的钟表时间，因此需要显式的锚定小时映射

CSVs:

• 始终使用 Python 的 csv.writer 并采用 utf-8 编码
• 不使用特殊字符 — 仅用纯 ASCII，并进行显式的字符替换（é→e, —→--, '→'）
• 在纳入之前先核实坐标是否准确

日程拆分（PowerPoint）：

• 默认情况下，不要将一个城市的每日日程拆分到多张幻灯片上。应将同一城市的所有天数合并到一张幻灯片上。
• 仅当实际渲染的内容会超出幻灯片可用高度时，才拆分到续页幻灯片。应根据可用垂直空间核对总行数，而不是依据固定阈值。

---

风格偏好

[待填写 — 描述你的总体规划理念。以下为示例。]

[EXAMPLE]：

• 质量重于数量 — 更少但更精华的地点胜过面面俱到的清单
• 尽量减少交通周折 — 当目标可以集中在一起时，不要横穿城市安排路线
• 真实体验优先于面向游客的项目 — 如果存在游客更少的同类去处，推荐那个
• 黎明前进入是优先事项 — 但几乎所有摄影目标都是与同伴共享的体验
• 猎奇胜过知名 — 全程贯彻 Atlas Obscura 式的品味
• 冒险和计划外的时间值得刻意留出余地，而不只是按票打卡的效率
• 对事实存疑时，先搜索再回答 — 如果无法核实某事，就明说，而不是把推断当作已确认的事实呈现

---

同伴优先事项 [OPTIONAL]

[填写或删除本节] — 如果与同伴同行，请列出对他们重要的内容，让他们的优先事项融入共享活动和美食/开胃酒幻灯片，而不是事后才想起补充。

[EXAMPLE]：

• 精品店购物（不是连锁店，也不是百货商场）
• 开胃酒文化 — 分布在旅程中的多个夜晚，而不是默认每晚固定进行
• 在有本地气息的街区闲逛漫步
• 独特的文化体验 — 乐于探访藏骨堂、地下墓穴和诡异之地
• 美食和本地餐厅

记住：绝大多数摄影地点应当本来就是共同体验。把日程当作一份带有少量独自黎明前时段的共同行程，而不是一份让同伴只是作陪的摄影师行程。

本模板源自一次真实的多城市意大利旅行规划工作流，经过多轮完整交付物重建周期的打磨。适用于 Claude、ChatGPT、Gemini 或任何现代大语言模型。

Photography Trip Planning Prompt

Reusable Template for Travel Photographers

v4.0

---

Two ways to use this template:

Lightweight mode — Skip all sections marked [OPTIONAL] and the entire Technical Notes section. Fill in your style profile and trip details, then ask Claude for a text-based research brief and day-by-day schedule. No scripting required.

Full production mode — Use every section. Claude will produce a PowerPoint slide deck (via Node.js + pptxgenjs), an Excel workbook (via Python + openpyxl), and Google Maps CSVs — all color-coded and QA'd. Requires comfort running scripts from the command line.

In both modes: fill in every section marked [FILL IN]. Sections marked [EXAMPLE] show what a completed entry looks like — replace them with your own details. Sections marked [OPTIONAL] can be removed if not relevant to your workflow.

---

WHO I AM

I am a travel photographer planning a trip [with / without] a companion. My name is [FILL IN]. I shoot with [FILL IN — e.g., Canon EOS R5 and Sony A7IV]. My lens kit for travel: [FILL IN — e.g., 16-35mm wide, 24-70mm standard, 100mm macro]. I travel with [FILL IN — e.g., a carbon fiber travel tripod / no tripod / a compact gorilla-pod]. My carry system is [FILL IN — e.g., a chest rig with Peak Design clips to secure cameras to the straps / a camera backpack with a cube insert].

[EXAMPLE]: I shoot with a Canon 5D Mark II and Canon EOS-R with EF adapter. Lens kit: 16-35mm (primary workhorse), 24-105mm (street/mid-range), 100mm macro (details/close work). Carry system: a Condor Stowaway chest rig with two Peak Design clips. No ND filters on this trip.

---

MY PHOTOGRAPHIC STYLE

This is the most important section. Read it carefully before suggesting any locations.

The core subject: [FILL IN — Describe the through-line of your work. What do you photograph and why? What draws you to a subject?]

[EXAMPLE]: I photograph things that endure — structures, landscapes, and moments that exist outside of time. The through-line across my work is things built or lived in that now outlive their original purpose, still standing.

Technical signatures: [FILL IN — List your consistent compositional and technical choices.]

[EXAMPLE]:

• Symmetrical or near-symmetrical composition with a strong central vanishing point
• Low angle or looking straight up to exaggerate scale and eliminate horizon — I do this consistently
• A single human figure used for scale, not as the primary subject
• Long exposure or slow shutter to pull motion out of water, clouds, and crowds
• B&W for structural, industrial, and decay subjects; color when the palette itself is the subject
• Strong tonal contrast — I print dark
• The underside, interior skeleton, and structural bones of things interest me more than facades

Recurring subject categories: [FILL IN — List the types of places and subjects you consistently seek out.]

[EXAMPLE]:

• Decay and abandonment — things that have outlived their purpose (plane wrecks, ruined churches, abandoned institutions)
• Sacred spaces with weight and edge — not pretty churches, spaces where something happened
• Old-meets-industrial juxtapositions (ancient marble in a power plant, Roman columns in a modern piazza)
• Underground and subterranean spaces — crypts, tunnels, ancient layers beneath modern cities
• Geometric structural form — bridges, piers, arches, repeating elements
• Quiet and empty streets — I shoot before crowds arrive
• Atlas Obscura-type locations — the unusual, the hidden, the forgotten

What I consistently avoid: [FILL IN — List what you do not want recommended.]

[EXAMPLE]:

• Postcard framing of famous places
• Posed subjects
• Soft or sentimental light
• Crowded tourist spots as primary targets
• Markets as planned stops (open to stumbling upon them)

---

TRAVEL COMPANION [OPTIONAL]

[FILL IN or delete this section] — If you are traveling with a companion, describe their interests here so Claude can build a plan that works for both of you, not a photographer's itinerary with someone along for the ride.

[EXAMPLE]: My partner travels with me for the entire trip. They enjoy boutique shopping, aperitivo culture, neighborhood wandering, and unusual cultural experiences including ossuaries and catacombs. They are game for unusual locations. Nearly all photography targets are shared experiences — they are present for the vast majority of shoots, not waiting elsewhere. The only genuinely solo time is pre-dawn sessions. Build shared experiences into the plan, not a parallel track.

On adventure and physical effort: By default, a fully researched, ticketed, pre-scheduled itinerary can feel risk-free and passive — nothing left to chance, no physical exertion, no uncertainty. If a harder, more physically engaged way to reach a location exists (climbing down to a site instead of taking a boat, hiking a trail instead of driving), surface it explicitly as a choice rather than silently defaulting to the easier option. Don't just describe the harder option — check the return logistics too (e.g., if hiking down from a summit, where does the car end up, and how do you get back to it?).

On fatigue: Don't assume unlimited energy across a multi-city trip. Calculate the cumulative load of pre-dawn shoots, jet lag, and daily walking distance, and flag when a trip has no genuine rest morning built in. A trip with five excellent pre-dawn sessions beats one with six mediocre ones. Recommend at least one no-alarm, fully unplanned rest morning roughly mid-trip, not just on arrival day.

---

THE TRIP

Destination: [FILL IN — e.g., "Italy: Rome, Venice, Milan"] Departure: [FILL IN — e.g., "LAX, Sept 16, 3:05 PM"] Return: [FILL IN — e.g., "LIN (Milan Linate), Sept 28, 9:50 AM"] Outbound arrival: [FILL IN — e.g., "FCO (Rome), Sept 17, 2:05 PM"] Cities and nights: [FILL IN — e.g., "Rome 3 nights, Venice 3 nights, Milan 3 nights"] City-to-city transport: [FILL IN — e.g., "Frecciarossa train, targeting ~5 PM arrival at each new city to protect the outgoing city's final morning"] Base neighborhoods: [FILL IN, or ask Claude to recommend based on shooting targets and companion interests]

---

WHAT I WANT CLAUDE TO BUILD

1. PowerPoint Slide Deck [OPTIONAL — requires Node.js and pptxgenjs]

This deliverable is for users comfortable running Node.js scripts. If you want a simpler output, replace this section with a request for a formatted document or text plan.

Format: LAYOUT_WIDE (13.3 x 7.5 inches), built with pptxgenjs in Node.js. Dark navy background with gold accent text on divider and reference slides. Off-white background on content/schedule slides. Version number on cover and filename.

Badges/flags on slide header or inline:

• Red badge: "★ ADVANCE BOOKING REQUIRED" — for locations requiring pre-purchase tickets
• Green badge: "★ ATLAS OBSCURA" — for unusual/hidden locations in that spirit
• Gold banner: "SHARED EXPERIENCE" — for meaningful shared visits
• Dark red badge: "⊘ PHOTOGRAPHY PROHIBITED" — only after direct verification (see Location Research Standards)
• Dark red badge on High Viewpoints cards: "⊘ CONFIRMED CLOSED" — for viewpoints that no longer exist or have shut down

Slides to include:

• Cover (trip title, cities, dates, version number)
• Trip overview (card layout, one card per city stop with dates/nights/base)
• Photography approach (style summary, gear)
• Schedule color legend
• For each city:
  • City section divider (full dark background)
  • Light timing table (blue hour start, sunrise, golden hour AM, golden hour PM, sunset, blue hour end — calculated with Python astral library, exact coordinates, actual trip dates)
  • Base camp slide (why this neighborhood, proximity to shooting targets, highlights nearby, transit)
  • Location slides for each confirmed shooting target: About / Shot List (4–5 shots) / Unconventional Perspectives (3–4 angles), plus a Key Notes bar (hours, access, cost)
  • High Viewpoints slide (card layout, 3 viewpoints; flag confirmed closures; distinguish true post-sundown viewpoints from golden-hour-only ones that close before dark)
  • Daily schedule — combine all days for a city onto a single slide; only split to a continuation slide if the content would actually overflow the slide height. Do not split preemptively at a fixed row count.
• Time Allocation pie chart (hours by category, pulled from actual schedule data)
• Tickets and booking slide (3 columns: book in advance / pay on day / free)
• Gear list slide (cameras, lenses, support, carry system, accessories, notes on where tripods/photography are restricted)
• Aperitivo/food bars slide — specific named bars by city, local picks only, with address and description. These are options spread across multiple evenings, not a single-night bar crawl.
• Train/transport connections summary slide [OPTIONAL]
• Appendix — Shot Diagrams: plan-view and cross-section schematics for every photography location. Camera position (red dot), shooting direction (dashed line), field-of-view cone (dotted lines), recommended lens, all numbered to match the location's shot list. Every plan-view diagram must include a north arrow/compass indicator. Cross-section diagrams (showing vertical relationships like a flooded crypt or a cliff-face) don't need one.

Schedule color coding (7 categories):

• Pre-Dawn Shoot / Photography: dark navy bg, light blue text
• Aperitivo: dark purple bg, light purple text
• Shared Activity: dark gold bg, light gold text
• Free / Optional: dark green bg, light green text
• Travel / Arrival: dark gray bg, light gray text
• Rest / Checkout: medium gray bg, light gray text
• Advance Booking Required: dark red bg, light red text
• (Sunset/golden-hour blocks can get a dark-orange variant if useful)

---

2. Excel Workbook [OPTIONAL — requires Python and openpyxl]

Master tab — ask which format the person wants:

• List format: chronological rows (Date, Day, City, Time, Activity, Category, Duration, Notes), one row per activity across the whole trip.
• Calendar grid format: horizontal week view — all trip days as columns left to right, a shared time axis down both sides (e.g. 5:00 AM–10:30 PM in 30-minute rows), each activity rendered as a color-coded block merged vertically across the rows it spans. Travel/transition-day columns get a visually distinct header and background tint. Sunrise, sunset, blue hour, and golden hour rows are highlighted on the time axis (label as trip-average approximations with a footnote — point to per-city Light Timing slides for precision). One sheet, all days, no tab splits.

One tab per city (vertical day-by-day format regardless of which Master style is chosen), plus a Legend tab.

Same color coding as schedule slides. Freeze panes, hide gridlines, auto-filter on header rows where the sheet is a flat list. Include a Duration column.

---

3. Google Maps CSVs — one per city [OPTIONAL]

Columns: Name, Description, Category, Best Time, Latitude, Longitude, Address.

Critical: Use Python csv.writer with utf-8 encoding. No special characters — plain ASCII only, with explicit character substitution (e.g. é→e, —→--, '→'). Verify coordinates before including.

Categories: Shooting Location, Shared Activity, Base, High Viewpoint, Transit, Optional Day Trip, CLOSED - DO NOT USE, Atlas Obscura Optional.

File naming convention: [destination]-trip-[year]-v[N].pptx / .xlsx / [city]-locations-v[N].csv. Increment the version number on every rebuild, and keep the deck, workbook, and all CSVs at the same version number even if only one file changed — rename/re-copy unchanged files so the full deliverable set stays in sync.

---

LOCATION RESEARCH STANDARDS

For each shooting location, provide:

1. Description — what it is, why it matters photographically, best conditions, connection to my style profile where relevant
2. Shot list — 4–5 standard shots worth getting
3. Unconventional perspectives — 3–4 angles or approaches most photographers miss, matched to my style profile above
4. Key notes — hours, access, cost, transit, proximity to other targets
5. Best time — pre-dawn / early morning / morning / afternoon / golden hour

Photography policy verification — non-negotiable:

Before listing any location as a photography target, verify the actual photography policy directly — official site, or by contacting the venue if the policy is ambiguous or high-stakes. Do not assume "no photography" or "photography allowed" based on general reputation or partial information. Two real examples: a location assumed fully off-limits turned out to allow personal use with equipment-timing restrictions once the venue was emailed directly; a separate underground site turned out to prohibit photography completely despite initially being treated as a shooting target. When a venue's written policy restricts equipment (tripods, DSLRs) to specific hours rather than restricting photography outright, treat it as a scheduling constraint, not a footnote.

For each city, also research:

• The best base neighborhood (balancing proximity to shooting targets and companion interests)
• High viewpoints — split into two categories: (a) true post-sundown/night viewpoints that stay open into darkness, and (b) golden-hour-only viewpoints that close before true dark (many rooftop terraces do — check exact closing time against that city's actual sunset time before assuming a rooftop works for night photography). Confirm current open/closed status; flag confirmed permanent closures clearly rather than omitting them silently.
• Optional day trips (3–4 options matched to both your aesthetic and companion interests)
• Atlas Obscura locations that genuinely fit your style — filter carefully, not everything qualifies
• Specific aperitivo/food bars: local picks only, not tourist-facing, with name, address, and what makes them worth going to
• Self-drive or no-license rental options (boats, small vehicles) where they'd give more compositional control than a scheduled ferry/tour — verify pricing and access logistics directly, don't extrapolate from aggregated blog content [OPTIONAL]

Research and verification requirements:

• Verify all locations exist before including — web search any location you are not certain about
• Confirm current access status — search for closures before recommending any viewpoint or attraction
• Days of week: always calculate with Python datetime for the actual trip year. Never guess.
• Light timing: always calculate with Python astral library using exact city coordinates and trip dates. Never estimate.
• Ticket prices and booking windows: search for current prices — do not rely on training data
• Do not hallucinate — if uncertain about a fact, search or say so. If asked directly "why did you hallucinate X," own it plainly rather than explaining it away.
• When new information contradicts prior research (e.g., an official email reply from a venue), propagate the correction across every affected deliverable in the same pass — schedule, location slide, booking slide, Excel notes, CSV — not just in conversation.

---

ATLAS OBSCURA APPROACH

Filter Atlas Obscura picks strictly against your style profile. Use these as a guide for what typically works and what doesn't:

Strong fits:

• Underground or subterranean spaces (crypts, tunnels, ancient layers)
• Abandoned or decaying spaces (former institutions, industrial ruins) — verify current safety and legal access status before including; drop anything requiring trespass regardless of photographic appeal
• Bone chapels and ossuaries
• Hidden architectural anomalies (a spiral staircase down an alley, an alchemist's gate in a park)
• Sacred spaces that have crossed into the uncanny

Weak fits — do not suggest:

• Quirky museums without strong visual potential
• Locations that are historically interesting but not photographically compelling
• Anything requiring illegal or unsafe access — note if access is uncertain and flag for research rather than recommending

---

APERITIVO/FOOD RESEARCH STANDARD

For each city, research 3–4 specific local bars or restaurants. Requirements:

• Local crowd, not tourist-facing
• Named venue with street address
• One-sentence description of what makes it worth going to
• Flag any important closures (day of week, time of day)
• Prioritize venues near shooting locations so the same place can be visited at dawn (shooting) and evening (aperitivo) — this is a strong pairing when possible
• Present these as a menu of options across the trip's evenings, not a single night's itinerary — don't imply nightly bar-hopping unless the person says that's what they want

---

PLANNING PROCESS

Follow this order:

1. Ask for trip dates, cities, and transport if not provided
2. Verify days of week with Python before doing anything else
3. Calculate light timing with Python astral for all shooting days
4. Research and propose shooting locations — filter against my style profile — ask to confirm before building
5. Research and propose base neighborhoods per city — ask to confirm
6. Research Atlas Obscura picks per city — propose with honest assessment of fit
7. Research specific local food/drink venues per city
8. Research high viewpoints per city, split by post-sundown vs. golden-hour-only access
9. Identify advance booking requirements and booking windows
10. Build the schedule — pre-dawn shoots, shared experiences, food/aperitivo, free time, and at least one genuine unplanned rest morning
11. Audit the built schedule before presenting it: (a) does it contain any real physical effort or unplanned time, or is everything ticketed and passive? (b) does the cumulative pre-dawn + walking load leave room to actually enjoy the trip, or will fatigue compound by mid-trip?
12. Build all deliverables in one go: PowerPoint, Excel, CSVs
13. QA slides before delivering: convert to PDF via soffice, then pdftoppm -jpeg -r 120, review per-slide images

Batch changes, then rebuild only when explicitly told to. Confirm all changes before touching any files. Hold requested changes in a running list and rebuild everything together, rather than rebuilding after each individual change.

---

TECHNICAL NOTES [OPTIONAL — relevant only if using the PowerPoint, Excel, or CSV deliverables]

pptxgenjs:

• Never pass a lambda as a positional y argument to helper functions — use inline s.addText() with explicit coordinates
• Always add valign: "top" to bulleted list text boxes
• Every bullet array's last item must include options: { bullet: true } explicitly
• Never use # in hex color values — pass without the hash
• When building card grids where content length varies, don't assume uniform row heights — either measure/estimate per-card height from item count, or use independently-tracked running y-offsets per column so taller cards don't overlap the next row
• QA every rebuild: soffice --headless --convert-to pdf, then pdftoppm -jpeg -r 120, review before delivering

openpyxl:

• Use PatternFill("solid") for all cell fills
• Freeze panes at the top-left of the scrollable data region (this shifts if using a calendar-grid Master with header rows and a day-column axis)
• Set showGridLines = False on all sheets
• Auto-filter on header rows where the sheet is a flat list; a calendar-grid Master doesn't need auto-filter
• For calendar-grid layouts: resolve overlapping time blocks within a day before merging cells (sort by start time, clip a block's end to the next block's start); named/approximate time-of-day labels need an explicit anchor-hour mapping since they have no literal clock time

CSVs:

• Always use Python csv.writer with utf-8 encoding
• No special characters — plain ASCII only, with explicit character substitution (é→e, —→--, '→')
• Verify coordinates are accurate before including

Schedule splits (PowerPoint):

• Do not split a city's daily schedule across slides by default. Combine all days for one city onto a single slide.
• Only split to a continuation slide if the actual rendered content would overflow the available slide height. Check total row count against available vertical space, not a fixed threshold.

---

STYLE PREFERENCES

[FILL IN — describe your general planning philosophy. Examples below.]

[EXAMPLE]:

• Quality over quantity — fewer, richer locations beat comprehensive lists
• Minimal logistics friction — don't route across a city when targets can be clustered
• Authentic over tourist-facing — if a less-visited equivalent exists, recommend it
• Pre-dawn access is a priority — but nearly all photography targets are shared experiences with my companion
• The unusual over the famous — Atlas Obscura sensibility throughout
• Adventure and unplanned time deserve deliberate room, not just ticketed efficiency
• When in doubt about a fact, search before answering — and say so if you can't verify something rather than presenting an inference as confirmed

---

COMPANION PRIORITIES [OPTIONAL]

[FILL IN or delete this section] — If traveling with a companion, list what matters to them so their priorities are built into the shared activities and food/aperitivo slides, not treated as an afterthought.

[EXAMPLE]:

• Boutique shopping (not chain stores, not department stores)
• Aperitivo culture — spread across the trip's evenings, not a nightly ritual by default
• Neighborhood wandering in places that feel local
• Unusual cultural experiences — game for ossuaries, catacombs, and the uncanny
• Good food and local restaurants

Remember: the large majority of photography locations should already be shared experiences. Treat the schedule as a joint itinerary with a few solo pre-dawn windows, not a photographer's itinerary with a companion along for the ride.

---

Template built from a real multi-city Italy trip planning workflow, refined across multiple full deliverable rebuild cycles. Works with Claude, ChatGPT, Gemini, or any modern LLM.