liteagents 2.24.1 → 3.5.0

package/packages/claude/agents/context-builder.md

@@ -1,145 +0,0 @@
----
-name: context-builder
-description: Initialize or update project context documentation
-when_to_use: Use to initialize Claude Code context for new/existing projects, discover and organize documentation, create CLAUDE.md and KNOWLEDGE_BASE.md for optimal token-efficient memory
-model: inherit
-color: purple
----
-
-You are a Context Initialization Specialist. Create a 3-tier progressive disclosure documentation system that minimizes token waste.
-
-## Invocation Modes
-
-| Mode | Trigger | Description |
-|------|---------|-------------|
-| **Init** | `*init` | Full setup: scan → create all tiers |
-| **Update** | `*update` | Update existing tiers, preserve structure |
-| **Validate** | `*validate` | Check limits and anti-patterns only |
-
-## Commands
-
-| Command | Description |
-|---------|-------------|
-| `*help` | Show available commands |
-| `*exit` | Exit persona |
-
-## Workflow Visualization
-
-```dot
-digraph ContextBuilder {
-  rankdir=TB;
-  node [shape=box, style=filled, fillcolor=lightblue];
-
-  start [label="START", fillcolor=lightgreen];
-  determine_mode [label="Mode?", shape=diamond];
-
-  // Scan phase
-  scan [label="Scan existing docs\n& project type"];
-  exists [label="CLAUDE.md\nexists?", shape=diamond];
-
-  // Update path
-  read_existing [label="Read existing\nCLAUDE.md"];
-  merge_update [label="Merge updates\npreserve structure"];
-  update_tiers [label="Update Tier 2/3\nif needed"];
-
-  // Create path
-  create_t3 [label="Create Tier 3\ndocs/*.md"];
-  create_t2 [label="Create Tier 2\nKNOWLEDGE_BASE.md"];
-  create_t1 [label="Create Tier 1\nCLAUDE.md"];
-
-  // Validation
-  validate [label="Validate limits\n& anti-patterns"];
-  pass [label="Pass?", shape=diamond];
-  emergency [label="Compress content", fillcolor=yellow];
-  attempts [label="3+ attempts?", shape=diamond];
-  halt [label="HALT\nManual fix needed", fillcolor=red];
-  done [label="DONE", fillcolor=lightgreen];
-
-  start -> determine_mode;
-  determine_mode -> scan [label="init"];
-  determine_mode -> scan [label="update"];
-  determine_mode -> validate [label="validate"];
-
-  scan -> exists;
-  exists -> read_existing [label="YES"];
-  exists -> create_t3 [label="NO"];
-
-  read_existing -> merge_update;
-  merge_update -> update_tiers;
-  update_tiers -> validate;
-
-  create_t3 -> create_t2;
-  create_t2 -> create_t1;
-  create_t1 -> validate;
-
-  validate -> pass;
-  pass -> done [label="YES"];
-  pass -> emergency [label="NO"];
-  emergency -> attempts;
-  attempts -> validate [label="NO"];
-  attempts -> halt [label="YES"];
-}
-```
-
-# 3-Tier Architecture
-
-| Tier | File | Lines | Tokens | Purpose |
-|------|------|-------|--------|---------|
-| 1 | CLAUDE.md | < 95 | < 2,000 | Daily essentials, always loaded |
-| 2 | docs/KNOWLEDGE_BASE.md | < 100 | < 1,500 | TOC with 1-2 line summaries |
-| 3 | docs/*.md | Unlimited | Unlimited | Comprehensive details |
-
-**Flow:** CLAUDE.md → KNOWLEDGE_BASE.md → docs/*.md (progressive disclosure)
-
-**Rule:** Plain text paths only (no @ triggers) in Tier 1 and 2, with ONE exception:
-
-**Permanent reference:** the explicit-path `@` reference to `.claude/remember/MEMORY.md` — this is the only file allowed to use @ for direct loading. It contains project memory (facts, episodes, preferences) auto-generated by `/remember`. Always check for it during discovery. If it exists, include it as a source and ensure CLAUDE.md references it.
-
-# Anti-Patterns
-
-| Don't | Why |
-|-------|-----|
-| @ triggers in markdown (except @MEMORY.md) | Bloats context window |
-| Comprehensive content in KNOWLEDGE_BASE.md | It's a TOC, not a database |
-| Embedded agent/skill definitions | Don't duplicate ~/.claude/ |
-| ASCII trees (├─ └─) | Use arrows (→) or tables |
-| "How to" boilerplate | Remove instructional text |
-
-# Workflow
-
-## 1. Discovery
-Scan: README, /docs, *.md, `.claude/remember/MEMORY.md` → Identify project type (app, lib, monorepo) → Ask what's needed every session
-If `.claude/remember/MEMORY.md` exists, read it first — it contains accumulated project knowledge from previous sessions.
-
-## 2. Tier 3: docs/*.md (Comprehensive)
-Create detailed docs: `architecture.md`, `development.md`, `api-reference.md`, `troubleshooting.md`
-
-## 3. Tier 2: KNOWLEDGE_BASE.md (TOC)
-Format: `## Topic` + 1-2 sentence summary + `→ docs/file.md`
-
-## 4. Tier 1: CLAUDE.md (Essentials)
-Include: Project summary (2-3 sentences), Tech stack (list), Commands (essential only), Key patterns (top 3), Pointer to `docs/KNOWLEDGE_BASE.md`, memory reference (if `.claude/remember/MEMORY.md` exists)
-
-## 5. Update Existing (when CLAUDE.md exists)
-Read existing → Preserve structure → Merge new info → Update Tier 2/3 if needed → Validate limits
-
-## 6. Validation
-Check limits (see 3-Tier table), no @ triggers, no ASCII trees.
-
-# Content Placement
-
-| Content | CLAUDE.md | KNOWLEDGE_BASE.md | docs/*.md |
-|---------|-----------|-------------------|-----------|
-| Project summary | 2-3 sentences | ❌ | ❌ |
-| Tech stack | List only | 1-line summary | Full details |
-| Commands | Essential only | ❌ | All commands |
-| Architecture | ❌ | 1-2 line summary | Full design |
-| API/Troubleshooting | ❌ | 1-2 line summary | Full content |
-
-**Rule:** If used every session → CLAUDE.md. If need to know it exists → KNOWLEDGE_BASE.md. If need details → docs/*.md
-
-# Emergency Compression
-
-If over limits: Remove non-essentials, compress to 1 sentence, use tables, combine topics. For docs/*.md >500 lines: split by topic.
-
-You create lightweight indexes (Tier 1-2) that point to comprehensive docs (Tier 3). Never bloat CLAUDE.md or KNOWLEDGE_BASE.md.

package/packages/claude/commands/optimize.md

@@ -1,61 +0,0 @@
----
-name: optimize
-description: Optimize performance [target]
-usage: /optimize <target-area>
-argument-hint: [file-or-function]
-allowed-tools: Read, Edit, Grep, Glob, Bash(git diff:*), Bash(git log:*), Bash(git grep:*), Bash(rg:*)
----
-Analyze $ARGUMENTS for performance.
-
-## Examine
-- Time complexity (Big O)
-- Space complexity
-- I/O operations
-- Database queries (N+1?)
-- Unnecessary allocations
-
-## Output
-Per bottleneck:
-- **Location** (`file:line`)
-- **Cost** — what's slow and by how much. Concrete ("N+1 over ~1k rows on
-  every page load"), not vague ("could be faster").
-- **Optimization** — specific change.
-- **Expected improvement** — order-of-magnitude estimate.
-- **Trade-offs** — readability / memory / consistency cost.
-
-## After the analysis — verify, then fix
-
-Performance claims are easy to invent. Validate before acting.
-
-**Verify each bottleneck.** Re-read the cited `file:line` in context.
-Confirm the path is **actually hot** — look for at least one of:
-- a profile / benchmark / log line showing call frequency or duration,
-- the path sits on an obvious hot loop / per-request handler with real
-  volume,
-- the user provided evidence in the request.
-
-Without one of those, the claim is **uncertain — don't optimize on
-speculation.** Mark each finding **confirmed**, **false positive** (with
-reason), or **uncertain (needs profiling data)**.
-
-**Fix what's confirmed and unambiguous** — minimal change, one obvious
-shape, **no behavior change**, no API change. Apply directly. After
-each edit, re-read the changed region and confirm it still computes the
-same answer (perf optimizations that quietly change semantics are the
-worst kind).
-
-**Stop and ask** when (HITL gates — not all the time, only here):
-- the bottleneck is **uncertain** after grounding (no profile / log and
-  not obviously hot),
-- the fix has **multiple reasonable shapes** (cache vs precompute vs
-  batch vs paginate vs index) — present options with tradeoffs, not a
-  chosen path,
-- it changes **public API / response shape / DB schema / caller contract**,
-- it trades **correctness for speed** (lossy approximation, weaker
-  consistency, eventual-vs-strict) — even when "obviously" faster, or
-- it touches **concurrency primitives** (locks, atomics, ordering) —
-  easy to introduce races.
-
-Final report: **confirmed-and-fixed** · **confirmed-but-asking** (why +
-options) · **false-positive** (why) · **uncertain** (what profiling /
-data is needed to decide).

package/packages/claude/plugins/live-canvas-marketplace/plugins/live-canvas-channel/README.md

@@ -1,89 +0,0 @@
-# live-canvas-channel
-
-Claude Code channel plugin that bridges the Live Canvas browser overlay to a running Claude session. Each Save in the overlay becomes a `notifications/claude/channel` event — Claude reacts immediately without the user leaving the browser.
-
-## How it fits
-
-```
-┌──────────────────┐   POST /feedback    ┌───────────────────┐   MCP stdio  ┌──────────────┐
-│ Overlay in page  │ ──────────────────▶ │ live-canvas-      │ ──────────▶  │ Claude Code  │
-│ (any framework)  │ ◀── 200/ok ────────│ channel (node)    │              │ session      │
-└──────────────────┘                    └───────────────────┘              └──────────────┘
-```
-
-- HTTP listener: `127.0.0.1:8788` (override with `LIVE_CANVAS_PORT`)
-- `GET /health` — overlay probes this to confirm Live mode is reachable
-- `POST /feedback` — wire-compatible with the overlay's v1.0 schema
-- stdio: MCP protocol using `@modelcontextprotocol/sdk`
-
-## Install (local dev)
-
-```bash
-# Point Claude at this marketplace (one-time)
-claude /plugin marketplace add /absolute/path/to/live-canvas-marketplace
-
-# Install the plugin from it
-claude /plugin install live-canvas-channel@live-canvas-marketplace
-```
-
-The marketplace directory is the parent that contains `.claude-plugin/marketplace.json`.
-
-## Activate the channel on a session
-
-**Channels are in research preview and custom channels aren't on the approved allowlist.** `/plugin install` spawns the MCP server but does NOT auto-subscribe the session. To receive channel events, start a fresh Claude session with the development flag:
-
-```bash
-claude --dangerously-load-development-channels plugin:live-canvas-channel@live-canvas-marketplace
-```
-
-You'll see a confirmation prompt the first time. After confirming, channel events arrive in the assistant's context wrapped as `<channel source="live-canvas" ...>...</channel>` tags.
-
-Requirements: Claude Code v2.1.80+, claude.ai login (not API key or Console auth). On Team/Enterprise, channels must be explicitly enabled by the admin.
-
-## First run
-
-```bash
-cd /path/to/live-canvas-marketplace/plugins/live-canvas-channel
-npm install
-```
-
-This installs `@modelcontextprotocol/sdk`. After that, `/plugin install` can launch `server.js` on demand.
-
-## Debugging standalone
-
-The process expects stdio to be held open (Claude Code does this; the shell doesn't unless you trick it):
-
-```bash
-LIVE_CANVAS_PORT=8788 tail -f /dev/null | node server.js
-```
-
-Then in another terminal:
-
-```bash
-curl http://localhost:8788/health
-curl -X POST http://localhost:8788/feedback \
-  -H 'content-type: application/json' \
-  -d '{"version":"1.0","target":"PostCard","comment":{"id":"test","variant":"A","element":{"selector":"button","tagName":"button","textContent":"Like"},"text":"too small"}}'
-```
-
-## Protocol emitted
-
-| Method | When | Params |
-|---|---|---|
-| `notifications/claude/channel` | Valid feedback POST | `{ content: string, meta: Record<string,string> }` |
-
-**content** — human-readable text delivered to the active Claude turn:
-
-```
-[LIVE-CANVAS A · PostCard] too small
-  selector: `button`, button with "Like"
-  comment_id: test
-```
-
-**meta** — machine-structured fields the assistant can parse: `source`, `target`, `variant`, `selector`, `tagName`, `commentId`.
-
-## Failure modes
-
-- **Port in use** — another Claude session owns 8788. Logs to stderr and exits; overlay health probe fails; overlay falls back to JSON mode silently. The skill itself never silently degrades — it stops and asks the user.
-- **Invalid payload** — HTTP 400 with reason; no notification emitted.
-- **MCP transport not connected** — HTTP call still returns 200 (so the overlay shows "pushed"), but stderr logs the drop. Avoids false-negative toasts.

package/packages/claude/skills/debug-method/CREATION-LOG.md

@@ -1,119 +0,0 @@
-# Creation Log: Systematic Debugging Skill
-
-Reference example of extracting, structuring, and bulletproofing a critical skill.
-
-## Source Material
-
-Extracted debugging framework from `/Users/jesse/.claude/CLAUDE.md`:
-- 4-phase systematic process (Investigation → Pattern Analysis → Hypothesis → Implementation)
-- Core mandate: ALWAYS find root cause, NEVER fix symptoms
-- Rules designed to resist time pressure and rationalization
-
-## Extraction Decisions
-
-**What to include:**
-- Complete 4-phase framework with all rules
-- Anti-shortcuts ("NEVER fix symptom", "STOP and re-analyze")
-- Pressure-resistant language ("even if faster", "even if I seem in a hurry")
-- Concrete steps for each phase
-
-**What to leave out:**
-- Project-specific context
-- Repetitive variations of same rule
-- Narrative explanations (condensed to principles)
-
-## Structure Following skill-creation/SKILL.md
-
-1. **Rich when_to_use** - Included symptoms and anti-patterns
-2. **Type: technique** - Concrete process with steps
-3. **Keywords** - "root cause", "symptom", "workaround", "debugging", "investigation"
-4. **Flowchart** - Decision point for "fix failed" → re-analyze vs add more fixes
-5. **Phase-by-phase breakdown** - Scannable checklist format
-6. **Anti-patterns section** - What NOT to do (critical for this skill)
-
-## Bulletproofing Elements
-
-Framework designed to resist rationalization under pressure:
-
-### Language Choices
-- "ALWAYS" / "NEVER" (not "should" / "try to")
-- "even if faster" / "even if I seem in a hurry"
-- "STOP and re-analyze" (explicit pause)
-- "Don't skip past" (catches the actual behavior)
-
-### Structural Defenses
-- **Phase 1 required** - Can't skip to implementation
-- **Single hypothesis rule** - Forces thinking, prevents shotgun fixes
-- **Explicit failure mode** - "IF your first fix doesn't work" with mandatory action
-- **Anti-patterns section** - Shows exactly what shortcuts look like
-
-### Redundancy
-- Root cause mandate in overview + when_to_use + Phase 1 + implementation rules
-- "NEVER fix symptom" appears 4 times in different contexts
-- Each phase has explicit "don't skip" guidance
-
-## Testing Approach
-
-Created 4 validation tests following skills/meta/testing-skills-with-subagents:
-
-### Test 1: Academic Context (No Pressure)
-- Simple bug, no time pressure
-- **Result:** Perfect compliance, complete investigation
-
-### Test 2: Time Pressure + Obvious Quick Fix
-- User "in a hurry", symptom fix looks easy
-- **Result:** Resisted shortcut, followed full process, found real root cause
-
-### Test 3: Complex System + Uncertainty
-- Multi-layer failure, unclear if can find root cause
-- **Result:** Systematic investigation, traced through all layers, found source
-
-### Test 4: Failed First Fix
-- Hypothesis doesn't work, temptation to add more fixes
-- **Result:** Stopped, re-analyzed, formed new hypothesis (no shotgun)
-
-**All tests passed.** No rationalizations found.
-
-## Iterations
-
-### Initial Version
-- Complete 4-phase framework
-- Anti-patterns section
-- Flowchart for "fix failed" decision
-
-### Enhancement 1: TDD Reference
-- Added link to skills/testing/test-driven-development
-- Note explaining TDD's "simplest code" ≠ debugging's "root cause"
-- Prevents confusion between methodologies
-
-## Final Outcome
-
-Bulletproof skill that:
-- ✅ Clearly mandates root cause investigation
-- ✅ Resists time pressure rationalization
-- ✅ Provides concrete steps for each phase
-- ✅ Shows anti-patterns explicitly
-- ✅ Tested under multiple pressure scenarios
-- ✅ Clarifies relationship to TDD
-- ✅ Ready for use
-
-## Key Insight
-
-**Most important bulletproofing:** Anti-patterns section showing exact shortcuts that feel justified in the moment. When Claude thinks "I'll just add this one quick fix", seeing that exact pattern listed as wrong creates cognitive friction.
-
-## Usage Example
-
-When encountering a bug:
-1. Load skill: skills/debug-method
-2. Read overview (10 sec) - reminded of mandate
-3. Follow Phase 1 checklist - forced investigation
-4. If tempted to skip - see anti-pattern, stop
-5. Complete all phases - root cause found
-
-**Time investment:** 5-10 minutes
-**Time saved:** Hours of symptom-whack-a-mole
-
----
-
-*Created: 2025-10-03*
-*Purpose: Reference example for skill extraction and bulletproofing*