@hivehub/rulebook 5.7.0 → 5.8.0

package/templates/cli/AIDER.md

@@ -1,49 +1,49 @@
-<!-- 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 -->
+<!-- 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/cli/AMAZON_Q.md

@@ -1,25 +1,25 @@
-<!-- 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 -->
+<!-- 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/cli/AUGGIE.md

@@ -1,32 +1,32 @@
-<!-- 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 -->
+<!-- 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/cli/CLAUDE.md

@@ -1,117 +1,117 @@
-<!-- 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
-5. Save learnings to persistent memory
-
-**Critical**: Claude has 200K context - paste full AGENTS.md for best results.
-
-## ⚠️ Token Optimization (CRITICAL)
-
-**MINIMIZE unnecessary output to reduce token consumption:**
-
-### DO ✅
-- Output code directly without explanations
-- Use code comments for complex logic instead of markdown
-- Return results concisely: "✅ Done" or "❌ Error: reason"
-- Use tables only when absolutely necessary
-- Combine multiple small outputs into single response
-
-### DON'T ❌
-- **NEVER generate markdown reports or summaries** unless explicitly requested
-- **NEVER use excessive heading levels** (#, ##, ###, etc.)
-- **NEVER create "Quality Checks" sections** with status boxes
-- **NEVER output commit messages verbatim** - just say "committed"
-- **NEVER explain what you did** - assume user knows project structure
-- **NEVER use emoji status lines** (✅ Type check: Passed) - too verbose
-- **NEVER generate "Next Steps" sections** - just do the work
-- **NEVER output implementation details in plain text** - put in code comments
-
-### Example: BAD (Wastes Tokens)
-```
-✅ Implementation Complete
-
-📝 Changes:
-- Added UserService class
-- Added authentication middleware
-- Updated routes configuration
-
-🧪 Quality Checks:
-- ✅ Type check: Passed
-- ✅ Linting: Passed (0 warnings)
-- ✅ Tests: 45/45 passed (100%)
-- ✅ Coverage: 96% (threshold: 95%)
-
-📊 Summary:
-This implementation adds...
-
-Next Steps:
-1. Review the code
-2. Deploy to production
-```
-
-### Example: GOOD (Efficient)
-```
-✅ Done. UserService added with auth middleware.
-```
-
-Put details in code comments, not markdown.
-
-## Persistent Memory Integration
-
-### Search for Past Context
-Before implementing a feature, search memory for similar past work:
-
-```bash
-# Search for past implementations
-rulebook memory search "feature name" --mode hybrid --type feature
-
-# View timeline of related work
-rulebook memory timeline --memoryId <id>
-```
-
-### Save Implementation Insights
-After completing implementation, capture key learnings:
-
-```bash
-# Save feature implementation
-rulebook memory save "Implemented [feature] with [approach]. Key decision: [why]. Gotcha: [edge case]. Pattern: [reusable solution]" --type feature --title "[Feature name]" --tags tag1,tag2
-
-# Save bugfix insights
-rulebook memory save "Fixed [bug] by [solution]. Root cause: [why it happened]. Test case: [added validation]" --type bugfix --title "[Bug description]" --tags bugfix,area
-
-# Save architectural decisions
-rulebook memory save "Chose [approach] over [alternative] because [reasoning]. Tradeoffs: [what was sacrificed]. Future implications: [impact on architecture]" --type decision --title "[Decision name]" --tags architecture,decision
-```
-
-### Use Context from Memory
-When Claude Code returns, your memory system auto-captures learnings. Review and augment:
-1. Search relevant memories: `rulebook memory search "your topic"`
-2. Review 3-layer search results: compact → timeline → full details
-3. Reference past patterns in new implementations
-
-<!-- CLAUDE:END -->
+<!-- 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
+5. Save learnings to persistent memory
+
+**Critical**: Claude has 200K context - paste full AGENTS.md for best results.
+
+## ⚠️ Token Optimization (CRITICAL)
+
+**MINIMIZE unnecessary output to reduce token consumption:**
+
+### DO ✅
+- Output code directly without explanations
+- Use code comments for complex logic instead of markdown
+- Return results concisely: "✅ Done" or "❌ Error: reason"
+- Use tables only when absolutely necessary
+- Combine multiple small outputs into single response
+
+### DON'T ❌
+- **NEVER generate markdown reports or summaries** unless explicitly requested
+- **NEVER use excessive heading levels** (#, ##, ###, etc.)
+- **NEVER create "Quality Checks" sections** with status boxes
+- **NEVER output commit messages verbatim** - just say "committed"
+- **NEVER explain what you did** - assume user knows project structure
+- **NEVER use emoji status lines** (✅ Type check: Passed) - too verbose
+- **NEVER generate "Next Steps" sections** - just do the work
+- **NEVER output implementation details in plain text** - put in code comments
+
+### Example: BAD (Wastes Tokens)
+```
+✅ Implementation Complete
+
+📝 Changes:
+- Added UserService class
+- Added authentication middleware
+- Updated routes configuration
+
+🧪 Quality Checks:
+- ✅ Type check: Passed
+- ✅ Linting: Passed (0 warnings)
+- ✅ Tests: 45/45 passed (100%)
+- ✅ Coverage: 96% (threshold: 95%)
+
+📊 Summary:
+This implementation adds...
+
+Next Steps:
+1. Review the code
+2. Deploy to production
+```
+
+### Example: GOOD (Efficient)
+```
+✅ Done. UserService added with auth middleware.
+```
+
+Put details in code comments, not markdown.
+
+## Persistent Memory Integration
+
+### Search for Past Context
+Before implementing a feature, search memory for similar past work:
+
+```bash
+# Search for past implementations
+rulebook memory search "feature name" --mode hybrid --type feature
+
+# View timeline of related work
+rulebook memory timeline --memoryId <id>
+```
+
+### Save Implementation Insights
+After completing implementation, capture key learnings:
+
+```bash
+# Save feature implementation
+rulebook memory save "Implemented [feature] with [approach]. Key decision: [why]. Gotcha: [edge case]. Pattern: [reusable solution]" --type feature --title "[Feature name]" --tags tag1,tag2
+
+# Save bugfix insights
+rulebook memory save "Fixed [bug] by [solution]. Root cause: [why it happened]. Test case: [added validation]" --type bugfix --title "[Bug description]" --tags bugfix,area
+
+# Save architectural decisions
+rulebook memory save "Chose [approach] over [alternative] because [reasoning]. Tradeoffs: [what was sacrificed]. Future implications: [impact on architecture]" --type decision --title "[Decision name]" --tags architecture,decision
+```
+
+### Use Context from Memory
+When Claude Code returns, your memory system auto-captures learnings. Review and augment:
+1. Search relevant memories: `rulebook memory search "your topic"`
+2. Review 3-layer search results: compact → timeline → full details
+3. Reference past patterns in new implementations
+
+<!-- CLAUDE:END -->

package/templates/cli/CLINE.md

@@ -1,99 +1,99 @@
-<!-- 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. Search memory for similar past implementations before starting
-4. Review proposed changes before approval
-5. Verify tests pass after implementation
-6. Save learnings to persistent memory
-
-**Critical**: Reference @AGENTS.md in every prompt for consistent output.
-
-## ⚠️ Token Optimization (CRITICAL)
-
-**Minimize output to reduce token consumption:**
-
-### DO ✅
-- Output code directly
-- Use code comments for explanations
-- Return concise results: "✅ Done" instead of reports
-- Combine multiple small outputs
-
-### DON'T ❌
-- **NEVER generate markdown reports** unless explicitly requested
-- **NEVER use emoji status lines** (✅ Type check: Passed)
-- **NEVER create "Quality Checks" sections** with status boxes
-- **NEVER explain implementation details** in plain text
-- **NEVER add "Next Steps" sections**
-
-**Example**:
-- ❌ BAD: "✅ Type check: Passed. ✅ Linting: 0 warnings. ✅ Tests: 45/45..." (500+ tokens)
-- ✅ GOOD: "✅ Checks pass. Tests: 45/45." (~50 tokens)
-
-## Persistent Memory Integration
-
-### Before Implementation
-Always search for past similar work:
-
-```bash
-# Search for feature implementations
-rulebook memory search "your feature" --mode hybrid
-
-# View specific implementation details
-rulebook memory get <memory-id>
-```
-
-### Prompt Template with Memory
-When requesting a feature, include memory context:
-
-```
-Follow @AGENTS.md and @.rulebook/memory.md.
-
-Similar past implementations from memory:
-[paste relevant memory summaries]
-
-Implement [feature]...
-```
-
-### After Implementation
-Cline's auto-capture may save learnings. Augment with additional context:
-
-```bash
-# Verify auto-captured memory
-rulebook memory search "feature name" --type feature
-
-# Add additional context if needed
-rulebook memory save "Implementation details and patterns..." --type feature --title "Feature name"
-```
-
-## Memory-Aware Development
-
-The memory system provides:
-- **Pattern discovery**: Find reusable solutions from past work
-- **Gotcha avoidance**: Learn from past edge cases
-- **Decision context**: Understand architectural choices
-- **Faster iteration**: Reference proven approaches
-
-<!-- CLINE:END -->
+<!-- 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. Search memory for similar past implementations before starting
+4. Review proposed changes before approval
+5. Verify tests pass after implementation
+6. Save learnings to persistent memory
+
+**Critical**: Reference @AGENTS.md in every prompt for consistent output.
+
+## ⚠️ Token Optimization (CRITICAL)
+
+**Minimize output to reduce token consumption:**
+
+### DO ✅
+- Output code directly
+- Use code comments for explanations
+- Return concise results: "✅ Done" instead of reports
+- Combine multiple small outputs
+
+### DON'T ❌
+- **NEVER generate markdown reports** unless explicitly requested
+- **NEVER use emoji status lines** (✅ Type check: Passed)
+- **NEVER create "Quality Checks" sections** with status boxes
+- **NEVER explain implementation details** in plain text
+- **NEVER add "Next Steps" sections**
+
+**Example**:
+- ❌ BAD: "✅ Type check: Passed. ✅ Linting: 0 warnings. ✅ Tests: 45/45..." (500+ tokens)
+- ✅ GOOD: "✅ Checks pass. Tests: 45/45." (~50 tokens)
+
+## Persistent Memory Integration
+
+### Before Implementation
+Always search for past similar work:
+
+```bash
+# Search for feature implementations
+rulebook memory search "your feature" --mode hybrid
+
+# View specific implementation details
+rulebook memory get <memory-id>
+```
+
+### Prompt Template with Memory
+When requesting a feature, include memory context:
+
+```
+Follow @AGENTS.md and @.rulebook/memory.md.
+
+Similar past implementations from memory:
+[paste relevant memory summaries]
+
+Implement [feature]...
+```
+
+### After Implementation
+Cline's auto-capture may save learnings. Augment with additional context:
+
+```bash
+# Verify auto-captured memory
+rulebook memory search "feature name" --type feature
+
+# Add additional context if needed
+rulebook memory save "Implementation details and patterns..." --type feature --title "Feature name"
+```
+
+## Memory-Aware Development
+
+The memory system provides:
+- **Pattern discovery**: Find reusable solutions from past work
+- **Gotcha avoidance**: Learn from past edge cases
+- **Decision context**: Understand architectural choices
+- **Faster iteration**: Reference proven approaches
+
+<!-- CLINE:END -->