@hivehub/rulebook 5.5.2 → 5.8.0

package/templates/rules/session-workflow.md

@@ -1,24 +1,24 @@
----
-name: session-workflow
-tier: 2
-description: "Read PLANS.md at session start, save summary at session end"
-alwaysApply: true
-filePatterns: ["*"]
-tools: ["all"]
----
-
-# Session Workflow — Preserve Context Across Sessions
-
-## At Session Start
-1. Read `.rulebook/PLANS.md` for current context and active task
-2. Search memory for relevant past work: `rulebook_memory_search` or `rulebook_session_start`
-3. Check `.rulebook/tasks/` for pending work
-
-## During Session
-- Update PLANS.md when making key decisions or discoveries
-- Save important context to memory as you go
-
-## At Session End
-1. Save session summary to PLANS.md: `rulebook_session_end`
-2. Summary should include: what was accomplished, key decisions, next steps
-3. Update tasks.md with completed items
+---
+name: session-workflow
+tier: 2
+description: "Read PLANS.md at session start, save summary at session end"
+alwaysApply: true
+filePatterns: ["*"]
+tools: ["all"]
+---
+
+# Session Workflow — Preserve Context Across Sessions
+
+## At Session Start
+1. Read `.rulebook/PLANS.md` for current context and active task
+2. Search memory for relevant past work: `rulebook_memory_search` or `rulebook_session_start`
+3. Check `.rulebook/tasks/` for pending work
+
+## During Session
+- Update PLANS.md when making key decisions or discoveries
+- Save important context to memory as you go
+
+## At Session End
+1. Save session summary to PLANS.md: `rulebook_session_end`
+2. Summary should include: what was accomplished, key decisions, next steps
+3. Update tasks.md with completed items

package/templates/rules/task-decomposition.md

@@ -1,32 +1,32 @@
----
-name: task-decomposition
-tier: 2
-description: "Decompose multi-file tasks into 1-2 file sub-tasks"
-alwaysApply: true
-filePatterns: ["*"]
-tools: ["all"]
----
-
-# Task Decomposition
-
-When a task touches multiple subsystems, decompose into sub-tasks where each modifies **at most 1-2 files**.
-
-## Why
-
-AI agents lose accuracy when editing 3+ files in one pass. Context from earlier files gets compressed away.
-
-## Rules
-
-1. **Each sub-task modifies 1-2 files** — never more
-2. **Each sub-task is independently verifiable** — it compiles, it doesn't break existing behavior
-3. **Sub-tasks follow data flow order** — upstream first (component → buffer → renderer → shader)
-4. **Each sub-task has a clear "done when"** — not "implement X", but "field Y exists with default Z"
-5. **Build after each sub-task** — verify compilation before proceeding
-
-## When an Agent Receives a Multi-File Task
-
-1. **STOP** — do not start implementing
-2. **Create a change plan** listing all files and dependency order
-3. **Decompose** into sub-tasks following this rule
-4. **Report back** with the decomposition
-5. **Implement** one sub-task at a time
+---
+name: task-decomposition
+tier: 2
+description: "Decompose multi-file tasks into 1-2 file sub-tasks"
+alwaysApply: true
+filePatterns: ["*"]
+tools: ["all"]
+---
+
+# Task Decomposition
+
+When a task touches multiple subsystems, decompose into sub-tasks where each modifies **at most 1-2 files**.
+
+## Why
+
+AI agents lose accuracy when editing 3+ files in one pass. Context from earlier files gets compressed away.
+
+## Rules
+
+1. **Each sub-task modifies 1-2 files** — never more
+2. **Each sub-task is independently verifiable** — it compiles, it doesn't break existing behavior
+3. **Sub-tasks follow data flow order** — upstream first (component → buffer → renderer → shader)
+4. **Each sub-task has a clear "done when"** — not "implement X", but "field Y exists with default Z"
+5. **Build after each sub-task** — verify compilation before proceeding
+
+## When an Agent Receives a Multi-File Task
+
+1. **STOP** — do not start implementing
+2. **Create a change plan** listing all files and dependency order
+3. **Decompose** into sub-tasks following this rule
+4. **Report back** with the decomposition
+5. **Implement** one sub-task at a time

package/templates/rules/typescript.md

@@ -1,40 +1,40 @@
----
-paths:
-  - "**/*.ts"
-  - "**/*.tsx"
-  - "tsconfig.json"
-  - "tsconfig.*.json"
----
-<!-- Generated by @hivehub/rulebook v5.3.0 — delete this comment to prevent regeneration on `rulebook update` -->
-
-# TypeScript rules
-
-Loaded by Claude Code when touching TypeScript files. Keeps guidance focused so the main `CLAUDE.md` stays small.
-
-## Non-negotiables
-
-1. **Type-check before test.** Run the project's `type-check` (usually `tsc --noEmit` or `npm run type-check`) before running the test suite. A type error is a faster, cheaper signal than a test failure.
-2. **No `any`** unless the value is genuinely untyped (e.g. `JSON.parse` output before validation). Prefer `unknown` with a narrowing step.
-3. **No `// @ts-ignore` / `// @ts-expect-error`** without a one-line comment explaining why. If you can fix the type, fix it.
-4. **Strict null checks.** Treat `undefined` and `null` as distinct. Use optional chaining (`?.`) and nullish coalescing (`??`), not `||`, for "value might be absent" logic.
-5. **ESM everywhere.** Use `import`/`export`, not `require`. Relative imports include the `.js` extension (Node ESM rule) even when the source file is `.ts`.
-
-## Conventions
-
-- Public API types live next to their implementation. Large shared types go in `src/types.ts` or `src/types/`.
-- Interfaces for object shapes, `type` aliases for unions and mapped types.
-- `readonly` wherever mutation is not required.
-- Exhaustive `switch` on union types uses a `const _exhaustive: never = x;` tail.
-- Async functions return `Promise<T>` explicitly on public APIs.
-
-## Testing
-
-- Use the project's configured test runner (Vitest, Jest, Node test) — do not add a new one.
-- Mock at the module boundary, not inside the unit under test.
-- Every `describe` has at least one `it`; no empty test blocks.
-
-## Build & tooling
-
-- Never commit `dist/`, `build/`, `.tsbuildinfo`, or `node_modules/`.
-- `tsconfig.json` is the source of truth for compiler options. Do not override via inline comments unless explicitly required.
-- Prefer `tsx` / `ts-node` for scripts; never shell-execute a raw `.ts` file in production.
+---
+paths:
+  - "**/*.ts"
+  - "**/*.tsx"
+  - "tsconfig.json"
+  - "tsconfig.*.json"
+---
+<!-- Generated by @hivehub/rulebook v5.3.0 — delete this comment to prevent regeneration on `rulebook update` -->
+
+# TypeScript rules
+
+Loaded by Claude Code when touching TypeScript files. Keeps guidance focused so the main `CLAUDE.md` stays small.
+
+## Non-negotiables
+
+1. **Type-check before test.** Run the project's `type-check` (usually `tsc --noEmit` or `npm run type-check`) before running the test suite. A type error is a faster, cheaper signal than a test failure.
+2. **No `any`** unless the value is genuinely untyped (e.g. `JSON.parse` output before validation). Prefer `unknown` with a narrowing step.
+3. **No `// @ts-ignore` / `// @ts-expect-error`** without a one-line comment explaining why. If you can fix the type, fix it.
+4. **Strict null checks.** Treat `undefined` and `null` as distinct. Use optional chaining (`?.`) and nullish coalescing (`??`), not `||`, for "value might be absent" logic.
+5. **ESM everywhere.** Use `import`/`export`, not `require`. Relative imports include the `.js` extension (Node ESM rule) even when the source file is `.ts`.
+
+## Conventions
+
+- Public API types live next to their implementation. Large shared types go in `src/types.ts` or `src/types/`.
+- Interfaces for object shapes, `type` aliases for unions and mapped types.
+- `readonly` wherever mutation is not required.
+- Exhaustive `switch` on union types uses a `const _exhaustive: never = x;` tail.
+- Async functions return `Promise<T>` explicitly on public APIs.
+
+## Testing
+
+- Use the project's configured test runner (Vitest, Jest, Node test) — do not add a new one.
+- Mock at the module boundary, not inside the unit under test.
+- Every `describe` has at least one `it`; no empty test blocks.
+
+## Build & tooling
+
+- Never commit `dist/`, `build/`, `.tsbuildinfo`, or `node_modules/`.
+- `tsconfig.json` is the source of truth for compiler options. Do not override via inline comments unless explicitly required.
+- Prefer `tsx` / `ts-node` for scripts; never shell-execute a raw `.ts` file in production.

package/templates/skills/cli/aider/SKILL.md

@@ -1,59 +1,59 @@
----
-name: "Aider"
-description: "Tool: AI pair programming in terminal (`pip install aider-chat`)"
-version: "1.0.0"
-category: "cli"
-author: "Rulebook"
-tags: ["cli", "cli-tool"]
-dependencies: []
-conflicts: []
----
-<!-- AIDER:START -->
-# Aider CLI Rules
-
-**Tool**: AI pair programming in terminal (`pip install aider-chat`)
-
-## Quick Start
-
-```bash
-# Always include AGENTS.md
-aider AGENTS.md src/feature.ts tests/feature.test.ts
-
-# In chat:
-"Follow AGENTS.md standards. Implement [feature] with tests first."
-```
-
-## Essential Commands
-
-```bash
-/add file.ts          # Add files to context
-/drop file.ts         # Remove from context
-/run npm test         # Run command
-/commit "message"     # Commit changes
-/undo                 # Undo last change
-/diff                 # Review changes
-```
-
-## Configuration (.aider.conf.yml)
-
-```yaml
-model: gpt-4
-read: [AGENTS.md]
-lint: true
-lint-cmd: "npm run lint"
-test-cmd: "npm test"
-auto-commits: true
-commit-prompt: true
-```
-
-## Workflow
-
-1. Start session with `aider AGENTS.md [files]`
-2. Request: "Follow AGENTS.md. Implement [feature] with tests first (95%+ coverage)"
-3. Review diffs with `/diff`
-4. Test with `/run npm test`
-5. Commit with `/commit "feat: description"`
-
-**Critical**: Always reference AGENTS.md in your requests for consistent standards.
-
-<!-- AIDER:END -->
+---
+name: "Aider"
+description: "Tool: AI pair programming in terminal (`pip install aider-chat`)"
+version: "1.0.0"
+category: "cli"
+author: "Rulebook"
+tags: ["cli", "cli-tool"]
+dependencies: []
+conflicts: []
+---
+<!-- AIDER:START -->
+# Aider CLI Rules
+
+**Tool**: AI pair programming in terminal (`pip install aider-chat`)
+
+## Quick Start
+
+```bash
+# Always include AGENTS.md
+aider AGENTS.md src/feature.ts tests/feature.test.ts
+
+# In chat:
+"Follow AGENTS.md standards. Implement [feature] with tests first."
+```
+
+## Essential Commands
+
+```bash
+/add file.ts          # Add files to context
+/drop file.ts         # Remove from context
+/run npm test         # Run command
+/commit "message"     # Commit changes
+/undo                 # Undo last change
+/diff                 # Review changes
+```
+
+## Configuration (.aider.conf.yml)
+
+```yaml
+model: gpt-4
+read: [AGENTS.md]
+lint: true
+lint-cmd: "npm run lint"
+test-cmd: "npm test"
+auto-commits: true
+commit-prompt: true
+```
+
+## Workflow
+
+1. Start session with `aider AGENTS.md [files]`
+2. Request: "Follow AGENTS.md. Implement [feature] with tests first (95%+ coverage)"
+3. Review diffs with `/diff`
+4. Test with `/run npm test`
+5. Commit with `/commit "feat: description"`
+
+**Critical**: Always reference AGENTS.md in your requests for consistent standards.
+
+<!-- AIDER:END -->

package/templates/skills/cli/amazon-q/SKILL.md

@@ -1,35 +1,35 @@
----
-name: "Amazon Q"
-description: "Tool: AWS-focused AI assistant with security scanning"
-version: "1.0.0"
-category: "cli"
-author: "Rulebook"
-tags: ["cli", "cli-tool"]
-dependencies: []
-conflicts: []
----
-<!-- AMAZON_Q:START -->
-# Amazon Q Developer Rules
-
-**Tool**: AWS-focused AI assistant with security scanning
-
-## Quick Start
-
-Available in AWS IDE Toolkit or via AWS Console.
-
-## Usage
-
-```
-"Follow @AGENTS.md standards. Implement [feature] with tests (95%+ coverage)."
-```
-
-## Workflow
-
-1. Reference AGENTS.md in prompts
-2. Leverage Q's security scanning for vulnerabilities
-3. Review generated code
-4. Run quality checks
-
-**Critical**: Q excels at AWS/security - combine with AGENTS.md standards.
-
-<!-- AMAZON_Q:END -->
+---
+name: "Amazon Q"
+description: "Tool: AWS-focused AI assistant with security scanning"
+version: "1.0.0"
+category: "cli"
+author: "Rulebook"
+tags: ["cli", "cli-tool"]
+dependencies: []
+conflicts: []
+---
+<!-- AMAZON_Q:START -->
+# Amazon Q Developer Rules
+
+**Tool**: AWS-focused AI assistant with security scanning
+
+## Quick Start
+
+Available in AWS IDE Toolkit or via AWS Console.
+
+## Usage
+
+```
+"Follow @AGENTS.md standards. Implement [feature] with tests (95%+ coverage)."
+```
+
+## Workflow
+
+1. Reference AGENTS.md in prompts
+2. Leverage Q's security scanning for vulnerabilities
+3. Review generated code
+4. Run quality checks
+
+**Critical**: Q excels at AWS/security - combine with AGENTS.md standards.
+
+<!-- AMAZON_Q:END -->

package/templates/skills/cli/auggie/SKILL.md

@@ -1,42 +1,42 @@
----
-name: "Auggie"
-description: "Tool: TDD mode and intelligent refactoring"
-version: "1.0.0"
-category: "cli"
-author: "Rulebook"
-tags: ["cli", "cli-tool"]
-dependencies: []
-conflicts: []
----
-<!-- AUGGIE:START -->
-# Auggie (Augment CLI) Rules
-
-**Tool**: TDD mode and intelligent refactoring
-
-## Quick Start
-
-```bash
-npm install -g augment-cli
-augment --tdd
-```
-
-## Usage
-
-```bash
-# TDD mode with AGENTS.md:
-augment --tdd --context AGENTS.md
-
-# In prompts:
-"Follow @AGENTS.md. Write tests for [feature], then implement."
-```
-
-## Workflow
-
-1. Use `--tdd` flag for test-first development
-2. Include `--context AGENTS.md`
-3. Auggie writes tests, then implementation
-4. Review and verify coverage
-
-**Critical**: TDD mode aligns perfectly with AGENTS.md test-first approach.
-
-<!-- AUGGIE:END -->
+---
+name: "Auggie"
+description: "Tool: TDD mode and intelligent refactoring"
+version: "1.0.0"
+category: "cli"
+author: "Rulebook"
+tags: ["cli", "cli-tool"]
+dependencies: []
+conflicts: []
+---
+<!-- AUGGIE:START -->
+# Auggie (Augment CLI) Rules
+
+**Tool**: TDD mode and intelligent refactoring
+
+## Quick Start
+
+```bash
+npm install -g augment-cli
+augment --tdd
+```
+
+## Usage
+
+```bash
+# TDD mode with AGENTS.md:
+augment --tdd --context AGENTS.md
+
+# In prompts:
+"Follow @AGENTS.md. Write tests for [feature], then implement."
+```
+
+## Workflow
+
+1. Use `--tdd` flag for test-first development
+2. Include `--context AGENTS.md`
+3. Auggie writes tests, then implementation
+4. Review and verify coverage
+
+**Critical**: TDD mode aligns perfectly with AGENTS.md test-first approach.
+
+<!-- AUGGIE:END -->

package/templates/skills/cli/claude/SKILL.md

@@ -1,42 +1,42 @@
----
-name: "Claude"
-description: "Tool: Anthropic Claude API with 200K context window"
-version: "1.0.0"
-category: "cli"
-author: "Rulebook"
-tags: ["cli", "cli-tool"]
-dependencies: []
-conflicts: []
----
-<!-- CLAUDE:START -->
-# Claude API/CLI Rules
-
-**Tool**: Anthropic Claude API with 200K context window
-
-## Quick Start
-
-```bash
-export ANTHROPIC_API_KEY=your_key
-# Use via API or compatible CLIs
-```
-
-## Usage
-
-In API requests or CLI prompts, include:
-```
-"Follow these project standards from AGENTS.md:
-[paste relevant AGENTS.md sections]
-
-Implement [feature] with tests first (95%+ coverage)."
-```
-
-## Workflow
-
-1. Include AGENTS.md content in system prompt or context
-2. Request features with standards reference
-3. Review generated code
-4. Run quality checks
-
-**Critical**: Claude has 200K context - paste full AGENTS.md for best results.
-
-<!-- CLAUDE:END -->
+---
+name: "Claude"
+description: "Tool: Anthropic Claude API with 200K context window"
+version: "1.0.0"
+category: "cli"
+author: "Rulebook"
+tags: ["cli", "cli-tool"]
+dependencies: []
+conflicts: []
+---
+<!-- CLAUDE:START -->
+# Claude API/CLI Rules
+
+**Tool**: Anthropic Claude API with 200K context window
+
+## Quick Start
+
+```bash
+export ANTHROPIC_API_KEY=your_key
+# Use via API or compatible CLIs
+```
+
+## Usage
+
+In API requests or CLI prompts, include:
+```
+"Follow these project standards from AGENTS.md:
+[paste relevant AGENTS.md sections]
+
+Implement [feature] with tests first (95%+ coverage)."
+```
+
+## Workflow
+
+1. Include AGENTS.md content in system prompt or context
+2. Request features with standards reference
+3. Review generated code
+4. Run quality checks
+
+**Critical**: Claude has 200K context - paste full AGENTS.md for best results.
+
+<!-- CLAUDE:END -->

package/templates/skills/cli/cline/SKILL.md

@@ -1,42 +1,42 @@
----
-name: "Cline"
-description: "Tool: VS Code extension with autonomous mode"
-version: "1.0.0"
-category: "cli"
-author: "Rulebook"
-tags: ["cli", "cli-tool"]
-dependencies: []
-conflicts: []
----
-<!-- CLINE:START -->
-# Cline CLI Rules
-
-**Tool**: VS Code extension with autonomous mode
-
-## Quick Start
-
-Install Cline extension in VS Code or use CLI mode.
-
-## Usage
-
-```bash
-# In prompts, always reference standards:
-"Follow @AGENTS.md. Implement [feature] with tests first (95%+ coverage)."
-
-# Cline will:
-- Read AGENTS.md
-- Write tests
-- Implement feature
-- Run quality checks
-```
-
-## Workflow
-
-1. Keep AGENTS.md open in workspace
-2. Request features with "Follow @AGENTS.md" prefix
-3. Review proposed changes before approval
-4. Verify tests pass after implementation
-
-**Critical**: Reference @AGENTS.md in every prompt for consistent output.
-
-<!-- CLINE:END -->
+---
+name: "Cline"
+description: "Tool: VS Code extension with autonomous mode"
+version: "1.0.0"
+category: "cli"
+author: "Rulebook"
+tags: ["cli", "cli-tool"]
+dependencies: []
+conflicts: []
+---
+<!-- CLINE:START -->
+# Cline CLI Rules
+
+**Tool**: VS Code extension with autonomous mode
+
+## Quick Start
+
+Install Cline extension in VS Code or use CLI mode.
+
+## Usage
+
+```bash
+# In prompts, always reference standards:
+"Follow @AGENTS.md. Implement [feature] with tests first (95%+ coverage)."
+
+# Cline will:
+- Read AGENTS.md
+- Write tests
+- Implement feature
+- Run quality checks
+```
+
+## Workflow
+
+1. Keep AGENTS.md open in workspace
+2. Request features with "Follow @AGENTS.md" prefix
+3. Review proposed changes before approval
+4. Verify tests pass after implementation
+
+**Critical**: Reference @AGENTS.md in every prompt for consistent output.
+
+<!-- CLINE:END -->