@ngxtm/devkit 3.19.0 → 3.21.0

package/skills/writing-skills/references/cso/README.md

@@ -75,7 +75,7 @@ When searching, dispatch agent with template...
 
 # ✅ GOOD: Reference other skill
 
-Use subagents for searches. See [delegating-to-subagents] for workflow.
+Use Task agents for searches. See [delegating-to-subagents] for workflow.
 ```
 
 **3. Compress examples**:
@@ -85,13 +85,13 @@ Use subagents for searches. See [delegating-to-subagents] for workflow.
 
 Partner: "How did we handle auth errors in React Router?"
 You: I'll search past conversations for patterns.
-[Dispatch subagent with query: "React Router authentication error handling 401"]
+[Dispatch Task agent with query: "React Router authentication error handling 401"]
 
 # ✅ GOOD: Minimal (20 words)
 
 Partner: "Auth errors in React Router?"
 You: Searching...
-[Dispatch subagent → synthesis]
+[Dispatch Task agent → synthesis]
 ```
 
 ## Keyword Strategy

package/skills/writing-skills/testing-skills-with-subagents.md

@@ -1,4 +1,4 @@
-# Testing Skills With Subagents
+# Testing Skills With Task Agents
 
 **Load this reference when:** creating or editing skills, before deployment, to verify they work under pressure and resist rationalization.
 

package/skills-graph.json

@@ -1,7 +1,7 @@
 {
   "_meta": {
     "version": 2,
-    "lastUpdated": "2026-02-27",
+    "lastUpdated": "2026-02-28",
     "stats": {
       "totalSkills": 1127,
       "graphedSkills": 1070,

package/templates/base/rules/auto-skill.md

@@ -4,14 +4,14 @@
 
 ## When to Activate
 
-Before starting ANY coding task, you SHOULD check if a relevant skill exists:
+Before starting ANY coding task, check if a relevant skill exists:
 
-1. **Analyze the user's request** - Extract key technologies, patterns, or domains
-2. **Check compact index** - Read `skills-compact.json` (~20KB) for skill names and categories
-3. **Suggest to user** - Present top 1-3 matching skills
-4. **Load on-demand** - When user confirms, read full skill from `skills/{name}/SKILL.md`
+1. **Analyze** the user's request — extract key technologies, patterns, or domains
+2. **Search** `skills-compact.json` for matching skill names/descriptions
+3. **Suggest** top 1-3 matching skills with name and category
+4. **Load** on user confirmation — read full skill from `skills/{name}/SKILL.md`
 
-## Quick Reference: Skill Categories
+## Skill Categories
 
 | Code | Category | Examples |
 |------|----------|----------|
@@ -27,69 +27,15 @@ Before starting ANY coding task, you SHOULD check if a relevant skill exists:
 | `py` | Python | django, flask, fastapi, pandas |
 | `go` | Golang | gin, echo, fiber, concurrency |
 
-## Detection Flow
-
-```
-User Request → Extract keywords (react, auth, test, etc.)
-                    ↓
-            Read skills-compact.json
-                    ↓
-            Match skill names containing keywords
-                    ↓
-            Found? → Suggest: "I found /skill-name. Use it?"
-              ↓ No
-            Check category (fe, be, ai, etc.)
-                    ↓
-            Suggest skills in that category
-```
-
 ## How to Search
 
-### Step 1: Read Compact Index
-```
-Read: .claude/skills-compact.json
-Format: { "_categories": {...}, "skills": { "skill-name": { "c": "category", "d": "short description" } } }
-Note: Some skills may be just a category string if no description available.
-```
-
-### Step 2: Match by Name/Keyword
-Look for skills whose name OR description contains user's keywords:
-- User says "react" → find skills with "react" in name
-- User says "authentication" → find "auth" skills
-- User says "docker" → find "docker" skills
-
-### Step 3: Load Full Skill
-When user confirms, read the full skill:
-```
-Read: .claude/skills/{skill-name}/SKILL.md
-```
-
-## Suggestion Format
-
-**Single match:**
-```
-I found a skill that might help:
-
-📌 /skill-name - [category]
-
-Load this skill? It has specialized patterns for your task.
-```
-
-**Multiple matches (max 3):**
-```
-I found skills that might help:
-
-1. /skill-1 - [category]
-2. /skill-2 - [category]
-3. /skill-3 - [category]
-
-Which one should I use? (or "none" to proceed without)
-```
+1. Read `skills-compact.json` — format: `{ "skills": { "name": { "c": "category", "d": "description" } } }`
+2. Match skills whose name or description contains user's keywords
+3. If no direct match, suggest skills from the matching category
+4. On confirmation, read `skills/{skill-name}/SKILL.md`
 
 ## Auto-Activate Triggers
 
-Some patterns should auto-suggest specific skills:
-
 | User says... | Suggest skill |
 |--------------|---------------|
 | "create PR", "pull request" | /git-advanced-workflows |
@@ -105,36 +51,10 @@ Some patterns should auto-suggest specific skills:
 | "authentication", "auth" | /auth-implementation-patterns |
 | "mcp server" | /mcp-developer |
 
-## Important Rules
-
-1. **Don't auto-load** - Always ask before loading a skill
-2. **Max 3 suggestions** - Don't overwhelm user
-3. **Be concise** - One-line per skill
-4. **Remember context** - If user said "none", don't suggest again for same task
-5. **On-demand loading** - Only read full SKILL.md when user confirms
-6. **Core commands available** - /learn, /react-expert, /docker-expert, etc. are pre-loaded
-
-## File Locations
-
-| File | Purpose | Size |
-|------|---------|------|
-| `skills-compact.json` | Quick lookup index | ~20KB |
-| `skills/{name}/SKILL.md` | Full skill content | varies |
-| `commands/*.md` | Core commands (pre-loaded) | ~400KB |
-
-## Example Interaction
-
-**User:** "Help me add JWT authentication to my Express API"
-
-**Claude:** (reads skills-compact.json, finds "auth-implementation-patterns")
-```
-I found a skill that matches your task:
-
-📌 /auth-implementation-patterns - security
-
-This skill has JWT, OAuth2, and session patterns. Load it?
-```
-
-**User:** "yes"
+## Rules
 
-**Claude:** (reads skills/auth-implementation-patterns/SKILL.md and applies it)
+1. **Don't auto-load** — always ask before loading a skill
+2. **Max 3 suggestions** — don't overwhelm user
+3. **Be concise** — one-line per skill suggestion
+4. **Remember context** — if user said "none", don't suggest again for same task
+5. **On-demand only** — only read full SKILL.md when user confirms

package/templates/base/rules/command-routing.md

@@ -50,19 +50,6 @@ Is this a complex, full-lifecycle feature?
 | `/fix` | Low | No | Quick bug fixes |
 | `/fix:hard` | Medium | Yes (debugger, tester) | Complex debugging |
 
-## Multi-Agent Phases in /cook:hard
-
-```
-Phase 1: brainstormer  → Requirements discovery
-Phase 2: researcher    → Best practices research
-Phase 3: scouter       → Codebase analysis
-Phase 4: designer      → UI/UX design (if needed)
-Phase 5: planner       → Implementation plan
-Phase 6: tech-lead     → Routes to specialist engineers
-Phase 7: tester        → Testing
-Phase 8: reviewer      → Code review
-```
-
 ## When to Suggest Skills
 
 After choosing the right command, check if a domain-specific skill would help:

package/templates/base/rules/context-checkpoint.md

@@ -0,0 +1,38 @@
+# Context Checkpoint
+
+Auto-save session state to `.claude/sessions/` for context recovery.
+
+## When to Checkpoint
+After completing a subtask: implementing a feature step, running tests, phase transitions,
+receiving Task agent results, making key decisions.
+Do NOT checkpoint per individual file edit — wait until the subtask is complete.
+
+## Skip Checkpoint
+Simple Q&A, exploration reads, brainstorming, tasks completing in < 3 steps.
+
+## Protocol
+1. First checkpoint → ensure `.claude/sessions` is covered by `.gitignore`
+   (skip if `.claude/` or `.claude/sessions` already in gitignore), then create
+   `.claude/sessions/{YYMMDD-HHMM-desc}.md`
+2. Include `branch:{branch}` in header if in a git repo. Omit if not git.
+3. Update same file at each subsequent trigger. Silent — don't announce.
+4. Keep each section to 10 items max. Summarize older items if needed.
+5. On task completion → delete the checkpoint file.
+
+## Recovery
+If you recall working on a task but notice gaps in your prior context (earlier messages
+seem compressed or summarized), check `.claude/sessions/` for a matching checkpoint
+to restore state. Verify checkpoint has a `#` header and `## Next Action` before using.
+Say: "Resumed from checkpoint. Continuing..."
+Do NOT auto-load checkpoints in a fresh session — use `/recover` for cross-session.
+
+## Format
+```
+# {desc} | {command} | {phase} | branch:{branch}
+## Plan — {path or "none"}
+## Done — {bullets}
+## Pending — {bullets}
+## Decisions — {bullets}
+## Next Action — {exact step}
+## Files — Modified: {list} | Remaining: {list}
+```