cmp-standards 2.0.1 → 2.6.0

package/templates/commands/experts.md

@@ -1,138 +1,138 @@
-## /experts - AI Code Review System
-
-> **Purpose**: Multi-expert code review with consensus voting
-> **Usage**: `/experts [files or task description]`
-
----
-
-## Overview
-
-The `/experts` command launches a panel of AI experts to review your code:
-
-1. **Security Expert** - SQL injection, auth, input validation
-2. **Performance Expert** - Waterfalls, N+1, lazy loading
-3. **Architecture Expert** - Types, modules, SOLID principles
-4. **UX Expert** - Accessibility, mobile-first, design tokens
-5. **Database Expert** - Schema, migrations, queries
-6. **Memory Expert** - Pattern detection, auto-improvement
-
----
-
-## Usage Examples
-
-```bash
-# Review specific file
-/experts src/components/UserForm.tsx
-
-# Review directory
-/experts src/server/api/routers/
-
-# Review with context
-/experts "Review the new authentication flow"
-```
-
----
-
-## How It Works
-
-```
-1. ANALYZE CODE
-   • Detect criticality (CRITICAL vs NORMAL)
-   • Select relevant experts
-
-2. PARALLEL REVIEW (30-45 seconds)
-   • Each expert reviews independently
-   • Generates vote and findings
-
-3. CONSENSUS VOTING
-   • CRITICAL: Unanimity required (0 REJECT)
-   • NORMAL: Majority required (3/5 APPROVE)
-
-4. RESULT
-   • APPROVED → Verification runs
-   • REJECTED → Detailed feedback provided
-```
-
----
-
-## Criticality Detection
-
-Code is **CRITICAL** if it involves:
-- Authentication/Authorization
-- Financial operations
-- Database schema changes
-- External payment integrations
-
-Critical code requires **unanimous approval** (no REJECT votes).
-
----
-
-## Expert Responsibilities
-
-| Expert | Checks | Rejects On |
-|--------|--------|------------|
-| Security | SQL injection, auth, validation | Any security hole |
-| Performance | N+1, waterfalls, bundle size | Critical perf issues |
-| Architecture | Types, modules, SOLID | Type violations |
-| UX | A11y, mobile, tokens | Missing accessibility |
-| Database | Schema, migrations | Data loss risk |
-| Memory | Patterns | Never (ABSTAIN) |
-
----
-
-## Output Example
-
-```
-## Expert Review
-Files: 1
-Criticality: NORMAL
-Experts: Security, Performance, Architecture, UX (4)
-
-[30 seconds - parallel review]
-
-✅ APPROVED (4/4)
-  Security: ✓ APPROVE
-  Performance: ✓ APPROVE
-  Architecture: ✓ APPROVE
-  UX: ✓ APPROVE
-
-Running verification...
-  ✓ typecheck passed
-  ✓ lint passed
-
-All checks passed! ✅
-```
-
----
-
-## When to Use
-
-✅ **Use /experts for:**
-- Critical changes (auth, payments, schema)
-- Before submitting PRs
-- Large refactors
-- Learning (get feedback)
-
-❌ **Don't use for:**
-- WIP code
-- Trivial changes (typos)
-- Generated code
-
----
-
-## Advanced Options
-
-```bash
-# Review specific experts only
-/experts src/file.ts --only security,architecture
-
-# Verbose output (show reasoning)
-/experts src/file.ts --verbose
-
-# Dry run (no auto-improvements)
-/experts src/file.ts --dry-run
-```
-
----
-
-*Part of cmp-memory-system - MetaNautical Group*
+## /experts - AI Code Review System
+
+> **Purpose**: Multi-expert code review with consensus voting
+> **Usage**: `/experts [files or task description]`
+
+---
+
+## Overview
+
+The `/experts` command launches a panel of AI experts to review your code:
+
+1. **Security Expert** - SQL injection, auth, input validation
+2. **Performance Expert** - Waterfalls, N+1, lazy loading
+3. **Architecture Expert** - Types, modules, SOLID principles
+4. **UX Expert** - Accessibility, mobile-first, design tokens
+5. **Database Expert** - Schema, migrations, queries
+6. **Memory Expert** - Pattern detection, auto-improvement
+
+---
+
+## Usage Examples
+
+```bash
+# Review specific file
+/experts src/components/UserForm.tsx
+
+# Review directory
+/experts src/server/api/routers/
+
+# Review with context
+/experts "Review the new authentication flow"
+```
+
+---
+
+## How It Works
+
+```
+1. ANALYZE CODE
+   • Detect criticality (CRITICAL vs NORMAL)
+   • Select relevant experts
+
+2. PARALLEL REVIEW (30-45 seconds)
+   • Each expert reviews independently
+   • Generates vote and findings
+
+3. CONSENSUS VOTING
+   • CRITICAL: Unanimity required (0 REJECT)
+   • NORMAL: Majority required (3/5 APPROVE)
+
+4. RESULT
+   • APPROVED → Verification runs
+   • REJECTED → Detailed feedback provided
+```
+
+---
+
+## Criticality Detection
+
+Code is **CRITICAL** if it involves:
+- Authentication/Authorization
+- Financial operations
+- Database schema changes
+- External payment integrations
+
+Critical code requires **unanimous approval** (no REJECT votes).
+
+---
+
+## Expert Responsibilities
+
+| Expert | Checks | Rejects On |
+|--------|--------|------------|
+| Security | SQL injection, auth, validation | Any security hole |
+| Performance | N+1, waterfalls, bundle size | Critical perf issues |
+| Architecture | Types, modules, SOLID | Type violations |
+| UX | A11y, mobile, tokens | Missing accessibility |
+| Database | Schema, migrations | Data loss risk |
+| Memory | Patterns | Never (ABSTAIN) |
+
+---
+
+## Output Example
+
+```
+## Expert Review
+Files: 1
+Criticality: NORMAL
+Experts: Security, Performance, Architecture, UX (4)
+
+[30 seconds - parallel review]
+
+✅ APPROVED (4/4)
+  Security: ✓ APPROVE
+  Performance: ✓ APPROVE
+  Architecture: ✓ APPROVE
+  UX: ✓ APPROVE
+
+Running verification...
+  ✓ typecheck passed
+  ✓ lint passed
+
+All checks passed! ✅
+```
+
+---
+
+## When to Use
+
+✅ **Use /experts for:**
+- Critical changes (auth, payments, schema)
+- Before submitting PRs
+- Large refactors
+- Learning (get feedback)
+
+❌ **Don't use for:**
+- WIP code
+- Trivial changes (typos)
+- Generated code
+
+---
+
+## Advanced Options
+
+```bash
+# Review specific experts only
+/experts src/file.ts --only security,architecture
+
+# Verbose output (show reasoning)
+/experts src/file.ts --verbose
+
+# Dry run (no auto-improvements)
+/experts src/file.ts --dry-run
+```
+
+---
+
+*Part of cmp-memory-system - MetaNautical Group*

package/templates/hooks/README.md

@@ -1,158 +1,158 @@
-# Claude Code Hooks Configuration
-
-This directory contains hook templates for Claude Code integration.
-
-## Available Hooks
-
-| Hook | When | Purpose |
-|:---|:---|:---|
-| `SessionStart` | Session begins | Load context, memories, work plan |
-| `PreToolUse` | Before tool runs | Guards, validation, knowledge injection |
-| `PostToolUse` | After tool runs | Change tracking, checkpoints |
-| `NotificationReceived` | On notifications | Custom notification handling |
-| `PromptSubmit` | Before prompt | Pre-processing user input |
-| `SubagentStop` | Agent completes | Post-agent processing |
-
-## Configuration
-
-Add to your `.claude/settings.local.json`:
-
-```json
-{
-  "hooks": {
-    "SessionStart": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "npx cmp-memory session-context"
-          }
-        ]
-      }
-    ],
-    "PreToolUse": [
-      {
-        "matcher": "Edit|Write",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "npx cmp-memory pre-tool-guard $EVENT"
-          }
-        ]
-      }
-    ],
-    "PostToolUse": [
-      {
-        "matcher": "Edit|Write",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "npx cmp-memory post-tool-record $EVENT"
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-## Environment Variables
-
-Required for full functionality:
-
-```bash
-# Database connection (for memory persistence)
-DATABASE_URL="mysql://user:pass@host:port/database"
-
-# Embedding (for semantic search - optional)
-OPENAI_API_KEY="sk-..."
-# or
-GEMINI_API_KEY="..."
-```
-
-## Guard Rules
-
-Define guards in `project.config.json`:
-
-```json
-{
-  "guards": {
-    "enabled": true,
-    "rules": [
-      {
-        "id": "no-modify-auth",
-        "type": "block",
-        "filePattern": "**/auth/**",
-        "message": "Auth files require explicit approval",
-        "excludeFiles": ["**/*.test.ts"]
-      },
-      {
-        "id": "no-raw-sql",
-        "type": "warn",
-        "filePattern": "**/*.ts",
-        "contentTrigger": "\\$\\{[^}]+\\}.*(?:SELECT|INSERT|UPDATE|DELETE)",
-        "message": "Potential SQL injection - use parameterized queries"
-      }
-    ]
-  }
-}
-```
-
-## Custom Hooks
-
-Create custom hook scripts in `.claude/hooks/`:
-
-```bash
-#!/bin/bash
-# .claude/hooks/my-custom-hook.sh
-
-# Access event data
-EVENT_DATA="$1"
-
-# Parse with jq if needed
-TOOL_NAME=$(echo "$EVENT_DATA" | jq -r '.tool_name')
-
-# Your logic here
-echo "Tool called: $TOOL_NAME"
-```
-
-Register in settings:
-
-```json
-{
-  "hooks": {
-    "PreToolUse": [
-      {
-        "matcher": "*",
-        "hooks": [
-          {
-            "type": "command",
-            "command": ".claude/hooks/my-custom-hook.sh $EVENT"
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-## Troubleshooting
-
-### Hook not running
-- Check that hook command is executable
-- Verify matcher pattern matches the tool name
-- Check `.claude/settings.local.json` syntax
-
-### Guards not blocking
-- Ensure `guards.enabled: true` in `project.config.json`
-- Verify file patterns match (use glob syntax)
-- Check that rule `type` is "block" not "warn"
-
-### Memory not persisting
-- Verify `DATABASE_URL` is set
-- Check database connection with `npx cmp-memory status`
-
----
-
-For more information, see the [cmp-memory-system documentation](https://github.com/carlosmartinpavon/carlosmartinpavon).
+# Claude Code Hooks Configuration
+
+This directory contains hook templates for Claude Code integration.
+
+## Available Hooks
+
+| Hook | When | Purpose |
+|:---|:---|:---|
+| `SessionStart` | Session begins | Load context, memories, work plan |
+| `PreToolUse` | Before tool runs | Guards, validation, knowledge injection |
+| `PostToolUse` | After tool runs | Change tracking, checkpoints |
+| `NotificationReceived` | On notifications | Custom notification handling |
+| `PromptSubmit` | Before prompt | Pre-processing user input |
+| `SubagentStop` | Agent completes | Post-agent processing |
+
+## Configuration
+
+Add to your `.claude/settings.local.json`:
+
+```json
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "*",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "npx cmp-memory session-context"
+          }
+        ]
+      }
+    ],
+    "PreToolUse": [
+      {
+        "matcher": "Edit|Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "npx cmp-memory pre-tool-guard $EVENT"
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "npx cmp-memory post-tool-record $EVENT"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+## Environment Variables
+
+Required for full functionality:
+
+```bash
+# Database connection (for memory persistence)
+DATABASE_URL="mysql://user:pass@host:port/database"
+
+# Embedding (for semantic search - optional)
+OPENAI_API_KEY="sk-..."
+# or
+GEMINI_API_KEY="..."
+```
+
+## Guard Rules
+
+Define guards in `project.config.json`:
+
+```json
+{
+  "guards": {
+    "enabled": true,
+    "rules": [
+      {
+        "id": "no-modify-auth",
+        "type": "block",
+        "filePattern": "**/auth/**",
+        "message": "Auth files require explicit approval",
+        "excludeFiles": ["**/*.test.ts"]
+      },
+      {
+        "id": "no-raw-sql",
+        "type": "warn",
+        "filePattern": "**/*.ts",
+        "contentTrigger": "\\$\\{[^}]+\\}.*(?:SELECT|INSERT|UPDATE|DELETE)",
+        "message": "Potential SQL injection - use parameterized queries"
+      }
+    ]
+  }
+}
+```
+
+## Custom Hooks
+
+Create custom hook scripts in `.claude/hooks/`:
+
+```bash
+#!/bin/bash
+# .claude/hooks/my-custom-hook.sh
+
+# Access event data
+EVENT_DATA="$1"
+
+# Parse with jq if needed
+TOOL_NAME=$(echo "$EVENT_DATA" | jq -r '.tool_name')
+
+# Your logic here
+echo "Tool called: $TOOL_NAME"
+```
+
+Register in settings:
+
+```json
+{
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": "*",
+        "hooks": [
+          {
+            "type": "command",
+            "command": ".claude/hooks/my-custom-hook.sh $EVENT"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+## Troubleshooting
+
+### Hook not running
+- Check that hook command is executable
+- Verify matcher pattern matches the tool name
+- Check `.claude/settings.local.json` syntax
+
+### Guards not blocking
+- Ensure `guards.enabled: true` in `project.config.json`
+- Verify file patterns match (use glob syntax)
+- Check that rule `type` is "block" not "warn"
+
+### Memory not persisting
+- Verify `DATABASE_URL` is set
+- Check database connection with `npx cmp-memory status`
+
+---
+
+For more information, see the [cmp-memory-system documentation](https://github.com/carlosmartinpavon/carlosmartinpavon).