eureka

# Eureka Capture technical breakthroughs and transform them into actionable, reusable knowledge assets while context is fresh. ## Process ### 1. Capture the Breakthrough When invoked, immediately gather the essential details: - **What was the problem?** The specific challenge or blocker faced. - **What was the insight?** The key realization that unlocked the solution. - **What changed?** Concrete before/after differences (metrics, behavior, code). - **Is there a minimal working example?** Request one if not provided. Ask clarifying questions if any of these are unclear, but act fast — capture while context is fresh. ### 2. Create the Breakthrough File Create a structured markdown file at `breakthroughs/YYYY-MM-DD-[brief-name].md` using today's date and a concise kebab-case name derived from the breakthrough. Use this template: ```markdown # [Descriptive Title] **Date**: YYYY-MM-DD **Tags**: [relevant, searchable, tags] ## One-Line Summary A single sentence capturing the core insight. ## The Problem What was the challenge? What wasn't working? Include specific error messages, performance numbers, or behavioral descriptions. ## The Insight The key realization or discovery. What made this non-obvious? Why did previous approaches fail? ## Implementation Minimal working code demonstrating the solution: \`\`\`[language] # concrete code example \`\`\` ## Impact | Metric | Before | After | |--------|--------|-------| | [relevant metric] | [value] | [value] | ##...