@su-record/vibe 2.9.21 → 2.9.23

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@su-record/vibe",
-  "version": "2.9.21",
+  "version": "2.9.23",
   "description": "AI Coding Framework for Claude Code — 56 agents, 45 skills, multi-LLM orchestration",
   "type": "module",
   "main": "dist/cli/index.js",
@@ -64,12 +64,12 @@
     "node": ">=18.0.0"
   },
   "optionalDependencies": {
-    "@ast-grep/napi": "^0.40.5",
-    "@anthropic-ai/claude-agent-sdk": "^0.2.6"
+    "@anthropic-ai/claude-agent-sdk": "^0.2.6",
+    "@ast-grep/napi": "^0.40.5"
   },
   "dependencies": {
     "@clack/prompts": "^1.0.0",
-    "better-sqlite3": "^12.6.2",
+    "better-sqlite3": "^12.9.0",
     "chalk": "^5.3.0",
     "glob": "^13.0.1",
     "papaparse": "^5.5.3",
@@ -97,5 +97,10 @@
     "CLAUDE.md",
     "README.md",
     "LICENSE"
-  ]
+  ],
+  "pnpm": {
+    "onlyBuiltDependencies": [
+      "better-sqlite3"
+    ]
+  }
 }

package/skills/agents-md/SKILL.md

@@ -1,121 +1,121 @@
----
-name: agents-md
-tier: standard
-description: "Optimize AGENTS.md / CLAUDE.md by removing discoverable info and keeping only gotchas. Based on Addy Osmani's AGENTS.md principles. Activates on agents.md, claude.md, context file optimization."
-triggers: [agents.md, claude.md, context file, optimize agents, optimize claude]
-priority: 50
----
-
-# agents-md — Context File Optimizer
-
-Optimize AGENTS.md / CLAUDE.md files.
-Reference: https://addyosmani.com/blog/agents-md/
-
-## Core Principle
-
-**One-line test**: "Can the agent discover this by reading the code?" → Yes = delete.
-
-## Step 1: Find Target Files
-
-Search project root for these files:
-
-```
-Glob: pattern="AGENTS.md"
-Glob: pattern="CLAUDE.md"
-Glob: pattern=".cursorrules"
-Glob: pattern=".github/copilot-instructions.md"
-Glob: pattern=".windsurfrules"
-```
-
-If no target files exist, ask the user whether to create one.
-
-## Step 2: Classify Current Content
-
-Classify each entry by the following criteria:
-
-### Delete (Discoverable)
-
-Information the agent can find by exploring the code:
-
-| Type | Example | Discovery Path |
-|------|---------|---------------|
-| Directory structure | "Components are in src/" | `ls`, `Glob` |
-| Tech stack | "Uses React + TypeScript" | `package.json`, file extensions |
-| Phase/progress tables | "Phase 1 ✅, Phase 2 ✅..." | Just history, not actionable guidance |
-| Build/test commands | "Run tests with npm test" | `package.json` scripts |
-| API endpoint lists | "POST /api/users" | Router code |
-| Feature descriptions | "Phase 3 implements circuit breaker" | Readable from the code itself |
-| Architecture diagrams | ASCII box diagrams | Conceptual only, no mistake prevention |
-
-### Keep (Non-discoverable)
-
-Traps and rules the agent cannot know from code alone:
-
-| Type | Example |
-|------|---------|
-| Runtime traps | "This is Bun, not Node" (not in package.json) |
-| Forbidden patterns | "Never use require()", "No React patterns" |
-| SSOT locations | "Only edit model-registry.ts, no hardcoding" |
-| Invariant ordering | "Priority: A → B → C, never change this order" |
-| Retry/fallback limits | "Max 2 retries, never 3+" |
-| Tool choices | "Use Zod only, no joi/yup" |
-| Naming conventions | Non-standard patterns only (if standard, delete) |
-| Project one-liner | Only when purpose is unclear from code |
-| Language/response directives | "Respond in Korean" etc. |
-
-### Anchoring Warning
-
-Mentioning a technology name anchors the agent toward it. "Don't use X" is useful, but "We use X" is unnecessary if already visible in code.
-
-## Step 3: Restructure
-
-Rewrite in this structure:
-
-```markdown
-# {Project Name} — {One-liner}
-
-{What the project does in 1-2 sentences. Only if purpose is unclear from code.}
-
-# Gotchas
-
-- **{Trap title}.** {Specific do/don't description}.
-- ...
-
-# Naming
-
-{Only if non-standard naming patterns exist. Omit if standard (camelCase etc.).}
-```
-
-Rules:
-- Maximum 3 sections (Intro, Gotchas, Naming)
-- Each gotcha has **bold title + specific do/don't**
-- "Don't use X" is more useful than "We use X"
-- Target under 50 lines total
-
-## Step 4: CLAUDE.md Separation (if applicable)
-
-If CLAUDE.md exists, keep only Claude-specific directives:
-
-```markdown
-{Claude-specific directives. e.g., "Always respond in Korean."}
-```
-
-Put common rules in AGENTS.md. Claude Code reads both.
-
-## Step 5: Report Results
-
-```markdown
-## AGENTS.md Optimization Results
-
-| Metric | Before | After |
-|--------|--------|-------|
-| Lines | N | N |
-| Deleted items | - | N (discoverable) |
-| Kept items | - | N (gotchas) |
-
-### Deleted Items
-- {Item}: {Reason for deletion}
-
-### Kept/Added Items
-- {Item}: {Reason for keeping}
-```
+---
+name: agents-md
+tier: standard
+description: "Optimize AGENTS.md / CLAUDE.md by removing discoverable info and keeping only gotchas. Based on Addy Osmani's AGENTS.md principles. Activates on agents.md, claude.md, context file optimization."
+triggers: [agents.md, claude.md, context file, optimize agents, optimize claude]
+priority: 50
+---
+
+# agents-md — Context File Optimizer
+
+Optimize AGENTS.md / CLAUDE.md files.
+Reference: https://addyosmani.com/blog/agents-md/
+
+## Core Principle
+
+**One-line test**: "Can the agent discover this by reading the code?" → Yes = delete.
+
+## Step 1: Find Target Files
+
+Search project root for these files:
+
+```
+Glob: pattern="AGENTS.md"
+Glob: pattern="CLAUDE.md"
+Glob: pattern=".cursorrules"
+Glob: pattern=".github/copilot-instructions.md"
+Glob: pattern=".windsurfrules"
+```
+
+If no target files exist, ask the user whether to create one.
+
+## Step 2: Classify Current Content
+
+Classify each entry by the following criteria:
+
+### Delete (Discoverable)
+
+Information the agent can find by exploring the code:
+
+| Type | Example | Discovery Path |
+|------|---------|---------------|
+| Directory structure | "Components are in src/" | `ls`, `Glob` |
+| Tech stack | "Uses React + TypeScript" | `package.json`, file extensions |
+| Phase/progress tables | "Phase 1 ✅, Phase 2 ✅..." | Just history, not actionable guidance |
+| Build/test commands | "Run tests with npm test" | `package.json` scripts |
+| API endpoint lists | "POST /api/users" | Router code |
+| Feature descriptions | "Phase 3 implements circuit breaker" | Readable from the code itself |
+| Architecture diagrams | ASCII box diagrams | Conceptual only, no mistake prevention |
+
+### Keep (Non-discoverable)
+
+Traps and rules the agent cannot know from code alone:
+
+| Type | Example |
+|------|---------|
+| Runtime traps | "This is Bun, not Node" (not in package.json) |
+| Forbidden patterns | "Never use require()", "No React patterns" |
+| SSOT locations | "Only edit model-registry.ts, no hardcoding" |
+| Invariant ordering | "Priority: A → B → C, never change this order" |
+| Retry/fallback limits | "Max 2 retries, never 3+" |
+| Tool choices | "Use Zod only, no joi/yup" |
+| Naming conventions | Non-standard patterns only (if standard, delete) |
+| Project one-liner | Only when purpose is unclear from code |
+| Language/response directives | "Respond in Korean" etc. |
+
+### Anchoring Warning
+
+Mentioning a technology name anchors the agent toward it. "Don't use X" is useful, but "We use X" is unnecessary if already visible in code.
+
+## Step 3: Restructure
+
+Rewrite in this structure:
+
+```markdown
+# {Project Name} — {One-liner}
+
+{What the project does in 1-2 sentences. Only if purpose is unclear from code.}
+
+# Gotchas
+
+- **{Trap title}.** {Specific do/don't description}.
+- ...
+
+# Naming
+
+{Only if non-standard naming patterns exist. Omit if standard (camelCase etc.).}
+```
+
+Rules:
+- Maximum 3 sections (Intro, Gotchas, Naming)
+- Each gotcha has **bold title + specific do/don't**
+- "Don't use X" is more useful than "We use X"
+- Target under 50 lines total
+
+## Step 4: CLAUDE.md Separation (if applicable)
+
+If CLAUDE.md exists, keep only Claude-specific directives:
+
+```markdown
+{Claude-specific directives. e.g., "Always respond in Korean."}
+```
+
+Put common rules in AGENTS.md. Claude Code reads both.
+
+## Step 5: Report Results
+
+```markdown
+## AGENTS.md Optimization Results
+
+| Metric | Before | After |
+|--------|--------|-------|
+| Lines | N | N |
+| Deleted items | - | N (discoverable) |
+| Kept items | - | N (gotchas) |
+
+### Deleted Items
+- {Item}: {Reason for deletion}
+
+### Kept/Added Items
+- {Item}: {Reason for keeping}
+```

package/skills/agents-md/rubrics/what-to-keep.md

@@ -1,49 +1,49 @@
-# What to Keep vs Remove in AGENTS.md
-
-## The One-Line Test
-
-> "Can the agent discover this by reading the code?" → Yes = delete.
-
-## Keep (Non-discoverable Gotchas)
-
-| Type | Example | Why Keep |
-|------|---------|----------|
-| Runtime trap | "Bun runtime, not Node" | Not visible in package.json |
-| Forbidden pattern | "Never use `require()` — ESM only" | Agent will default to CJS without this |
-| SSOT location | "Edit only `constants.ts` for stack mapping" | Agent will create duplicates |
-| Ordering invariant | "Build before test — always" | Violating silently breaks things |
-| Non-standard convention | "Exports need `.js` extension" | Counterintuitive in TS projects |
-| Tool choice | "Zod only — no joi or yup" | Agent picks any validation lib |
-| Boundary | "Never edit `dist/` directly" | Agent may "fix" generated files |
-| Response directive | "Respond in Korean" | Claude-specific, not in code |
-
-## Remove (Discoverable)
-
-| Type | Why Remove | Where to Find Instead |
-|------|------------|----------------------|
-| Directory structure | `ls` or Glob reveals it | The repo itself |
-| Tech stack list | Listed in `package.json` | `package.json` |
-| Build/test commands | Listed in `scripts` | `package.json` |
-| Phase progress tables | Historical record, not actionable | Git history |
-| API endpoint list | Readable from router code | Source files |
-| Architecture diagrams | Visual aid, no mistake prevention | Readme or separate doc |
-| Feature descriptions | Code speaks for itself | Source files |
-| General best practices | LLM already knows them | Unnecessary |
-
-## Anchoring Warning
-
-Mentioning any technology name biases the agent toward it:
-- "We use React" → unnecessary (visible in package.json) and creates anchoring
-- "Never use jQuery, even for legacy modules" → useful (prevents a specific mistake)
-
-Rule: Only name a technology when saying **don't use it** or when it's a **hidden runtime detail**.
-
-## Size Target
-
-| Outcome | Lines |
-|---------|-------|
-| Ideal | Under 50 |
-| Acceptable | 50-80 |
-| Warning | 80+ |
-
-If over 80 lines, almost certainly contains discoverable content. Audit again.
+# What to Keep vs Remove in AGENTS.md
+
+## The One-Line Test
+
+> "Can the agent discover this by reading the code?" → Yes = delete.
+
+## Keep (Non-discoverable Gotchas)
+
+| Type | Example | Why Keep |
+|------|---------|----------|
+| Runtime trap | "Bun runtime, not Node" | Not visible in package.json |
+| Forbidden pattern | "Never use `require()` — ESM only" | Agent will default to CJS without this |
+| SSOT location | "Edit only `constants.ts` for stack mapping" | Agent will create duplicates |
+| Ordering invariant | "Build before test — always" | Violating silently breaks things |
+| Non-standard convention | "Exports need `.js` extension" | Counterintuitive in TS projects |
+| Tool choice | "Zod only — no joi or yup" | Agent picks any validation lib |
+| Boundary | "Never edit `dist/` directly" | Agent may "fix" generated files |
+| Response directive | "Respond in Korean" | Claude-specific, not in code |
+
+## Remove (Discoverable)
+
+| Type | Why Remove | Where to Find Instead |
+|------|------------|----------------------|
+| Directory structure | `ls` or Glob reveals it | The repo itself |
+| Tech stack list | Listed in `package.json` | `package.json` |
+| Build/test commands | Listed in `scripts` | `package.json` |
+| Phase progress tables | Historical record, not actionable | Git history |
+| API endpoint list | Readable from router code | Source files |
+| Architecture diagrams | Visual aid, no mistake prevention | Readme or separate doc |
+| Feature descriptions | Code speaks for itself | Source files |
+| General best practices | LLM already knows them | Unnecessary |
+
+## Anchoring Warning
+
+Mentioning any technology name biases the agent toward it:
+- "We use React" → unnecessary (visible in package.json) and creates anchoring
+- "Never use jQuery, even for legacy modules" → useful (prevents a specific mistake)
+
+Rule: Only name a technology when saying **don't use it** or when it's a **hidden runtime detail**.
+
+## Size Target
+
+| Outcome | Lines |
+|---------|-------|
+| Ideal | Under 50 |
+| Acceptable | 50-80 |
+| Warning | 80+ |
+
+If over 80 lines, almost certainly contains discoverable content. Audit again.

package/skills/agents-md/templates/agents-md.md

@@ -1,36 +1,36 @@
-# {{PROJECT_NAME}} — {{ONE_LINER}}
-
-{{OPTIONAL: What the project does in 1-2 sentences. Only include if purpose is unclear from code.}}
-
-## Gotchas
-
-- **{{TRAP_TITLE}}.** {{Specific do/don't — e.g., "Use Bun, not Node. `bun run dev`, not `node`."}}
-- **{{TRAP_TITLE}}.** {{Specific do/don't}}
-- **{{TRAP_TITLE}}.** {{Specific do/don't}}
-
-## Naming
-
-{{Only if non-standard naming patterns exist. Delete this section if standard conventions apply.}}
-
-- {{Pattern}}: {{Example}}
-
----
-
-<!--
-INSTRUCTIONS FOR FILLING THIS TEMPLATE
-
-1. Replace {{PROJECT_NAME}} and {{ONE_LINER}} with your project.
-2. For each Gotcha, ask: "Would an AI agent make this mistake without being told?"
-   - YES → keep it as a gotcha
-   - NO  → delete it (discoverable from code)
-3. Delete the Naming section if you use standard conventions (camelCase, PascalCase, etc.).
-4. Target: under 50 lines total.
-5. Delete this comment block before committing.
-
-WHAT NOT TO ADD:
-- Directory structure (use ls/Glob)
-- Tech stack list (see package.json)
-- Build/test commands (see package.json scripts)
-- Phase progress or history
-- General best practices the LLM already knows
--->
+# {{PROJECT_NAME}} — {{ONE_LINER}}
+
+{{OPTIONAL: What the project does in 1-2 sentences. Only include if purpose is unclear from code.}}
+
+## Gotchas
+
+- **{{TRAP_TITLE}}.** {{Specific do/don't — e.g., "Use Bun, not Node. `bun run dev`, not `node`."}}
+- **{{TRAP_TITLE}}.** {{Specific do/don't}}
+- **{{TRAP_TITLE}}.** {{Specific do/don't}}
+
+## Naming
+
+{{Only if non-standard naming patterns exist. Delete this section if standard conventions apply.}}
+
+- {{Pattern}}: {{Example}}
+
+---
+
+<!--
+INSTRUCTIONS FOR FILLING THIS TEMPLATE
+
+1. Replace {{PROJECT_NAME}} and {{ONE_LINER}} with your project.
+2. For each Gotcha, ask: "Would an AI agent make this mistake without being told?"
+   - YES → keep it as a gotcha
+   - NO  → delete it (discoverable from code)
+3. Delete the Naming section if you use standard conventions (camelCase, PascalCase, etc.).
+4. Target: under 50 lines total.
+5. Delete this comment block before committing.
+
+WHAT NOT TO ADD:
+- Directory structure (use ls/Glob)
+- Tech stack list (see package.json)
+- Build/test commands (see package.json scripts)
+- Phase progress or history
+- General best practices the LLM already knows
+-->