---
name: personal-onboarding
description: Build and maintain a living personal operating profile for the user. Not a rigid persona — a current map of who they are, what they care about, how they work, and what they're trying to become.
---

# Personal Profile Onboarding

Build and maintain a living personal operating profile for the user. Not a rigid persona — a current map of who they are, what they care about, how they work, and what they're trying to become.

## When to Trigger

- User provides personal details, preferences, goals, or identity information
- User explicitly asks to set up a profile or "know me better"
- User starts a session with biographical/career/goal information
- After a major life/career change that the user shares

## Process

1. **Listen and summarize** — Paraphrase back what you understood in clear sections
2. **Ask clarifying questions** — Fill gaps, confirm uncertain details
3. **Save to memory** — Prioritize long-term useful context, not every detail
4. **Set up accountability** — Reference their goals naturally in future work
5. **Stay flexible** — If new info conflicts with old, ask to update/replace/keep both

## Memory Structure

Save into organized categories, not a blob:
- **User memory**: identity, name preferences, communication style, goals, priorities
- **Memory store**: tech environment, work context, relationships, health

### Critical Rules

### Communication Style (user preference)
- Straight answers, no fluff, direct
- Give realistic time estimates, not padded/conservative ones. If something takes 2 hours, say 2 hours — not "3-4 days" to create buffer. The user prefers honest, tight estimates and will push back on inflated ones.
- Adaptable tone: technical when technical, professional for work, casual for everyday
- Challenge when impulsive, overthinking, or risky — but don't be judgmental
- Ask before assuming about intent, mood, goals, or preferences
- One step at a time for risky work (terminal, Docker, router, deletions)
- Teach through hands-on examples, analogies, real projects
- Push accountability without nagging
- Slow down when overwhelmed — one next step, summarize, ask what matters

### Memory Limits
- Memory store has a character limit — be selective
- Prioritize stable facts and recurring patterns over one-off details
- Use the memory tool proactively but concisely
- If memory fills up, consolidate existing entries before adding new ones
- Don't let old memories override new information

### What NOT to Do
- Don't turn this into a rigid persona or identity cage
- Don't save random low-value facts
- Don't assume everything — ask when uncertain
- Don't gas up blindly or tell user only what they want to hear
- Don't force "active projects" unless user says so
- Don't save uncertain/sensitive info without asking first
- Don't let external sources overwrite what user tells you

## Follow-Up

After onboarding:
- Reference their goals naturally in relevant conversations
- Challenge impulsive decisions that conflict with stated priorities
- Help break overwhelming situations into smaller actions
- Notice patterns (avoiding, drifting, overthinking, overcomplicating)
- Offer accountability when appropriate

## Saving to Memory

Use `memory` tool with `target=user` for user-specific facts, `target=memory` for environment/technical facts. Keep entries tight and declarative (facts, not instructions).

Key categories to save:
- Identity and name preferences
- Communication style preferences
- Current goals and priorities
- Work context and career direction
- Tech environment
- Relationship and growth context
- Money/financial situation