qualia-framework 2.6.0 → 3.2.0

package/tests/statusline.test.sh

@@ -0,0 +1,243 @@
+#!/bin/bash
+# Qualia Framework v2 — statusline.js behavioral tests
+# Run: bash tests/statusline.test.sh
+#
+# Strategy: statusline.js reads a single JSON blob from stdin and prints two
+# ANSI-formatted lines to stdout. We pipe JSON, capture stdout, and assert on
+# exit code + presence of expected substrings (including raw ANSI escape codes
+# for color assertions).
+#
+# Workspace dirs point at /tmp/qualia-sl-nonexistent so git subprocesses fail
+# fast (statusline swallows the error) — no real git repo required.
+
+PASS=0
+FAIL=0
+# Resolve SL_JS to an ABSOLUTE path so `cd` inside subshells doesn't break it.
+SL_JS="$(cd "$(dirname "$0")/../bin" && pwd)/statusline.js"
+NODE="${NODE:-node}"
+
+# statusline.js caches git state per-user in $TMPDIR/qualia-git-cache-$USER
+# (3-second TTL). Wipe before every test so cached results from a previous
+# run don't leak branch/changes values into the current assertion.
+CACHE_GLOB_DIR="${TMPDIR:-/tmp}"
+clean_cache() {
+  rm -f "$CACHE_GLOB_DIR"/qualia-git-cache-* 2>/dev/null || true
+}
+trap clean_cache EXIT
+clean_cache
+
+# Colors used by statusline.js — hardcoded from bin/statusline.js
+# These are raw ANSI escape sequences (printf %b interpolates \x1b -> ESC).
+TEAL_ESC=$(printf '\x1b[38;2;0;206;209m')
+YELLOW_ESC=$(printf '\x1b[38;2;234;179;8m')
+RED_ESC=$(printf '\x1b[38;2;239;68;68m')
+
+pass() {
+  echo "  ✓ $1"
+  PASS=$((PASS + 1))
+}
+
+fail_case() {
+  echo "  ✗ $1${2:+ — $2}"
+  FAIL=$((FAIL + 1))
+}
+
+# run_sl <json> → populates OUT (stdout) and RC (exit code).
+# Uses a nonexistent workspace dir so git commands fail gracefully.
+# We write stdout to a tmp file (not $()) so we can capture exit code
+# without losing it to a subshell on the left side of the pipeline.
+SL_OUTFILE=$(mktemp)
+run_sl() {
+  local json="$1"
+  clean_cache
+  # printf %s (not echo) to avoid trailing newlines affecting JSON.parse.
+  printf '%s' "$json" | $NODE "$SL_JS" > "$SL_OUTFILE" 2>/dev/null
+  RC=$?
+  OUT=$(cat "$SL_OUTFILE")
+}
+# Extend the cleanup trap to also remove the tmp output file.
+cleanup_sl() {
+  clean_cache
+  [ -f "$SL_OUTFILE" ] && rm -f "$SL_OUTFILE"
+}
+trap cleanup_sl EXIT
+
+echo "=== statusline.js Behavioral Tests ==="
+echo ""
+
+# Sanity check
+if [ ! -f "$SL_JS" ]; then
+  echo "FATAL: statusline.js not found at $SL_JS"
+  exit 1
+fi
+
+# ─── Basic rendering ─────────────────────────────────────
+echo "basic rendering:"
+
+# 1. Minimal input renders without crash — two lines, contains dir basename + model
+NONEXIST="/tmp/qualia-sl-nonexist-$$"
+JSON='{"model":{"display_name":"Claude Opus 4.6"},"workspace":{"current_dir":"'"$NONEXIST"'"},"context_window":{"used_percentage":0},"cost":{"total_cost_usd":0},"agent":{},"worktree":{}}'
+run_sl "$JSON"
+LINES=$(wc -l < "$SL_OUTFILE")
+if [ "$RC" -eq 0 ] \
+   && [ "$LINES" -eq 2 ] \
+   && grep -qF "qualia-sl-nonexist" "$SL_OUTFILE" \
+   && grep -qF "Claude Opus 4.6" "$SL_OUTFILE"; then
+  pass "minimal input → exit 0, 2 lines, contains dir basename + model name"
+else
+  fail_case "minimal input" "exit=$RC lines=$LINES"
+fi
+
+# 2. Two lines always produced (check trailing newline count)
+# process.stdout.write twice with '\n' → exactly 2 newlines in output
+if [ "$LINES" -eq 2 ]; then
+  pass "always prints exactly 2 lines"
+else
+  fail_case "two lines" "got $LINES newlines"
+fi
+
+# ─── Context bar color thresholds ────────────────────────
+echo ""
+echo "context bar color:"
+
+# 3. Teal at low % (<50)
+JSON='{"model":{"display_name":"M"},"workspace":{"current_dir":"'"$NONEXIST"'"},"context_window":{"used_percentage":30},"cost":{"total_cost_usd":0},"agent":{},"worktree":{}}'
+run_sl "$JSON"
+if [ "$RC" -eq 0 ] && grep -qF "$TEAL_ESC" "$SL_OUTFILE"; then
+  pass "30% → teal color on bar"
+else
+  fail_case "30% → teal" "exit=$RC"
+fi
+
+# 4. Yellow at medium % (50–79)
+JSON='{"model":{"display_name":"M"},"workspace":{"current_dir":"'"$NONEXIST"'"},"context_window":{"used_percentage":60},"cost":{"total_cost_usd":0},"agent":{},"worktree":{}}'
+run_sl "$JSON"
+if [ "$RC" -eq 0 ] && grep -qF "$YELLOW_ESC" "$SL_OUTFILE"; then
+  pass "60% → yellow color on bar"
+else
+  fail_case "60% → yellow" "exit=$RC"
+fi
+
+# 5. Red at high % (>=80)
+JSON='{"model":{"display_name":"M"},"workspace":{"current_dir":"'"$NONEXIST"'"},"context_window":{"used_percentage":85},"cost":{"total_cost_usd":0},"agent":{},"worktree":{}}'
+run_sl "$JSON"
+if [ "$RC" -eq 0 ] && grep -qF "$RED_ESC" "$SL_OUTFILE"; then
+  pass "85% → red color on bar"
+else
+  fail_case "85% → red" "exit=$RC"
+fi
+
+# ─── Cost and duration formatting ────────────────────────
+echo ""
+echo "cost and duration:"
+
+# 6. Cost formatting: $X.XX
+JSON='{"model":{"display_name":"M"},"workspace":{"current_dir":"'"$NONEXIST"'"},"context_window":{"used_percentage":10},"cost":{"total_cost_usd":2.47,"total_duration_ms":0},"agent":{},"worktree":{}}'
+run_sl "$JSON"
+if [ "$RC" -eq 0 ] && grep -qF '$2.47' "$SL_OUTFILE"; then
+  pass "cost 2.47 → \$2.47"
+else
+  fail_case "cost formatting" "exit=$RC"
+fi
+
+# 7. Duration under 60s shown as seconds
+JSON='{"model":{"display_name":"M"},"workspace":{"current_dir":"'"$NONEXIST"'"},"context_window":{"used_percentage":10},"cost":{"total_cost_usd":0,"total_duration_ms":45000},"agent":{},"worktree":{}}'
+run_sl "$JSON"
+if [ "$RC" -eq 0 ] && grep -qF "45s" "$SL_OUTFILE"; then
+  pass "duration 45000ms → 45s"
+else
+  fail_case "duration seconds" "exit=$RC"
+fi
+
+# 8. Duration >=60s shown as minutes
+JSON='{"model":{"display_name":"M"},"workspace":{"current_dir":"'"$NONEXIST"'"},"context_window":{"used_percentage":10},"cost":{"total_cost_usd":0,"total_duration_ms":125000},"agent":{},"worktree":{}}'
+run_sl "$JSON"
+if [ "$RC" -eq 0 ] && grep -qF "2m" "$SL_OUTFILE"; then
+  pass "duration 125000ms → 2m"
+else
+  fail_case "duration minutes" "exit=$RC"
+fi
+
+# ─── Optional segments: agent + worktree ─────────────────
+echo ""
+echo "optional segments:"
+
+# 9. Agent name segment appears
+JSON='{"model":{"display_name":"M"},"workspace":{"current_dir":"'"$NONEXIST"'"},"context_window":{"used_percentage":10},"cost":{"total_cost_usd":0},"agent":{"name":"qualia-planner"},"worktree":{}}'
+run_sl "$JSON"
+if [ "$RC" -eq 0 ] && grep -qF "qualia-planner" "$SL_OUTFILE"; then
+  pass "agent.name rendered on line 1"
+else
+  fail_case "agent segment" "exit=$RC"
+fi
+
+# 10. Worktree name segment appears
+JSON='{"model":{"display_name":"M"},"workspace":{"current_dir":"'"$NONEXIST"'"},"context_window":{"used_percentage":10},"cost":{"total_cost_usd":0},"agent":{},"worktree":{"name":"feature-x"}}'
+run_sl "$JSON"
+if [ "$RC" -eq 0 ] && grep -qF "feature-x" "$SL_OUTFILE"; then
+  pass "worktree.name rendered on line 1"
+else
+  fail_case "worktree segment" "exit=$RC"
+fi
+
+# ─── Degraded input ──────────────────────────────────────
+echo ""
+echo "degraded input:"
+
+# 11. Empty stdin → still exit 0, still produces two lines
+run_sl ""
+LINES=$(wc -l < "$SL_OUTFILE")
+if [ "$RC" -eq 0 ] && [ "$LINES" -eq 2 ]; then
+  pass "empty stdin → exit 0, 2 lines (degraded, no crash)"
+else
+  fail_case "empty stdin" "exit=$RC lines=$LINES"
+fi
+
+# 12. Invalid JSON → still exit 0, no crash
+run_sl "not json{"
+LINES=$(wc -l < "$SL_OUTFILE")
+if [ "$RC" -eq 0 ] && [ "$LINES" -eq 2 ]; then
+  pass "invalid JSON → exit 0, 2 lines (degraded, no crash)"
+else
+  fail_case "invalid JSON" "exit=$RC lines=$LINES"
+fi
+
+# ─── Phase info from tracking.json ───────────────────────
+echo ""
+echo "phase info:"
+
+# 13. tracking.json with phase=2/4 status=built → "P2/4" and "built" appear
+TMP=$(mktemp -d)
+mkdir -p "$TMP/.planning"
+cat > "$TMP/.planning/tracking.json" <<'EOF'
+{"phase": 2, "total_phases": 4, "status": "built"}
+EOF
+JSON='{"model":{"display_name":"M"},"workspace":{"current_dir":"'"$TMP"'"},"context_window":{"used_percentage":10},"cost":{"total_cost_usd":0},"agent":{},"worktree":{}}'
+run_sl "$JSON"
+if [ "$RC" -eq 0 ] \
+   && grep -qF "P2/4" "$SL_OUTFILE" \
+   && grep -qF "built" "$SL_OUTFILE"; then
+  pass "tracking.json phase=2/4 status=built → P2/4 + built rendered"
+else
+  fail_case "phase info from tracking.json" "exit=$RC"
+fi
+rm -rf "$TMP"
+
+# 14. Malformed tracking.json does not crash → still exits 0
+TMP=$(mktemp -d)
+mkdir -p "$TMP/.planning"
+echo 'not json' > "$TMP/.planning/tracking.json"
+JSON='{"model":{"display_name":"M"},"workspace":{"current_dir":"'"$TMP"'"},"context_window":{"used_percentage":10},"cost":{"total_cost_usd":0},"agent":{},"worktree":{}}'
+run_sl "$JSON"
+LINES=$(wc -l < "$SL_OUTFILE")
+if [ "$RC" -eq 0 ] && [ "$LINES" -eq 2 ]; then
+  pass "malformed tracking.json → exit 0, no crash"
+else
+  fail_case "malformed tracking.json" "exit=$RC lines=$LINES"
+fi
+rm -rf "$TMP"
+
+# ─── Summary ─────────────────────────────────────────────
+echo ""
+echo "=== Results: $PASS passed, $FAIL failed ==="
+[ "$FAIL" -eq 0 ] && exit 0 || exit 1

package/bin/collect-metrics.sh

@@ -1,62 +0,0 @@
-#!/bin/bash
-# Qualia Framework Metrics Collection
-# Run after a project ships to capture performance data.
-# Usage: collect-metrics.sh [project-dir]
-# Output: appends to ~/.claude/knowledge/framework-metrics.md
-
-PROJECT_DIR="${1:-.}"
-METRICS_FILE="$HOME/.claude/knowledge/framework-metrics.md"
-DATE=$(date +%Y-%m-%d)
-
-# Ensure metrics file exists
-if [ ! -f "$METRICS_FILE" ]; then
-  cat > "$METRICS_FILE" << 'HEADER'
-# Framework Performance Metrics
-
-> Auto-collected after each project ships. Read by `/qualia-evolve` to optimize the framework.
-
-| Date | Project | Phases | Sessions | Deviations | IDK Calls | Verify Pass Rate | Lab Notes | FQS |
-|------|---------|--------|----------|------------|-----------|-----------------|-----------|-----|
-HEADER
-fi
-
-cd "$PROJECT_DIR" || exit 1
-
-# Project name
-PROJECT=$(basename "$(pwd)")
-
-# Phase count
-PHASES=$(ls -d .planning/phases/*/ 2>/dev/null | wc -l)
-
-# Session count (from session-digest entries for this project)
-SESSIONS=$(grep -c "$PROJECT" ~/.claude/knowledge/session-digest.md 2>/dev/null || echo "?")
-
-# Deviation count (gap-fix plans)
-DEVIATIONS=$(find .planning/phases/ -name "*-PLAN.md" -exec grep -l "gaps" {} \; 2>/dev/null | wc -l)
-
-# IDK calls (search session digest for qualia-idk mentions with this project)
-IDK_CALLS=$(grep "$PROJECT" ~/.claude/knowledge/session-digest.md 2>/dev/null | grep -c "idk\|stuck\|lost" || echo "0")
-
-# Verify pass rate (UAT files with PASSED vs total UAT files)
-TOTAL_UAT=$(find .planning/phases/ -name "*-UAT.md" 2>/dev/null | wc -l)
-PASSED_UAT=$(grep -rl "PASSED\|✅.*Overall" .planning/phases/*/*.md 2>/dev/null | wc -l)
-if [ "$TOTAL_UAT" -gt 0 ]; then
-  PASS_RATE=$(( PASSED_UAT * 100 / TOTAL_UAT ))%
-else
-  PASS_RATE="n/a"
-fi
-
-# Lab Notes count
-LAB_NOTES=$(grep -c "^###" .planning/LAB-NOTES.md 2>/dev/null || echo "0")
-
-# FQS calculation (completion_rate / sessions * 100) — assume 100% if we're collecting
-if [ "$SESSIONS" != "?" ] && [ "$SESSIONS" -gt 0 ]; then
-  FQS=$(( 100 * 100 / SESSIONS ))
-else
-  FQS="?"
-fi
-
-# Append to metrics file
-echo "| $DATE | $PROJECT | $PHASES | $SESSIONS | $DEVIATIONS | $IDK_CALLS | $PASS_RATE | $LAB_NOTES | $FQS |" >> "$METRICS_FILE"
-
-echo "Metrics collected for $PROJECT → $METRICS_FILE"

package/framework/.claudeignore

@@ -1,51 +0,0 @@
-# ~/.claude/.claudeignore
-# Patterns to exclude from Claude Code context
-
-# Secrets and credentials
-.env
-.env.*
-*.pem
-*.key
-credentials.json
-*secret*
-.credentials.json
-askpass.sh
-
-# Analytics and internal state
-usage-data/
-sessions/
-statsig/
-
-# Node modules (anywhere)
-skills/*/node_modules/
-plugins/cache/*/node_modules/
-node_modules/
-
-# Large generated directories
-.next/
-dist/
-build/
-*.log
-
-# Claude internals (prevent recursion/bloat)
-plugins/cache/
-shell-snapshots/
-debug/
-file-history/
-projects/
-archive/
-todos/
-session-env/
-paste-cache/
-backups/
-cache/
-cowork-knowledge-pack.md
-
-# IDE and editor
-.vscode/
-.idea/
-
-# History and state files
-history.jsonl
-*.jsonl
-cleanup.log

package/framework/CLAUDE.md

@@ -1,51 +0,0 @@
-# CLAUDE.md — OWNER Profile
-
-## Identity
-**Fawzi Goussous** — Founder at Qualia Solutions. Nicosia, Cyprus.
-One-man dev shop. Websites, AI agents, voice agents, AI automation.
-- Direct, action-oriented, no fluff. Code > theory.
-- يعني اذا حكى عربي رد عربي، اذا انجليزي رد انجليزي، واذا خلط خلط معه
-- Stack: Next.js 16+, React 19, TypeScript, Supabase, Vercel, VAPI, ElevenLabs, Telnyx, Retell AI, OpenRouter
-
-## Role: OWNER
-You are the founder. Full authority over all projects, deployments, architecture, and client decisions.
-- Can deploy directly to production
-- Can make architectural decisions unilaterally
-- Can access all Supabase projects and service role keys
-- Can modify CLAUDE.md, skills, hooks, and framework config
-- Can approve/reject employee work
-
-## Rules
-- Read before Write/Edit — no exceptions
-- Feature branches preferred — OWNER may push to main when necessary (branch-guard enforces for non-OWNER)
-- MVP first. Build only what's asked. No over-engineering.
-- Root cause on failures — no band-aids
-- `npx tsc --noEmit` after multi-file TS changes
-- Glob/Grep directly — no Task(Explore) unless 5+ rounds needed
-- For non-trivial work (multi-file changes, architectural decisions, unfamiliar codebases), confirm understanding before coding: "Here's what I understand: [summary]. Correct?" — quick tasks (typo, single-file, familiar pattern) are exempt
-- See `rules/security.md` for auth, RLS, Zod, secrets rules
-- See `rules/frontend.md` for design standards
-- See `rules/deployment.md` for deploy checklist
-
-## Collaboration
-Collaborator, not executor. Speak up about bugs, simpler approaches, bad architecture.
-Be honest. Default to action. Never speculate on unread code. Say when blocked.
-
-## Workflow
-- **MANDATORY FIRST ACTION**: On every session start, invoke the `qualia-start` skill before doing anything else. This is non-negotiable — do not wait for user input, do not skip it, do not just acknowledge the hook message. Actually invoke the skill using the Skill tool.
-- Subagents default to Opus (set via CLAUDE_CODE_SUBAGENT_MODEL).
-- `/compact` at 60%. `/clear` between tasks. `/learn` after mistakes.
-
-## Qualia Mode (always active)
-These behaviors apply to ALL interactions:
-- **Frontend guard:** Read .planning/DESIGN.md before any frontend file changes
-- **Deploy guard:** Check .planning/REVIEW.md freshness before any deploy command (run /qualia-review to generate)
-- **Intent verification:** Confirm before modifying 3+ files in one response
-- **Task-type detection:** Auto-load relevant skill patterns based on what's being done
-- **Quality defaults:** Security rules, tsc checks, RLS consideration — always enforced
-
-## Compaction — ALWAYS preserve:
-Project path/name/ref, branch, modified files, decisions, test results, in-progress work, errors, Qualia phase/milestone state, Qualia mode active/inactive state, session digest context.
-
-## Learned Patterns & Gotchas
-See ~/.claude/knowledge/learned-patterns.md for full rules and project gotchas.

package/framework/MCP_SETUP.md

@@ -1,229 +0,0 @@
-# MCP Server Setup & Security Guide
-
-Configuration and security best practices for Model Context Protocol servers.
-
----
-
-## Current Configuration
-
-### Active MCP Servers (as of 2026-03-30)
-
-| Server | Package | Purpose | Status |
-|--------|---------|---------|--------|
-| `filesystem` | `@modelcontextprotocol/server-filesystem` | Local file operations | Active |
-| `context7` | `@context7/mcp-server` | Documentation search | Active |
-| `playwright` | `@playwright/mcp@latest` | Browser automation | Active |
-| `vapi` | `@vapi-ai/mcp-server` | Voice AI integration | Active |
-| `telnyx_api` | `telnyx-mcp-server` | Telecom integration | Active |
-| `elevenlabs` | `@anthropic/elevenlabs-mcp-server` | Audio synthesis | Active |
-
-**Removed servers:**
-- `supabase` MCP — replaced by the `/supabase` skill (CLI + Management API, zero context overhead)
-- `n8n-mcp` — removed, not actively used
-
----
-
-## Server Details
-
-### Filesystem
-```json
-{
-  "filesystem": {
-    "command": "npx",
-    "args": ["-y", "@modelcontextprotocol/server-filesystem", "/home/qualia"]
-  }
-}
-```
-**Security:** Restricts access to home directory only.
-
----
-
-### Context7
-```json
-{
-  "context7": {
-    "command": "npx",
-    "args": ["-y", "@context7/mcp-server"]
-  }
-}
-```
-**Purpose:** Search and retrieve up-to-date library documentation.
-
----
-
-### Playwright
-```json
-{
-  "playwright": {
-    "command": "npx",
-    "args": ["-y", "@playwright/mcp@latest"]
-  }
-}
-```
-**Purpose:** Browser automation and web testing.
-
----
-
-### ~~Supabase~~ (REMOVED)
-Replaced by the `/supabase` skill which uses CLI + Management API with zero context overhead.
-
-Previously:
-    "command": "npx",
-    "args": ["-y", "@anthropic-ai/mcp-supabase"],
-    "env": {
-      "SUPABASE_URL": "${SUPABASE_URL}",
-      "SUPABASE_KEY": "${SUPABASE_KEY}"
-    }
-  }
-}
-```
-**Security:** Store credentials in `.env.claude` only.
-
----
-
-## Security Best Practices
-
-### 1. Credential Storage
-
-**DO:**
-```bash
-# Store in .env.claude
-SUPABASE_URL="https://xxx.supabase.co"
-SUPABASE_KEY="your-key-here"
-```
-
-**DON'T:**
-```json
-// Never put credentials directly in settings.json
-"env": {
-  "SUPABASE_KEY": "eyJhbGciOiJIUzI1NiIs..."  // BAD!
-}
-```
-
-### 2. File Permissions
-```bash
-chmod 600 ~/.claude/.env.claude
-chmod 600 ~/.claude/settings.json
-chmod 600 ~/.claude/.credentials.json
-```
-
-### 3. Environment Variable Reference
-Use variable interpolation in settings.json:
-```json
-"env": {
-  "API_KEY": "${API_KEY}"  // References .env.claude
-}
-```
-
-### 4. Read-Only Mode
-For production safety, consider read-only configurations:
-```json
-"env": {
-  "SUPABASE_READ_ONLY": "true"
-}
-```
-
----
-
-## Adding New MCP Servers
-
-### Step 1: Install the Server
-```bash
-npx -y @anthropic-ai/mcp-<server-name>
-```
-
-### Step 2: Add to settings.json
-```json
-{
-  "mcpServers": {
-    "new-server": {
-      "command": "npx",
-      "args": ["-y", "@anthropic-ai/mcp-new-server"],
-      "env": {
-        "API_KEY": "${NEW_SERVER_API_KEY}"
-      }
-    }
-  }
-}
-```
-
-### Step 3: Add Credentials to .env.claude
-```bash
-echo 'NEW_SERVER_API_KEY="your-key"' >> ~/.claude/.env.claude
-```
-
-### Step 4: Restart Claude Code
-```bash
-source ~/.claude/.env.claude && claude
-```
-
----
-
-## Troubleshooting
-
-### Server Not Starting
-1. Check if package is installed: `npx -y @anthropic-ai/mcp-<name> --help`
-2. Verify environment variables are set
-3. Check Claude Code logs: `~/.claude/debug/`
-
-### Authentication Errors
-1. Verify credentials in `.env.claude`
-2. Check file permissions
-3. Ensure variables are exported: `source ~/.env.claude`
-
-### Connection Timeouts
-1. Check network connectivity
-2. Verify API endpoint is accessible
-3. Consider adding timeout configuration
-
----
-
-## Credential Rotation
-
-### Schedule
-- API keys: Every 90 days
-- OAuth tokens: Automatic refresh
-- Service role keys: Every 90 days
-
-### Rotation Process
-1. Generate new key in service dashboard
-2. Update `.env.claude`
-3. Test connectivity
-4. Revoke old key
-
----
-
-## Monitoring
-
-### Health Checks
-MCP servers should respond to basic requests within 5 seconds.
-
-### Log Locations
-- MCP errors: `~/.claude/debug/`
-- Connection issues: Check terminal output
-
----
-
-## Permissions Matrix
-
-| Server | Read | Write | Execute |
-|--------|------|-------|---------|
-| filesystem | ✓ | ✓ | - |
-| supabase | ✓ | ✓ | - |
-| playwright | - | - | ✓ |
-| context7 | ✓ | - | - |
-
----
-
-## Quick Commands
-
-```bash
-# Start Claude with MCP servers
-source ~/.claude/.env.claude && claude
-
-# List active servers
-cat ~/.claude/settings.json | jq '.mcpServers | keys'
-
-# Test specific server
-npx -y @anthropic-ai/mcp-supabase --help
-```

package/framework/agents/architecture-strategist.md

@@ -1,53 +0,0 @@
----
-name: architecture-strategist
-description: "Analyze code changes from an architectural perspective — component boundaries, coupling, SOLID principles, design pattern compliance. Use after refactors, new service additions, or when validating structural decisions."
-model: inherit
-tools: Read, Bash, Grep, Glob
----
-
-You are a System Architecture Expert specializing in analyzing code changes and system design decisions. Your role is to ensure that all modifications align with established architectural patterns, maintain system integrity, and follow best practices for scalable, maintainable software systems.
-
-Your analysis follows this systematic approach:
-
-1. **Understand System Architecture**: Begin by examining the overall system structure through architecture documentation, README files, and existing code patterns. Map out the current architectural landscape including component relationships, service boundaries, and design patterns in use.
-
-2. **Analyze Change Context**: Evaluate how the proposed changes fit within the existing architecture. Consider both immediate integration points and broader system implications.
-
-3. **Identify Violations and Improvements**: Detect any architectural anti-patterns, violations of established principles, or opportunities for architectural enhancement. Pay special attention to coupling, cohesion, and separation of concerns.
-
-4. **Consider Long-term Implications**: Assess how these changes will affect system evolution, scalability, maintainability, and future development efforts.
-
-When conducting your analysis, you will:
-
-- Read and analyze architecture documentation and README files to understand the intended system design
-- Map component dependencies by examining import statements and module relationships
-- Analyze coupling metrics including import depth and potential circular dependencies
-- Verify compliance with SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion)
-- Assess microservice boundaries and inter-service communication patterns where applicable
-- Evaluate API contracts and interface stability
-- Check for proper abstraction levels and layering violations
-
-Your evaluation must verify:
-- Changes align with the documented and implicit architecture
-- No new circular dependencies are introduced
-- Component boundaries are properly respected
-- Appropriate abstraction levels are maintained throughout
-- API contracts and interfaces remain stable or are properly versioned
-- Design patterns are consistently applied
-- Architectural decisions are properly documented when significant
-
-Provide your analysis in a structured format that includes:
-1. **Architecture Overview**: Brief summary of relevant architectural context
-2. **Change Assessment**: How the changes fit within the architecture
-3. **Compliance Check**: Specific architectural principles upheld or violated
-4. **Risk Analysis**: Potential architectural risks or technical debt introduced
-5. **Recommendations**: Specific suggestions for architectural improvements or corrections
-
-Be proactive in identifying architectural smells such as:
-- Inappropriate intimacy between components
-- Leaky abstractions
-- Violation of dependency rules
-- Inconsistent architectural patterns
-- Missing or inadequate architectural boundaries
-
-When you identify issues, provide concrete, actionable recommendations that maintain architectural integrity while being practical for implementation. Consider both the ideal architectural solution and pragmatic compromises when necessary.