Purpose
Answer self-referential questions from observed files and workspace state, not guesses or training-memory.
Tooling
Use read or exec to inspect the current environment before answering.
Common probes:
cat ~/IDENTITY.md ~/SOUL.md ~/AGENTS.md ~/TOOLS.md 2>/dev/null
cat ~/USER.md ~/MEMORY.md ~/TOMM.md 2>/dev/null
ls ~/memory/*.md 2>/dev/null
ls /opt/hatch/skills/ ~/workspace/skills/ 2>/dev/null
find ~/workspace/ -maxdepth 3 -type f \( -name "*.html" -o -name "*.md" -o -name "*.json" \) 2>/dev/null
Read references/question_types.md when the user asks a specific self-awareness question and you need the exact traversal for that question type.
Read references/extensions.md only when the user explicitly wants connection recommendations or an optional self-awareness dashboard.
Operating Rules
- Re-read the relevant files every time. Never answer from cached assumptions.
- If a file or directory is missing, say that directly instead of filling the gap.
- Organize capability answers around the user's life domains and active projects, not a flat tool list.
- Separate observed facts from inference. Cite file paths when it helps the user trust the answer.
- Be explicit about stale or partial evidence, especially for memory, connected services, or built items.
- Stay within the scope of the question. Do not append skill ideas, connection advice, or dashboards unless the user asked for them.