cc-discipline 2.10.1 → 2.10.3

package/bin/cli.sh

@@ -1,96 +1,96 @@
-#!/usr/bin/env bash
-# cc-discipline CLI entry point
-# Resolves symlinks (npm bin creates symlinks) to find the real package directory
-
-set -e
-
-# Resolve the real path of this script (works through npm symlinks)
-SOURCE="${BASH_SOURCE[0]}"
-while [ -L "$SOURCE" ]; do
-    DIR="$(cd "$(dirname "$SOURCE")" && pwd)"
-    SOURCE="$(readlink "$SOURCE")"
-    # If SOURCE is relative, resolve it relative to DIR
-    [[ "$SOURCE" != /* ]] && SOURCE="$DIR/$SOURCE"
-done
-BIN_DIR="$(cd "$(dirname "$SOURCE")" && pwd)"
-PKG_DIR="$(cd "$BIN_DIR/.." && pwd)"
-
-export CC_DISCIPLINE_PKG_DIR="$PKG_DIR"
-
-# ─── Version ───
-VERSION=$(node -p "require('$PKG_DIR/package.json').version" 2>/dev/null || echo "unknown")
-
-# ─── Route subcommands ───
-COMMAND="${1:-init}"
-
-case "$COMMAND" in
-    init)
-        shift 2>/dev/null || true
-        bash "$PKG_DIR/init.sh" "$@"
-        ;;
-    upgrade)
-        shift
-        bash "$PKG_DIR/init.sh" --auto "$@"
-        ;;
-    status)
-        bash "$PKG_DIR/lib/status.sh"
-        ;;
-    doctor)
-        bash "$PKG_DIR/lib/doctor.sh"
-        ;;
-    add-stack)
-        shift
-        if [ -z "$1" ]; then
-            echo "Usage: cc-discipline add-stack <numbers>"
-            echo "  e.g.: cc-discipline add-stack 3 4"
-            exit 1
-        fi
-        bash "$PKG_DIR/init.sh" --stack "$*" --no-global
-        ;;
-    remove-stack)
-        shift
-        bash "$PKG_DIR/lib/stack-remove.sh" "$@"
-        ;;
-    -v|--version|version)
-        echo "cc-discipline v${VERSION}"
-        ;;
-    -h|--help|help)
-        cat <<EOF
-cc-discipline v${VERSION} — Discipline framework for Claude Code
-
-Usage: cc-discipline <command> [options]
-
-Commands:
-  init [options]        Install discipline into current project (default)
-  upgrade               Upgrade rules/hooks (shortcut for init --auto)
-  add-stack <numbers>   Add stack rules (e.g., add-stack 3 4)
-  remove-stack <numbers> Remove stack rules
-  status                Show installed version, stacks, and hooks
-  doctor                Check installation integrity
-  version               Show version
-
-Init options:
-  --auto                Non-interactive with defaults
-  --stack <choices>     Stack selection: 1-7, space-separated
-  --name <name>         Project name (default: directory name)
-  --global              Install global rules to ~/.claude/CLAUDE.md
-  --no-global           Skip global rules install
-
-Stacks:
-  1=RTL  2=Embedded  3=Python  4=JS/TS  5=Mobile  6=Fullstack  7=General
-
-Examples:
-  npx cc-discipline                           # Interactive setup
-  npx cc-discipline init --auto               # Non-interactive defaults
-  npx cc-discipline init --auto --stack "3 4"  # Python + JS/TS
-  npx cc-discipline upgrade                   # Upgrade to latest
-  npx cc-discipline status                    # Check what's installed
-  npx cc-discipline doctor                    # Diagnose issues
-EOF
-        ;;
-    *)
-        echo "Unknown command: $COMMAND"
-        echo "Run 'cc-discipline --help' for usage"
-        exit 1
-        ;;
-esac
+#!/usr/bin/env bash
+# cc-discipline CLI entry point
+# Resolves symlinks (npm bin creates symlinks) to find the real package directory
+
+set -e
+
+# Resolve the real path of this script (works through npm symlinks)
+SOURCE="${BASH_SOURCE[0]}"
+while [ -L "$SOURCE" ]; do
+    DIR="$(cd "$(dirname "$SOURCE")" && pwd)"
+    SOURCE="$(readlink "$SOURCE")"
+    # If SOURCE is relative, resolve it relative to DIR
+    [[ "$SOURCE" != /* ]] && SOURCE="$DIR/$SOURCE"
+done
+BIN_DIR="$(cd "$(dirname "$SOURCE")" && pwd)"
+PKG_DIR="$(cd "$BIN_DIR/.." && pwd)"
+
+export CC_DISCIPLINE_PKG_DIR="$PKG_DIR"
+
+# ─── Version ───
+VERSION=$(node -p "require('$PKG_DIR/package.json').version" 2>/dev/null || echo "unknown")
+
+# ─── Route subcommands ───
+COMMAND="${1:-init}"
+
+case "$COMMAND" in
+    init)
+        shift 2>/dev/null || true
+        bash "$PKG_DIR/init.sh" "$@"
+        ;;
+    upgrade)
+        shift
+        bash "$PKG_DIR/init.sh" --auto "$@"
+        ;;
+    status)
+        bash "$PKG_DIR/lib/status.sh"
+        ;;
+    doctor)
+        bash "$PKG_DIR/lib/doctor.sh"
+        ;;
+    add-stack)
+        shift
+        if [ -z "$1" ]; then
+            echo "Usage: cc-discipline add-stack <numbers>"
+            echo "  e.g.: cc-discipline add-stack 3 4"
+            exit 1
+        fi
+        bash "$PKG_DIR/init.sh" --stack "$*" --no-global
+        ;;
+    remove-stack)
+        shift
+        bash "$PKG_DIR/lib/stack-remove.sh" "$@"
+        ;;
+    -v|--version|version)
+        echo "cc-discipline v${VERSION}"
+        ;;
+    -h|--help|help)
+        cat <<EOF
+cc-discipline v${VERSION} — Discipline framework for Claude Code
+
+Usage: cc-discipline <command> [options]
+
+Commands:
+  init [options]        Install discipline into current project (default)
+  upgrade               Upgrade rules/hooks (shortcut for init --auto)
+  add-stack <numbers>   Add stack rules (e.g., add-stack 3 4)
+  remove-stack <numbers> Remove stack rules
+  status                Show installed version, stacks, and hooks
+  doctor                Check installation integrity
+  version               Show version
+
+Init options:
+  --auto                Non-interactive with defaults
+  --stack <choices>     Stack selection: 1-7, space-separated
+  --name <name>         Project name (default: directory name)
+  --global              Install global rules to ~/.claude/CLAUDE.md
+  --no-global           Skip global rules install
+
+Stacks:
+  1=RTL  2=Embedded  3=Python  4=JS/TS  5=Mobile  6=Fullstack  7=General
+
+Examples:
+  npx cc-discipline                           # Interactive setup
+  npx cc-discipline init --auto               # Non-interactive defaults
+  npx cc-discipline init --auto --stack "3 4"  # Python + JS/TS
+  npx cc-discipline upgrade                   # Upgrade to latest
+  npx cc-discipline status                    # Check what's installed
+  npx cc-discipline doctor                    # Diagnose issues
+EOF
+        ;;
+    *)
+        echo "Unknown command: $COMMAND"
+        echo "Run 'cc-discipline --help' for usage"
+        exit 1
+        ;;
+esac

package/global/CLAUDE.md

@@ -1,45 +1,45 @@
-# Global Discipline — applies to all projects
-
-> This file is placed at ~/.claude/CLAUDE.md and applies to all projects.
-> Project-specific rules go in each project's CLAUDE.md and .claude/rules/.
-
----
-
-## Mindset
-
-You are an **engineer**, not a **code generator**.
-An engineer's core competency is: understand the problem → analyze approaches → weigh trade-offs → execute precisely.
-Don't skip the first three steps and jump straight to the fourth.
-
----
-
-## Universal Principles
-
-1. **Understand before acting** — If unsure, ask. Don't guess.
-2. **Minimal changes** — Do what is asked. Don't do what isn't asked.
-3. **One thing at a time** — Don't mix unrelated changes in a single modification.
-4. **Explain your reasoning** — Especially when making trade-off judgments.
-5. **Admit uncertainty** — "I'm not sure because..." is 100x better than a confident wrong answer.
-
-<!-- Anti-pattern checks moved to .claude/rules/00-core-principles.md and 04-no-mole-whacking.md,
-     project-level rules are auto-injected, no need to repeat here. -->
-
----
-
-## Collaboration with Humans
-
-- When human says "stop", stop immediately. Don't say "let me try one more thing".
-- When human corrects you, first understand why you were wrong. Don't just change to what human said and move on.
-- When unsure of human's intent, confirm before acting.
-- Provide options for human to decide, rather than making decisions for them.
-- When human changes direction, follow immediately. Don't revisit the previous goal or ask "should we finish X first?" — the user decides priorities, and your role is to execute the current direction with full commitment.
-- Don't comment on the time, suggest rest, or advise the human to "continue tomorrow". The human manages their own schedule.
-
----
-
-## Context Hygiene
-
-- Use subagents for research. Don't read large volumes of files in the main conversation.
-- Update docs/progress.md after completing each milestone.
-- Proactively warn when context is nearly full. Don't wait for auto-compact.
-- First thing after compact: read `docs/progress.md` and `docs/debug-log.md`.
+# Global Discipline — applies to all projects
+
+> This file is placed at ~/.claude/CLAUDE.md and applies to all projects.
+> Project-specific rules go in each project's CLAUDE.md and .claude/rules/.
+
+---
+
+## Mindset
+
+You are an **engineer**, not a **code generator**.
+An engineer's core competency is: understand the problem → analyze approaches → weigh trade-offs → execute precisely.
+Don't skip the first three steps and jump straight to the fourth.
+
+---
+
+## Universal Principles
+
+1. **Understand before acting** — If unsure, ask. Don't guess.
+2. **Minimal changes** — Do what is asked. Don't do what isn't asked.
+3. **One thing at a time** — Don't mix unrelated changes in a single modification.
+4. **Explain your reasoning** — Especially when making trade-off judgments.
+5. **Admit uncertainty** — "I'm not sure because..." is 100x better than a confident wrong answer.
+
+<!-- Anti-pattern checks moved to .claude/rules/00-core-principles.md and 04-no-mole-whacking.md,
+     project-level rules are auto-injected, no need to repeat here. -->
+
+---
+
+## Collaboration with Humans
+
+- When human says "stop", stop immediately. Don't say "let me try one more thing".
+- When human corrects you, first understand why you were wrong. Don't just change to what human said and move on.
+- When unsure of human's intent, confirm before acting.
+- Provide options for human to decide, rather than making decisions for them.
+- When human changes direction, follow immediately. Don't revisit the previous goal or ask "should we finish X first?" — the user decides priorities, and your role is to execute the current direction with full commitment.
+- Don't comment on the time, suggest rest, or advise the human to "continue tomorrow". The human manages their own schedule.
+
+---
+
+## Context Hygiene
+
+- Use subagents for research. Don't read large volumes of files in the main conversation.
+- Update docs/progress.md after completing each milestone.
+- Don't proactively warn about context running low or suggest compacting. The system auto-compacts at 0% — you cannot see the percentage. Keep progress.md updated instead.
+- First thing after compact: read `docs/progress.md` and `docs/debug-log.md`.