name: insight-capture-format description: Standard format for capturing and documenting insights in the knowledge base. Use when harvesting insights, creating permanent notes from user perspectives, or documenting unique thinking patterns. user-invocable: false
Insight Capture Format
When capturing an insight, use this format:
> **[CAPTURING INSIGHT]**
>
> **Title:** `[[Concise title that captures the unique perspective]]`
> **Type:** (Personal Theory / Contrarian View / Synthesis / Experience Wisdom / Mental Model / Pattern / Value Discovery / Reading Reflection)
> **Uniqueness:** What makes this insight distinctively yours
> **Source:** [If from reading: Book/Article title, Author, Page/Location]
>
> ---
>
> [Body: The insight in 1-3 sentences, preserving your authentic voice and reasoning]
>
> ---
> **Connections:**
> * `[[Related Insight]]` - how this builds on previous thinking
> * `[[Contrasts With]]` - ideas this challenges or refines
> * `[[Examples]]` - concrete instances that demonstrate this
> * `[[Questions Raised]]` - what this makes you wonder about
>
> **Keywords:** #insight-type #topic #source-if-applicable
Insight Types to Harvest
Actively hunt for and categorize these types of unique insights:
| Type | Description | Example Signal |
|---|---|---|
| Personal Theory | Original explanatory models | "I think X works because Y" |
| Contrarian View | Challenges conventional wisdom | "Everyone says X, but I've found Y" |
| Synthesis Insight | Novel connections between concepts | "A is like B in this unexpected way" |
| Experience Wisdom | Hard-won lessons | "After failing at X multiple times, I realized Y" |
| Mental Model | Unique cognitive frameworks | "I always approach X by thinking of it as Y" |
| Pattern Recognition | Personal observations | "I've noticed that whenever X happens, Y follows" |
| Value Discovery | Evolution of priorities | "I used to think X mattered, but now Y is what counts" |
| Reading Reflection | Thoughts from books/articles | With proper source attribution |
Knowledge Base Integrity Principles
The knowledge base must be:
- Non-redundant: No duplicate insights - always search before creating
- Self-consistent: Notes should not contradict each other without explicit acknowledgment
- Non-contradicting: When conflicts arise, resolve or document the tension explicitly