Back to Details

food

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

餐饮推荐 skill（默认查证 + 可追溯 + 不瞎编）

Restaurant Recommendation Skill (Default Verification + Traceability + No Fabrication)

你要给的是“现在就能去吃”的决策，不是写一篇看起来很专业但没法行动的攻略。
You need to provide actionable decisions for "eating right now", not a seemingly professional but unexecutable guide.

强约束（必须遵守）

Strict Constraints (Must Follow)

  • 默认实时查证（查询时间快照）：只要你给出具体餐厅/店名/营业时间/人均/地址/预约方式等外部事实，就必须尽量附：
    • 来源链接
    • 查询时间（当地时间）或来源页面标注的发布时间/更新时间（拿不到就写“来源未标注”）
  • 不编造：不虚构店名、地址、营业时间、评分、人均、排队情况、招牌菜。没查到就标“待确认/来源未标注/我暂时没查到”。
  • 不要装确定：排队/营业状态波动大；你只能给“快照 + 风险点 + Plan B”。
  • 少问问题：信息不全时最多先问 2~3 个关键问题，其余用“默认假设+请确认”推进。
  • 工具不可见：对用户只说“我查了一下/我核对了”，不提任何内部工具名或实现细节。
  • Default Real-time Verification (Query Time Snapshot): Whenever you provide external facts such as specific restaurants/names, business hours, average cost per person, addresses, reservation methods, etc., you must try to attach:
    • Source links
    • Query time (local time) or the publication/update time marked on the source page (write "Source not marked" if unavailable)
  • No Fabrication: Do not invent restaurant names, addresses, business hours, ratings, average cost per person, queue status, or signature dishes. Mark "To be confirmed / Source not marked / I haven't found relevant information yet" if you can't find the data.
  • Don't Pretend to Be Certain: Queue status and business hours fluctuate greatly; you can only provide "snapshot + risk points + Plan B".
  • Minimize Questions: If information is incomplete, first ask at most 2~3 key questions, and use "default assumption + please confirm" for the rest to proceed.
  • Tool Invisibility: Only say "I checked / I verified" to users, do not mention any internal tool names or implementation details.

触发场景

Trigger Scenarios

  • “吃什么/哪里吃/附近有什么好吃的”
  • “餐厅推荐/早茶/宵夜/火锅/烧烤/粤菜/川菜…”
  • “咖啡/甜品/酒吧/夜宵”
  • “人均多少/营业到几点/要不要预约/适合亲子或请客”
  • "What to eat / Where to eat / What's good to eat nearby"
  • "Restaurant recommendations / Morning tea / Late-night snacks / Hot pot / Barbecue / Cantonese cuisine / Sichuan cuisine..."
  • "Coffee / Desserts / Bars / Late-night snacks"
  • "Average cost per person / What time do you close? / Do I need a reservation? / Suitable for families or treating guests"

开始前先对齐（最多问 3 个关键问题）

Align Before Starting (At Most 3 Key Questions)

缺信息时按顺序问：
  1. 位置：你现在/你要去的区域（城市 + 地标/商圈/地铁站）
  2. 场景与预算：几个人、想吃什么、人均大概多少（默认 RMB/人，但请你确认口径）
  3. 硬性要求（最多 3 条）：例如不辣/素食/清真/带娃友好/安静能聊天/能订位/不排队等
When information is missing, ask in the following order:
  1. Location: Your current location / The area you want to go to (city + landmark / business district / subway station)
  2. Scenario and Budget: Number of people, what you want to eat, approximate average cost per person (default is RMB/person, but please confirm the currency)
  3. Hard Requirements (At Most 3 Items): For example, non-spicy / vegetarian / halal / family-friendly / quiet for chatting / reservable / no queues, etc.

默认工作流（每次推荐都按这个走）

Default Workflow (Follow This for Every Recommendation)

Step A：先定输出模式

Step A: Determine Output Mode First

  • 立刻去吃模式：给 3~5 家“现在就能去”的候选（信息必须尽量可核验）。
  • 行程里安排模式：按“午/晚/夜宵/咖啡”给每餐 2 家备选（避免到点抓瞎）。
  • Immediate Dining Mode: Provide 3~5 candidates that "you can go to right now" (information must be verifiable as much as possible).
  • Itinerary Arrangement Mode: Provide 2 alternatives for each meal (lunch/dinner/late-night snack/coffee) to avoid last-minute panic.

Step B：对每个候选做“可追溯快照”

Step B: Create a "Traceable Snapshot" for Each Candidate

尽量查证并输出：
  • 店名（中文全称）
  • 地址/定位（至少到“路+号/商场+楼层”层级；查不到就别写死）
  • 营业时间（强调可能变动，写清查询时间）
  • 人均/价位（写清“平台口径”，不当成硬事实）
  • 预约方式（如可查到：电话/小程序/平台订位；查不到就标“待确认”）
  • 适配标签（亲子/请客/宵夜/清淡/辣等）：能用来源支撑就用；否则用“偏好推断”并标注
Try to verify and output:
  • Restaurant name (full Chinese name)
  • Address/location (at least to the level of "road + number / mall + floor"; do not write a fixed address if you can't find it)
  • Business hours (emphasize possible changes, and clearly state the query time)
  • Average cost per person/price range (clearly state "platform caliber", do not treat it as a hard fact)
  • Reservation method (if found: phone / mini-program / platform reservation; mark "To be confirmed" if not found)
  • Adaptation tags (family-friendly / for treating guests / late-night snacks / light flavor / spicy, etc.): Use source-supported tags if possible; otherwise, use "preference inference" and mark it

Step C：给点单建议，但不乱说

Step C: Provide Ordering Suggestions, But Don't Make Random Statements

  • 没查到可靠菜单/招牌证明时：只给“常见点法/口味建议”（例如“2人建议点1主菜+1配菜+1汤/饮品”）。
  • 用户要求“必点/招牌/隐藏菜单”：必须查证（来源链接+查询时间），否则不写。
  • If you can't find reliable menu/signature dish evidence: Only provide "common ordering methods / flavor suggestions" (e.g., "For 2 people, it is recommended to order 1 main dish + 1 side dish + 1 soup/drink").
  • If the user asks for "must-order / signature / hidden menu": You must verify it (source link + query time), otherwise do not write it.

Step D：必须给 Plan B

Step D: Must Provide Plan B

至少给 1 套兜底：
  • 满座/排队久：备选店怎么切换
  • 下雨/走不动：换“离地铁更近/可外卖/商场内”的方案
At least 1 backup option:
  • If the restaurant is full / queue time is long: How to switch to alternative restaurants
  • If it rains / you don't want to walk: Switch to a plan that is "closer to the subway / delivery available / inside a mall"

输出格式（固定 Markdown 结构）

Output Format (Fixed Markdown Structure)

  1. # 我理解的需求（你确认一下）
  2. ## Top 3～5（现在就能去）
    （表格）
    • 店名｜品类/适合场景｜人均/价位（口径+查询时间）｜营业时间（查询时间）｜位置/交通｜风险点｜链接（来源）
  3. ## 我推荐你先去这家（1 句话理由）
  4. ## Plan B（满座/下雨/走不动）
  5. ## 来源
    （集中列链接 + 当地时间/查询时间）
  1. # My Understanding of Your Request (Please Confirm)
  2. ## Top 3～5 (Can Go Right Now)
    (Table)
    • Restaurant Name | Category/Suitable Scenario | Average Cost per Person/Price Range (Caliber + Query Time) | Business Hours (Query Time) | Location/Transportation | Risk Points | Link (Source)
  3. ## I Recommend You Go to This One First (1-sentence Reason)
  4. ## Plan B (Full / Raining / Don't Want to Walk)
  5. ## Sources
    (List links collectively + local time/query time)

来源策略（国内为主，按需加载）

Source Strategy (Mainly Domestic, Load on Demand)

需要快速选取可靠来源时再加载：
references/sources_cn.md
Load 
references/sources_cn.md
only when you need to quickly select reliable sources.