claudify-agent 1.0.10 → 1.0.12

package/.claude/commands/backbone-init.md

@@ -18,4 +18,10 @@ Draft or refresh `BACKBONE.md` at the project root. Notes from me: $ARGUMENTS
 3. Keep it under ~80 lines. Link, never copy.
 4. List what you could not determine as questions, batched in one message.
 5. Set `Last synced: <HEAD short sha> (<date>)` so `/backbone-sync` can diff from here.
-6. Show the full diff and wait for my approval before writing.
+6. Slim `CLAUDE.md`: it is loaded every session too, so project facts in it are paid twice. Only touch content OUTSIDE the `<!-- claudify:start -->`…`<!-- claudify:end -->` block. If that content is more than ~30 lines, propose:
+   - project facts (overview, repos, structure, commands) → the matching `BACKBONE.md` section;
+   - must-follow rules and known traps → `BACKBONE.md` Invariants;
+   - long procedures (deploy, onboarding, runbooks) → keep or move to a doc under `docs/`, linked from the Docs index;
+   - AI working rules specific to this project → keep in `CLAUDE.md`.
+   Show a table "original line range → destination" so nothing disappears silently. Never drop content that has no destination; when unsure, keep it in `CLAUDE.md`.
+7. Show the full diff (`BACKBONE.md`, and `CLAUDE.md` / new docs if slimming) and wait for my approval before writing. If I decline the slimming, write only `BACKBONE.md`.

package/.claude/commands/backbone-sync.md

@@ -17,4 +17,5 @@ Sync `BACKBONE.md` with the code as it is now. Focus: $ARGUMENTS
    - Open changes: entries whose `spec/changes/*.md` is gone or done.
 3. Also compare with `spec/specs/*.md` for the touched areas. Report code that contradicts an archived requirement, but do not edit specs: that is my call (fix the code or open a change).
 4. Ask me about anything you cannot decide from evidence, batched in one message. Never invent invariants.
-5. Show the `BACKBONE.md` diff, including `Last synced: <HEAD short sha> (<date>)`, and wait for my approval before writing.
+5. If `CLAUDE.md` outside the claudify block grew past ~30 lines or repeats backbone facts, propose slimming it exactly as in step 6 of `.claude/commands/backbone-init.md`.
+6. Show the diff (`BACKBONE.md` including `Last synced: <HEAD short sha> (<date>)`, plus `CLAUDE.md` if slimming) and wait for my approval before writing.

package/.claude/commands/spec-apply.md

@@ -7,6 +7,7 @@ Implement spec change: $ARGUMENTS
 
 1. Read `spec/changes/<change-name>.md`; respect the Invariants in `BACKBONE.md`. Nothing else up front; read code only as each task needs it.
 2. Take the requested task, or the first unchecked `- [ ]` task. Work one task at a time.
+   Business-rule guard: money amounts, limits, fees, refunds, permissions, status transitions, legal/compliance rules MUST come from an AC, the Invariants or a linked doc. If the task needs one that is not written down, stop and ask me; never pick a "reasonable" value. Add my answer to the spec before coding it.
 3. Implement it with tests for the ACs it covers. Each test name contains the full AC ID, e.g. `describe("refund/AC-2: expired QR is refunded", ...)` or `func TestRefund_AC2` with a `// refund/AC-2` comment. Use the Domain glossary terms for names. Then run its DoD. Fix until it passes (max 5 attempts, then stop and report).
 4. Tick it `- [x]` in the change file. If reality differs from the spec, update the spec (Requirements/Design) in the same step and tell me.
 5. If I ask you to commit: `feat(<change-name>): <what>` and list the AC IDs covered in the body.

package/CLAUDE.md

@@ -9,6 +9,7 @@
 
 If it still holds `<placeholders>`, suggest `/backbone-init`. Follow its Invariants on every task.
 If you finish work without a spec that changes structure, docs, commands or capabilities, suggest `/backbone-sync`.
+Never invent business rules (money, limits, refunds, permissions, status transitions, legal): if no spec, invariant or doc states it, ask.
 
 ## 1. 🛑 Context & Token Preservation (Sub-20 Line Core)
 - Keep responses concise and targeted. Never dump entire files when diffs suffice.
@@ -21,6 +22,7 @@ If you finish work without a spec that changes structure, docs, commands or capa
 ## 2. 📋 Plan First Protocol (Anti-Drift)
 - For tasks touching **>= 2 files** or core architecture:
   - Generate a concise Plan before modifying files.
+  - Inside `/spec-apply`, the approved spec Tasks are the plan; do not write another one.
   - Research protocol: `.claude/rules/plan-mode-research.md`
   - Execution checklist: `.claude/rules/plan-mode-execution.md`
   - Validation steps: `.claude/rules/plan-mode-validation.md`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudify-agent",
-  "version": "1.0.10",
+  "version": "1.0.12",
   "description": "Enterprise-grade workflow & context optimization framework for Claude Code, Claude Desktop, and AI coding agents.",
   "repository": {
     "type": "git",