@hivehub/rulebook 5.1.2 → 5.1.3

package/templates/skills/dev/architect/SKILL.md

@@ -1,17 +1,17 @@
----
-name: architect
-description: Architecture review, design decisions, and ADR writing
-model: opus
-context: fork
-agent: architect
----
-Analyze architecture for: $ARGUMENTS
-
-If no arguments, do a general architecture review of the project.
-
-Steps:
-1. Map the current system architecture (modules, dependencies, data flow)
-2. Identify architectural concerns (coupling, scalability, complexity)
-3. Evaluate alternative approaches with trade-offs
-4. Write an Architecture Decision Record (ADR) if a decision is needed
-5. Present recommendations with clear rationale
+---
+name: architect
+description: Architecture review, design decisions, and ADR writing
+model: opus
+context: fork
+agent: architect
+---
+Analyze architecture for: $ARGUMENTS
+
+If no arguments, do a general architecture review of the project.
+
+Steps:
+1. Map the current system architecture (modules, dependencies, data flow)
+2. Identify architectural concerns (coupling, scalability, complexity)
+3. Evaluate alternative approaches with trade-offs
+4. Write an Architecture Decision Record (ADR) if a decision is needed
+5. Present recommendations with clear rationale

package/templates/skills/dev/build-fix/SKILL.md

@@ -1,17 +1,17 @@
----
-name: build-fix
-description: Diagnose and fix build failures or CI issues
-model: sonnet
-context: fork
-agent: build-engineer
----
-Diagnose and fix the current build failure.
-
-If $ARGUMENTS is provided, focus on that specific build error or CI job.
-
-Steps:
-1. Run the build command and capture the error output
-2. Read the error message and trace to the source file
-3. Identify the root cause (missing dep, type error, config issue)
-4. Apply the minimal fix
-5. Re-run the build to verify the fix works
+---
+name: build-fix
+description: Diagnose and fix build failures or CI issues
+model: sonnet
+context: fork
+agent: build-engineer
+---
+Diagnose and fix the current build failure.
+
+If $ARGUMENTS is provided, focus on that specific build error or CI job.
+
+Steps:
+1. Run the build command and capture the error output
+2. Read the error message and trace to the source file
+3. Identify the root cause (missing dep, type error, config issue)
+4. Apply the minimal fix
+5. Re-run the build to verify the fix works

package/templates/skills/dev/db-design/SKILL.md

@@ -1,15 +1,15 @@
----
-name: db-design
-description: Database schema design, migrations, and query optimization
-model: sonnet
-context: fork
-agent: database-architect
----
-Design or review the database for: $ARGUMENTS
-
-Steps:
-1. Understand the data model requirements
-2. Design or review the schema (tables, relationships, indexes)
-3. Plan migration strategy if schema changes are needed
-4. Review existing queries for optimization opportunities
-5. Document the schema decisions and trade-offs
+---
+name: db-design
+description: Database schema design, migrations, and query optimization
+model: sonnet
+context: fork
+agent: database-architect
+---
+Design or review the database for: $ARGUMENTS
+
+Steps:
+1. Understand the data model requirements
+2. Design or review the schema (tables, relationships, indexes)
+3. Plan migration strategy if schema changes are needed
+4. Review existing queries for optimization opportunities
+5. Document the schema decisions and trade-offs

package/templates/skills/dev/debug/SKILL.md

@@ -1,16 +1,16 @@
----
-name: debug
-description: Systematic debugging workflow for bugs and test failures
-model: sonnet
-context: fork
-agent: researcher
----
-Debug the following issue: $ARGUMENTS
-
-Steps:
-1. Reproduce the issue by reading the error message or running the failing test
-2. Read the relevant source code and trace the execution path
-3. Form a hypothesis about the root cause
-4. Search for similar patterns in the codebase that work correctly
-5. Identify the exact root cause with file and line reference
-6. Propose a minimal fix with explanation
+---
+name: debug
+description: Systematic debugging workflow for bugs and test failures
+model: sonnet
+context: fork
+agent: researcher
+---
+Debug the following issue: $ARGUMENTS
+
+Steps:
+1. Reproduce the issue by reading the error message or running the failing test
+2. Read the relevant source code and trace the execution path
+3. Form a hypothesis about the root cause
+4. Search for similar patterns in the codebase that work correctly
+5. Identify the exact root cause with file and line reference
+6. Propose a minimal fix with explanation

package/templates/skills/dev/deploy/SKILL.md

@@ -1,17 +1,17 @@
----
-name: deploy
-description: Prepare deployment artifacts and verify CI/CD readiness
-model: sonnet
-context: fork
-agent: devops-engineer
----
-Prepare the project for deployment.
-
-If $ARGUMENTS is provided, focus on that specific deployment target or environment.
-
-Steps:
-1. Verify the build succeeds with no errors
-2. Check CI/CD pipeline configuration is valid
-3. Validate environment variables and secrets are documented
-4. Review Dockerfile or deployment configs if present
-5. Generate a deployment checklist with any missing items
+---
+name: deploy
+description: Prepare deployment artifacts and verify CI/CD readiness
+model: sonnet
+context: fork
+agent: devops-engineer
+---
+Prepare the project for deployment.
+
+If $ARGUMENTS is provided, focus on that specific deployment target or environment.
+
+Steps:
+1. Verify the build succeeds with no errors
+2. Check CI/CD pipeline configuration is valid
+3. Validate environment variables and secrets are documented
+4. Review Dockerfile or deployment configs if present
+5. Generate a deployment checklist with any missing items

package/templates/skills/dev/docs/SKILL.md

@@ -1,17 +1,17 @@
----
-name: docs
-description: Generate or update project documentation based on recent changes
-model: haiku
-context: fork
-agent: docs-writer
----
-Analyze recent code changes and update project documentation accordingly.
-
-If $ARGUMENTS is provided, focus documentation on that specific topic or file.
-
-Steps:
-1. Run `git diff HEAD~5 --name-only` to find recently changed files
-2. Read the changed files to understand what was modified
-3. Check existing docs for sections that need updating
-4. Update or create documentation to reflect the changes
-5. Ensure code examples are accurate and up-to-date
+---
+name: docs
+description: Generate or update project documentation based on recent changes
+model: haiku
+context: fork
+agent: docs-writer
+---
+Analyze recent code changes and update project documentation accordingly.
+
+If $ARGUMENTS is provided, focus documentation on that specific topic or file.
+
+Steps:
+1. Run `git diff HEAD~5 --name-only` to find recently changed files
+2. Read the changed files to understand what was modified
+3. Check existing docs for sections that need updating
+4. Update or create documentation to reflect the changes
+5. Ensure code examples are accurate and up-to-date

package/templates/skills/dev/migrate/SKILL.md

@@ -1,15 +1,15 @@
----
-name: migrate
-description: Plan and execute migrations (database, API, framework)
-model: sonnet
-context: fork
-agent: migration-engineer
----
-Plan and execute migration for: $ARGUMENTS
-
-Steps:
-1. Assess the scope and impact of the migration
-2. Create a step-by-step migration plan with rollback strategy
-3. Write migration scripts or code changes
-4. Test the migration including rollback path
-5. Document breaking changes and migration guide
+---
+name: migrate
+description: Plan and execute migrations (database, API, framework)
+model: sonnet
+context: fork
+agent: migration-engineer
+---
+Plan and execute migration for: $ARGUMENTS
+
+Steps:
+1. Assess the scope and impact of the migration
+2. Create a step-by-step migration plan with rollback strategy
+3. Write migration scripts or code changes
+4. Test the migration including rollback path
+5. Document breaking changes and migration guide

package/templates/skills/dev/perf/SKILL.md

@@ -1,17 +1,17 @@
----
-name: perf
-description: Performance analysis, profiling, and optimization
-model: sonnet
-context: fork
-agent: performance-engineer
----
-Analyze performance for: $ARGUMENTS
-
-If no arguments, do a general performance review of the project.
-
-Steps:
-1. Identify the performance bottleneck or area of concern
-2. Profile the code (check for N+1 queries, unnecessary allocations, blocking I/O)
-3. Benchmark the current performance baseline
-4. Propose optimizations with expected impact
-5. Implement the optimization and measure improvement
+---
+name: perf
+description: Performance analysis, profiling, and optimization
+model: sonnet
+context: fork
+agent: performance-engineer
+---
+Analyze performance for: $ARGUMENTS
+
+If no arguments, do a general performance review of the project.
+
+Steps:
+1. Identify the performance bottleneck or area of concern
+2. Profile the code (check for N+1 queries, unnecessary allocations, blocking I/O)
+3. Benchmark the current performance baseline
+4. Propose optimizations with expected impact
+5. Implement the optimization and measure improvement

package/templates/skills/dev/refactor/SKILL.md

@@ -1,17 +1,17 @@
----
-name: refactor
-description: Identify code smells and execute safe refactorings
-model: sonnet
-context: fork
-agent: refactoring-agent
----
-Analyze and refactor the specified code.
-
-Target: $ARGUMENTS (file path, module, or area to refactor)
-
-Steps:
-1. Read the target code and understand its purpose
-2. Identify code smells (long functions, duplication, high complexity)
-3. Propose specific refactorings with rationale
-4. Implement refactorings one at a time, verifying tests pass after each
-5. Report what was changed and why
+---
+name: refactor
+description: Identify code smells and execute safe refactorings
+model: sonnet
+context: fork
+agent: refactoring-agent
+---
+Analyze and refactor the specified code.
+
+Target: $ARGUMENTS (file path, module, or area to refactor)
+
+Steps:
+1. Read the target code and understand its purpose
+2. Identify code smells (long functions, duplication, high complexity)
+3. Propose specific refactorings with rationale
+4. Implement refactorings one at a time, verifying tests pass after each
+5. Report what was changed and why

package/templates/skills/dev/research/SKILL.md

@@ -1,14 +1,14 @@
----
-name: research
-description: Explore codebase and gather context about a topic or area
-model: haiku
-context: fork
-agent: researcher
----
-Research the following topic in this codebase: $ARGUMENTS
-
-Steps:
-1. Search for relevant files, types, and patterns related to the topic
-2. Read key files to understand the architecture and conventions
-3. Identify dependencies and relationships between components
-4. Report findings with file paths, key types, and patterns discovered
+---
+name: research
+description: Explore codebase and gather context about a topic or area
+model: haiku
+context: fork
+agent: researcher
+---
+Research the following topic in this codebase: $ARGUMENTS
+
+Steps:
+1. Search for relevant files, types, and patterns related to the topic
+2. Read key files to understand the architecture and conventions
+3. Identify dependencies and relationships between components
+4. Report findings with file paths, key types, and patterns discovered

package/templates/skills/dev/review/SKILL.md

@@ -1,18 +1,18 @@
----
-name: review
-description: Deep code review of recent changes or specified files
-model: sonnet
-context: fork
-agent: code-reviewer
----
-Perform a thorough code review.
-
-If $ARGUMENTS is provided, review those specific files or the given PR/commit.
-Otherwise, review uncommitted changes via `git diff`.
-
-Steps:
-1. Get the diff (git diff or specified files)
-2. Review for correctness, bugs, and edge cases
-3. Check adherence to project patterns and conventions
-4. Identify security concerns
-5. Report findings as: blocker / suggestion / nit with file:line references
+---
+name: review
+description: Deep code review of recent changes or specified files
+model: sonnet
+context: fork
+agent: code-reviewer
+---
+Perform a thorough code review.
+
+If $ARGUMENTS is provided, review those specific files or the given PR/commit.
+Otherwise, review uncommitted changes via `git diff`.
+
+Steps:
+1. Get the diff (git diff or specified files)
+2. Review for correctness, bugs, and edge cases
+3. Check adherence to project patterns and conventions
+4. Identify security concerns
+5. Report findings as: blocker / suggestion / nit with file:line references

package/templates/skills/dev/security-audit/SKILL.md

@@ -1,17 +1,17 @@
----
-name: security-audit
-description: Run a security audit on the project (dependencies, secrets, OWASP)
-model: haiku
-context: fork
-agent: security-reviewer
----
-Perform a comprehensive security audit of this project.
-
-If $ARGUMENTS is provided, focus the audit on that specific area.
-
-Steps:
-1. Run dependency audit (npm audit, pip-audit, cargo audit, etc.)
-2. Scan for hardcoded secrets, API keys, and credentials
-3. Review authentication and authorization patterns
-4. Check for OWASP Top 10 vulnerabilities in the codebase
-5. Report findings categorized by severity (critical/high/medium/low)
+---
+name: security-audit
+description: Run a security audit on the project (dependencies, secrets, OWASP)
+model: haiku
+context: fork
+agent: security-reviewer
+---
+Perform a comprehensive security audit of this project.
+
+If $ARGUMENTS is provided, focus the audit on that specific area.
+
+Steps:
+1. Run dependency audit (npm audit, pip-audit, cargo audit, etc.)
+2. Scan for hardcoded secrets, API keys, and credentials
+3. Review authentication and authorization patterns
+4. Check for OWASP Top 10 vulnerabilities in the codebase
+5. Report findings categorized by severity (critical/high/medium/low)

package/templates/skills/frameworks/angular/SKILL.md

@@ -1,46 +1,46 @@
----
-name: "Angular"
-description: "Angular projects must meet these standards before delivery."
-version: "1.0.0"
-category: "frameworks"
-author: "Rulebook"
-tags: ["frameworks", "framework"]
-dependencies: []
-conflicts: []
----
-<!-- ANGULAR:START -->
-# Angular Framework Rules
-
-**CRITICAL**: Angular projects must meet these standards before delivery.
-
-## Quality Commands
-- Lint: `npm run lint`
-- Unit tests: `npm run test -- --watch=false --code-coverage`
-- e2e tests: `npm run e2e`
-- Build: `npm run build -- --configuration production`
-
-## Project Structure
-- Colocate features inside `src/app/<feature>/`
-- Keep shared modules in `src/app/shared`
-- Avoid `providedIn: 'root'` unless service truly global
-- Leverage `OnPush` change detection for performance-critical components
-
-## Implementation Guidelines
-- Define interfaces for component inputs/outputs
-- Use `HttpClient` interceptors for auth/logging
-- Isolate environment variables in `src/environments/`
-- Prefer Reactive Forms and RxJS operators over manual subscriptions
-
-## Pre-Commit Sequence
-```bash
-npm run lint
-npm run test -- --watch=false
-npm run build -- --configuration production
-```
-
-## Documentation
-- Update `/docs/angular-architecture.md` with new modules and routes
-- Record shared component APIs in Storybook or `/docs/ui-components.md`
-- Version major route changes in `/docs/roadmap.md`
-
-<!-- ANGULAR:END -->
+---
+name: "Angular"
+description: "Angular projects must meet these standards before delivery."
+version: "1.0.0"
+category: "frameworks"
+author: "Rulebook"
+tags: ["frameworks", "framework"]
+dependencies: []
+conflicts: []
+---
+<!-- ANGULAR:START -->
+# Angular Framework Rules
+
+**CRITICAL**: Angular projects must meet these standards before delivery.
+
+## Quality Commands
+- Lint: `npm run lint`
+- Unit tests: `npm run test -- --watch=false --code-coverage`
+- e2e tests: `npm run e2e`
+- Build: `npm run build -- --configuration production`
+
+## Project Structure
+- Colocate features inside `src/app/<feature>/`
+- Keep shared modules in `src/app/shared`
+- Avoid `providedIn: 'root'` unless service truly global
+- Leverage `OnPush` change detection for performance-critical components
+
+## Implementation Guidelines
+- Define interfaces for component inputs/outputs
+- Use `HttpClient` interceptors for auth/logging
+- Isolate environment variables in `src/environments/`
+- Prefer Reactive Forms and RxJS operators over manual subscriptions
+
+## Pre-Commit Sequence
+```bash
+npm run lint
+npm run test -- --watch=false
+npm run build -- --configuration production
+```
+
+## Documentation
+- Update `/docs/angular-architecture.md` with new modules and routes
+- Record shared component APIs in Storybook or `/docs/ui-components.md`
+- Version major route changes in `/docs/roadmap.md`
+
+<!-- ANGULAR:END -->