@hivehub/rulebook 5.3.3 → 5.4.1

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

@@ -1,27 +1,27 @@
----
-name: handoff
-description: Save session state to .rulebook/handoff/_pending.md for cross-session continuity
-model: sonnet
-context: fork
-agent: researcher
----
-Save a session handoff to `.rulebook/handoff/_pending.md`.
-
-The handoff file MUST contain:
-
-1. **Active task**: current task ID + phase + which checklist items are done
-2. **Decisions made this session**: architectural choices, trade-offs, rejected alternatives
-3. **Files touched**: list of files modified with one-line reason each
-4. **Next steps**: concrete, actionable items (not vague "continue working")
-5. **Exact resume command**: what to tell the next session to do first
-6. **Open questions / blockers**: anything unresolved that needs the user's input
-
-Write the file to `.rulebook/handoff/_pending.md` using the Write tool.
-
-After writing successfully, display this message prominently:
-
->>> TYPE /clear NOW — your context will be auto-restored in the next session <<<
-
-If the file `.rulebook/handoff/.urgent` exists, skip any confirmations and write immediately.
-
-The SessionStart hook (`resume-from-handoff.sh`) will automatically inject the handoff content into the next session and archive the file.
+---
+name: handoff
+description: Save session state to .rulebook/handoff/_pending.md for cross-session continuity
+model: sonnet
+context: fork
+agent: researcher
+---
+Save a session handoff to `.rulebook/handoff/_pending.md`.
+
+The handoff file MUST contain:
+
+1. **Active task**: current task ID + phase + which checklist items are done
+2. **Decisions made this session**: architectural choices, trade-offs, rejected alternatives
+3. **Files touched**: list of files modified with one-line reason each
+4. **Next steps**: concrete, actionable items (not vague "continue working")
+5. **Exact resume command**: what to tell the next session to do first
+6. **Open questions / blockers**: anything unresolved that needs the user's input
+
+Write the file to `.rulebook/handoff/_pending.md` using the Write tool.
+
+After writing successfully, display this message prominently:
+
+>>> TYPE /clear NOW — your context will be auto-restored in the next session <<<
+
+If the file `.rulebook/handoff/.urgent` exists, skip any confirmations and write immediately.
+
+The SessionStart hook (`resume-from-handoff.sh`) will automatically inject the handoff content into the next session and archive the file.

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 -->

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

@@ -1,93 +1,93 @@
----
-name: "Django"
-description: "Language: Python"
-version: "1.0.0"
-category: "frameworks"
-author: "Rulebook"
-tags: ["frameworks", "framework"]
-dependencies: []
-conflicts: []
----
-<!-- DJANGO:START -->
-# Django Framework Rules
-
-**Language**: Python  
-**Version**: Django 4.2+ (LTS) or 5.0+
-
-## Setup & Configuration
-
-```python
-# settings.py
-SECRET_KEY = env('SECRET_KEY')  # Never hardcode
-DEBUG = env.bool('DEBUG', default=False)
-ALLOWED_HOSTS = env.list('ALLOWED_HOSTS')
-
-INSTALLED_APPS = [
-    # Django apps
-    'django.contrib.admin',
-    'django.contrib.auth',
-    # Third-party
-    'rest_framework',
-    'corsheaders',
-    # Local apps
-    'apps.users',
-]
-
-DATABASES = {
-    'default': env.db('DATABASE_URL')  # Use django-environ
-}
-```
-
-## Quality Gates
-
-```bash
-# Code quality
-black .                          # Format
-ruff check .                     # Lint
-mypy .                          # Type check
-
-# Tests
-python manage.py test            # Run tests
-pytest --cov=apps --cov-report=html  # With coverage
-
-# Security
-python manage.py check --deploy  # Production checks
-bandit -r apps/                  # Security scan
-```
-
-## Best Practices
-
-✅ **DO:**
-- Use Class-Based Views (CBVs) or Django REST Framework ViewSets
-- Implement custom User model from start
-- Use Django ORM properly (select_related, prefetch_related)
-- Enable CSRF protection
-- Use environment variables for secrets
-- Write tests for views, models, and forms
-
-❌ **DON'T:**
-- Use `DEBUG=True` in production
-- Store secrets in settings.py
-- Use raw SQL without parameterization
-- Skip migrations
-- Ignore security middleware
-
-## Project Structure
-
-```
-project/
-├── manage.py
-├── requirements.txt
-├── apps/
-│   ├── users/
-│   ├── api/
-│   └── core/
-├── config/
-│   ├── settings.py
-│   ├── urls.py
-│   └── wsgi.py
-└── tests/
-```
-
-<!-- DJANGO:END -->
-
+---
+name: "Django"
+description: "Language: Python"
+version: "1.0.0"
+category: "frameworks"
+author: "Rulebook"
+tags: ["frameworks", "framework"]
+dependencies: []
+conflicts: []
+---
+<!-- DJANGO:START -->
+# Django Framework Rules
+
+**Language**: Python  
+**Version**: Django 4.2+ (LTS) or 5.0+
+
+## Setup & Configuration
+
+```python
+# settings.py
+SECRET_KEY = env('SECRET_KEY')  # Never hardcode
+DEBUG = env.bool('DEBUG', default=False)
+ALLOWED_HOSTS = env.list('ALLOWED_HOSTS')
+
+INSTALLED_APPS = [
+    # Django apps
+    'django.contrib.admin',
+    'django.contrib.auth',
+    # Third-party
+    'rest_framework',
+    'corsheaders',
+    # Local apps
+    'apps.users',
+]
+
+DATABASES = {
+    'default': env.db('DATABASE_URL')  # Use django-environ
+}
+```
+
+## Quality Gates
+
+```bash
+# Code quality
+black .                          # Format
+ruff check .                     # Lint
+mypy .                          # Type check
+
+# Tests
+python manage.py test            # Run tests
+pytest --cov=apps --cov-report=html  # With coverage
+
+# Security
+python manage.py check --deploy  # Production checks
+bandit -r apps/                  # Security scan
+```
+
+## Best Practices
+
+✅ **DO:**
+- Use Class-Based Views (CBVs) or Django REST Framework ViewSets
+- Implement custom User model from start
+- Use Django ORM properly (select_related, prefetch_related)
+- Enable CSRF protection
+- Use environment variables for secrets
+- Write tests for views, models, and forms
+
+❌ **DON'T:**
+- Use `DEBUG=True` in production
+- Store secrets in settings.py
+- Use raw SQL without parameterization
+- Skip migrations
+- Ignore security middleware
+
+## Project Structure
+
+```
+project/
+├── manage.py
+├── requirements.txt
+├── apps/
+│   ├── users/
+│   ├── api/
+│   └── core/
+├── config/
+│   ├── settings.py
+│   ├── urls.py
+│   └── wsgi.py
+└── tests/
+```
+
+<!-- DJANGO:END -->
+