claude-dev-env 2.13.0 → 2.14.1

package/skills/skill-builder/CLAUDE.md

@@ -1,49 +1 @@
-# skill-builder
-
-Orchestrates the skill-building lifecycle: classify type, scaffold folders, write via the `skill-writer-agent` agent, enforce modularity (sub-skills / composition), write description as a trigger catalog, require deterministic steps as code, self-audit, and refine from real usage.
-
-**Trigger:** build a skill, new skill workflow, improve this skill, optimize skill description, skill development lifecycle, skill modularity, description trigger catalog, deterministic skill scripts.
-
-## Purpose
-
-Enforces craft standards for new and existing skills. For quick one-off SKILL.md edits, spawn the `skill-writer-agent` agent directly. This skill classifies, scaffolds, gathers context (composition plan, description triggers, deterministic inventory), delegates writing, and self-audits.
-
-## Key files
-
-| File | Purpose |
-|---|---|
-| `SKILL.md` | Hub — routing, principles, file index |
-| `references/skill-types.md` | 9-type taxonomy with folder structures per type |
-| `references/progressive-disclosure.md` | Hub pattern, folder conventions, hard rules |
-| `references/skill-modularity.md` | Cross-skill modularity, sub-skills, composition plan |
-| `references/description-field.md` | Description as trigger catalog (not story prose) |
-| `references/deterministic-elements.md` | Deterministic steps as code/task seeds; no markdown checkbox boards |
-| `references/self-audit-checklist.md` | Post-build audit task seeds (TaskCreate / TodoWrite) |
-| `references/delegation-map.md` | Subagent handoff patterns and transcript guidance |
-| `references/thariq-x-post-skills.json` | Source reference — lessons from building Claude Code skills |
-| `workflows/new-skill.md` | Full lifecycle for new skills (6 steps) |
-| `workflows/improve-skill.md` | Observation-first flow for existing skills (6 steps) |
-| `workflows/polish-skill.md` | Description trigger-catalog audit and final validation (5 steps) |
-| `templates/gap-analysis.md` | Gaps, composition plan, description triggers, deterministic inventory |
-
-## Subdirectories
-
-| Directory | Purpose |
-|---|---|
-| `references/` | Best-practice specs and the audit checklist |
-| `workflows/` | Step-by-step workflows for each lifecycle phase |
-| `templates/` | Reusable templates for skill artifacts |
-
-## Routing
-
-- **New skill** → `workflows/new-skill.md`
-- **Improve existing** → `workflows/improve-skill.md`
-- **Final polish only** → `workflows/polish-skill.md`
-- **Ambiguous** → ask the user which one applies
-
-## Conventions
-
-- Every build ends with the self-audit at `references/self-audit-checklist.md`; fix failures before delivery.
-- Modularity items, description trigger-catalog items, and deterministic-element classification are mandatory on every delivery.
-- `skill-builder` orchestrates; the `skill-writer-agent` agent authors. Handoff packet must include type, gap analysis, composition plan, description trigger catalog, deterministic inventory, degree-of-freedom assessment, and constraints.
-- Claude A / Claude B: Claude A (this session) designs; Claude B (subagents) tests the built skill on real tasks.
+@AGENTS.md

package/skills/skill-builder/references/AGENTS.md

@@ -0,0 +1,25 @@
+# skill-builder/references
+
+Best-practice specifications and the mandatory self-audit checklist for the `/skill-builder` skill.
+
+## Key files
+
+| File | Purpose |
+|---|---|
+| `self-audit-checklist.md` | Audit task seeds after every build, improve, or polish. Register via TaskCreate / TodoWrite. |
+| `skill-types.md` | 9-type skill taxonomy with folder structures per type. |
+| `progressive-disclosure.md` | Hub pattern, folder conventions, hard rules: SKILL.md under 500 lines, one-level references. |
+| `skill-modularity.md` | Cross-skill modularity: one capability, sub-skills by name, composition plan, anti-monolith. |
+| `description-field.md` | Frontmatter description as trigger catalog (capability stem + Triggers). No story prose. |
+| `deterministic-elements.md` | Classify process steps; deterministic ones ship as code, task seeds, or fixed artifacts under CODE_RULES. |
+| `delegation-map.md` | Subagent handoff patterns and transcript guidance for skill-builder → skill-writer-agent. |
+| `thariq-x-post-skills.json` | Source reference data from Anthropic lessons on building Claude Code skills. |
+
+## Conventions
+
+- These files load on demand from `SKILL.md` routing — not all on every run.
+- `self-audit-checklist.md` always loads at the end of a build cycle.
+- Load `skill-modularity.md` during Gather and when scope/overlap is diagnosed.
+- Load `description-field.md` during Gather, polish Step 1, and any activation diagnosis.
+- Load `deterministic-elements.md` during Gather, when prose-as-code is diagnosed, and on polish structure audit.
+- `thariq-x-post-skills.json` is source reference data, not executable content.

package/skills/skill-builder/references/CLAUDE.md

@@ -1,25 +1 @@
-# skill-builder/references
-
-Best-practice specifications and the mandatory self-audit checklist for the `/skill-builder` skill.
-
-## Key files
-
-| File | Purpose |
-|---|---|
-| `self-audit-checklist.md` | Audit task seeds after every build, improve, or polish. Register via TaskCreate / TodoWrite. |
-| `skill-types.md` | 9-type skill taxonomy with folder structures per type. |
-| `progressive-disclosure.md` | Hub pattern, folder conventions, hard rules: SKILL.md under 500 lines, one-level references. |
-| `skill-modularity.md` | Cross-skill modularity: one capability, sub-skills by name, composition plan, anti-monolith. |
-| `description-field.md` | Frontmatter description as trigger catalog (capability stem + Triggers). No story prose. |
-| `deterministic-elements.md` | Classify process steps; deterministic ones ship as code, task seeds, or fixed artifacts under CODE_RULES. |
-| `delegation-map.md` | Subagent handoff patterns and transcript guidance for skill-builder → skill-writer-agent. |
-| `thariq-x-post-skills.json` | Source reference data from Anthropic lessons on building Claude Code skills. |
-
-## Conventions
-
-- These files load on demand from `SKILL.md` routing — not all on every run.
-- `self-audit-checklist.md` always loads at the end of a build cycle.
-- Load `skill-modularity.md` during Gather and when scope/overlap is diagnosed.
-- Load `description-field.md` during Gather, polish Step 1, and any activation diagnosis.
-- Load `deterministic-elements.md` during Gather, when prose-as-code is diagnosed, and on polish structure audit.
-- `thariq-x-post-skills.json` is source reference data, not executable content.
+@AGENTS.md

package/skills/skill-builder/references/deterministic-elements.md

@@ -112,7 +112,7 @@ The seed list file lives under `reference/` (or is a named section of an existin
 
 ## CODE_RULES bar (every code file in the skill)
 
-Skill scripts are production code. They obey the same rules as the rest of the repo (`docs/CODE_RULES.md` / root `AGENTS.md`), including:
+Skill scripts are production code. They obey the same rules as the rest of the repo (`docs/CODE_RULES.md`), including:
 
 - **Named constants** — no bare magic numbers/strings in function bodies; skill-local values live in a `*_constants/` package the script imports.
 - **Types** — parameters and returns annotated; no bare `Any` / untyped escape hatches.

package/skills/skill-builder/templates/AGENTS.md

@@ -0,0 +1,14 @@
+# skill-builder/templates
+
+Reusable templates for skill-building artifacts.
+
+## Key files
+
+| File | Purpose |
+|---|---|
+| `gap-analysis.md` | Template for gaps, composition plan, description triggers, and deterministic-elements inventory. Used in new-skill Gather and improve diagnosis. |
+
+## Conventions
+
+- Fill the template inline during the workflow; do not commit completed gap analyses to this directory.
+- Composition plan, Description triggers, and Deterministic Elements Inventory sections are required before Write on a new skill.

package/skills/skill-builder/templates/CLAUDE.md

@@ -1,14 +1 @@
-# skill-builder/templates
-
-Reusable templates for skill-building artifacts.
-
-## Key files
-
-| File | Purpose |
-|---|---|
-| `gap-analysis.md` | Template for gaps, composition plan, description triggers, and deterministic-elements inventory. Used in new-skill Gather and improve diagnosis. |
-
-## Conventions
-
-- Fill the template inline during the workflow; do not commit completed gap analyses to this directory.
-- Composition plan, Description triggers, and Deterministic Elements Inventory sections are required before Write on a new skill.
+@AGENTS.md

package/skills/skill-builder/workflows/AGENTS.md

@@ -0,0 +1,19 @@
+# skill-builder/workflows
+
+Step-by-step workflow files for each skill lifecycle phase, loaded on demand by `SKILL.md` routing.
+
+## Key files
+
+| File | Purpose |
+|---|---|
+| `new-skill.md` | Full lifecycle: classify, scaffold, gather (composition + description triggers + deterministic inventory), write via the skill-writer-agent agent, self-audit, deliver. |
+| `improve-skill.md` | Observation-first improve: diagnose activation/modularity/quality/deterministic prose, targeted fix, re-audit. |
+| `polish-skill.md` | Description trigger-catalog audit; progressive disclosure + modularity + deterministic audit; task-seeded self-audit. |
+
+## Conventions
+
+- `SKILL.md` routes to exactly one workflow file per invocation based on the user's intent (new / improve / polish).
+- Each workflow references `../references/self-audit-checklist.md` at its final verification step.
+- New and improve load `skill-modularity.md`, `description-field.md`, and `deterministic-elements.md` when gathering or diagnosing.
+- Polish Step 1 is the dedicated description rewrite pass; Step 2 covers structure, modularity, and deterministic placement.
+- Load only the workflow that matches the active task; the other two stay out of context.

package/skills/skill-builder/workflows/CLAUDE.md

@@ -1,19 +1 @@
-# skill-builder/workflows
-
-Step-by-step workflow files for each skill lifecycle phase, loaded on demand by `SKILL.md` routing.
-
-## Key files
-
-| File | Purpose |
-|---|---|
-| `new-skill.md` | Full lifecycle: classify, scaffold, gather (composition + description triggers + deterministic inventory), write via the skill-writer-agent agent, self-audit, deliver. |
-| `improve-skill.md` | Observation-first improve: diagnose activation/modularity/quality/deterministic prose, targeted fix, re-audit. |
-| `polish-skill.md` | Description trigger-catalog audit; progressive disclosure + modularity + deterministic audit; task-seeded self-audit. |
-
-## Conventions
-
-- `SKILL.md` routes to exactly one workflow file per invocation based on the user's intent (new / improve / polish).
-- Each workflow references `../references/self-audit-checklist.md` at its final verification step.
-- New and improve load `skill-modularity.md`, `description-field.md`, and `deterministic-elements.md` when gathering or diagnosing.
-- Polish Step 1 is the dedicated description rewrite pass; Step 2 covers structure, modularity, and deterministic placement.
-- Load only the workflow that matches the active task; the other two stay out of context.
+@AGENTS.md

package/skills/task-build/AGENTS.md

@@ -0,0 +1,29 @@
+# task-build
+
+Gathers every open task in the current session and registers each one with the best available task or plan tool.
+
+**Trigger:** `/task-build`, "build my task list", "capture these tasks", "add open tasks to the task list", "track these".
+
+## Purpose
+
+Collects outstanding work from the conversation, `$ARGUMENTS`, and any plan documents or task items raised this session, then registers one item per open task — skipping anything already tracked or already complete.
+
+## Key files
+
+| File | Purpose |
+|---|---|
+| `SKILL.md` | Complete task discovery and registration workflow |
+| `reference/tool-routing.md` | Progressive-disclosure routing and fallback rules |
+
+## How the skill runs
+
+1. Reads the current list or visible plan with the selected host tool — prevents duplicates.
+2. Scans `$ARGUMENTS`, the conversation, and any plan or checklist items for open, actionable work.
+3. Prefers `update_plan`; otherwise uses `TaskList`/`TaskCreate`, then `TodoWrite` as the fallback. See `reference/tool-routing.md` for field mapping.
+4. Reports the selected tool, how many tasks were added, and how many were already tracked.
+
+## Conventions
+
+- This skill only records tasks — it does not start, assign, or complete them.
+- Use the matching host operation to set status after the list is built.
+- `disable-model-invocation: true` is not set; the skill uses model judgment to classify open vs. complete items.

package/skills/task-build/CLAUDE.md

@@ -1,29 +1 @@
-# task-build
-
-Gathers every open task in the current session and registers each one with the best available task or plan tool.
-
-**Trigger:** `/task-build`, "build my task list", "capture these tasks", "add open tasks to the task list", "track these".
-
-## Purpose
-
-Collects outstanding work from the conversation, `$ARGUMENTS`, and any plan documents or task items raised this session, then registers one item per open task — skipping anything already tracked or already complete.
-
-## Key files
-
-| File | Purpose |
-|---|---|
-| `SKILL.md` | Complete task discovery and registration workflow |
-| `reference/tool-routing.md` | Progressive-disclosure routing and fallback rules |
-
-## How the skill runs
-
-1. Reads the current list or visible plan with the selected host tool — prevents duplicates.
-2. Scans `$ARGUMENTS`, the conversation, and any plan or checklist items for open, actionable work.
-3. Prefers `update_plan`; otherwise uses `TaskList`/`TaskCreate`, then `TodoWrite` as the fallback. See `reference/tool-routing.md` for field mapping.
-4. Reports the selected tool, how many tasks were added, and how many were already tracked.
-
-## Conventions
-
-- This skill only records tasks — it does not start, assign, or complete them.
-- Use the matching host operation to set status after the list is built.
-- `disable-model-invocation: true` is not set; the skill uses model judgment to classify open vs. complete items.
+@AGENTS.md

package/skills/update/AGENTS.md

@@ -0,0 +1,38 @@
+# update
+
+Fast-forwards a local git repository's `main` branch to a chosen remote's `main`.
+
+**Trigger:** `/update`, "update main", "fast-forward main", "sync main from origin", "pull latest main into <path>", "bring main up to date".
+
+## Purpose
+
+Advances the `main` ref in a safe, confirmed, fast-forward-only way. Never forces, never merges. Confirms the repo path and source remote before any write. Offers to switch the checkout to `main` after the ref moves, with a clean-tree safety check.
+
+## Key files
+
+| File | Purpose |
+|---|---|
+| `SKILL.md` | The complete skill — five phases, refusals, gotchas. Flat by design; no companion files. |
+
+## Five phases
+
+| Phase | Key action |
+|---|---|
+| 1 — Resolve path | `git -C "<path>" rev-parse --show-toplevel` |
+| 2 — Confirm path + remote | One `AskUserQuestion` listing remote/URL pairs; recommends `origin/main` first |
+| 3 — Fetch + fast-forward | Fetch, check ancestry with `merge-base --is-ancestor`, apply via `merge --ff-only` (on main) or `fetch main:main` (off main) |
+| 4 — Report | Old SHA → new SHA, checkout state, dirty tracked files |
+| 5 — Offer to land on disk | `AskUserQuestion` to switch checkout to `main` (only when tree is clean and `main` is not held by another worktree) |
+
+## Refusals (first match wins)
+
+- Path is not a git repository → stated error, stop.
+- Remote has no `main` → stated error, stop.
+- Local `main` has diverged (not a fast-forward) → stated error, stop. Use `/rebase` to reconcile.
+
+## Conventions
+
+- Every command uses `git -C "<path>"` — never `cd` into the repo.
+- Path confirmation is mandatory even when the path comes from the argument.
+- The skill never switches to any branch other than `main`, and only in Phase 5 with operator approval.
+- `origin` is not always the source of truth; the confirmed remote may be `upstream` or another name.

package/skills/update/CLAUDE.md

@@ -1,38 +1 @@
-# update
-
-Fast-forwards a local git repository's `main` branch to a chosen remote's `main`.
-
-**Trigger:** `/update`, "update main", "fast-forward main", "sync main from origin", "pull latest main into <path>", "bring main up to date".
-
-## Purpose
-
-Advances the `main` ref in a safe, confirmed, fast-forward-only way. Never forces, never merges. Confirms the repo path and source remote before any write. Offers to switch the checkout to `main` after the ref moves, with a clean-tree safety check.
-
-## Key files
-
-| File | Purpose |
-|---|---|
-| `SKILL.md` | The complete skill — five phases, refusals, gotchas. Flat by design; no companion files. |
-
-## Five phases
-
-| Phase | Key action |
-|---|---|
-| 1 — Resolve path | `git -C "<path>" rev-parse --show-toplevel` |
-| 2 — Confirm path + remote | One `AskUserQuestion` listing remote/URL pairs; recommends `origin/main` first |
-| 3 — Fetch + fast-forward | Fetch, check ancestry with `merge-base --is-ancestor`, apply via `merge --ff-only` (on main) or `fetch main:main` (off main) |
-| 4 — Report | Old SHA → new SHA, checkout state, dirty tracked files |
-| 5 — Offer to land on disk | `AskUserQuestion` to switch checkout to `main` (only when tree is clean and `main` is not held by another worktree) |
-
-## Refusals (first match wins)
-
-- Path is not a git repository → stated error, stop.
-- Remote has no `main` → stated error, stop.
-- Local `main` has diverged (not a fast-forward) → stated error, stop. Use `/rebase` to reconcile.
-
-## Conventions
-
-- Every command uses `git -C "<path>"` — never `cd` into the repo.
-- Path confirmation is mandatory even when the path comes from the argument.
-- The skill never switches to any branch other than `main`, and only in Phase 5 with operator approval.
-- `origin` is not always the source of truth; the confirmed remote may be `upstream` or another name.
+@AGENTS.md

package/system-prompts/AGENTS.md

@@ -0,0 +1,17 @@
+# system-prompts
+
+System-prompt reference files installed into `~/.claude/system-prompts/` by `bin/install.mjs`. Rules and skills pull a file (or one of its sections) into context on demand by citing its installed path.
+
+## Files
+
+| File | Purpose |
+|---|---|
+| `software-engineer.xml` | Software-engineering reference: defines the engineering role, task-scope rules, output style, and the BDD `<behavior_protocol>` that `rules/bdd.md` cites on demand |
+
+## Format
+
+Files use XML with named sections (`<role>`, `<task_scope>`, `<output_style>`, `<behavior_protocol>`, etc.). A rule or skill cites a file, or one of its sections, to pull it into context when the task needs it.
+
+## Adding a prompt
+
+Create a new `.xml` file and run `bin/install.mjs` to copy it to `~/.claude/system-prompts/`. Reference the new file in the relevant rule or skill by its installed path.

package/system-prompts/CLAUDE.md

@@ -1,17 +1 @@
-# system-prompts
-
-System-prompt reference files installed into `~/.claude/system-prompts/` by `bin/install.mjs`. Rules and skills pull a file (or one of its sections) into context on demand by citing its installed path.
-
-## Files
-
-| File | Purpose |
-|---|---|
-| `software-engineer.xml` | Software-engineering reference: defines the engineering role, task-scope rules, output style, and the BDD `<behavior_protocol>` that `rules/bdd.md` cites on demand |
-
-## Format
-
-Files use XML with named sections (`<role>`, `<task_scope>`, `<output_style>`, `<behavior_protocol>`, etc.). A rule or skill cites a file, or one of its sections, to pull it into context when the task needs it.
-
-## Adding a prompt
-
-Create a new `.xml` file and run `bin/install.mjs` to copy it to `~/.claude/system-prompts/`. Reference the new file in the relevant rule or skill by its installed path.
+@AGENTS.md

package/system-prompts/software-engineer.xml

@@ -90,9 +90,9 @@
 </problem_solving>
 
 <code_quality>
-  Canonical code-quality policy is repository-root AGENTS.md (installed review contract).
-  ~/.claude/docs/CODE_RULES.md is the compact projection of AGENTS.md for generation load —
-  when the two disagree, AGENTS.md wins. The checklist below is a short reminder, not a
+  The checked-in .cursor/BUGBOT.md is the full code-quality review contract.
+  ~/.claude/docs/CODE_RULES.md is the compact projection for generation load.
+  The checklist below is a short reminder, not a
   second canonical source.
 
   Naming — full words only:

package/agents/caveman.md

@@ -1,73 +0,0 @@
----
-name: caveman
-description: Trims noise from an artifact the main caller has already authored. Input is a draft (skill, doc, plan, response, README, prompt, PR description) — output is the same artifact with filler, hedging, preamble, recap, and restatement removed. Preserves structure, technical substance, frontmatter, and anything load-bearing. Does NOT redesign, restructure, or overrule the caller's scope decisions.
-color: red
----
-
-You are the caveman. You trim. You do not build. You do not restructure.
-
-## What you are
-
-A noise filter. The main caller has already decided *what* the artifact is, *how* it is structured, and *what lives in it*. Your job is to strip fluff off that artifact without touching the bones.
-
-You are downstream of design decisions, not upstream.
-
-## What you trim
-
-| Noise type | Example |
-|---|---|
-| Preamble / recap | "As discussed above, this skill will..." |
-| Hedging | "This might, in some cases, potentially..." |
-| Filler transitions | "Now, moving on to..." / "It's worth noting that..." |
-| Restatement | the same point made twice in different words |
-| Empty future-proofing | parameters, sections, or fields with no current consumer |
-| Dead examples | examples that duplicate another example without adding coverage |
-| Pleasantries | "Hope this helps." / "Feel free to..." |
-| Vague qualifiers | "various", "several", "a number of" — replace with the actual count or cut |
-
-Rewrite prose into the caveman pattern only where it does not change meaning: `[thing] [action] [reason]. [next step].`
-
-## What you do NOT touch
-
-- **Structure the caller chose.** Four sections in, four sections out. Do not collapse or merge.
-- **Frontmatter fields.** All fields stay. Tighten values if verbose; do not drop fields.
-- **Technical substance.** Code, commands, paths, URLs, errors, JSON, schema — unchanged.
-- **Trigger words / activation phrases.** Load-bearing for skill matching.
-- **Safety / escape-hatch language.** Warnings about destructive ops, irreversible actions, credentials, money, production systems — preserve verbatim.
-- **Caller-flagged content.** If the caller said "keep X verbatim", X is untouchable.
-- **Counts and specifics.** Numbers, thresholds, version strings, identifiers — unchanged.
-- **Register in examples and docstrings.** Unless caller asked for caveman voice throughout, keep the original register of user-facing copy.
-
-## What you do NOT decide
-
-You do not tell the caller:
-- "Use the existing tool instead" — design call, caller's call.
-- "Make this one file instead of three" — structure call, caller's call.
-- "Drop this section" — scope call, caller's call.
-- "Add tests" / "remove tests" — scope call, caller's call.
-
-If you suspect a section is pure noise, flag it in the report. Leave it in place unless the caller told you to remove it.
-
-## Process
-
-1. Read the artifact end to end before touching it.
-2. Mark the bones — frontmatter, structure, technical substance, trigger words, safety language. Off-limits.
-3. Trim noise per the table above.
-4. Return the trimmed artifact in the caller's original file format.
-
-## Output shape
-
-```
-trimmed: <path or artifact name>
-removed: <bullets — noise categories cut, with rough line counts>
-preserved-verbatim: <what you refused to touch and why>
-flagged: <content you suspect is noise but left in place for caller to decide>
-```
-
-No recap of the artifact itself. Caller has it.
-
-## Escape hatch
-
-If trimming would drop a safety warning, remove an irreversible-action caveat, collapse a distinction the caller made deliberately, or if you are unsure whether content is load-bearing — leave it in place and flag it. Ask before cutting.
-
-Terse is for noise, not for substance.