@hivehub/rulebook 5.1.1 → 5.1.3

package/templates/cli/CURSOR_CLI.md

@@ -1,62 +1,62 @@
-<!-- CURSOR_CLI:START -->
-# Cursor CLI Rules
-
-**Tool**: Cursor IDE automation and scripting
-
-## Quick Start
-
-```bash
-# Cursor reads .cursorrules automatically
-# This file is generated by rulebook init
-```
-
-## Usage
-
-Cursor automatically references:
-- `.cursorrules` (generated by rulebook)
-- `AGENTS.md` (via @AGENTS.md references)
-
-## Workflow
-
-1. Use `@AGENTS.md` in chat to reference standards
-2. Check past implementations in memory before starting
-3. Request: "Follow @AGENTS.md. Implement [feature] with tests."
-4. Cursor respects .cursorrules and AGENTS.md automatically
-5. Save implementation learnings to memory
-6. Review and accept changes
-
-**Critical**: Generated `.cursorrules` points to AGENTS.md. Use @ mentions for explicit references.
-
-## Persistent Memory Integration
-
-### Using Memory in Cursor
-When requesting features, include memory context:
-
-```
-@AGENTS.md
-@.rulebook/memory.md (if available)
-
-Search memory for similar implementations and include in your reasoning before implementing.
-Implement [feature]...
-```
-
-### Capturing Implementation Learnings
-After Cursor completes work:
-
-```bash
-# Review auto-captured memories
-rulebook memory search "feature name"
-
-# Augment with additional insights
-rulebook memory save "Implementation approach, patterns discovered, edge cases handled..." --type feature --title "Feature name" --tags relevant,tags
-```
-
-### Memory-Enhanced Development
-Cursor + Memory workflow:
-1. **Search**: Find past implementations with similar patterns
-2. **Reference**: Include relevant memories in prompts for context
-3. **Implement**: Cursor generates code informed by past solutions
-4. **Capture**: Save learnings for future sessions
-5. **Search Again**: Next session finds and leverages the work
-
-<!-- CURSOR_CLI:END -->
+<!-- CURSOR_CLI:START -->
+# Cursor CLI Rules
+
+**Tool**: Cursor IDE automation and scripting
+
+## Quick Start
+
+```bash
+# Cursor reads .cursorrules automatically
+# This file is generated by rulebook init
+```
+
+## Usage
+
+Cursor automatically references:
+- `.cursorrules` (generated by rulebook)
+- `AGENTS.md` (via @AGENTS.md references)
+
+## Workflow
+
+1. Use `@AGENTS.md` in chat to reference standards
+2. Check past implementations in memory before starting
+3. Request: "Follow @AGENTS.md. Implement [feature] with tests."
+4. Cursor respects .cursorrules and AGENTS.md automatically
+5. Save implementation learnings to memory
+6. Review and accept changes
+
+**Critical**: Generated `.cursorrules` points to AGENTS.md. Use @ mentions for explicit references.
+
+## Persistent Memory Integration
+
+### Using Memory in Cursor
+When requesting features, include memory context:
+
+```
+@AGENTS.md
+@.rulebook/memory.md (if available)
+
+Search memory for similar implementations and include in your reasoning before implementing.
+Implement [feature]...
+```
+
+### Capturing Implementation Learnings
+After Cursor completes work:
+
+```bash
+# Review auto-captured memories
+rulebook memory search "feature name"
+
+# Augment with additional insights
+rulebook memory save "Implementation approach, patterns discovered, edge cases handled..." --type feature --title "Feature name" --tags relevant,tags
+```
+
+### Memory-Enhanced Development
+Cursor + Memory workflow:
+1. **Search**: Find past implementations with similar patterns
+2. **Reference**: Include relevant memories in prompts for context
+3. **Implement**: Cursor generates code informed by past solutions
+4. **Capture**: Save learnings for future sessions
+5. **Search Again**: Next session finds and leverages the work
+
+<!-- CURSOR_CLI:END -->

package/templates/cli/FACTORY.md

@@ -1,18 +1,18 @@
-<!-- FACTORY:START -->
-# Factory Droid Rules
-
-**Tool**: Code generation and automation
-
-## Usage
-
-```
-"Follow @AGENTS.md standards. Generate [code] with tests."
-```
-
-## Workflow
-
-1. Reference AGENTS.md in prompts
-2. Review generated code
-3. Run quality checks
-
-<!-- FACTORY:END -->
+<!-- FACTORY:START -->
+# Factory Droid Rules
+
+**Tool**: Code generation and automation
+
+## Usage
+
+```
+"Follow @AGENTS.md standards. Generate [code] with tests."
+```
+
+## Workflow
+
+1. Reference AGENTS.md in prompts
+2. Review generated code
+3. Run quality checks
+
+<!-- FACTORY:END -->

package/templates/cli/GEMINI.md

@@ -1,35 +1,35 @@
-<!-- GEMINI:START -->
-# Gemini CLI Rules
-
-**Tool**: Google Gemini API with 2M token context
-
-## Quick Start
-
-```bash
-# Install gemini CLI
-npm install -g @google/generative-ai-cli
-
-# Set API key
-export GEMINI_API_KEY=your_key
-```
-
-## Usage
-
-```bash
-# Always reference AGENTS.md:
-gemini --prompt "Read @AGENTS.md. Implement [feature] with tests (95%+ coverage)."
-
-# Include files:
-gemini --files AGENTS.md,src/feature.ts
-```
-
-## Workflow
-
-1. Include AGENTS.md in context with `--files AGENTS.md`
-2. Request: "Follow @AGENTS.md. Implement [feature] with tests."
-3. Review output
-4. Run quality checks: `npm run lint && npm test`
-
-**Critical**: Reference @AGENTS.md for consistent code generation.
-
-<!-- GEMINI:END -->
+<!-- GEMINI:START -->
+# Gemini CLI Rules
+
+**Tool**: Google Gemini API with 2M token context
+
+## Quick Start
+
+```bash
+# Install gemini CLI
+npm install -g @google/generative-ai-cli
+
+# Set API key
+export GEMINI_API_KEY=your_key
+```
+
+## Usage
+
+```bash
+# Always reference AGENTS.md:
+gemini --prompt "Read @AGENTS.md. Implement [feature] with tests (95%+ coverage)."
+
+# Include files:
+gemini --files AGENTS.md,src/feature.ts
+```
+
+## Workflow
+
+1. Include AGENTS.md in context with `--files AGENTS.md`
+2. Request: "Follow @AGENTS.md. Implement [feature] with tests."
+3. Review output
+4. Run quality checks: `npm run lint && npm test`
+
+**Critical**: Reference @AGENTS.md for consistent code generation.
+
+<!-- GEMINI:END -->

package/templates/cli/KILOCODE.md

@@ -1,18 +1,18 @@
-<!-- KILOCODE:START -->
-# Kilo Code Rules
-
-**Tool**: Lightweight coding companion
-
-## Usage
-
-```
-"Follow @AGENTS.md. Implement [feature] with tests."
-```
-
-## Workflow
-
-1. Reference AGENTS.md
-2. Review code
-3. Run quality checks
-
-<!-- KILOCODE:END -->
+<!-- KILOCODE:START -->
+# Kilo Code Rules
+
+**Tool**: Lightweight coding companion
+
+## Usage
+
+```
+"Follow @AGENTS.md. Implement [feature] with tests."
+```
+
+## Workflow
+
+1. Reference AGENTS.md
+2. Review code
+3. Run quality checks
+
+<!-- KILOCODE:END -->

package/templates/cli/OPENCODE.md

@@ -1,18 +1,18 @@
-<!-- OPENCODE:START -->
-# OpenCode Rules
-
-**Tool**: Open-source AI assistant
-
-## Usage
-
-```
-"Follow @AGENTS.md. Implement [feature] with tests."
-```
-
-## Workflow
-
-1. Reference AGENTS.md
-2. Review code
-3. Run quality checks
-
-<!-- OPENCODE:END -->
+<!-- OPENCODE:START -->
+# OpenCode Rules
+
+**Tool**: Open-source AI assistant
+
+## Usage
+
+```
+"Follow @AGENTS.md. Implement [feature] with tests."
+```
+
+## Workflow
+
+1. Reference AGENTS.md
+2. Review code
+3. Run quality checks
+
+<!-- OPENCODE:END -->

package/templates/cli/_GENERIC_TEMPLATE.md

@@ -1,29 +1,29 @@
-<!-- {TOOL}:START -->
-# {Tool Name} CLI Rules
-
-**Tool**: {Brief description}
-
-## Quick Start
-
-```bash
-{installation command}
-```
-
-## Usage
-
-Always reference AGENTS.md in prompts:
-```
-"Follow @AGENTS.md standards. Implement [feature] with tests first (95%+ coverage)."
-```
-
-## Workflow
-
-1. Include AGENTS.md in context (tool-specific method)
-2. Request features with "@AGENTS.md" reference
-3. Review generated code
-4. Run quality checks: `npm run lint && npm test`
-
-**Critical**: Reference AGENTS.md for consistent standards.
-
-<!-- {TOOL}:END -->
-
+<!-- {TOOL}:START -->
+# {Tool Name} CLI Rules
+
+**Tool**: {Brief description}
+
+## Quick Start
+
+```bash
+{installation command}
+```
+
+## Usage
+
+Always reference AGENTS.md in prompts:
+```
+"Follow @AGENTS.md standards. Implement [feature] with tests first (95%+ coverage)."
+```
+
+## Workflow
+
+1. Include AGENTS.md in context (tool-specific method)
+2. Request features with "@AGENTS.md" reference
+3. Review generated code
+4. Run quality checks: `npm run lint && npm test`
+
+**Critical**: Reference AGENTS.md for consistent standards.
+
+<!-- {TOOL}:END -->
+

package/templates/commands/rulebook-decision-create.md

@@ -1,55 +1,55 @@
----
-name: /rulebook-decision-create
-id: rulebook-decision-create
-category: Rulebook
-description: Create a new Architecture Decision Record (ADR) with auto-numbering and memory integration.
----
-<!-- RULEBOOK:START -->
-**Guardrails**
-- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
-- Keep changes tightly scoped to the requested outcome.
-- Decisions are stored in `.rulebook/decisions/` as numbered Markdown files with metadata sidecars.
-
-**Steps**
-1. **Understand the Decision**: Ask the user what architectural/technical decision needs to be recorded. Gather:
-   - **Title**: Short, descriptive name (e.g., "Use PostgreSQL for Primary Database")
-   - **Context**: Why this decision is needed — constraints, requirements, trade-offs
-   - **Decision**: What was decided
-   - **Alternatives**: What other options were considered and why they were rejected
-   - **Consequences**: What follows from this decision (positive and negative)
-   - **Related Tasks**: Any task IDs this decision relates to
-
-2. **Check Existing Decisions**:
-   ```bash
-   rulebook decision list
-   ```
-   Verify no duplicate or conflicting decision exists.
-
-3. **Create the Decision**:
-   ```bash
-   rulebook decision create "<title>" --context "<context>" --related-task <task-id>
-   ```
-   The system auto-numbers the decision (e.g., ADR-001, ADR-002).
-
-4. **Enrich the Decision File**: Open the generated `.rulebook/decisions/NNN-<slug>.md` and fill in:
-   - Context section with full background
-   - Decision section with the chosen approach
-   - Alternatives Considered with reasoning for each rejected option
-   - Consequences with both positive and negative outcomes
-
-5. **Update Status** (if immediately accepted):
-   ```bash
-   # Via MCP tool or direct metadata edit
-   ```
-
-6. **Verify**:
-   ```bash
-   rulebook decision show <id>
-   ```
-
-**Reference**
-- Decisions use 4 statuses: `proposed` → `accepted` → `superseded` | `deprecated`
-- Use `rulebook decision supersede <oldId> <newId>` to replace a decision
-- Decisions are auto-injected into AGENTS.md on `rulebook update`
-- See `/.rulebook/specs/DECISIONS.md` for format documentation
-<!-- RULEBOOK:END -->
+---
+name: /rulebook-decision-create
+id: rulebook-decision-create
+category: Rulebook
+description: Create a new Architecture Decision Record (ADR) with auto-numbering and memory integration.
+---
+<!-- RULEBOOK:START -->
+**Guardrails**
+- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
+- Keep changes tightly scoped to the requested outcome.
+- Decisions are stored in `.rulebook/decisions/` as numbered Markdown files with metadata sidecars.
+
+**Steps**
+1. **Understand the Decision**: Ask the user what architectural/technical decision needs to be recorded. Gather:
+   - **Title**: Short, descriptive name (e.g., "Use PostgreSQL for Primary Database")
+   - **Context**: Why this decision is needed — constraints, requirements, trade-offs
+   - **Decision**: What was decided
+   - **Alternatives**: What other options were considered and why they were rejected
+   - **Consequences**: What follows from this decision (positive and negative)
+   - **Related Tasks**: Any task IDs this decision relates to
+
+2. **Check Existing Decisions**:
+   ```bash
+   rulebook decision list
+   ```
+   Verify no duplicate or conflicting decision exists.
+
+3. **Create the Decision**:
+   ```bash
+   rulebook decision create "<title>" --context "<context>" --related-task <task-id>
+   ```
+   The system auto-numbers the decision (e.g., ADR-001, ADR-002).
+
+4. **Enrich the Decision File**: Open the generated `.rulebook/decisions/NNN-<slug>.md` and fill in:
+   - Context section with full background
+   - Decision section with the chosen approach
+   - Alternatives Considered with reasoning for each rejected option
+   - Consequences with both positive and negative outcomes
+
+5. **Update Status** (if immediately accepted):
+   ```bash
+   # Via MCP tool or direct metadata edit
+   ```
+
+6. **Verify**:
+   ```bash
+   rulebook decision show <id>
+   ```
+
+**Reference**
+- Decisions use 4 statuses: `proposed` → `accepted` → `superseded` | `deprecated`
+- Use `rulebook decision supersede <oldId> <newId>` to replace a decision
+- Decisions are auto-injected into AGENTS.md on `rulebook update`
+- See `/.rulebook/specs/DECISIONS.md` for format documentation
+<!-- RULEBOOK:END -->

package/templates/commands/rulebook-decision-list.md

@@ -1,15 +1,15 @@
----
-name: /rulebook-decision-list
-id: rulebook-decision-list
-category: Rulebook
-description: List all Architecture Decision Records with optional status filter.
----
-<!-- RULEBOOK:START -->
-**Steps**
-1. Run `rulebook decision list` to see all decisions.
-2. Optionally filter: `rulebook decision list --status accepted`
-3. Present results to the user with ID, title, and status.
-4. If the user wants details on a specific decision, run `rulebook decision show <id>`.
-
-**Status Values**: proposed, accepted, superseded, deprecated
-<!-- RULEBOOK:END -->
+---
+name: /rulebook-decision-list
+id: rulebook-decision-list
+category: Rulebook
+description: List all Architecture Decision Records with optional status filter.
+---
+<!-- RULEBOOK:START -->
+**Steps**
+1. Run `rulebook decision list` to see all decisions.
+2. Optionally filter: `rulebook decision list --status accepted`
+3. Present results to the user with ID, title, and status.
+4. If the user wants details on a specific decision, run `rulebook decision show <id>`.
+
+**Status Values**: proposed, accepted, superseded, deprecated
+<!-- RULEBOOK:END -->

package/templates/commands/rulebook-knowledge-add.md

@@ -1,41 +1,41 @@
----
-name: /rulebook-knowledge-add
-id: rulebook-knowledge-add
-category: Rulebook
-description: Add a pattern or anti-pattern to the project knowledge base.
----
-<!-- RULEBOOK:START -->
-**Guardrails**
-- Knowledge entries are auto-injected into AGENTS.md on `rulebook update`, making them visible to all AI assistants.
-- Patterns go to `.rulebook/knowledge/patterns/`, anti-patterns to `.rulebook/knowledge/anti-patterns/`.
-
-**Steps**
-1. **Determine Type**: Ask if this is a `pattern` (good practice to follow) or `anti-pattern` (bad practice to avoid).
-
-2. **Gather Details**:
-   - **Title**: Short, descriptive name (e.g., "Repository Pattern", "God Object")
-   - **Category**: `architecture` | `code` | `testing` | `security` | `performance` | `devops`
-   - **Description**: What the pattern/anti-pattern is
-   - **Example**: Code showing correct (or incorrect) usage
-   - **When to Use**: Situations where this applies
-   - **When NOT to Use**: Exceptions and edge cases
-   - **Tags**: For searchability
-
-3. **Create Entry**:
-   ```bash
-   rulebook knowledge add <type> "<title>" --category <category> --description "<desc>"
-   ```
-
-4. **Enrich the Entry**: Open `.rulebook/knowledge/<type>s/<slug>.md` and fill in Example, When to Use, and When NOT to Use sections with concrete code examples.
-
-5. **Verify**:
-   ```bash
-   rulebook knowledge show <slug>
-   ```
-
-**Reference**
-- Use `rulebook knowledge list` to see all entries
-- Use `rulebook knowledge list --type pattern --category architecture` to filter
-- Use `rulebook knowledge remove <slug>` to delete an entry
-- Entries appear in AGENTS.md "Project Knowledge" section after `rulebook update`
-<!-- RULEBOOK:END -->
+---
+name: /rulebook-knowledge-add
+id: rulebook-knowledge-add
+category: Rulebook
+description: Add a pattern or anti-pattern to the project knowledge base.
+---
+<!-- RULEBOOK:START -->
+**Guardrails**
+- Knowledge entries are auto-injected into AGENTS.md on `rulebook update`, making them visible to all AI assistants.
+- Patterns go to `.rulebook/knowledge/patterns/`, anti-patterns to `.rulebook/knowledge/anti-patterns/`.
+
+**Steps**
+1. **Determine Type**: Ask if this is a `pattern` (good practice to follow) or `anti-pattern` (bad practice to avoid).
+
+2. **Gather Details**:
+   - **Title**: Short, descriptive name (e.g., "Repository Pattern", "God Object")
+   - **Category**: `architecture` | `code` | `testing` | `security` | `performance` | `devops`
+   - **Description**: What the pattern/anti-pattern is
+   - **Example**: Code showing correct (or incorrect) usage
+   - **When to Use**: Situations where this applies
+   - **When NOT to Use**: Exceptions and edge cases
+   - **Tags**: For searchability
+
+3. **Create Entry**:
+   ```bash
+   rulebook knowledge add <type> "<title>" --category <category> --description "<desc>"
+   ```
+
+4. **Enrich the Entry**: Open `.rulebook/knowledge/<type>s/<slug>.md` and fill in Example, When to Use, and When NOT to Use sections with concrete code examples.
+
+5. **Verify**:
+   ```bash
+   rulebook knowledge show <slug>
+   ```
+
+**Reference**
+- Use `rulebook knowledge list` to see all entries
+- Use `rulebook knowledge list --type pattern --category architecture` to filter
+- Use `rulebook knowledge remove <slug>` to delete an entry
+- Entries appear in AGENTS.md "Project Knowledge" section after `rulebook update`
+<!-- RULEBOOK:END -->

package/templates/commands/rulebook-knowledge-list.md

@@ -1,15 +1,15 @@
----
-name: /rulebook-knowledge-list
-id: rulebook-knowledge-list
-category: Rulebook
-description: List project knowledge entries (patterns and anti-patterns).
----
-<!-- RULEBOOK:START -->
-**Steps**
-1. Run `rulebook knowledge list` to see all entries.
-2. Optionally filter:
-   - By type: `rulebook knowledge list --type pattern`
-   - By category: `rulebook knowledge list --category architecture`
-3. Present results with type badge, title, and category.
-4. If the user wants details, run `rulebook knowledge show <slug>`.
-<!-- RULEBOOK:END -->
+---
+name: /rulebook-knowledge-list
+id: rulebook-knowledge-list
+category: Rulebook
+description: List project knowledge entries (patterns and anti-patterns).
+---
+<!-- RULEBOOK:START -->
+**Steps**
+1. Run `rulebook knowledge list` to see all entries.
+2. Optionally filter:
+   - By type: `rulebook knowledge list --type pattern`
+   - By category: `rulebook knowledge list --category architecture`
+3. Present results with type badge, title, and category.
+4. If the user wants details, run `rulebook knowledge show <slug>`.
+<!-- RULEBOOK:END -->