@a13xu/lucid 1.16.0 → 1.16.2

package/build/tools/plan.js

@@ -16,10 +16,10 @@ export const PlanListSchema = z.object({
     status: z.enum(["active", "completed", "abandoned", "all"]).optional().default("active"),
 });
 export const PlanGetSchema = z.object({
-    plan_id: z.number().int().positive(),
+    plan_id: z.coerce.number().int().positive(),
 });
 export const PlanUpdateTaskSchema = z.object({
-    task_id: z.number().int().positive(),
+    task_id: z.coerce.number().int().positive(),
     status: z.enum(["pending", "in_progress", "done", "blocked"]),
     note: z.string().optional(),
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@a13xu/lucid",
-  "version": "1.16.0",
+  "version": "1.16.2",
   "description": "Token-efficient memory, code indexing, and validation for Claude Code agents — SQLite + FTS5, TF-IDF + Qdrant retrieval, AST skeleton pruning, diff-aware context, Logic Guardian drift detection",
   "type": "module",
   "bin": {
@@ -15,6 +15,7 @@
   ],
   "scripts": {
     "build": "tsc",
+    "compress-prompts": "node scripts/compress-prompts.mjs",
     "prepublishOnly": "npm run build"
   },
   "keywords": [
@@ -53,6 +54,7 @@
     "better-sqlite3": "^12.0.0",
     "chokidar": "^4.0.3",
     "express": "^5.2.1",
+    "sharp": "^0.34.5",
     "zod": "^3.23.8"
   },
   "devDependencies": {

package/skills/lucid-audit/SKILL.md

@@ -1,73 +1,84 @@
----
-name: lucid-audit
-description: MANDATORY before marking any task done — runs Logic Guardian + Code Quality checks. HARD-GATE blocks completion without validation.
-argument-hint: "[file path or 'all changed files']"
----
-
-<HARD-GATE>
-You are about to say "done", "fixed", "complete", or "implemented".
-STOP. You have NOT verified the code yet.
-
-Do NOT mark any task as done, do NOT commit, do NOT say the work is complete
-until you have run BOTH validators below and fixed all 🔴 CRITICAL issues.
-
-"It looks correct" is not verification. Run the tools.
-</HARD-GATE>
-
-## When to invoke
-
-**INVOKE when:** about to say done/fixed/complete/implemented, before committing, before creating a PR
-**DO NOT INVOKE for:** read-only tasks, pure research, config changes with no logic
-
-## Steps
-
-```dot
-digraph lucid_audit {
-    "About to say done?" -> "validate_file(path)";
-    "validate_file(path)" -> "Critical issues?";
-    "Critical issues?" -> "Fix issues" [label="yes 🔴"];
-    "Fix issues" -> "validate_file(path)";
-    "Critical issues?" -> "check_code_quality(path)" [label="no ✓"];
-    "check_code_quality(path)" -> "HIGH issues?";
-    "HIGH issues?" -> "Fix if safe" [label="yes 🟠"];
-    "Fix if safe" -> "Mark done ✓";
-    "HIGH issues?" -> "Mark done ✓" [label="no ✓"];
-}
-```
-
-### 0. Get model recommendation
-```
-suggest_model(task_description="<paste the file path or description of what was written>")
-```
-Say: **"Using [model] — [reasoning]"** then proceed.
-
-### 1. Validate logic correctness
-```
-validate_file(path="<file you wrote or modified>")
-```
-Fix every 🔴 CRITICAL issue. Re-run until clean.
-
-### 2. Validate code quality
-```
-check_code_quality(path="<same file>")
-```
-Fix 🔴 HIGH severity issues. Address 🟠 MEDIUM where practical.
-
-### 3. For complex logic — get the full checklist
-```
-get_checklist()
-```
-Run all 5 mental passes before marking done.
-
-### 4. Pre-write validation (before writing to disk)
-```
-check_drift(code="<your code snippet>", language="typescript")
-```
-
-## Severity guide
-
-| Icon | Level | Action |
-|---|---|---|
-| 🔴 | Critical/High | Fix immediately — do not proceed |
-| 🟠 | Medium | Fix if the refactor is safe |
-| 🔵 | Low/Info | Note for future cleanup |
+---
+name: lucid-audit
+description: MANDATORY before marking any task done — runs Logic Guardian + Code Quality checks. HARD-GATE blocks completion without validation.
+argument-hint: "[file path or 'all changed files']"
+allowed-tools:
+  - mcp__lucid__suggest_model
+  - mcp__lucid__validate_file
+  - mcp__lucid__check_drift
+  - mcp__lucid__get_checklist
+  - mcp__lucid__check_code_quality
+  - mcp__lucid__coding_rules
+  - mcp__lucid__get_recent
+  - mcp__lucid__sync_file
+  - Read
+  - Glob
+---
+
+<HARD-GATE>
+You are about to say "done", "fixed", "complete", or "implemented".
+STOP. You have NOT verified the code yet.
+
+Do NOT mark any task as done, do NOT commit, do NOT say the work is complete
+until you have run BOTH validators below and fixed all 🔴 CRITICAL issues.
+
+"It looks correct" is not verification. Run the tools.
+</HARD-GATE>
+
+## When to invoke
+
+**INVOKE when:** about to say done/fixed/complete/implemented, before committing, before creating a PR
+**DO NOT INVOKE for:** read-only tasks, pure research, config changes with no logic
+
+## Steps
+
+```dot
+digraph lucid_audit {
+    "About to say done?" -> "validate_file(path)";
+    "validate_file(path)" -> "Critical issues?";
+    "Critical issues?" -> "Fix issues" [label="yes 🔴"];
+    "Fix issues" -> "validate_file(path)";
+    "Critical issues?" -> "check_code_quality(path)" [label="no ✓"];
+    "check_code_quality(path)" -> "HIGH issues?";
+    "HIGH issues?" -> "Fix if safe" [label="yes 🟠"];
+    "Fix if safe" -> "Mark done ✓";
+    "HIGH issues?" -> "Mark done ✓" [label="no ✓"];
+}
+```
+
+### 0. Get model recommendation
+```
+suggest_model(task_description="<paste the file path or description of what was written>")
+```
+Say: **"Using [model] — [reasoning]"** then proceed.
+
+### 1. Validate logic correctness
+```
+validate_file(path="<file you wrote or modified>")
+```
+Fix every 🔴 CRITICAL issue. Re-run until clean.
+
+### 2. Validate code quality
+```
+check_code_quality(path="<same file>")
+```
+Fix 🔴 HIGH severity issues. Address 🟠 MEDIUM where practical.
+
+### 3. For complex logic — get the full checklist
+```
+get_checklist()
+```
+Run all 5 mental passes before marking done.
+
+### 4. Pre-write validation (before writing to disk)
+```
+check_drift(code="<your code snippet>", language="typescript")
+```
+
+## Severity guide
+
+| Icon | Level | Action |
+|---|---|---|
+| 🔴 | Critical/High | Fix immediately — do not proceed |
+| 🟠 | Medium | Fix if the refactor is safe |
+| 🔵 | Low/Info | Note for future cleanup |

package/skills/lucid-context/SKILL.md

@@ -1,69 +1,78 @@
----
-name: lucid-context
-description: Use BEFORE starting any coding task — retrieves relevant context via smart_context (code + knowledge graph). HARD-GATE: do not read files manually before calling smart_context.
-argument-hint: "[what you are working on]"
----
-
-<HARD-GATE>
-Do NOT open any source file, read any code, or start implementation
-until you have called smart_context and reviewed the result.
-Reading files manually when Lucid is available wastes tokens and misses context.
-</HARD-GATE>
-
-## When to invoke this skill
-
-**INVOKE when:** about to work on a feature, fix a bug, understand a module, or any coding task
-**DO NOT INVOKE for:** pure conversation, reading docs, non-code questions
-
-## Steps
-
-```dot
-digraph lucid_context {
-    "Describe task" -> "suggest_model";
-    "suggest_model" -> "call smart_context";
-    "call smart_context" -> "Result relevant?";
-    "Result relevant?" -> "call reward()" [label="yes"];
-    "Result relevant?" -> "call penalize()" [label="no — note what was missing"];
-    "reward()" -> "Start coding";
-    "penalize()" -> "Start coding";
-}
-```
-
-### 0. Get model recommendation
-```
-suggest_model(task_description="<concise description of what you are working on>")
-```
-Say: **"Using [model] — [reasoning]"**
-
-### 1. Call smart_context
-```
-smart_context(query="<concise description of what you are working on>", task_type="moderate")
-```
-
-Use `dirs` to narrow scope and `task_type` to adjust budget:
-```
-smart_context(query="...", dirs=["src/api"], task_type="simple")
-```
-
-### 2. Review results and give feedback
-
-| Result quality | Action |
-|---|---|
-| Included the files you needed | `reward()` |
-| Missed important files you had to find manually | `penalize(note="missed: src/path/file.ts")` |
-| Partially useful | no action |
-
-### 3. Supplement if needed
-
-```
-grep_code(pattern="functionName")          # locate specific usages
-get_recent(hours=2)                        # after git pull — see what changed
-recall(query="<topic>")                    # search accumulated knowledge
-```
-
-### 4. After finishing — sync
-
-After every Write/Edit:
-```
-sync_file(path="<modified file>")
-```
+---
+name: lucid-context
+description: Use BEFORE starting any coding task — retrieves relevant context via smart_context (code + knowledge graph). HARD-GATE: do not read files manually before calling smart_context.
+argument-hint: "[what you are working on]"
+allowed-tools:
+  - mcp__lucid__suggest_model
+  - mcp__lucid__smart_context
+  - mcp__lucid__get_context
+  - mcp__lucid__get_recent
+  - mcp__lucid__recall
+  - mcp__lucid__grep_code
+  - mcp__lucid__reward
+  - mcp__lucid__penalize
+---
+
+<HARD-GATE>
+Do NOT open any source file, read any code, or start implementation
+until you have called smart_context and reviewed the result.
+Reading files manually when Lucid is available wastes tokens and misses context.
+</HARD-GATE>
+
+## When to invoke this skill
+
+**INVOKE when:** about to work on a feature, fix a bug, understand a module, or any coding task
+**DO NOT INVOKE for:** pure conversation, reading docs, non-code questions
+
+## Steps
+
+```dot
+digraph lucid_context {
+    "Describe task" -> "suggest_model";
+    "suggest_model" -> "call smart_context";
+    "call smart_context" -> "Result relevant?";
+    "Result relevant?" -> "call reward()" [label="yes"];
+    "Result relevant?" -> "call penalize()" [label="no — note what was missing"];
+    "reward()" -> "Start coding";
+    "penalize()" -> "Start coding";
+}
+```
+
+### 0. Get model recommendation
+```
+suggest_model(task_description="<concise description of what you are working on>")
+```
+Say: **"Using [model] — [reasoning]"**
+
+### 1. Call smart_context
+```
+smart_context(query="<concise description of what you are working on>", task_type="moderate")
+```
+
+Use `dirs` to narrow scope and `task_type` to adjust budget:
+```
+smart_context(query="...", dirs=["src/api"], task_type="simple")
+```
+
+### 2. Review results and give feedback
+
+| Result quality | Action |
+|---|---|
+| Included the files you needed | `reward()` |
+| Missed important files you had to find manually | `penalize(note="missed: src/path/file.ts")` |
+| Partially useful | no action |
+
+### 3. Supplement if needed
+
+```
+grep_code(pattern="functionName")          # locate specific usages
+get_recent(hours=2)                        # after git pull — see what changed
+recall(query="<topic>")                    # search accumulated knowledge
+```
+
+### 4. After finishing — sync
+
+After every Write/Edit:
+```
+sync_file(path="<modified file>")
+```

package/skills/lucid-plan/SKILL.md

@@ -1,52 +1,61 @@
----
-name: lucid-plan
-description: MANDATORY before writing code for any non-trivial feature — creates a persisted plan with tasks. HARD-GATE: no coding without a plan.
-argument-hint: "[feature or task description]"
----
-
-<HARD-GATE>
-You are about to write code for a feature or fix.
-STOP. Create a plan first. Plans survive session restarts.
-Do NOT write implementation code until a plan exists and tasks are defined.
-</HARD-GATE>
-
-## When to invoke
-
-**INVOKE when:** implementing a feature, fixing a non-trivial bug, any task with 3+ steps
-**DO NOT INVOKE for:** single-line fixes, config changes, documentation-only tasks
-
-## Steps
-
-### 0. Get model recommendation
-```
-suggest_model(task_description="<paste the user's task description>")
-```
-Say: **"Using [model] — [reasoning]"** then proceed.
-
-### 1. Create the plan
-```
-plan_create(
-  title="<short descriptive title>",
-  description="<what this accomplishes>",
-  user_story="As a <user>, I want <goal>, so that <benefit>.",
-  tasks=[
-    { title: "Task 1", description: "...", test_criteria: "How to verify it's done" },
-    { title: "Task 2", description: "...", test_criteria: "..." },
-  ]
-)
-```
-Returns a `plan_id` and task IDs (format: `planId * 100 + sequence`).
-
-### 2. Mark tasks in progress / done as you work
-```
-plan_update_task(task_id=101, status="in_progress")
-plan_update_task(task_id=101, status="done", note="Decision made: used X instead of Y")
-```
-
-### 3. Resume a session
-```
-plan_list()           # all active plans
-plan_get(plan_id=1)   # full details + task status
-```
-
-## Task statuses: `pending` → `in_progress` → `done` | `blocked`
+---
+name: lucid-plan
+description: MANDATORY before writing code for any non-trivial feature — creates a persisted plan with tasks. HARD-GATE: no coding without a plan.
+argument-hint: "[feature or task description]"
+allowed-tools:
+  - mcp__lucid__suggest_model
+  - mcp__lucid__plan_create
+  - mcp__lucid__plan_list
+  - mcp__lucid__plan_get
+  - mcp__lucid__plan_update_task
+  - mcp__lucid__smart_context
+  - mcp__lucid__recall
+  - mcp__lucid__remember
+---
+
+<HARD-GATE>
+You are about to write code for a feature or fix.
+STOP. Create a plan first. Plans survive session restarts.
+Do NOT write implementation code until a plan exists and tasks are defined.
+</HARD-GATE>
+
+## When to invoke
+
+**INVOKE when:** implementing a feature, fixing a non-trivial bug, any task with 3+ steps
+**DO NOT INVOKE for:** single-line fixes, config changes, documentation-only tasks
+
+## Steps
+
+### 0. Get model recommendation
+```
+suggest_model(task_description="<paste the user's task description>")
+```
+Say: **"Using [model] — [reasoning]"** then proceed.
+
+### 1. Create the plan
+```
+plan_create(
+  title="<short descriptive title>",
+  description="<what this accomplishes>",
+  user_story="As a <user>, I want <goal>, so that <benefit>.",
+  tasks=[
+    { title: "Task 1", description: "...", test_criteria: "How to verify it's done" },
+    { title: "Task 2", description: "...", test_criteria: "..." },
+  ]
+)
+```
+Returns a `plan_id` and task IDs (format: `planId * 100 + sequence`).
+
+### 2. Mark tasks in progress / done as you work
+```
+plan_update_task(task_id=101, status="in_progress")
+plan_update_task(task_id=101, status="done", note="Decision made: used X instead of Y")
+```
+
+### 3. Resume a session
+```
+plan_list()           # all active plans
+plan_get(plan_id=1)   # full details + task status
+```
+
+## Task statuses: `pending` → `in_progress` → `done` | `blocked`

package/skills/lucid-security/SKILL.md

@@ -1,41 +1,50 @@
----
-name: lucid-security
-description: Run before merging any code that handles user input, auth, or external data — security scan + drift check for injection, XSS, and credential exposure.
-argument-hint: "[file path or directory]"
----
-
-<HARD-GATE>
-Before merging code that:
-- Handles user input (forms, query params, file uploads)
-- Implements auth, tokens, sessions, or permissions
-- Calls external APIs or parses external data
-- Manages files or runs shell commands
-
-Run this skill. No exceptions.
-</HARD-GATE>
-
-## Steps
-
-### 0. Get model recommendation
-```
-suggest_model(task_description="<paste the user's task description>")
-```
-Say: **"Using [model] — [reasoning]"** then proceed.
-
-### 1. Security scan
-```
-security_scan(code="<file contents or snippet>", language="typescript", context="backend")
-```
-
-### 2. Drift check for security-sensitive snippets
-```
-check_drift(code="<auth/input-handling code>", language="typescript")
-```
-
-### 3. Fix all CRITICAL issues before merging
-
-| Severity | Action |
-|---|---|
-| 🔴 CRITICAL | Block merge — fix immediately |
-| 🟠 HIGH | Fix before merge |
-| 🔵 MEDIUM/LOW | Track, fix in follow-up |
+---
+name: lucid-security
+description: Run before merging any code that handles user input, auth, or external data — security scan + drift check for injection, XSS, and credential exposure.
+argument-hint: "[file path or directory]"
+allowed-tools:
+  - mcp__lucid__suggest_model
+  - mcp__lucid__security_scan
+  - mcp__lucid__check_drift
+  - mcp__lucid__validate_file
+  - mcp__lucid__get_recent
+  - mcp__lucid__grep_code
+  - Read
+  - Glob
+---
+
+<HARD-GATE>
+Before merging code that:
+- Handles user input (forms, query params, file uploads)
+- Implements auth, tokens, sessions, or permissions
+- Calls external APIs or parses external data
+- Manages files or runs shell commands
+
+Run this skill. No exceptions.
+</HARD-GATE>
+
+## Steps
+
+### 0. Get model recommendation
+```
+suggest_model(task_description="<paste the user's task description>")
+```
+Say: **"Using [model] — [reasoning]"** then proceed.
+
+### 1. Security scan
+```
+security_scan(code="<file contents or snippet>", language="typescript", context="backend")
+```
+
+### 2. Drift check for security-sensitive snippets
+```
+check_drift(code="<auth/input-handling code>", language="typescript")
+```
+
+### 3. Fix all CRITICAL issues before merging
+
+| Severity | Action |
+|---|---|
+| 🔴 CRITICAL | Block merge — fix immediately |
+| 🟠 HIGH | Fix before merge |
+| 🔵 MEDIUM/LOW | Track, fix in follow-up |