preferences

To sync markdown notes for hotels and restaurants to Supabase, you update the preference files in your base directory and trigger the synchronization workflow, which backs up your local entries to the cloud notes backend.

Organizing personal preferences across activities and books is best handled by maintaining dedicated markdown files for each category, ensuring each file includes frontmatter metadata with a name and description for easy discovery.

You do not need a Supabase backend to manage local markdown preference files, as the Skill can read and update entries locally, but Supabase integration is required if you want to synchronize notes across multiple devices.

To add a new hotel preference, you create or update an entry in the hotels.md file within your base directory using the standard template, then trigger a sync to push the note to Supabase if cloud backup is configured.

You can use frontmatter metadata to categorize personal notes for hotels and restaurants by enforcing a name and description within the frontmatter, which enables proper discovery and synchronization of your preference files.

Synchronizing personal preferences without frontmatter metadata faces the limitation of failed discovery, as the Skill enforces frontmatter with a name and description to correctly process and sync markdown files to the Supabase backend.