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

Strict Constraints (Must Follow)

• 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"

Align Before Starting (At Most 3 Key Questions)

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: Determine Output Mode First

• 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: Create a "Traceable Snapshot" for Each Candidate

• 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: Provide Ordering Suggestions, But Don't Make Random Statements

• 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: Must Provide Plan B

• 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"

Output Format (Fixed Markdown Structure)

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