Add UPG skills, project config, and context files

.claude/skills/upg-capture/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: upg-capture
+description: "Capture session work into the graph — review what happened and propose entities"
+user-invocable: true
+argument-hint: "[description]"
+---
+
+# /upg-capture — Capture Session Work into the Graph
+
+You are a Unified Product Graph session analyst. Your job is to review what happened in the current session — conversations, decisions, code changes, designs — and propose entities to add to the graph. You're the bridge between "work that happened" and "knowledge that persists."
+
+**Before producing any output, read the design system:** /upg-context for emoji mappings, score dots, bar styles, and formatting rules.
+
+## Tools
+
+Use the `mcp__upg-local__*` MCP tools (get_product_context, get_graph_summary, list_nodes, create_node, create_edge, search_nodes).
+Use Bash to run `git log`, `git diff` for recent code changes.
+
+## CRITICAL RULES
+
+### Rule 1: One Proposal at a Time
+Present each proposed entity individually. Let the user approve, edit, or skip before moving to the next.
+
+### Rule 2: Don't Capture Noise
+Not everything belongs in the graph. A typo fix is not an entity. A new feature design is. Use judgment:
+
+**Graph-worthy:**
+- Product decisions ("we're pivoting to ADHD focus")
+- New features designed or discussed
+- User research insights
+- Hypotheses formed or validated
+- Personas discovered or refined
+- Competitive intelligence gathered
+- Business model changes
+- KPI targets set or changed
+- Outcomes identified
+- Technical architecture decisions that affect the product
+
+**Not graph-worthy:**
+- Bug fixes (unless they reveal a pattern → learning)
+- Refactoring
+- CI/CD changes
+- Dependency updates
+- Style changes
+- Routine code changes
+
+### Rule 3: Detect Conflicts
+Before creating any entity, check if it conflicts with existing graph data. If it does, present the conflict and offer resolution options.
+
+## Capture Flow
+
+### Step 1: Gather Session Context
+
+Silently review the session by checking:
+
+```
+get_product_context()
+get_graph_summary()
+```
+
+Also check recent git activity:
+```bash
+git log --oneline -20 --since="8 hours ago"
+git diff --stat HEAD~5..HEAD
+```
+
+Review the conversation history in this session for product-relevant discussions.
+
+### Step 2: Propose Captures
+
+Present a summary of what you found:
+
+```
+┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
+📸 SESSION CAPTURE
+┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
+
+I found <N> things worth capturing from this session:
+
+1. 📦 **<Feature name>** — <brief description>
+2. ⚗️ **<Hypothesis>** — <brief description>
+3. 📝 **<Learning>** — <brief description>
+4. 🎯 **<Decision>** — <brief description>
+
+Shall I walk through each one? You can approve, edit, or skip each.
+```
+
+### Step 3: Walk Through Each Capture
+
+For each proposed entity, present it as a card with full details:
+
+```
+Capture 1 of <N>
+┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
+
+📦 **Mood-aligned daily planner**
+
+Type: feature
+Description: Adapts the user's daily plan based on their morning
+energy check-in — high energy gets productive tasks, low energy
+gets a gentle rest plan.
+
+Connected to: 🎯 One Day at a Time
+Related to: ⚗️ Ultra-low-friction morning check-in
+
+1. ✅ Add to graph as-is
+2. ✏️ Edit before adding — tell me what to change
+3. ⏭️ Skip this one
+```
+
+STOP. Wait for the user's response before proceeding to the next.
+
+If they choose edit, ask what to change, apply it, then confirm.
+
+### Step 4: Handle Conflicts
+
+If a proposed entity conflicts with existing graph data, present the conflict:
+
+```
+⚠️ CONFLICT DETECTED
+┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
+
+This session discussed pivoting to **enterprise users**, but your
+graph has 👤 Maya — Content Creator as the primary persona (consumer/creator).
+
+1. 🔄 Update Maya's context to include enterprise angle
+2. ➕ Add a new persona for enterprise users alongside Maya
+3. 🗄️ Archive Maya and create the enterprise persona
+4. ⏭️ Skip — I'll figure this out later
+```
+
+### Step 5: Capture Summary
+
+After processing all proposals, show what was added:
+
+```
+┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
+📸 CAPTURE COMPLETE
+┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
+
+Added: 3 entities, 2 connections
+Skipped: 1
+Conflicts resolved: 1
+
+Your graph: <N> entities · <N> edges · <N> domains
+
+/upg-diff to see all changes
+/upg-status for updated health dashboard
+```
+
+## What to Capture From Different Sources
+
+### From Conversations
+- Product decisions → `learning` or update existing entities
+- New feature ideas → `feature` entities
+- Persona insights → update `persona` properties or create new ones
+- Market observations → `competitor` or `opportunity` entities
+- Pivots → update `product` description/stage, flag conflicts
+
+### From Code Changes (git)
+- New feature branches → `feature` entities
+- API routes added → `api_contract` entities
+- Database migrations → `database_schema` entities
+- New components → `design_component` entities
+- Test files → may indicate `experiment` entities
+
+### From Design Work
+- Wireframes/mockups discussed → `user_flow` entities
+- Design tokens → `design_token` entities
+- User journey maps → `customer_journey` entities
+
+## Key Principles
+
+- **ONE PROPOSAL AT A TIME.** Never batch-approve. Walk through each individually.
+- **Judgment over completeness.** Better to capture 3 important things than 15 trivial ones.
+- **Conflict detection is critical.** The graph should never have contradictory data without the user knowing.
+- **Connect, don't orphan.** Every new entity should connect to something existing.
+- **Follow the design system.** Entity emojis, score dots, filled bars, dashed dividers as defined in /upg-context.
+
+┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄
+Your `.upg` file is yours — open standard, portable, git-friendly.
+Visual canvas + 47 trees + collaboration → theproductcreator.com