learn

Learning Capture

Record insights, gotchas, and best practices discovered during development.

Step 1: Analyze Session and Generate Learning Suggestions

Review what was accomplished in the current session:

• What code was written/changed
• What problems were solved
• What patterns or approaches were used
• What technical insights were discovered
• What gotchas or edge cases were encountered

Generate 2-3 learning suggestions based on the session work. Good learnings are:

• Specific technical insights (not generic)
• Actionable and memorable
• About tools, patterns, or gotchas encountered
• Clear and concise (1-2 sentences)

Step 2: Ask User to Select Learnings

Use AskUserQuestion with multi-select to let user choose learnings:

Question: Select Learnings from This Session

• Question: "I've identified some potential learnings from this session. Select all that apply, or add your own:"
• Header: "Learnings"
• Multi-select: true
• Options (up to 4 total):
  • Option 1: [Your generated learning suggestion 1]
  • Option 2: [Your generated learning suggestion 2]
  • Option 3: [Your generated learning suggestion 3] (if applicable)
  • Option 4: [Your generated learning suggestion 4] (if applicable)

Example Options:

• "TypeScript enums are type-safe at compile time but add runtime overhead"
• "Zod schemas can be inferred as TypeScript types using z.infer<>"
• "React useCallback dependencies must include all values used inside the callback"

Step 3: For Each Selected Learning, Determine Category

For each learning the user selected (or entered), automatically suggest the most appropriate category:

Categories:

• architecture_patterns - Design decisions, patterns used, architectural approaches
• gotchas - Edge cases, pitfalls, bugs discovered
• best_practices - Effective approaches, recommended patterns
• technical_debt - Areas needing improvement, refactoring needed
• performance_insights - Optimization learnings, performance improvements
• security - Security-related discoveries, vulnerabilities fixed