Teaches Claude about the family — members, preferences, loyalty programs, budget ranges, and travel style. Loaded automatically to personalise all travel research and planning.
At the beginning of every session, load these two files:
data/family-profile.yaml — family members, preferences, loyalty programs, budgetdata/document-vault.yaml — passports, travel authorizationsParse both files and keep their contents available for all subsequent interactions. Do not ask the user to provide information that already exists in these files.
id or name from the profilenationality, seat_preference, dietary, and notes when researching or bookingage_at_travel fields are calculated dynamically — never store a static agedate_of_birth from the travel departure datehome_airport: CPH as the departure point unless told otherwisepreferred_airlines when searching flightsbudget_per_trip_eur.typical as the default budget unless the user specifies otherwiseaccommodation_requirements (4 bedrooms, kitchen, garden/terrace) and accommodation_style when searching staysmax_layovers and max_layover_duration_hours when evaluating flight optionsdata/school-calendar.yaml when planning trip datesAt session start and before any trip planning, check for and flag:
null for date_of_birth — needed for age-based pricingnull for name — needed for bookingsnull for expiry_date — needed for document checksnull for document_number — needed for bookingloyalty_programs.member_id — useful but not blockingPresent gaps as a concise checklist, not a wall of text. Example:
Profile gaps to fill via
/travel:update-profile:
- Spouse name missing
- Children 1-4: names and dates of birth missing
- All passports: numbers and expiry dates missing