@hivehub/rulebook 3.2.0 → 3.3.0

package/templates/core/RULEBOOK.md

@@ -152,7 +152,7 @@ rulebook task show <task-id>
 rulebook task create <task-id>
 
 # This creates:
-# /rulebook/tasks/<task-id>/
+# /.rulebook/tasks/<task-id>/
 #   ├── proposal.md       # Why and what changes
 #   ├── tasks.md          # Implementation checklist
 #   ├── design.md         # Technical decisions (optional)
@@ -163,7 +163,7 @@ rulebook task create <task-id>
 
 ### Step 5: Write Proposal
 
-**File**: `/rulebook/tasks/<task-id>/proposal.md`
+**File**: `/.rulebook/tasks/<task-id>/proposal.md`
 
 ```markdown
 # Proposal: Task Name
@@ -188,7 +188,7 @@ Detailed description of what will change:
 
 ### Step 6: Write Tasks Checklist
 
-**File**: `/rulebook/tasks/<task-id>/tasks.md`
+**File**: `/.rulebook/tasks/<task-id>/tasks.md`
 
 ```markdown
 ## 1. Implementation Phase
@@ -206,7 +206,7 @@ Detailed description of what will change:
 
 ### Step 7: Write Spec Delta
 
-**File**: `/rulebook/tasks/<task-id>/specs/<module>/spec.md`
+**File**: `/.rulebook/tasks/<task-id>/specs/<module>/spec.md`
 
 **CRITICAL FORMAT REQUIREMENTS:**
 
@@ -301,7 +301,7 @@ rulebook task archive <task-id> --yes
 1. Validates task format
 2. Checks task completion status
 3. Applies spec deltas to main specifications
-4. Moves task to `/rulebook/tasks/archive/YYYY-MM-DD-<task-id>/`
+4. Moves task to `/.rulebook/tasks/archive/YYYY-MM-DD-<task-id>/`
 5. Updates related specifications
 
 ## Task Format Examples
@@ -1088,12 +1088,12 @@ rulebook task list --archived
 
 **Archived tasks are moved to:**
 ```
-/rulebook/tasks/archive/YYYY-MM-DD-<task-id>/
+/.rulebook/tasks/archive/YYYY-MM-DD-<task-id>/
 ```
 
 **Structure:**
 ```
-/rulebook/tasks/archive/2025-11-13-add-auth/
+/.rulebook/tasks/archive/2025-11-13-add-auth/
 ├── proposal.md
 ├── tasks.md          # All items marked [x]
 ├── design.md
@@ -1338,7 +1338,7 @@ rulebook task create add-user-authentication
 ```
 
 **What it does:**
-- Creates `/rulebook/tasks/<task-id>/` directory
+- Creates `/.rulebook/tasks/<task-id>/` directory
 - Generates `proposal.md` template
 - Generates `tasks.md` template
 - Creates `specs/` directory for spec deltas
@@ -1351,7 +1351,7 @@ rulebook task create add-user-authentication
 ```bash
 $ rulebook task create add-email-notifications
 ✅ Task add-email-notifications created successfully
-Location: rulebook/tasks/add-email-notifications/
+Location: .rulebook/tasks/add-email-notifications/
 
 ⚠️  Remember to:
   1. Check Context7 MCP for OpenSpec format requirements
@@ -1515,7 +1515,7 @@ rulebook task archive add-user-authentication --skip-validation
 1. Validates task format (unless `--skip-validation` is used)
 2. Checks task completion status
 3. Applies spec deltas to main specifications
-4. Moves task to `/rulebook/tasks/archive/YYYY-MM-DD-<task-id>/`
+4. Moves task to `/.rulebook/tasks/archive/YYYY-MM-DD-<task-id>/`
 5. Updates related specifications
 
 **Example:**
@@ -1800,7 +1800,7 @@ rulebook config --feature agent --disable
 If your project previously used OpenSpec:
 
 1. **Automatic Migration**: Run `rulebook update` to automatically migrate OpenSpec tasks to Rulebook format
-2. **Manual Migration**: Tasks in `/openspec/changes/` will be moved to `/rulebook/tasks/`
+2. **Manual Migration**: Tasks in `/openspec/changes/` will be moved to `/.rulebook/tasks/`
 3. **Format Compatibility**: Rulebook uses OpenSpec-compatible format, so existing tasks remain valid
 
 ## Context7 MCP Requirement
@@ -1872,7 +1872,7 @@ If your project previously used OpenSpec:
 
 **Error**: "No tasks found"
 - **Fix**: Create a task first with `rulebook task create <task-id>`
-- **Check**: Verify `/rulebook/tasks/` directory exists
+- **Check**: Verify `/.rulebook/tasks/` directory exists
 
 ### Migration Errors
 
@@ -1887,7 +1887,7 @@ If your project previously used OpenSpec:
 
 ## Examples
 
-See `/rulebook/tasks/` directory for examples of correctly formatted tasks.
+See `/.rulebook/tasks/` directory for examples of correctly formatted tasks.
 
 <!-- RULEBOOK:END -->
 

package/templates/git/CI_CD_PATTERNS.md

@@ -655,7 +655,7 @@ npx @hivehub/rulebook workflows
 
 ## Related Templates
 
-- See `/rulebook/specs/GITHUB_ACTIONS.md` for GitHub Actions specifics
-- See `/rulebook/specs/GITLAB_CI.md` for GitLab CI specifics
-- See `/rulebook/specs/SECRETS_MANAGEMENT.md` for secrets handling
-- See `/rulebook/specs/QUALITY_ENFORCEMENT.md` for quality standards
+- See `/.rulebook/specs/GITHUB_ACTIONS.md` for GitHub Actions specifics
+- See `/.rulebook/specs/GITLAB_CI.md` for GitLab CI specifics
+- See `/.rulebook/specs/SECRETS_MANAGEMENT.md` for secrets handling
+- See `/.rulebook/specs/QUALITY_ENFORCEMENT.md` for quality standards

package/templates/git/GITHUB_ACTIONS.md

@@ -722,7 +722,7 @@ npx @hivehub/rulebook workflows
 
 ## Related Templates
 
-- See `/rulebook/specs/CI_CD_PATTERNS.md` for common CI/CD patterns
-- See `/rulebook/specs/SECRETS_MANAGEMENT.md` for secrets handling
-- See `/rulebook/specs/QUALITY_ENFORCEMENT.md` for quality gates
+- See `/.rulebook/specs/CI_CD_PATTERNS.md` for common CI/CD patterns
+- See `/.rulebook/specs/SECRETS_MANAGEMENT.md` for secrets handling
+- See `/.rulebook/specs/QUALITY_ENFORCEMENT.md` for quality gates
 - See language-specific templates for test/build commands

package/templates/git/GITLAB_CI.md

@@ -724,7 +724,7 @@ npx @hivehub/rulebook workflows
 
 ## Related Templates
 
-- See `/rulebook/specs/GITHUB_ACTIONS.md` for GitHub Actions comparison
-- See `/rulebook/specs/CI_CD_PATTERNS.md` for general CI/CD patterns
-- See `/rulebook/specs/SECRETS_MANAGEMENT.md` for secrets handling
-- See `/rulebook/specs/QUALITY_ENFORCEMENT.md` for quality gates
+- See `/.rulebook/specs/GITHUB_ACTIONS.md` for GitHub Actions comparison
+- See `/.rulebook/specs/CI_CD_PATTERNS.md` for general CI/CD patterns
+- See `/.rulebook/specs/SECRETS_MANAGEMENT.md` for secrets handling
+- See `/.rulebook/specs/QUALITY_ENFORCEMENT.md` for quality gates

package/templates/git/SECRETS_MANAGEMENT.md

@@ -579,7 +579,7 @@ AWS_SECRET_ACCESS_KEY=your-secret-key
 
 ## Related Templates
 
-- See `/rulebook/specs/GITHUB_ACTIONS.md` for GitHub Actions secrets
-- See `/rulebook/specs/GITLAB_CI.md` for GitLab CI secrets
-- See `/rulebook/specs/CI_CD_PATTERNS.md` for deployment patterns
-- See `/rulebook/specs/GIT.md` for .gitignore patterns
+- See `/.rulebook/specs/GITHUB_ACTIONS.md` for GitHub Actions secrets
+- See `/.rulebook/specs/GITLAB_CI.md` for GitLab CI secrets
+- See `/.rulebook/specs/CI_CD_PATTERNS.md` for deployment patterns
+- See `/.rulebook/specs/GIT.md` for .gitignore patterns

package/templates/hooks/COMMIT_MSG.md

@@ -524,7 +524,7 @@ npx @hivehub/rulebook init
 
 ## Related Templates
 
-- See `/rulebook/specs/PRE_COMMIT.md` for quality checks before commit
-- See `/rulebook/specs/PREPARE_COMMIT_MSG.md` for auto-generating commit messages
-- See `/rulebook/specs/GIT.md` for git workflow and commit conventions
-- See `/rulebook/specs/DOCUMENTATION_RULES.md` for changelog generation from commits
+- See `/.rulebook/specs/PRE_COMMIT.md` for quality checks before commit
+- See `/.rulebook/specs/PREPARE_COMMIT_MSG.md` for auto-generating commit messages
+- See `/.rulebook/specs/GIT.md` for git workflow and commit conventions
+- See `/.rulebook/specs/DOCUMENTATION_RULES.md` for changelog generation from commits

package/templates/hooks/POST_CHECKOUT.md

@@ -540,7 +540,7 @@ npx @hivehub/rulebook init
 
 ## Related Templates
 
-- See `/rulebook/specs/PRE_COMMIT.md` for pre-commit quality checks
-- See `/rulebook/specs/PRE_PUSH.md` for pre-push validation
-- See `/rulebook/specs/GIT.md` for git workflow
+- See `/.rulebook/specs/PRE_COMMIT.md` for pre-commit quality checks
+- See `/.rulebook/specs/PRE_PUSH.md` for pre-push validation
+- See `/.rulebook/specs/GIT.md` for git workflow
 - See language-specific templates for dependency management commands

package/templates/hooks/PREPARE_COMMIT_MSG.md

@@ -614,6 +614,6 @@ npx @hivehub/rulebook init
 
 ## Related Templates
 
-- See `/rulebook/specs/COMMIT_MSG.md` for commit message validation
-- See `/rulebook/specs/GIT.md` for git workflow and branch naming
-- See `/rulebook/specs/PRE_COMMIT.md` for pre-commit checks
+- See `/.rulebook/specs/COMMIT_MSG.md` for commit message validation
+- See `/.rulebook/specs/GIT.md` for git workflow and branch naming
+- See `/.rulebook/specs/PRE_COMMIT.md` for pre-commit checks

package/templates/hooks/PRE_COMMIT.md

@@ -407,8 +407,8 @@ Hook configuration in `.rulebook`:
 
 ## Related Templates
 
-- See `/rulebook/specs/PRE_PUSH.md` for build and test checks before push
-- See `/rulebook/specs/COMMIT_MSG.md` for commit message validation
-- See `/rulebook/specs/QUALITY_ENFORCEMENT.md` for quality standards
-- See `/rulebook/specs/GIT.md` for git workflow and commit conventions
+- See `/.rulebook/specs/PRE_PUSH.md` for build and test checks before push
+- See `/.rulebook/specs/COMMIT_MSG.md` for commit message validation
+- See `/.rulebook/specs/QUALITY_ENFORCEMENT.md` for quality standards
+- See `/.rulebook/specs/GIT.md` for git workflow and commit conventions
 - See language-specific templates for language-specific quality commands

package/templates/hooks/PRE_PUSH.md

@@ -594,8 +594,8 @@ Hook configuration in `.rulebook`:
 
 ## Related Templates
 
-- See `/rulebook/specs/PRE_COMMIT.md` for fast quality checks before commit
-- See `/rulebook/specs/QUALITY_ENFORCEMENT.md` for quality standards
-- See `/rulebook/specs/GIT.md` for git workflow and conventions
-- See `/rulebook/specs/GITHUB_ACTIONS.md` for CI/CD integration
+- See `/.rulebook/specs/PRE_COMMIT.md` for fast quality checks before commit
+- See `/.rulebook/specs/QUALITY_ENFORCEMENT.md` for quality standards
+- See `/.rulebook/specs/GIT.md` for git workflow and conventions
+- See `/.rulebook/specs/GITHUB_ACTIONS.md` for CI/CD integration
 - See language-specific templates for test commands and coverage tools

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

@@ -1,13 +1,13 @@
----
-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: []
----
+---
+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
 

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

@@ -1,13 +1,13 @@
----
-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: []
----
+---
+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
 

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

@@ -1,13 +1,13 @@
----
-name: "Auggie"
-description: "Tool: TDD mode and intelligent refactoring"
-version: "1.0.0"
-category: "cli"
-author: "Rulebook"
-tags: ["cli", "cli-tool"]
-dependencies: []
-conflicts: []
----
+---
+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
 

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

@@ -1,13 +1,13 @@
----
-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: []
----
+---
+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
 

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

@@ -1,146 +1,146 @@
----
-name: "Claude Code"
-description: "Tool: Anthropic Claude Code CLI (`npm install -g @anthropic-ai/claude-code`)"
-version: "1.0.0"
-category: "cli"
-author: "Rulebook"
-tags: ["cli", "cli-tool"]
-dependencies: []
-conflicts: []
----
-<!-- CLAUDE_CODE:START -->
-# Claude Code CLI Rules
-
-**Tool**: Anthropic Claude Code CLI (`npm install -g @anthropic-ai/claude-code`)
-
-## Quick Start
-
-```bash
-export ANTHROPIC_API_KEY=your_key
-claude --model claude-sonnet-4-20250514
-```
-
-## Essential Usage
-
-```bash
-# Always read AGENTS.md and CLAUDE.md first
-claude "Read AGENTS.md and CLAUDE.md, then implement [feature] with tests"
-
-# Key flags:
---model claude-sonnet-4-20250514  # Model selection (default: sonnet)
---dangerously-skip-permissions    # Skip permission prompts (use with caution)
---verbose                         # Debug mode
-```
-
-## ⚠️ CRITICAL: File Editing Rules
-
-**MANDATORY**: When editing multiple files, Claude Code MUST edit files **SEQUENTIALLY**, one at a time.
-
-### Why Sequential Editing is Required
-
-Claude Code's Edit tool uses exact string matching for replacements. When multiple files are edited in parallel:
-- The tool may fail to find the exact string in some files
-- Race conditions can cause partial or corrupted edits
-- Error recovery becomes impossible
-
-### Correct File Editing Pattern
-
-```
-✅ CORRECT (Sequential):
-1. Edit file A → Wait for confirmation
-2. Edit file B → Wait for confirmation
-3. Edit file C → Wait for confirmation
-
-❌ WRONG (Parallel):
-1. Edit files A, B, C simultaneously → Failures likely
-```
-
-### Implementation Rules
-
-1. **NEVER call multiple Edit tools in parallel** for different files
-2. **ALWAYS wait for each edit to complete** before starting the next
-3. **Verify each edit succeeded** before proceeding
-4. **If an edit fails**, retry that specific edit before moving on
-
-## ⚠️ CRITICAL: Test Implementation Rules
-
-**MANDATORY**: When implementing tests, Claude Code MUST write **complete, production-quality tests**.
-
-### Forbidden Test Patterns
-
-```typescript
-// ❌ NEVER do this - placeholder tests
-it('should work', () => {
-  expect(true).toBe(true);
-});
-
-// ❌ NEVER do this - skipped tests
-it.skip('should handle edge case', () => {});
-
-// ❌ NEVER do this - incomplete assertions
-it('should return data', () => {
-  const result = getData();
-  expect(result).toBeDefined(); // Too weak!
-});
-
-// ❌ NEVER do this - "simplify" by removing test cases
-// Original had 10 test cases, don't reduce to 3
-```
-
-### Required Test Patterns
-
-```typescript
-// ✅ CORRECT - complete test with proper assertions
-it('should return user data with correct structure', () => {
-  const result = getUserById(1);
-  expect(result).toEqual({
-    id: 1,
-    name: 'John Doe',
-    email: 'john@example.com',
-    createdAt: expect.any(Date),
-  });
-});
-
-// ✅ CORRECT - test edge cases and error paths
-it('should throw NotFoundError when user does not exist', () => {
-  expect(() => getUserById(999)).toThrow(NotFoundError);
-});
-
-// ✅ CORRECT - test all branches
-describe('validateEmail', () => {
-  it('should return true for valid email', () => {...});
-  it('should return false for missing @', () => {...});
-  it('should return false for missing domain', () => {...});
-  it('should return false for empty string', () => {...});
-});
-```
-
-### Test Implementation Rules
-
-1. **NEVER simplify tests** - Implement the full, complete test as originally designed
-2. **NEVER skip test cases** - Every test case in the spec must be implemented
-3. **NEVER use placeholder assertions** - Each assertion must verify actual behavior
-4. **ALWAYS test error paths** - Exceptions, edge cases, and failure modes
-5. **ALWAYS maintain coverage** - Tests must achieve the project's coverage threshold
-
-## Workflow
-
-1. **Always read AGENTS.md and CLAUDE.md first** for project standards
-2. **Plan file changes before editing** - List all files that need modification
-3. **Edit files sequentially** - One file at a time, verify each edit
-4. **Write complete tests** - No placeholders, no simplifications
-5. **Run quality checks**: `npm run lint && npm test`
-6. **Verify coverage threshold** is met before committing
-
-## Quality Gates
-
-Before completing any task:
-- [ ] All files edited successfully (sequential editing)
-- [ ] All tests implemented completely (no placeholders)
-- [ ] Linting passes with zero warnings
-- [ ] All tests pass (100% pass rate)
-- [ ] Coverage threshold met (check AGENTS.md for threshold)
-
-**Critical**: Reference AGENTS.md and CLAUDE.md in prompts for consistent code generation.
-
-<!-- CLAUDE_CODE:END -->
+---
+name: "Claude Code"
+description: "Tool: Anthropic Claude Code CLI (`npm install -g @anthropic-ai/claude-code`)"
+version: "1.0.0"
+category: "cli"
+author: "Rulebook"
+tags: ["cli", "cli-tool"]
+dependencies: []
+conflicts: []
+---
+<!-- CLAUDE_CODE:START -->
+# Claude Code CLI Rules
+
+**Tool**: Anthropic Claude Code CLI (`npm install -g @anthropic-ai/claude-code`)
+
+## Quick Start
+
+```bash
+export ANTHROPIC_API_KEY=your_key
+claude --model claude-sonnet-4-20250514
+```
+
+## Essential Usage
+
+```bash
+# Always read AGENTS.md and CLAUDE.md first
+claude "Read AGENTS.md and CLAUDE.md, then implement [feature] with tests"
+
+# Key flags:
+--model claude-sonnet-4-20250514  # Model selection (default: sonnet)
+--dangerously-skip-permissions    # Skip permission prompts (use with caution)
+--verbose                         # Debug mode
+```
+
+## ⚠️ CRITICAL: File Editing Rules
+
+**MANDATORY**: When editing multiple files, Claude Code MUST edit files **SEQUENTIALLY**, one at a time.
+
+### Why Sequential Editing is Required
+
+Claude Code's Edit tool uses exact string matching for replacements. When multiple files are edited in parallel:
+- The tool may fail to find the exact string in some files
+- Race conditions can cause partial or corrupted edits
+- Error recovery becomes impossible
+
+### Correct File Editing Pattern
+
+```
+✅ CORRECT (Sequential):
+1. Edit file A → Wait for confirmation
+2. Edit file B → Wait for confirmation
+3. Edit file C → Wait for confirmation
+
+❌ WRONG (Parallel):
+1. Edit files A, B, C simultaneously → Failures likely
+```
+
+### Implementation Rules
+
+1. **NEVER call multiple Edit tools in parallel** for different files
+2. **ALWAYS wait for each edit to complete** before starting the next
+3. **Verify each edit succeeded** before proceeding
+4. **If an edit fails**, retry that specific edit before moving on
+
+## ⚠️ CRITICAL: Test Implementation Rules
+
+**MANDATORY**: When implementing tests, Claude Code MUST write **complete, production-quality tests**.
+
+### Forbidden Test Patterns
+
+```typescript
+// ❌ NEVER do this - placeholder tests
+it('should work', () => {
+  expect(true).toBe(true);
+});
+
+// ❌ NEVER do this - skipped tests
+it.skip('should handle edge case', () => {});
+
+// ❌ NEVER do this - incomplete assertions
+it('should return data', () => {
+  const result = getData();
+  expect(result).toBeDefined(); // Too weak!
+});
+
+// ❌ NEVER do this - "simplify" by removing test cases
+// Original had 10 test cases, don't reduce to 3
+```
+
+### Required Test Patterns
+
+```typescript
+// ✅ CORRECT - complete test with proper assertions
+it('should return user data with correct structure', () => {
+  const result = getUserById(1);
+  expect(result).toEqual({
+    id: 1,
+    name: 'John Doe',
+    email: 'john@example.com',
+    createdAt: expect.any(Date),
+  });
+});
+
+// ✅ CORRECT - test edge cases and error paths
+it('should throw NotFoundError when user does not exist', () => {
+  expect(() => getUserById(999)).toThrow(NotFoundError);
+});
+
+// ✅ CORRECT - test all branches
+describe('validateEmail', () => {
+  it('should return true for valid email', () => {...});
+  it('should return false for missing @', () => {...});
+  it('should return false for missing domain', () => {...});
+  it('should return false for empty string', () => {...});
+});
+```
+
+### Test Implementation Rules
+
+1. **NEVER simplify tests** - Implement the full, complete test as originally designed
+2. **NEVER skip test cases** - Every test case in the spec must be implemented
+3. **NEVER use placeholder assertions** - Each assertion must verify actual behavior
+4. **ALWAYS test error paths** - Exceptions, edge cases, and failure modes
+5. **ALWAYS maintain coverage** - Tests must achieve the project's coverage threshold
+
+## Workflow
+
+1. **Always read AGENTS.md and CLAUDE.md first** for project standards
+2. **Plan file changes before editing** - List all files that need modification
+3. **Edit files sequentially** - One file at a time, verify each edit
+4. **Write complete tests** - No placeholders, no simplifications
+5. **Run quality checks**: `npm run lint && npm test`
+6. **Verify coverage threshold** is met before committing
+
+## Quality Gates
+
+Before completing any task:
+- [ ] All files edited successfully (sequential editing)
+- [ ] All tests implemented completely (no placeholders)
+- [ ] Linting passes with zero warnings
+- [ ] All tests pass (100% pass rate)
+- [ ] Coverage threshold met (check AGENTS.md for threshold)
+
+**Critical**: Reference AGENTS.md and CLAUDE.md in prompts for consistent code generation.
+
+<!-- CLAUDE_CODE:END -->

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

@@ -1,13 +1,13 @@
----
-name: "Cline"
-description: "Tool: VS Code extension with autonomous mode"
-version: "1.0.0"
-category: "cli"
-author: "Rulebook"
-tags: ["cli", "cli-tool"]
-dependencies: []
-conflicts: []
----
+---
+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