aw-ecc 1.4.21

package/skills/using-aw-skills/hooks/session-start.sh

@@ -0,0 +1,188 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+LOCAL_ROOT=""
+SEARCH_ROOT="$SCRIPT_DIR"
+while [[ "$SEARCH_ROOT" != "/" ]]; do
+  if [[ -f "$SEARCH_ROOT/skills/using-aw-skills/SKILL.md" ]]; then
+    LOCAL_ROOT="$SEARCH_ROOT"
+    break
+  fi
+  SEARCH_ROOT="$(dirname "$SEARCH_ROOT")"
+done
+
+AW_REGISTRY_ROOT=""
+SEARCH_ROOT="$SCRIPT_DIR"
+while [[ "$SEARCH_ROOT" != "/" ]]; do
+  if [[ -d "$SEARCH_ROOT/.aw_registry" ]]; then
+    AW_REGISTRY_ROOT="$SEARCH_ROOT/.aw_registry"
+    break
+  fi
+  if [[ "$(basename "$SEARCH_ROOT")" == ".aw_registry" ]]; then
+    AW_REGISTRY_ROOT="$SEARCH_ROOT"
+    break
+  fi
+  SEARCH_ROOT="$(dirname "$SEARCH_ROOT")"
+done
+
+if [[ -z "$AW_REGISTRY_ROOT" ]]; then
+  for CANDIDATE_ROOT in "$HOME/.aw_registry" "$HOME/.aw/.aw_registry"; do
+    if [[ -d "$CANDIDATE_ROOT" ]]; then
+      AW_REGISTRY_ROOT="$CANDIDATE_ROOT"
+      break
+    fi
+  done
+fi
+
+if [[ -z "$LOCAL_ROOT" && -z "$AW_REGISTRY_ROOT" ]]; then
+  echo '{"hookSpecificOutput": {"hookEventName": "SessionStart", "additionalContext": "WARNING: .aw_registry not found. AW skills unavailable."}}'
+  exit 0
+fi
+
+read_frontmatter_name() {
+  local file_path="$1"
+  [[ -f "$file_path" ]] || return 0
+
+  awk '
+    NR == 1 && $0 == "---" { in_frontmatter = 1; next }
+    in_frontmatter && $0 == "---" { exit }
+    in_frontmatter && /^name:[[:space:]]*/ {
+      sub(/^name:[[:space:]]*/, "", $0)
+      print
+      exit
+    }
+  ' "$file_path"
+}
+
+extract_skill_excerpt() {
+  local file_path="$1"
+  [[ -f "$file_path" ]] || return 0
+
+  awk '
+    NR == 1 && $0 == "---" { in_frontmatter = 1; next }
+    in_frontmatter && $0 == "---" { in_frontmatter = 0; next }
+    in_frontmatter { next }
+    /^[[:space:]]*$/ { next }
+    {
+      print
+      count++
+      if (count >= 4) exit
+    }
+  ' "$file_path"
+}
+
+collect_registry_skills() {
+  local registry_root="$1"
+  local count=0
+  [[ -d "$registry_root/platform" ]] || return 0
+
+  while IFS= read -r skill_file; do
+    local skill_name=""
+    if [[ "$skill_file" == */using-aw-skills/SKILL.md ]]; then
+      continue
+    fi
+    skill_name="$(read_frontmatter_name "$skill_file")"
+    if [[ -z "$skill_name" ]]; then
+      skill_name="$(basename "$(dirname "$skill_file")")"
+    fi
+    printf -- "- %s\n" "$skill_name"
+    count=$((count + 1))
+    if [[ "$count" -ge 6 ]]; then
+      break
+    fi
+  done < <(find "$registry_root/platform" -path '*/skills/*/SKILL.md' | sort)
+}
+
+collect_registry_commands() {
+  local registry_root="$1"
+  local count=0
+  [[ -d "$registry_root/commands" ]] || return 0
+
+  while IFS= read -r command_file; do
+    local command_slug=""
+    local command_name=""
+    command_slug="$(basename "$command_file" .md)"
+    command_name="$(read_frontmatter_name "$command_file")"
+    if [[ -n "$command_name" ]]; then
+      printf -- "- %s: %s\n" "$command_slug" "$command_name"
+    else
+      printf -- "- %s\n" "$command_slug"
+    fi
+    count=$((count + 1))
+    if [[ "$count" -ge 6 ]]; then
+      break
+    fi
+  done < <(find "$registry_root/commands" -mindepth 1 -maxdepth 1 -name '*.md' | sort)
+}
+
+ROUTER_SKILL_PATH=""
+if [[ -n "$LOCAL_ROOT" && -f "$LOCAL_ROOT/skills/using-aw-skills/SKILL.md" ]]; then
+  ROUTER_SKILL_PATH="$LOCAL_ROOT/skills/using-aw-skills/SKILL.md"
+elif [[ -n "$AW_REGISTRY_ROOT" && -f "$AW_REGISTRY_ROOT/platform/core/skills/using-aw-skills/SKILL.md" ]]; then
+  ROUTER_SKILL_PATH="$AW_REGISTRY_ROOT/platform/core/skills/using-aw-skills/SKILL.md"
+fi
+
+ROUTER_EXCERPT="$(extract_skill_excerpt "$ROUTER_SKILL_PATH")"
+REGISTRY_SKILLS=""
+REGISTRY_COMMANDS=""
+if [[ -n "$AW_REGISTRY_ROOT" ]]; then
+  REGISTRY_SKILLS="$(collect_registry_skills "$AW_REGISTRY_ROOT")"
+  REGISTRY_COMMANDS="$(collect_registry_commands "$AW_REGISTRY_ROOT")"
+fi
+
+CONTEXT="# AW Session Context
+
+## First Response Rule
+Before any substantive response, select the smallest correct AW skill stack from the repo-local router.
+Honor an explicit AW command and its mapped stage skill first.
+Otherwise choose the needed process skill, primary stage skill, and matching route by intent, then load deeper domain skills.
+Do not start with generic implementation, review, or deploy advice before skill selection.
+
+## Primary Routes
+- /aw:plan -> ideas, specs, task breakdown, architecture direction
+- /aw:build -> approved implementation work
+- /aw:investigate -> bugs, alerts, or unclear runtime failures
+- /aw:test -> QA proof and regression evidence
+- /aw:review -> findings, risk review, and readiness
+- /aw:deploy -> rollout or release execution
+- /aw:ship -> release closeout and final handoff
+
+## Compatibility Routes
+- /aw:execute -> compatibility route; resolve to /aw:build
+- /aw:verify -> compatibility route; resolve to /aw:test or /aw:review
+
+## Router Source
+Use skills/using-aw-skills/SKILL.md as the repo-local router.
+Load domain, platform, and craft skills only after the smallest correct AW route is selected."
+
+if [[ -n "$ROUTER_EXCERPT" ]]; then
+  CONTEXT="${CONTEXT}
+
+## Router Excerpt
+${ROUTER_EXCERPT}"
+fi
+
+if [[ -n "$REGISTRY_SKILLS" ]]; then
+  CONTEXT="${CONTEXT}
+
+## Registry Skills In Scope
+${REGISTRY_SKILLS}"
+fi
+
+if [[ -n "$REGISTRY_COMMANDS" ]]; then
+  CONTEXT="${CONTEXT}
+
+## Registry Commands In Scope
+${REGISTRY_COMMANDS}"
+fi
+
+# --- Output in Claude Code hookSpecificOutput format ---
+# Escape for JSON: newlines, quotes, backslashes
+JSON_CONTEXT=$(printf '%s' "$CONTEXT" | python3 -c '
+import sys, json
+content = sys.stdin.read()
+print(json.dumps(content))
+' 2>/dev/null || printf '%s' "$CONTEXT" | sed 's/\\/\\\\/g; s/"/\\"/g; s/\t/\\t/g' | awk '{printf "%s\\n", $0}')
+
+echo "{\"hookSpecificOutput\": {\"hookEventName\": \"SessionStart\", \"additionalContext\": ${JSON_CONTEXT}}}"

package/skills/using-platform-skills/SKILL.md

@@ -0,0 +1,163 @@
+---
+name: using-platform-skills
+description: Select the smallest correct GHL platform skill stack after the AW stage is known. Use when the task touches backend services, frontend MFAs, data systems, infra, review, test, or product-specific platform context.
+---
+
+# Using Platform Skills
+
+## Overview
+
+This is the second-hop router for GHL-specific work.
+Use it after `using-aw-skills` has already selected the primary AW stage.
+
+Its job is to:
+
+- identify the touched GHL domain
+- pick the smallest correct platform family
+- choose the first supporting platform skills for the selected stage
+- avoid loading every platform playbook by default
+
+## When to Use
+
+- the primary AW stage is already known
+- the task touches a real GHL backend, worker, frontend, data, infra, test, review, or product surface
+- platform-specific conventions materially change how the stage should be done
+
+Do not use:
+
+- before the primary AW stage is selected
+- for generic non-GHL work
+- when no platform family materially changes the implementation, test, review, or deploy path
+
+## Skill Discovery
+
+After the AW stage is selected, choose the platform family:
+
+```text
+Primary AW stage selected
+    │
+    ├── Backend service or worker? ───────────────→ platform-services:*
+    ├── Frontend MFA or design-system work? ─────→ platform-frontend:* + platform-design:*
+    ├── Data store, analytics, search, cache,
+    │   or data migration work? ──────────────────────→ platform-data:*
+    ├── Infra or deploy path work? ──────────────→ platform-infra:*
+    ├── Test system or QA governance work? ──────→ platform-sdet:*
+    ├── Formal review or readiness work? ────────→ platform-review:*
+    └── Product-context ambiguity? ──────────────→ platform-product:*
+```
+
+Then choose the smallest supporting skills for the current stage.
+
+## Workflow
+
+1. Confirm the AW stage first.
+   Do not pick platform skills until the primary route is clear.
+2. Identify the touched surface.
+   Backend, frontend, data, infra, review, test, or product context.
+3. Choose the first platform family.
+   Start from the family that most directly changes the current stage behavior.
+4. Add only the first supporting platform skills.
+   Prefer the smallest stack that changes implementation quality, test evidence, review depth, or release safety.
+   Do not duplicate planning-process skills already owned by `aw-plan`, `aw-spec`, `aw-tasks`, or Addy-style planning helpers.
+5. Add craft skills only if they sharpen the same stage.
+   Do not let craft skills replace platform families or vice versa.
+
+## Stage-to-Platform Matrix
+
+### Backend services and workers
+
+| AW stage | First platform skills to load |
+|---|---|
+| `aw-plan` | `platform-services:development` |
+| `aw-build` | `platform-services:development` |
+| `aw-investigate` | `platform-infra:grafana` |
+| `aw-test` | `platform-sdet:quality-gates` |
+| `aw-review` | `platform-review:code-review-pr`, `platform-sdet:quality-gates` |
+| `aw-deploy` | `platform-infra:staging-deploy`, `platform-infra:deployment-strategies`, `platform-infra:production-readiness` |
+| `aw-ship` | `platform-review:code-review-pr`, `platform-infra:staging-deploy`, `platform-infra:production-readiness` |
+
+### Frontend MFAs and design-system work
+
+| AW stage | First platform skills to load |
+|---|---|
+| `aw-plan` | `platform-design:system`, `platform-frontend:vue-development` |
+| `aw-build` | `platform-frontend:vue-development`, `highrise-ui-governance`, `quality-gate-coder` |
+| `aw-investigate` | `platform-infra:grafana` when runtime signals matter; otherwise use the smallest relevant frontend family |
+| `aw-test` | `platform-frontend:a11y-review`, `platform-sdet:quality-gates` |
+| `aw-review` | `platform-review:code-review-pr`, `platform-design:review`, `platform-frontend:a11y-review`, `platform-sdet:quality-gates` |
+| `aw-deploy` | `deploy-versioned-mfa`, `platform-infra:staging-deploy`, `platform-infra:production-readiness` |
+| `aw-ship` | `deploy-versioned-mfa`, `platform-infra:staging-deploy`, `platform-infra:production-readiness` |
+
+### Data, migration, and storage work
+
+`platform-data:*` is the family for the data team surface.
+Use it for:
+
+- transactional databases
+- document stores
+- analytical databases and warehouses
+- search indexes
+- realtime data stores
+- cache and key-value systems
+- migration and cross-database movement
+
+Current concrete data families include:
+
+- `platform-data:cloudsql-clickhouse` for CloudSQL and ClickHouse
+- `platform-data:mongodb-patterns`
+- `platform-data:firestore-patterns`
+- `platform-data:redis-patterns`
+- `platform-data:elasticsearch-patterns`
+- `platform-data:migration-patterns`
+
+Keep infra ownership separate:
+
+- provisioning clusters, secrets, Helm, Terraform, Jenkins, or deploy topology -> `platform-infra:*`
+- modeling schemas, indexes, migrations, sync workers, queries, or search mappings -> `platform-data:*`
+
+| AW stage | First platform skills to load |
+|---|---|
+| `aw-plan` | `platform-data:migration-patterns` or the narrow storage family |
+| `aw-build` | `platform-data:migration-patterns`, `platform-data:mongodb-patterns`, `platform-data:redis-patterns`, `platform-data:elasticsearch-patterns`, `platform-data:cloudsql-clickhouse`, or another narrow data family |
+| `aw-test` | `platform-sdet:quality-gates` |
+| `aw-review` | `platform-review:code-review-pr` plus the narrow data family when contracts or safety need checking |
+| `aw-deploy` / `aw-ship` | `platform-infra:deployment-strategies`, plus the narrow data family when rollout safety depends on it |
+
+### Infra, release, and operational work
+
+| AW stage | First platform skills to load |
+|---|---|
+| `aw-plan` | `platform-infra:deployment-strategies` |
+| `aw-build` | `platform-infra:jenkins-pipelines`, `platform-infra:kubernetes-workloads`, `platform-infra:terraform-iac`, or another narrow infra family |
+| `aw-investigate` | `platform-infra:grafana`, `platform-infra:log-analysis` |
+| `aw-test` | `platform-sdet:quality-gates` |
+| `aw-review` | `platform-review:code-review-pr`, `platform-infra:production-readiness` |
+| `aw-deploy` | `platform-infra:staging-deploy`, `platform-infra:deployment-strategies`, `platform-infra:production-readiness` |
+| `aw-ship` | `platform-infra:deployment-strategies`, `platform-infra:production-readiness` |
+
+## Common Rationalizations
+
+| Rationalization | Reality |
+|---|---|
+| "The AW stage is enough; platform rules can be implied." | Platform families encode real org behavior and should be selected explicitly when they matter. |
+| "I'll just load everything platform-related to be safe." | Flooding the session makes routing less clear and increases noise. |
+| "Frontend only needs frontend skills." | Real frontend work often also needs design, accessibility, quality-gate, or deploy support. |
+| "Review and test don't need platform families." | Review depth and test evidence are some of the most platform-specific parts of the workflow. |
+
+## Red Flags
+
+- platform skills are chosen before the AW stage is known
+- every task loads multiple platform families with no clear reason
+- frontend tasks skip `platform-design:*` or accessibility support when UI quality matters
+- backend tasks skip platform service conventions and jump straight to generic coding
+- deploy and ship work proceed without platform infra or readiness support
+
+## Verification
+
+Before leaving platform selection, confirm:
+
+- [ ] the AW stage was chosen first
+- [ ] exactly one primary platform family was selected first
+- [ ] the first supporting platform skills match the current AW stage
+- [ ] only the smallest useful platform stack was loaded
+- [ ] craft skills complement the platform stack instead of replacing it

package/skills/using-platform-skills/evals/platform-selection-cases.json

@@ -0,0 +1,52 @@
+{
+  "cases": [
+    {
+      "id": "backend-plan",
+      "prompt": "Create the implementation spec for the approved Communities moderation API contract.",
+      "awStage": "aw-plan",
+      "surface": "backend-service",
+      "expectedPlatformFamilies": ["platform-services:*"],
+      "expectedSupportingSkills": ["platform-services:development"]
+    },
+    {
+      "id": "frontend-plan",
+      "prompt": "Create the implementation spec for the approved Communities feed MFA change.",
+      "awStage": "aw-plan",
+      "surface": "frontend-mfa",
+      "expectedPlatformFamilies": ["platform-frontend:*", "platform-design:*"],
+      "expectedSupportingSkills": ["platform-design:system", "platform-frontend:vue-development"]
+    },
+    {
+      "id": "backend-investigate",
+      "prompt": "Investigate this Communities moderation worker retry failure before patching.",
+      "awStage": "aw-investigate",
+      "surface": "backend-worker",
+      "expectedPlatformFamilies": ["platform-infra:*"],
+      "expectedSupportingSkills": ["platform-infra:grafana"]
+    },
+    {
+      "id": "frontend-test",
+      "prompt": "Test the approved Communities feed MFA UI change for responsive and accessibility regressions.",
+      "awStage": "aw-test",
+      "surface": "frontend-mfa",
+      "expectedPlatformFamilies": ["platform-frontend:*", "platform-sdet:*"],
+      "expectedSupportingSkills": ["platform-frontend:a11y-review", "platform-sdet:quality-gates"]
+    },
+    {
+      "id": "service-deploy",
+      "prompt": "Deploy this verified Communities moderation API service to staging.",
+      "awStage": "aw-deploy",
+      "surface": "backend-service",
+      "expectedPlatformFamilies": ["platform-infra:*"],
+      "expectedSupportingSkills": ["platform-infra:staging-deploy", "platform-infra:deployment-strategies", "platform-infra:production-readiness"]
+    },
+    {
+      "id": "data-build",
+      "prompt": "Add the new analytics projection and search mapping for this reporting workflow.",
+      "awStage": "aw-build",
+      "surface": "data-analytics-search",
+      "expectedPlatformFamilies": ["platform-data:*"],
+      "expectedSupportingSkills": ["platform-data:cloudsql-clickhouse", "platform-data:elasticsearch-patterns"]
+    }
+  ]
+}

package/skills/verification-loop/SKILL.md

@@ -0,0 +1,126 @@
+---
+name: verification-loop
+description: "A comprehensive verification system for Claude Code sessions."
+origin: ECC
+---
+
+# Verification Loop Skill
+
+A comprehensive verification system for Claude Code sessions.
+
+## When to Use
+
+Invoke this skill:
+- After completing a feature or significant code change
+- Before creating a PR
+- When you want to ensure quality gates pass
+- After refactoring
+
+## Verification Phases
+
+### Phase 1: Build Verification
+```bash
+# Check if project builds
+npm run build 2>&1 | tail -20
+# OR
+pnpm build 2>&1 | tail -20
+```
+
+If build fails, STOP and fix before continuing.
+
+### Phase 2: Type Check
+```bash
+# TypeScript projects
+npx tsc --noEmit 2>&1 | head -30
+
+# Python projects
+pyright . 2>&1 | head -30
+```
+
+Report all type errors. Fix critical ones before continuing.
+
+### Phase 3: Lint Check
+```bash
+# JavaScript/TypeScript
+npm run lint 2>&1 | head -30
+
+# Python
+ruff check . 2>&1 | head -30
+```
+
+### Phase 4: Test Suite
+```bash
+# Run tests with coverage
+npm run test -- --coverage 2>&1 | tail -50
+
+# Check coverage threshold
+# Target: 80% minimum
+```
+
+Report:
+- Total tests: X
+- Passed: X
+- Failed: X
+- Coverage: X%
+
+### Phase 5: Security Scan
+```bash
+# Check for secrets
+grep -rn "sk-" --include="*.ts" --include="*.js" . 2>/dev/null | head -10
+grep -rn "api_key" --include="*.ts" --include="*.js" . 2>/dev/null | head -10
+
+# Check for console.log
+grep -rn "console.log" --include="*.ts" --include="*.tsx" src/ 2>/dev/null | head -10
+```
+
+### Phase 6: Diff Review
+```bash
+# Show what changed
+git diff --stat
+git diff HEAD~1 --name-only
+```
+
+Review each changed file for:
+- Unintended changes
+- Missing error handling
+- Potential edge cases
+
+## Output Format
+
+After running all phases, produce a verification report:
+
+```
+VERIFICATION REPORT
+==================
+
+Build:     [PASS/FAIL]
+Types:     [PASS/FAIL] (X errors)
+Lint:      [PASS/FAIL] (X warnings)
+Tests:     [PASS/FAIL] (X/Y passed, Z% coverage)
+Security:  [PASS/FAIL] (X issues)
+Diff:      [X files changed]
+
+Overall:   [READY/NOT READY] for PR
+
+Issues to Fix:
+1. ...
+2. ...
+```
+
+## Continuous Mode
+
+For long sessions, run verification every 15 minutes or after major changes:
+
+```markdown
+Set a mental checkpoint:
+- After completing each function
+- After finishing a component
+- Before moving to next task
+
+Run: /verify
+```
+
+## Integration with Hooks
+
+This skill complements PostToolUse hooks but provides deeper verification.
+Hooks catch issues immediately; this skill provides comprehensive review.