@hivehub/rulebook 5.8.1 → 6.0.0

package/templates/skills/modules/github-mcp/SKILL.md

@@ -1,74 +1,74 @@
----
-name: "GitHub MCP"
-description: "Monitor CI/CD workflows after every `git push` using GitHub MCP."
-version: "1.0.0"
-category: "modules"
-author: "Rulebook"
-tags: ["modules", "mcp"]
-dependencies: []
-conflicts: []
----
-<!-- GITHUB_MCP:START -->
-# GitHub MCP Server Integration
-
-**CRITICAL**: Monitor CI/CD workflows after every `git push` using GitHub MCP.
-
-## Workflow After Push
-
-```
-1. Push changes
-2. Wait 10 seconds  
-3. Check workflow status via GitHub MCP
-4. If workflows running → check again in next interaction
-5. If workflows failed → fetch logs, analyze, fix
-6. If workflows passed → confirm to user
-```
-
-## Error Recovery
-
-**When CI/CD fails:**
-
-```
-1. Fetch error information (workflow, job, step, logs)
-2. Analyze against AGENTS.md standards
-3. Propose fix
-4. Implement fix with full quality checks
-5. Commit and provide push command
-6. Monitor workflows again
-```
-
-## Best Practices
-
-✅ **DO:**
-- Always check workflows after push
-- Fetch complete error logs on failures
-- Fix issues before next feature
-- Verify fixes locally before re-pushing
-- Report status to user
-
-❌ **DON'T:**
-- Ignore workflow failures
-- Push again without fixing
-- Skip error analysis
-- Proceed if workflows failing
-- Create tags if CI/CD failed
-
-## Configuration
-
-```json
-{
-  "mcpServers": {
-    "github": {
-      "command": "npx",
-      "args": ["-y", "@modelcontextprotocol/server-github"],
-      "env": {
-        "GITHUB_PERSONAL_ACCESS_TOKEN": "your_token_here"
-      }
-    }
-  }
-}
-```
-
-**Token permissions:** Repository (read), Actions (read), Workflows (read/write)
-
-<!-- GITHUB_MCP:END -->
+---
+name: "GitHub MCP"
+description: "Monitor CI/CD workflows after every `git push` using GitHub MCP."
+version: "1.0.0"
+category: "modules"
+author: "Rulebook"
+tags: ["modules", "mcp"]
+dependencies: []
+conflicts: []
+---
+<!-- GITHUB_MCP:START -->
+# GitHub MCP Server Integration
+
+**CRITICAL**: Monitor CI/CD workflows after every `git push` using GitHub MCP.
+
+## Workflow After Push
+
+```
+1. Push changes
+2. Wait 10 seconds  
+3. Check workflow status via GitHub MCP
+4. If workflows running → check again in next interaction
+5. If workflows failed → fetch logs, analyze, fix
+6. If workflows passed → confirm to user
+```
+
+## Error Recovery
+
+**When CI/CD fails:**
+
+```
+1. Fetch error information (workflow, job, step, logs)
+2. Analyze against AGENTS.md standards
+3. Propose fix
+4. Implement fix with full quality checks
+5. Commit and provide push command
+6. Monitor workflows again
+```
+
+## Best Practices
+
+✅ **DO:**
+- Always check workflows after push
+- Fetch complete error logs on failures
+- Fix issues before next feature
+- Verify fixes locally before re-pushing
+- Report status to user
+
+❌ **DON'T:**
+- Ignore workflow failures
+- Push again without fixing
+- Skip error analysis
+- Proceed if workflows failing
+- Create tags if CI/CD failed
+
+## Configuration
+
+```json
+{
+  "mcpServers": {
+    "github": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-github"],
+      "env": {
+        "GITHUB_PERSONAL_ACCESS_TOKEN": "your_token_here"
+      }
+    }
+  }
+}
+```
+
+**Token permissions:** Repository (read), Actions (read), Workflows (read/write)
+
+<!-- GITHUB_MCP:END -->

package/templates/skills/modules/playwright/SKILL.md

@@ -1,100 +1,100 @@
----
-name: "Playwright"
-description: "Use MCP Playwright for automated browser testing and web automation."
-version: "1.0.0"
-category: "modules"
-author: "Rulebook"
-tags: ["modules", "mcp"]
-dependencies: []
-conflicts: []
----
-<!-- PLAYWRIGHT:START -->
-# Playwright MCP Instructions
-
-**CRITICAL**: Use MCP Playwright for automated browser testing and web automation.
-
-## Core Operations
-
-### Navigation & Screenshots
-```typescript
-await playwright.navigate({ url: "https://example.com" });
-await playwright.takeScreenshot({ fullPage: true, filename: "page.png" });
-```
-
-### Interaction
-```typescript
-// Click
-await playwright.click({ element: "Submit Button", ref: "button[type='submit']" });
-
-// Type
-await playwright.type({ element: "Search", ref: "#search", text: "query" });
-
-// Fill form
-await playwright.fillForm({
-  fields: [
-    { name: "Email", type: "textbox", ref: "#email", value: "user@example.com" },
-    { name: "Password", type: "textbox", ref: "#password", value: "secret" }
-  ]
-});
-```
-
-### DOM & Monitoring
-```typescript
-// Get accessibility tree
-const snapshot = await playwright.snapshot();
-
-// Console errors
-const errors = await playwright.getConsoleMessages({ onlyErrors: true });
-
-// Network requests
-const requests = await playwright.getNetworkRequests();
-```
-
-## Common Patterns
-
-### Login Flow
-```typescript
-1. navigate to login page
-2. fillForm with credentials
-3. click submit button
-4. waitFor dashboard text
-5. verify success via snapshot
-```
-
-### Error Detection
-```typescript
-const errors = await playwright.getConsoleMessages({ onlyErrors: true });
-if (errors.length > 0) {
-  await playwright.takeScreenshot({ filename: "error-state.png" });
-}
-```
-
-## Best Practices
-
-✅ **DO:**
-- Wait for specific conditions (not time delays)
-- Use descriptive element names
-- Handle dialogs (`handleDialog`)
-- Check console errors after actions
-- Take screenshots at critical points
-
-❌ **DON'T:**
-- Use hard-coded delays
-- Use generic element selectors
-- Ignore console errors
-- Use relative file paths (uploads)
-
-## Configuration
-
-```json
-{
-  "mcpServers": {
-    "playwright": {
-      "command": "npx",
-      "args": ["-y", "@modelcontextprotocol/server-playwright"]
-    }
-  }
-}
-```
-
-<!-- PLAYWRIGHT:END -->
+---
+name: "Playwright"
+description: "Use MCP Playwright for automated browser testing and web automation."
+version: "1.0.0"
+category: "modules"
+author: "Rulebook"
+tags: ["modules", "mcp"]
+dependencies: []
+conflicts: []
+---
+<!-- PLAYWRIGHT:START -->
+# Playwright MCP Instructions
+
+**CRITICAL**: Use MCP Playwright for automated browser testing and web automation.
+
+## Core Operations
+
+### Navigation & Screenshots
+```typescript
+await playwright.navigate({ url: "https://example.com" });
+await playwright.takeScreenshot({ fullPage: true, filename: "page.png" });
+```
+
+### Interaction
+```typescript
+// Click
+await playwright.click({ element: "Submit Button", ref: "button[type='submit']" });
+
+// Type
+await playwright.type({ element: "Search", ref: "#search", text: "query" });
+
+// Fill form
+await playwright.fillForm({
+  fields: [
+    { name: "Email", type: "textbox", ref: "#email", value: "user@example.com" },
+    { name: "Password", type: "textbox", ref: "#password", value: "secret" }
+  ]
+});
+```
+
+### DOM & Monitoring
+```typescript
+// Get accessibility tree
+const snapshot = await playwright.snapshot();
+
+// Console errors
+const errors = await playwright.getConsoleMessages({ onlyErrors: true });
+
+// Network requests
+const requests = await playwright.getNetworkRequests();
+```
+
+## Common Patterns
+
+### Login Flow
+```typescript
+1. navigate to login page
+2. fillForm with credentials
+3. click submit button
+4. waitFor dashboard text
+5. verify success via snapshot
+```
+
+### Error Detection
+```typescript
+const errors = await playwright.getConsoleMessages({ onlyErrors: true });
+if (errors.length > 0) {
+  await playwright.takeScreenshot({ filename: "error-state.png" });
+}
+```
+
+## Best Practices
+
+✅ **DO:**
+- Wait for specific conditions (not time delays)
+- Use descriptive element names
+- Handle dialogs (`handleDialog`)
+- Check console errors after actions
+- Take screenshots at critical points
+
+❌ **DON'T:**
+- Use hard-coded delays
+- Use generic element selectors
+- Ignore console errors
+- Use relative file paths (uploads)
+
+## Configuration
+
+```json
+{
+  "mcpServers": {
+    "playwright": {
+      "command": "npx",
+      "args": ["-y", "@modelcontextprotocol/server-playwright"]
+    }
+  }
+}
+```
+
+<!-- PLAYWRIGHT:END -->

package/templates/skills/modules/rulebook-mcp/SKILL.md

@@ -1,166 +1,166 @@
----
-name: "Rulebook MCP"
-description: "Use MCP Rulebook server to manage tasks programmatically instead of executing terminal commands."
-version: "1.0.0"
-category: "modules"
-author: "Rulebook"
-tags: ["modules", "mcp"]
-dependencies: []
-conflicts: []
----
-<!-- RULEBOOK_MCP:START -->
-# Rulebook MCP Server Instructions
-
-**CRITICAL**: Use MCP Rulebook server to manage tasks programmatically instead of executing terminal commands.
-
-## Core Functions
-
-### 1. rulebook_task_create
-Create a new Rulebook task with OpenSpec-compatible format:
-```
-rulebook_task_create({
-  taskId: "add-feature-name",
-  proposal: {
-    why: "Users need this feature...",
-    whatChanges: "Add feature with X, Y, Z",
-    impact: {
-      affectedSpecs: ["specs/module/spec.md"],
-      affectedCode: ["src/module/"],
-      breakingChange: false,
-      userBenefit: "Better user experience"
-    }
-  }
-})
-```
-
-### 2. rulebook_task_list
-List all tasks with optional filters:
-```
-rulebook_task_list({
-  status: "in-progress",
-  includeArchived: false
-})
-```
-
-### 3. rulebook_task_show
-Show detailed task information:
-```
-rulebook_task_show({
-  taskId: "add-feature-name"
-})
-```
-
-### 4. rulebook_task_update
-Update task status or progress:
-```
-rulebook_task_update({
-  taskId: "add-feature-name",
-  status: "in-progress",
-  progress: 50
-})
-```
-
-### 5. rulebook_task_validate
-Validate task format against OpenSpec requirements:
-```
-rulebook_task_validate({
-  taskId: "add-feature-name"
-})
-```
-
-### 6. rulebook_task_archive
-Archive completed task and apply spec deltas:
-```
-rulebook_task_archive({
-  taskId: "add-feature-name",
-  skipValidation: false
-})
-```
-
-## Workflow
-
-**When creating tasks:**
-```
-1. Use rulebook_task_create instead of terminal command
-2. Provide complete proposal with why/whatChanges/impact
-3. Verify task creation with rulebook_task_show
-```
-
-**When managing task progress:**
-```
-1. Use rulebook_task_list to see all tasks
-2. Update status with rulebook_task_update as work progresses
-3. Validate format with rulebook_task_validate before archiving
-4. Archive completed tasks with rulebook_task_archive
-```
-
-**Before archiving:**
-```
-1. Always run rulebook_task_validate first
-2. Fix any validation errors
-3. Ensure all tasks in tasks.md are completed
-4. Archive with skipValidation: false
-```
-
-## Best Practices
-
-✅ **DO:**
-- Use MCP functions instead of terminal commands for task management
-- Always validate tasks before archiving
-- Update task status as work progresses
-- Provide complete proposal information when creating tasks
-- Check task details with rulebook_task_show before operations
-
-❌ **DON'T:**
-- Execute `rulebook task create` commands in terminal
-- Archive tasks without validation
-- Skip proposal content when creating tasks
-- Use terminal commands when MCP functions are available
-
-## Configuration
-
-The Rulebook MCP server is configured in `.cursor/mcp.json`:
-
-```json
-{
-  "mcpServers": {
-    "rulebook": {
-      "command": "node",
-      "args": ["dist/mcp/rulebook-server.js"],
-      "env": {}
-    }
-  }
-}
-```
-
-For production (npx):
-```json
-{
-  "mcpServers": {
-    "rulebook": {
-      "command": "npx",
-      "args": ["-y", "@hivehub/rulebook@latest", "mcp-server"],
-      "env": {}
-    }
-  }
-}
-```
-
-## Integration
-
-The MCP server integrates seamlessly with:
-- Cursor IDE (via `.cursor/mcp.json`)
-- Claude Desktop (via config file)
-- Other MCP-compatible clients
-
-All task operations are available through MCP functions, eliminating the need for terminal command execution.
-
-## Documentation
-
-For complete API documentation, see:
-- `/docs/MCP_SERVER.md` - Full API reference
-- `/docs/guides/MCP_SERVER_SETUP.md` - Setup guide
-- `/README.md` - General project information
-
-<!-- RULEBOOK_MCP:END -->
-
+---
+name: "Rulebook MCP"
+description: "Use MCP Rulebook server to manage tasks programmatically instead of executing terminal commands."
+version: "1.0.0"
+category: "modules"
+author: "Rulebook"
+tags: ["modules", "mcp"]
+dependencies: []
+conflicts: []
+---
+<!-- RULEBOOK_MCP:START -->
+# Rulebook MCP Server Instructions
+
+**CRITICAL**: Use MCP Rulebook server to manage tasks programmatically instead of executing terminal commands.
+
+## Core Functions
+
+### 1. rulebook_task_create
+Create a new Rulebook task with OpenSpec-compatible format:
+```
+rulebook_task_create({
+  taskId: "add-feature-name",
+  proposal: {
+    why: "Users need this feature...",
+    whatChanges: "Add feature with X, Y, Z",
+    impact: {
+      affectedSpecs: ["specs/module/spec.md"],
+      affectedCode: ["src/module/"],
+      breakingChange: false,
+      userBenefit: "Better user experience"
+    }
+  }
+})
+```
+
+### 2. rulebook_task_list
+List all tasks with optional filters:
+```
+rulebook_task_list({
+  status: "in-progress",
+  includeArchived: false
+})
+```
+
+### 3. rulebook_task_show
+Show detailed task information:
+```
+rulebook_task_show({
+  taskId: "add-feature-name"
+})
+```
+
+### 4. rulebook_task_update
+Update task status or progress:
+```
+rulebook_task_update({
+  taskId: "add-feature-name",
+  status: "in-progress",
+  progress: 50
+})
+```
+
+### 5. rulebook_task_validate
+Validate task format against OpenSpec requirements:
+```
+rulebook_task_validate({
+  taskId: "add-feature-name"
+})
+```
+
+### 6. rulebook_task_archive
+Archive completed task and apply spec deltas:
+```
+rulebook_task_archive({
+  taskId: "add-feature-name",
+  skipValidation: false
+})
+```
+
+## Workflow
+
+**When creating tasks:**
+```
+1. Use rulebook_task_create instead of terminal command
+2. Provide complete proposal with why/whatChanges/impact
+3. Verify task creation with rulebook_task_show
+```
+
+**When managing task progress:**
+```
+1. Use rulebook_task_list to see all tasks
+2. Update status with rulebook_task_update as work progresses
+3. Validate format with rulebook_task_validate before archiving
+4. Archive completed tasks with rulebook_task_archive
+```
+
+**Before archiving:**
+```
+1. Always run rulebook_task_validate first
+2. Fix any validation errors
+3. Ensure all tasks in tasks.md are completed
+4. Archive with skipValidation: false
+```
+
+## Best Practices
+
+✅ **DO:**
+- Use MCP functions instead of terminal commands for task management
+- Always validate tasks before archiving
+- Update task status as work progresses
+- Provide complete proposal information when creating tasks
+- Check task details with rulebook_task_show before operations
+
+❌ **DON'T:**
+- Execute `rulebook task create` commands in terminal
+- Archive tasks without validation
+- Skip proposal content when creating tasks
+- Use terminal commands when MCP functions are available
+
+## Configuration
+
+The Rulebook MCP server is configured in `.cursor/mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "rulebook": {
+      "command": "node",
+      "args": ["dist/mcp/rulebook-server.js"],
+      "env": {}
+    }
+  }
+}
+```
+
+For production (npx):
+```json
+{
+  "mcpServers": {
+    "rulebook": {
+      "command": "npx",
+      "args": ["-y", "@hivehub/rulebook@latest", "mcp-server"],
+      "env": {}
+    }
+  }
+}
+```
+
+## Integration
+
+The MCP server integrates seamlessly with:
+- Cursor IDE (via `.cursor/mcp.json`)
+- Claude Desktop (via config file)
+- Other MCP-compatible clients
+
+All task operations are available through MCP functions, eliminating the need for terminal command execution.
+
+## Documentation
+
+For complete API documentation, see:
+- `/docs/MCP_SERVER.md` - Full API reference
+- `/docs/guides/MCP_SERVER_SETUP.md` - Setup guide
+- `/README.md` - General project information
+
+<!-- RULEBOOK_MCP:END -->
+