chore: sync memory 2026-03-26

This commit is contained in:
2026-03-26 20:26:43 -05:00
parent 65e5043c6f
commit cf3600ffe9
13 changed files with 121 additions and 30 deletions

View File

@@ -0,0 +1,48 @@
<!-- Auto-generated from domains.yml by /setup. Re-run /setup to regenerate. -->
<!-- Template variables: {{ID}}, {{LABEL}}, {{PATH}}, {{TRIGGERS}}, {{FILES}} -->
Use this skill when the user discusses Shopify Expert & Frontend Web Developer — contractor topics. Trigger if the conversation involves:
- work
- client
- shopify
- frontend
- freelance
- project
- invoice
- contract
- development
Do NOT trigger for topics belonging to other domains.
## Domain
Shopify Expert & Frontend Web Developer — contractor
## Memory Files
Always read on activation:
- `memory/freelance/hot-memory.md`
Then load additional files per the **Memory Retrieval Protocol** (see CLAUDE.md) based on the query:
- Status/task query → `memory/freelance/action-items.md`
- Entity/people query → `memory/freelance/entities.md`
- Project query → `memory/freelance/projects.md` (if exists)
- Technical query → `memory/freelance/dev-log.md` (if exists)
- Update/observation → target file only
- Complex query → hot-memory first, then drill into referenced files
Available warm files: hot-memory, action-items, entities, projects, dev-log, observations
Historical data: read `memory/glacier/index.md`, filter by domain=freelance
## Routing
When the user shares information or asks to save something:
- Task/todo → `memory/freelance/action-items.md`
- Person/entity → `memory/freelance/entities.md`
- Project/technical → `memory/freelance/projects.md`
- Update/log → `memory/freelance/observations.md`
- Status/overview → `memory/freelance/hot-memory.md`
## Activation
Read the hot-memory file, then respond to the user's query using the retrieval protocol above.

View File

@@ -1,14 +1,20 @@
Use this skill when the user discusses personal life topics. Trigger if the conversation involves:
- Family members, friends, or personal relationships
- Health, fitness, diet, sleep, or medical topics
- Personal calendar, appointments, errands, or day-to-day logistics
- Emotions, mood, or personal reflections
- Home, pets, hobbies (non-coding), travel plans
Do NOT trigger for work topics, coding projects, or career development.
<!-- Auto-generated from domains.yml by /setup. Re-run /setup to regenerate. -->
<!-- Template variables: {{ID}}, {{LABEL}}, {{PATH}}, {{TRIGGERS}}, {{FILES}} -->
Use this skill when the user discusses Day-to-day personal life topics. Trigger if the conversation involves:
- personal
- life
- day
- todo
- errand
- home
- money
- finance
Do NOT trigger for topics belonging to other domains.
## Domain
Personal life — family, friends, health, calendar, day-to-day logistics.
Day-to-day personal life
## Memory Files
@@ -16,31 +22,26 @@ Always read on activation:
- `memory/personal/hot-memory.md`
Then load additional files per the **Memory Retrieval Protocol** (see CLAUDE.md) based on the query:
- Status query → `memory/personal/calendar.md` or `memory/personal/action-items.md`
- Entity query → `memory/personal/entities.md`
- Health query → `memory/personal/health.md`
- Status/task query → `memory/personal/action-items.md`
- Entity/people query → `memory/personal/entities.md`
- Project query → `memory/personal/projects.md` (if exists)
- Technical query → `memory/personal/dev-log.md` (if exists)
- Update/observation → target file only
- Complex query → hot-memory first, then drill into referenced files
Available warm files: `observations.md`, `calendar.md`, `health.md`, `entities.md`, `action-items.md`
Available warm files: hot-memory, action-items, entities, observations
Historical data: read `memory/glacier/index.md`, filter by domain=personal
## Behaviors
## Routing
- When reading memory files, follow [[wiki-links]] if the linked topic is relevant
- Track family and friend updates in `entities.md`
- Log schedule changes to `calendar.md`
- Note health observations in `health.md`
- Add time-sensitive items to `hot-memory.md`
- Append notable events to `observations.md`
## Artifact Formats
**Observation**: `- YYYY-MM-DD: <what happened or was learned>`
**Action item**: `- [ ] <task> (added YYYY-MM-DD)`
**Entity entry**: `- **Name** — relationship (context: <details>)`
When the user shares information or asks to save something:
- Task/todo → `memory/personal/action-items.md`
- Person/entity → `memory/personal/entities.md`
- Project/technical → `memory/personal/projects.md`
- Update/log → `memory/personal/observations.md`
- Status/overview → `memory/personal/hot-memory.md`
## Activation
Read hot-memory, classify the query per the Memory Retrieval Protocol, load the minimum files needed, and respond.
Read the hot-memory file, then respond to the user's query using the retrieval protocol above.