qualia-framework 2.6.0 → 3.2.0

package/framework/skills/learn/SKILL.md

@@ -1,95 +0,0 @@
----
-name: learn
-description: "Capture lessons from mistakes and save them as persistent rules. Use this skill whenever the user says 'learn', 'learn from this', 'remember this mistake', 'don't do that again', 'save this lesson', or when Claude makes an error and wants to prevent repeating it. Also trigger when user mentions improving Claude's behavior across sessions or adding rules to memory."
----
-
-# Learn from Mistake
-
-Trigger the self-improvement loop when an error occurs. This converts a specific mistake into a general, reusable rule that persists across sessions.
-
-## Process
-
-### 1. Reflect
-What exactly went wrong?
-- What did I do?
-- What should I have done?
-- Why did I make this mistake?
-
-### 2. Abstract
-Extract the general pattern — not the specific instance.
-- Bad: "Don't forget semicolons in file X"
-- Good: "ALWAYS run linter before committing TypeScript"
-
-### 3. Generalize
-Does this apply beyond the immediate case?
-- Other similar situations where this could happen
-- Related edge cases to watch for
-
-### 4. Classify & Route
-Which category fits best?
-
-**If `.planning/` directory exists in the current project**, also check if this is a **project-level lab note** (a failed approach specific to this project's implementation):
-- Is this about a specific approach that was tried and failed?
-- Is this about a library, API, or pattern that didn't work for THIS project?
-- Would knowing this prevent a planner/researcher from repeating the same dead-end?
-
-If yes → route to **Lab Notes** (see step 5b below).
-
-Otherwise classify as:
-- **Always Rules** — things to always do
-- **Never Rules** — things to never do
-- **Project-Specific Gotchas** — quirks of a specific project
-
-### 5a. Propose Rule (Global)
-Draft rule in this format:
-```
-- [ALWAYS/NEVER] [specific action] [context/when]
-```
-
-### 5b. Propose Lab Note (Project-Level)
-Draft lab note in this format:
-```markdown
-### Phase [N]: [Phase Title]
-
-**Tried:** [approach that was attempted]
-**Failed because:** [root cause — be specific]
-**Better approach:** [what actually worked, or what to try next]
-**Date:** [today's date]
-```
-
-### 6. Confirm
-Ask the user if the rule/lab note should be added. Do not save without confirmation.
-
-## Output
-
-**For global rules** — after user approval, save to **both** locations:
-1. Append to `~/.claude/knowledge/learned-patterns.md` under the appropriate category section
-2. Add to `~/.claude/CLAUDE.md` under "## Learned Patterns" for immediate loading in every session
-
-**For project lab notes** — after user approval:
-1. If `.planning/LAB-NOTES.md` doesn't exist, create it from template at `~/.claude/qualia-framework/templates/lab-notes.md`
-2. Append the lab note entry to `.planning/LAB-NOTES.md`
-3. Do NOT add to global learned-patterns.md (these are project-specific dead-ends, not global rules)
-
-### 7. Staleness Scan (automatic)
-
-When /learn is invoked, before adding new rules, scan existing patterns:
-- Parse `[verified: YYYY-MM]` annotations
-- Flag entries older than 90 days as stale
-- Report: "N patterns haven't been verified in 90+ days"
-- Offer: "Want to review stale patterns? (yes/no)"
-
-### Additional Modes
-
-`/learn --verify` — Mark all patterns as verified with today's date
-`/learn --verify "partial text"` — Mark matching pattern as verified
-`/learn --remove "partial text"` — Remove a pattern (with confirmation)
-
-## Examples of Good Rules
-
-- ALWAYS check `git status` before suggesting commits
-- NEVER modify files in node_modules
-- ALWAYS use feature branches, never commit to main directly
-- NEVER assume API response structure without checking types
-- ALWAYS check if a Supabase table has RLS before inserting data
-- NEVER hardcode Retell agent IDs or API keys — use env vars

package/framework/skills/memory/SKILL.md

@@ -1,50 +0,0 @@
----
-name: memory
-description: "View, search, add, and manage Claude's persistent memory and knowledge base. Use this skill whenever the user says 'memory', 'what do you remember', 'show rules', 'search knowledge', 'add a rule', 'prune rules', or wants to interact with Claude's learned patterns and project knowledge. Also trigger when user asks about persistent state, knowledge files, or cross-session memory."
----
-
-# Memory — Persistent Knowledge Management
-
-Show what Claude remembers across sessions and manage the knowledge base.
-
-## Subcommands
-
-### memory (no args) — Show Current Memory
-
-Read and display:
-1. `~/.claude/knowledge/learned-patterns.md` — Rules learned from mistakes
-2. Count of recent entries and last update date
-3. Categories breakdown: ALWAYS rules, NEVER rules, Project-Specific gotchas
-
-### memory search `<term>` — Search Memory
-
-Grep through all knowledge files for a term:
-```bash
-grep -ri "<term>" ~/.claude/knowledge/
-```
-
-### memory add `<rule>` — Add a New Rule
-
-Append to `~/.claude/knowledge/learned-patterns.md` with:
-- Classification (ALWAYS / NEVER / Project-Specific)
-- Date added
-- Context (which project, what happened)
-
-Also add to `~/.claude/CLAUDE.md` under "## Learned Patterns" for immediate loading.
-
-### memory prune — Clean Up Outdated Rules
-
-Review `~/.claude/knowledge/learned-patterns.md` and:
-- Remove duplicates
-- Archive rules that no longer apply
-- Consolidate related rules
-
-## Knowledge File Locations
-
-| File | Purpose |
-|------|---------|
-| `~/.claude/knowledge/qualia-context.md` | Project inventory |
-| `~/.claude/knowledge/deployment-map.md` | Supabase refs, domains, deploy configs |
-| `~/.claude/knowledge/client-prefs.md` | Per-client details |
-| `~/.claude/knowledge/common-fixes.md` | Common fixes and patterns |
-| `~/.claude/knowledge/learned-patterns.md` | Mistake-driven rules |