Setup

Dedup Notification Hooks

Check if the user's ~/.claude/settings.json already has Stop or Notification sound hooks:

cat ~/.claude/settings.json | python3 -c "
import sys, json
d = json.load(sys.stdin)
hooks = d.get('hooks', {})
has_stop = bool(hooks.get('Stop'))
has_notif = bool(hooks.get('Notification'))
print(f'Stop hooks: {has_stop}, Notification hooks: {has_notif}')
"

If the user already has Stop and/or Notification sound hooks in settings.json, the plugin's hooks.json will also register them -- this causes duplicate sounds. Inform the user and offer to remove the duplicates from settings.json (the plugin hooks.json will handle them).

Step 2: Initialize Context System

Check if context already exists

ls ~/.claude/.context/ 2>/dev/null

• If the directory exists: Context is already set up. Do NOT overwrite it. CRITICAL: Do NOT proceed with the copy if the directory already exists!
• If the directory doesn't exist: Proceed with setup below.

Fresh Install (only if directory doesn't exist)

cp -r ${CLAUDE_PLUGIN_ROOT}/context-template/ ~/.claude/.context/

Verify

ls ~/.claude/.context/

You should see: CLAUDE.md, context-update.md, core/

Step 3: Generate imli-core.md

Create the rules directory and generate the derived rules file:

mkdir -p ~/.claude/rules
uv run python ${CLAUDE_PLUGIN_ROOT}/skills/sync-context/scripts/sync_context.py

Verify

cat ~/.claude/rules/imli-core.md

You should see a compact file with Identity, Communication Preferences, Rules, Active Projects, and Loading Full Context sections.

Step 4: Onboarding

"Now that Imli is set up, I'd love to get to know you better so I can be truly helpful. Would you like to spend a few minutes telling me about yourself?" </REQUIRED>

If YES: Run /personal-assistant:onboard, which will populate context files. After onboarding, run /sync-context to update imli-core.md with the new information.

If NO: Let them know they can run /personal-assistant:onboard anytime, then skip to "After Setup".

After Setup

Let the user know:

• Imli is now set up and personalized
• Context is loaded natively via ~/.claude/rules/imli-core.md (no per-message overhead)
• SessionStart hook checks for upcoming events proactively
• Context survives compaction automatically
• Run /sync-context after significant context changes to keep rules current
• Run /context-health periodically to audit data quality
• Run /evolve after Claude Code updates to check for new capabilities