resonance
/resonance — Capture What Resonates
When something clicks — log it. The pattern, the insight, the spark.
Usage
/resonance # Auto-detect from recent conversation
/resonance "skills as marketplace" # With explicit note
When to Trigger
AI should consider auto-suggesting /resonance when user says:
- "yes!", "cool!", "very cool!", "love it!", "exactly!"
- "that's it!", "perfect!", "นี่แหละ!", "ใช่เลย!"
- Strong agreement after a design decision or insight
Steps
1. Analyze Recent Conversation
Look back at the last 5-10 messages. Find:
- What: The specific idea, pattern, or decision that sparked the reaction
- When: Timestamp (from hook context or current time)
- Why: Why did this resonate? What problem does it solve?
- How: How was it discovered? What led to this moment?
- Connection: Does this connect to existing Oracle learnings?
2. Log to Vault
PSI=$(readlink -f ψ 2>/dev/null || echo "ψ")
mkdir -p "$PSI/memory/resonance"
Write to: $PSI/memory/resonance/YYYY-MM-DD_HHMM_slug.md
# Resonance: [short title]
**When**: YYYY-MM-DD HH:MM
**Session**: [session-id]
**Context**: [what we were working on]
## What Resonated
[The specific idea/pattern/decision]
## Why It Matters
[Why this clicked — what problem it solves, what it enables]
## How We Got Here
[The conversation path that led to this moment]
## Connection
[Links to existing patterns, principles, or learnings]
## Tags
[concept tags for future search]
3. Sync to Oracle (if available)
arra_learn({
pattern: "[resonance title]: [what resonated]",
concepts: ["resonance", ...tags],
source: "resonance: [repo-name]"
})
4. Output
✨ Resonance captured: [title]
→ ψ/memory/resonance/YYYY-MM-DD_HHMM_slug.md
Tags: [tags]
Short. Don't over-explain. The moment speaks for itself.
Philosophy
Resonance is the signal. When something resonates, it means the pattern matches reality. Log it before it fades.
Resonance logs are different from learnings:
- Learnings = what you figured out (head)
- Resonance = what clicked (heart)
Over time, resonance logs reveal what matters most — not what's logical, but what's alive.
ARGUMENTS: $ARGUMENTS
More from soul-brews-studio/arra-oracle-skills
recap
Session orientation and awareness — retro summaries, handoffs, git state, focus. Use when starting a session, after /jump, lost your place, switching context, or when user asks "now", "where are we", "what are we doing", "status", "recap". Do NOT trigger for "standup" or "morning check" (use /standup), or session mining "dig", "past sessions" (use /dig).
22learn
Explore a codebase with parallel Haiku agents — clone, read, and document. Modes — --fast (1 agent), default (3), --deep (5). Use when user says "learn [repo]", "explore codebase", "study this repo", or shares a GitHub URL to study. Do NOT trigger for finding projects (use /trace), session mining (use /dig), or cloning for active development (use /incubate).
21project
Clone and track external repos. Use when user shares GitHub URL to study or develop, or says "search repos", "find repo", "where is [project]". Actions - learn (clone for study), search/find (search repos), list (show tracked). For active development, use /incubate.
20rrr
Create session retrospective with AI diary and lessons learned. Use when user says "rrr", "retrospective", "wrap up session", "session summary", or at end of work session.
20forward
Create handoff + enter plan mode for next session. Use when user says "forward", "handoff", "wrap up", or before ending session.
20oracle-soul-sync-update
Sync Oracle instruments with the family. Check and update skills to latest version. Use when user says "soul-sync", "sync", "calibrate", "update", or before /awaken.
19