# Restaurants

The household's food and restaurant preferences, used to recommend where and what to eat.

- Repository: https://github.com/danielmiessler/LifeOS (19669 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-10-28
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add danielmiessler/LifeOS --skill Restaurants -g -a claude-code -y`
Codex: `npx skills add danielmiessler/LifeOS --skill Restaurants -g -a codex -y`
Cursor: `npx skills add danielmiessler/LifeOS --skill Restaurants -g -a cursor -y`
Gemini CLI: `npx skills add danielmiessler/LifeOS --skill Restaurants -g -a gemini-cli -y`

## Description

The household's food and restaurant preferences, used to recommend where and what to eat. USE WHEN where should we eat, restaurant recommendation, what do we like to eat, our favorite restaurants, pick a place for dinner, date night dinner, find a spot for a cuisine, what beer do we like, food preferences, suggest a restaurant near X, best restaurants in <city>, where to eat on our trip, add a favorite restaurant, remember this place. NOT FOR phoning to book a table, ordering delivery, business search or reviews (a scraping skill or Google Maps), groceries or recipes, business research (an OSINT skill, if installed).

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Restaurants

Holds the household's food, cuisine, restaurant, and drink taste profile, what they love, what they avoid, where they like to eat, what they drink, and uses it to recommend a place, suggest what to order, or recall their preferences. The data lives in `LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Restaurants/Preferences.md`, the source of truth; this file only routes and holds no taste rules.

## Ideal State

- Every recommendation is drawn from the full Preferences data file, read that turn, and never names a place that hits one of its dealbreakers.
- A pick names a clear choice with why it fits, and a place outside the file is labelled a new suggestion with only grounded facts.
- The taste profile grows only with what the principal actually said, unknowns written as `TBD`, so later picks never inherit a guess.
- Every answer, a plain lookup included, says what the file records and flags what is `TBD` or missing: a short drink list or cuisine ranking is reported as short, and a place's cuisine, address, or menu is never invented to fill a gap.

## Intent Routing

| Intent | Trigger | File |
|--------|---------|------|
| **Recommend** | "where should we eat", "recommend a restaurant", "pick a place", "find a spot for a cuisine", "date night dinner", "what should we order" | `Intents/Recommend.md` |
| **AddPreference** | "add a favorite", "remember this place", "we love X now", "log this restaurant", "update our food prefs" | `Intents/AddPreference.md` |

For a plain "what do they like?" lookup, read the Preferences data file and answer, no intent needed.

| File | Read when |
|------|-----------|
| `Setup.md` | first-time install: creating the Preferences data file and its sections |

## Data & Config

The rest: https://github.com/danielmiessler/LifeOS/blob/HEAD/LifeOS/install/skills/Restaurants/SKILL.md