claude-dev-env 2.5.0 → 2.7.0

package/rules/package-inventory-stale-entry.md

@@ -1,25 +0,0 @@
----
-paths:
-  - "**/*.py"
-  - "**/*.mjs"
-  - "**/*.js"
-  - "**/*.ts"
-  - "**/*.ps1"
-  - "**/*.sh"
----
-
-# New Production File Absent From Its Package Inventory
-
-A package directory that documents its own files in a `README.md` Layout table, a `CLAUDE.md` "Key files" list, or a skill `SKILL.md` Layout table keeps that inventory in step with the directory. When you create a new production file in such a directory, add an entry naming it — a row in the table or a bullet in the list — in the same change. The entry names the file in backticks and says what it does.
-
-`package_inventory_stale_blocker.py` (PreToolUse on Write) blocks a new production file whose basename appears in no present inventory and names the fix. A skill `SKILL.md` Layout table that maps `scripts/` counts as the inventory for files in that subdirectory.
-
-## Judgment the gate cannot derive
-
-The file-list entry is the slice the gate checks by name. Two free-prose slices stay with judgment and belong in the same change:
-
-1. **Purpose / scope sentence.** When the new module adds a responsibility the package `## Purpose` (or the parent inventory's one-line summary of this subdirectory) omits, broaden that sentence to name it. A hook cannot derive a module's responsibility from its filename.
-
-2. **Per-file description clause.** When a file gains a responsibility the inventory's em-dash description omits — a new public function, a new module-level constant — broaden the description clause to name it. The gate only checks that the basename appears once; it never reads the description. Constants modules (`*_constants.py`, or any `.py` directly inside `config/`) are the common shape: the constant's other home is the module docstring, so the clause that lands in the docstring lands in the inventory description in the same change. The gate fires on Write of a new file and skips files directly inside `config/`, so an Edit that adds a constant to an existing config module matches neither path.
-
-This is the `category-o-docstring-vs-impl-drift` (O8) orphaned-doc-claim shape applied to a package inventory.

package/rules/right-sized-engineering.md

@@ -1,28 +0,0 @@
-# Right-Sized Engineering
-
-**Build it right, but build it simple.** Good engineering principles at the appropriate scale.
-
-## Always Do
-- Extract constants and configuration (no hardcoding)
-- Create reusable functions (no copy-paste)
-- Use proper error handling
-- Follow DRY from the start
-- Single responsibility per function
-
-## Never Do (Solo Scale)
-- Abstract base classes for single implementations
-- Dependency injection frameworks
-- Complex patterns (CQRS, microservices)
-- Multiple inheritance hierarchies
-- Over-abstracted interfaces
-
-## Complexity Budget
-
-**State BEFORE implementation:** Files (target 1-2, max 3), Lines (~50-300), Checkpoints ("Is this MINIMUM?", "Fewer files?", "Functions vs classes?")
-
-## YAGNI for API Surface
-
-**Don't expose optional parameters until they're actually used.**
-
-If a value will always be a constant for now, use the constant internally.
-Only add the parameter when callers actually need to vary it.

package/rules/self-contained-docs.md

@@ -1,17 +0,0 @@
-# Self-Contained Documentation
-
-**When this applies:** All generated artifacts — gists, decision docs, PR descriptions, issue bodies, plans, SKILL.md content. Exception: Obsidian session logs (intentionally conversation-scoped).
-
-## Rule
-
-Every document must be fully self-contained. A reader with zero prior context must understand every statement without needing access to the conversation that produced it.
-
-## Patterns to Catch and Replace
-
-| Pattern | Example | Fix |
-|---|---|---|
-| References to options/choices discussed in conversation | "This is not Option A from the original framing" | Delete the sentence, or restate the decision on its own terms |
-| "As discussed" / "as we decided" / "from the prior session" | "As discussed, we'll use embeddings" | "Sref matching uses sentence-transformer embeddings" |
-| Pronouns pointing to conversation context | "This approach addresses the concerns raised earlier" | State what the concerns were inline, or delete |
-| Relative framing ("instead of X") where X was only discussed verbally | "Instead of the three options considered" | State the chosen approach directly without referencing alternatives the reader can't see |
-| Session-specific sequencing | "After Round 3 we decided..." | State the decision as a fact |

package/rules/shell-invocation-policy.md

@@ -1,5 +0,0 @@
-# Shell Invocation Policy (pwsh-only)
-
-Every Bash-tool shell command on Windows uses `pwsh`: `pwsh -NoProfile -File '<script>.ps1' <args>` for scripts, `pwsh -NoProfile -Command "..."` (or a literal `@'...'@` here-string) for inline work, or the built-in `PowerShell` tool for pure-PowerShell workflows (it supports `run_in_background`). Never wrap a script path in `-Command "& '...'"` — `-File` keeps `permissions.allow` matching. The `&` call operator is fine for invoking an executable at a path (`& '<venv>\Scripts\python.exe' script.py`).
-
-Keep `powershell`, `powershell.exe`, `cmd /c`, and `bash -c` out of the `settings.json` permission rules. `Audit-ShellPolicy.ps1` reports those forms and `Migrate-ShellPolicy.ps1` rewrites them to `pwsh`, both in `packages/claude-dev-env/scripts/` and run on demand, not as a live gate.

package/rules/state-what-is.md

@@ -1,25 +0,0 @@
----
-paths:
-  - "**/*.md"
-  - "**/*.py"
-  - "**/*.mjs"
-  - "**/*.js"
-  - "**/*.ts"
-  - "**/*.ps1"
-  - "**/*.sh"
----
-
-# State What Is
-
-Write settled facts, decisions, and actions that are load-bearing for the reader now. Assert each claim, decision, or action directly, and let it stand on its own evidence.
-
-A detail earns its place by mattering now, or by being timeless enough to matter for future work or plans. Omit everything else as noise.
-
-## Two patterns to replace on sight
-
-- **Exclusion** — establishing a claim by naming what it is not, or by listing what is out of bounds. Replace it with the claim itself.
-- **Elimination** — walking rejected candidates (causes, options, paths, explanations) to reach the answer. Replace it with the answer and the evidence that supports it.
-
-## Sibling rules
-
-This rule sits beside the other prose-quality rules in this directory: [`no-historical-clutter.md`](no-historical-clutter.md) cuts references to old state, [`self-contained-docs.md`](self-contained-docs.md) cuts references to the conversation that produced a doc, [`no-justification-noise.md`](no-justification-noise.md) cuts sentences that only justify a stated choice, and [`plain-language.md`](plain-language.md) swaps heavy words for everyday ones. This rule governs how a claim gets established — directly, not by elimination or exclusion.

package/rules/tdd.md

@@ -1,7 +0,0 @@
-# TDD Process: Red-Green-Refactor
-
-**TEST-DRIVEN DEVELOPMENT IS NON-NEGOTIABLE.** Every single line of production code must be written in response to a failing test. No exceptions.
-
-1. **Red**: Write failing test. NO PRODUCTION CODE.
-2. **Green**: MINIMUM code to pass. Resist urge for more.
-3. **Refactor**: Assess improvements. Only if valuable.