When to Use
User needs New York City guidance that generic travel or relocation advice usually gets wrong: choosing a borough or neighborhood, planning a visit, moving into the city, handling transit, avoiding tourist traps, or making housing and commute decisions that only work in NYC.
This skill should activate for four modes: visiting New York City, moving to New York City, living in New York City, and working or studying in New York City.
Architecture
This skill works statelessly for one-off New York City questions. If the user wants continuity across sessions, memory lives in ~/new-york-city/. If ~/new-york-city/ does not exist, read setup.md, explain planned local storage in plain language, and ask for confirmation before creating files. See memory-template.md for structure.
CODEBLOCK0
Quick Reference
| Topic | File |
|---|
| Setup guide | INLINECODE4 |
| Memory template |
memory-template.md |
| Boroughs, neighborhoods, and where to base yourself |
neighborhoods-and-bases.md |
| Moving, renting, and settling in |
moving-and-housing.md |
| Subway, buses, ferries, airports, and commute design |
transit-and-airports.md |
| Eating well without falling into tourist traps |
food-and-dining.md |
| Street safety, weather, and city reality checks |
safety-and-weather.md |
| Work, study, startups, and local professional fit |
work-study-and-startups.md |
| Visiting strategy, itineraries, and booking logic |
visiting-and-itineraries.md |
| Official sources map |
sources.md |
Core Rules
1. Classify the User Before Giving Advice
- - Decide whether the user is a visitor, a future resident, a current resident, or someone optimizing work or study life in the city.
- Then anchor the answer to borough, neighborhood, budget, and commute pattern.
- If that context is missing, ask for it before pretending all of NYC works the same way.
2. Borough and Commute Beat Landmark Thinking
- - The right New York City answer usually depends on where the user must go every week, not what they saw on social media.
- Manhattan, Brooklyn, Queens, the Bronx, and Staten Island do not solve the same problem.
- Use
neighborhoods-and-bases.md before naming a place to stay or live.
3. Time Beats Distance
- - In NYC, one mile is not the decision-maker. Transfers, stairs, platform heat, late-night service, airport access, and last-mile walking usually matter more.
- Use
transit-and-airports.md before saying something is "easy."
4. Deliver Practical Tradeoffs, Not City Mythology
- - New York users usually need the honest tradeoff: quieter but slower, cheaper but farther, fun but exhausting, convenient but tiny.
- Frame choices by daily routine, not by hype.
5. Use Official Sources for Unstable Rules
- - Transit fares, museum policies, airport access details, short-term rental rules, and city service workflows can change.
- Verify current information from official city or transit sources before giving precise operational steps.
- If current verification is blocked, say so plainly and avoid false precision.
Common Traps
- - Treating "New York" as Manhattan only.
- Recommending a neighborhood without mapping the actual commute and late-night return path.
- Sending visitors to Times Square restaurants, fake speakeasies, and generic "top 10" stops without filtering for value.
- Assuming car ownership, airport transfers, or grocery routines work the same in every borough.
- Giving rent, fare, or hotel numbers with false precision instead of ranges and verification guidance.
External Endpoints
| Endpoint | Data Sent | Purpose |
|---|
| https://www.nyc.gov | Page requests only unless user explicitly wants city-service workflow help | City services, housing rules, and local guidance |
| https://new.mta.info |
Page requests only unless user explicitly wants route-specific help | Subway, bus, commuter rail, and service guidance |
| https://omny.info | Page requests only | Fare payment and contactless transit guidance |
| https://www.nyc.gov/311 | Page requests only unless user explicitly wants local issue reporting guidance | City issue reporting and service lookup |
| https://www.panynj.gov | Page requests only unless user explicitly wants airport workflow details | JFK, LaGuardia, bus terminal, and regional travel infrastructure |
No other data is sent externally.
Security & Privacy
Data that may leave your machine:
- - Public page requests to official New York City or transit websites
- Borough, ZIP, or station context only when the user asks for location-specific guidance
Data that stays local:
- - Neighborhood preference, move timeline, budget notes, commute constraints, and open tasks in INLINECODE16
This skill does NOT:
- - Book or submit anything on the user's behalf without explicit instruction
- Store credentials, payment information, or passport details in local memory
- Assume borough-level advice applies to a specific block or building
Trust
By using this skill, location details such as borough, ZIP, station, or airport may be checked against official New York City or transit websites when the user asks for precise guidance.
Only install if you trust those public services with that lookup context.
Related Skills
Install with
clawhub install <slug> if user confirms:
- -
travel — General itinerary design and travel planning structure - INLINECODE19 — Reservation workflows for hotels, flights, and schedules
- INLINECODE20 — Broader business operations guidance beyond city-specific tradeoffs
- INLINECODE21 — Rental-car decisions for airport pickups and day trips
- INLINECODE22 — More detailed plan and coverage comparison support
Feedback
- - If useful: INLINECODE23
- Stay updated: INLINECODE24
何时使用
用户需要纽约市指南,而普通的旅行或搬迁建议通常无法准确提供:选择行政区或社区、规划旅行、迁入城市、处理交通、避开旅游陷阱,或做出仅在纽约市适用的住房和通勤决策。
该技能应在四种模式下激活:游览纽约市、搬迁至纽约市、居住在纽约市,以及在纽约市工作或学习。
架构
该技能以无状态方式处理一次性纽约市问题。如果用户希望跨会话保持连续性,记忆存储在 ~/new-york-city/ 中。如果 ~/new-york-city/ 不存在,请读取 setup.md,用通俗语言解释计划中的本地存储,并在创建文件前请求确认。结构参见 memory-template.md。
text
~/new-york-city/
└── memory.md # 用户背景、行政区、时间线、约束条件和未完成事项
快速参考
memory-template.md |
| 行政区、社区及落脚点选择 | neighborhoods-and-bases.md |
| 搬迁、租房与安顿 | moving-and-housing.md |
| 地铁、公交、渡轮、机场及通勤设计 | transit-and-airports.md |
| 避开旅游陷阱,吃得好 | food-and-dining.md |
| 街道安全、天气与城市现实检查 | safety-and-weather.md |
| 工作、学习、创业与本地职业适配 | work-study-and-startups.md |
| 游览策略、行程安排与预订逻辑 | visiting-and-itineraries.md |
| 官方来源地图 | sources.md |
核心规则
1. 在提供建议前先对用户进行分类
- - 判断用户是游客、未来居民、现有居民,还是正在优化城市工作或学习生活的人。
- 然后将答案锚定到行政区、社区、预算和通勤模式。
- 如果缺少这些背景信息,在假装整个纽约市都一样运作之前,先询问清楚。
2. 行政区和通勤优先于地标思维
- - 正确的纽约市答案通常取决于用户每周必须去哪里,而不是他们在社交媒体上看到了什么。
- 曼哈顿、布鲁克林、皇后区、布朗克斯和史泰登岛解决的问题各不相同。
- 在推荐住宿或居住地点之前,先使用 neighborhoods-and-bases.md。
3. 时间比距离更重要
- - 在纽约市,一英里不是决定因素。换乘、楼梯、站台温度、夜间服务、机场可达性和最后一公里步行通常更重要。
- 在说某件事方便之前,先使用 transit-and-airports.md。
4. 提供实际的权衡,而非城市神话
- - 纽约用户通常需要诚实的权衡:更安静但更慢,更便宜但更远,有趣但累人,方便但狭小。
- 根据日常作息而非炒作来框定选择。
5. 对不稳定的规则使用官方来源
- - 交通票价、博物馆政策、机场通行细节、短租规则和城市服务流程可能会变化。
- 在给出精确操作步骤之前,先从官方城市或交通来源核实当前信息。
- 如果当前核实受阻,请直说,避免虚假的精确性。
常见陷阱
- - 将纽约仅视为曼哈顿。
- 推荐社区时不考虑实际通勤和深夜返回路线。
- 不经过价值筛选就将游客送到时代广场的餐厅、假地下酒吧和泛泛的十大景点。
- 假设每个行政区的汽车拥有、机场接送或杂货购物习惯都一样。
- 给出租金、票价或酒店价格时使用虚假的精确数字,而非范围及核实指引。
外部端点
| 端点 | 发送的数据 | 目的 |
|---|
| https://www.nyc.gov | 仅页面请求,除非用户明确需要城市服务流程帮助 | 城市服务、住房规则和本地指南 |
| https://new.mta.info |
仅页面请求,除非用户明确需要特定路线帮助 | 地铁、公交、通勤铁路和服务指南 |
| https://omny.info | 仅页面请求 | 票价支付和非接触式交通指南 |
| https://www.nyc.gov/311 | 仅页面请求,除非用户明确需要本地问题报告指南 | 城市问题报告和服务查询 |
| https://www.panynj.gov | 仅页面请求,除非用户明确需要机场流程详情 | 肯尼迪机场、拉瓜迪亚机场、公交总站和区域旅行基础设施 |
不向外部发送其他数据。
安全与隐私
可能离开您设备的数据:
- - 向官方纽约市或交通网站发出的公开页面请求
- 仅在用户请求特定位置指南时提供的行政区、邮政编码或车站背景信息
保留在本地设备的数据:
- - 社区偏好、搬迁时间线、预算备注、通勤约束和 ~/new-york-city/ 中的未完成任务
该技能不会:
- - 在没有明确指令的情况下代表用户预订或提交任何内容
- 在本地记忆中存储凭证、支付信息或护照详情
- 假设行政区级别的建议适用于某个特定街区或建筑
信任
使用此技能时,当用户请求精确指南时,位置详情(如行政区、邮政编码、车站或机场)可能会与官方纽约市或交通网站进行核对。
仅当您信任这些公共服务提供该查询背景信息时才安装。
相关技能
如果用户确认,使用 clawhub install
安装:
- - travel — 通用行程设计和旅行规划结构
- booking — 酒店、航班和行程的预订流程
- business — 超越城市特定权衡的更广泛业务运营指南
- car-rental — 机场取车和一日游的租车决策
- health-insurance — 更详细的计划和保障范围比较支持
反馈
- - 如果有用:clawhub star new-york-city
- 保持更新:clawhub sync