@hivehub/rulebook 4.2.2 → 4.3.1

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-memory-save.md

@@ -1,48 +1,48 @@
----
-name: /rulebook-memory-save
-id: rulebook-memory-save
-category: Rulebook
-description: Save a new persistent memory for context across AI sessions.
----
-<!-- RULEBOOK:START -->
-**Guardrails**
-- Use the MCP memory tools when available (preferred over CLI commands).
-- Choose the correct memory type for accurate classification and search.
-- Keep titles concise and content descriptive.
-- Use tags for better discoverability.
-
-**Steps**
-1. **Save a memory** using the MCP tool or CLI:
-   ```
-   # Via MCP (preferred)
-   rulebook_memory_save({
-     type: "feature",
-     title: "Short descriptive title",
-     content: "Detailed description of what happened, why, and context",
-     tags: ["relevant", "tags"]
-   })
-
-   # Via CLI
-   rulebook memory save "content text" --type feature --title "Title" --tags tag1,tag2
-   ```
-
-2. **Choose the right type**:
-   - `bugfix` - Fixed a bug or resolved an error
-   - `feature` - Added new functionality
-   - `refactor` - Restructured code without changing behavior
-   - `decision` - Made an architecture or design choice (protected from eviction)
-   - `discovery` - Found something important about the codebase
-   - `change` - General code modification
-   - `observation` - Noted something worth remembering
-
-3. **Verify** the memory was saved:
-   ```
-   rulebook_memory_search({ query: "your title keywords" })
-   ```
-
-**Best Practices**
-- Save decisions early - they are protected from cache eviction
-- Include "why" in content, not just "what"
-- Use consistent tags across related memories
-- Content within `<private>...</private>` tags will be automatically redacted
-<!-- RULEBOOK:END -->
+---
+name: /rulebook-memory-save
+id: rulebook-memory-save
+category: Rulebook
+description: Save a new persistent memory for context across AI sessions.
+---
+<!-- RULEBOOK:START -->
+**Guardrails**
+- Use the MCP memory tools when available (preferred over CLI commands).
+- Choose the correct memory type for accurate classification and search.
+- Keep titles concise and content descriptive.
+- Use tags for better discoverability.
+
+**Steps**
+1. **Save a memory** using the MCP tool or CLI:
+   ```
+   # Via MCP (preferred)
+   rulebook_memory_save({
+     type: "feature",
+     title: "Short descriptive title",
+     content: "Detailed description of what happened, why, and context",
+     tags: ["relevant", "tags"]
+   })
+
+   # Via CLI
+   rulebook memory save "content text" --type feature --title "Title" --tags tag1,tag2
+   ```
+
+2. **Choose the right type**:
+   - `bugfix` - Fixed a bug or resolved an error
+   - `feature` - Added new functionality
+   - `refactor` - Restructured code without changing behavior
+   - `decision` - Made an architecture or design choice (protected from eviction)
+   - `discovery` - Found something important about the codebase
+   - `change` - General code modification
+   - `observation` - Noted something worth remembering
+
+3. **Verify** the memory was saved:
+   ```
+   rulebook_memory_search({ query: "your title keywords" })
+   ```
+
+**Best Practices**
+- Save decisions early - they are protected from cache eviction
+- Include "why" in content, not just "what"
+- Use consistent tags across related memories
+- Content within `<private>...</private>` tags will be automatically redacted
+<!-- RULEBOOK:END -->

package/templates/commands/rulebook-memory-search.md

@@ -1,47 +1,47 @@
----
-name: /rulebook-memory-search
-id: rulebook-memory-search
-category: Rulebook
-description: Search persistent memories using hybrid BM25+vector search for context across sessions.
----
-<!-- RULEBOOK:START -->
-**Guardrails**
-- Use the MCP memory tools when available (preferred over CLI commands).
-- The memory system uses 3-layer search: Layer 1 (compact search), Layer 2 (timeline), Layer 3 (full details).
-- Always start with a broad search, then narrow down with timeline and full details.
-
-**Steps**
-1. **Search memories** using the MCP tool or CLI:
-   ```
-   # Via MCP (preferred)
-   rulebook_memory_search({ query: "search terms", mode: "hybrid", limit: 20 })
-
-   # Via CLI
-   rulebook memory search "search terms" --mode hybrid --limit 20
-   ```
-   Modes: `hybrid` (default, best results), `bm25` (keyword only), `vector` (semantic only).
-
-2. **Get timeline context** around a relevant result:
-   ```
-   rulebook_memory_timeline({ memoryId: "<id>", window: 5 })
-   ```
-
-3. **Get full details** for specific memories:
-   ```
-   rulebook_memory_get({ ids: ["<id1>", "<id2>"] })
-   ```
-
-**Memory Types**
-- `bugfix` - Bug fixes and error resolutions
-- `feature` - New features and capabilities
-- `refactor` - Code restructuring
-- `decision` - Architecture/design decisions (protected from eviction)
-- `discovery` - Findings about codebase or tools
-- `change` - General code changes
-- `observation` - General observations
-
-**Reference**
-- Use `rulebook memory stats` to check database health
-- Decisions are never evicted during cleanup
-- Privacy: content within `<private>...</private>` tags is automatically redacted
-<!-- RULEBOOK:END -->
+---
+name: /rulebook-memory-search
+id: rulebook-memory-search
+category: Rulebook
+description: Search persistent memories using hybrid BM25+vector search for context across sessions.
+---
+<!-- RULEBOOK:START -->
+**Guardrails**
+- Use the MCP memory tools when available (preferred over CLI commands).
+- The memory system uses 3-layer search: Layer 1 (compact search), Layer 2 (timeline), Layer 3 (full details).
+- Always start with a broad search, then narrow down with timeline and full details.
+
+**Steps**
+1. **Search memories** using the MCP tool or CLI:
+   ```
+   # Via MCP (preferred)
+   rulebook_memory_search({ query: "search terms", mode: "hybrid", limit: 20 })
+
+   # Via CLI
+   rulebook memory search "search terms" --mode hybrid --limit 20
+   ```
+   Modes: `hybrid` (default, best results), `bm25` (keyword only), `vector` (semantic only).
+
+2. **Get timeline context** around a relevant result:
+   ```
+   rulebook_memory_timeline({ memoryId: "<id>", window: 5 })
+   ```
+
+3. **Get full details** for specific memories:
+   ```
+   rulebook_memory_get({ ids: ["<id1>", "<id2>"] })
+   ```
+
+**Memory Types**
+- `bugfix` - Bug fixes and error resolutions
+- `feature` - New features and capabilities
+- `refactor` - Code restructuring
+- `decision` - Architecture/design decisions (protected from eviction)
+- `discovery` - Findings about codebase or tools
+- `change` - General code changes
+- `observation` - General observations
+
+**Reference**
+- Use `rulebook memory stats` to check database health
+- Decisions are never evicted during cleanup
+- Privacy: content within `<private>...</private>` tags is automatically redacted
+<!-- RULEBOOK:END -->