qualia-framework 2.2.1 → 2.4.0

package/framework/skills/qualia-verify-work/SKILL.md

@@ -22,11 +22,11 @@ Read:
 - Phase PLAN.md — for acceptance criteria
 - Phase SUMMARY.md — for what was implemented
 
-Reference: `~/.claude/qualia-engine/workflows/verify-work.md`
+Reference: `~/.claude/qualia-framework/workflows/verify-work.md`
 
 ### 2. Create UAT Tracking
 
-Create `{phase}-UAT.md` using template from `~/.claude/qualia-engine/templates/UAT.md`:
+Create `{phase}-UAT.md` using template from `~/.claude/qualia-framework/templates/UAT.md`:
 
 ```markdown
 # Phase {N}: {Name} — UAT Results
@@ -57,7 +57,14 @@ This is interactive — discuss findings with the user as you go.
 
 #### All tests pass:
 Update UAT.md overall status to ✅ PASSED. Update STATE.md phase status to `verified`.
-> "Phase {N} verified! Run `/qualia-progress` for next steps."
+
+Then check ROADMAP.md for remaining phases:
+
+**If more phases exist after this one:**
+> "Phase {N} verified! Next up: Phase {N+1} — {phase name}. Run `/qualia-plan-phase {N+1}`."
+
+**If this was the last phase:**
+> "All phases complete! Run `/qualia-audit-milestone` to verify the full milestone before wrapping up."
 
 #### Issues found:
 Document gaps in UAT.md. For each gap:
@@ -70,7 +77,7 @@ Then offer:
 
 ### 5. Shipping Checklist Cross-Reference
 
-After UAT testing, cross-reference results against the relevant shipping checklist from `~/.claude/qualia-engine/references/completion-checklists.md`.
+After UAT testing, cross-reference results against the relevant shipping checklist from `~/.claude/qualia-framework/references/completion-checklists.md`.
 
 Detect project type from `.planning/PROJECT.md` or `package.json` and load:
 - **website** → "Website-Specific Checklist" + "Universal Checklist"
@@ -103,3 +110,6 @@ Update `.planning/STATE.md` to reflect verification status.
 |-------|------|------|
 | `qualia-planner` | `~/.claude/agents/qualia-planner.md` | Creates fix plans from diagnosed gaps |
 | `qualia-plan-checker` | `~/.claude/agents/qualia-plan-checker.md` | Validates fix plans (max 3 iterations) |
+
+---
+> Stuck? Type `/qualia-idk` · Lost? Type `/qualia-help`

package/framework/skills/qualia-workflow/SKILL.md

@@ -16,9 +16,9 @@ Project conventions for Qualia Solutions client work. For specific tooling, use
 | Styling | Tailwind CSS + shadcn/ui | Custom themes per client |
 | Backend | Supabase | Postgres, Auth, RLS, Edge Functions |
 | Deployment | Vercel | Preview on PR, Production on main |
-| Voice AI | VAPI or Hume EVI | Depending on emotion needs |
-| Automation | n8n | Workflow orchestration |
-| Monitoring | LangSmith | LLM observability |
+| Voice AI | Retell AI + ElevenLabs | Call orchestration + TTS/voice cloning |
+| AI Models | OpenRouter | Model-flexible (Claude, Mistral, etc.) |
+| Payments | Stripe / HyperPay | Region-dependent |
 
 ## Project Structure
 
@@ -120,9 +120,9 @@ export async function createProduct(formData: FormData) {
 
 - **Supabase**: Use `/supabase` skill (CLI-first) or Supabase MCP plugin
 - **Context7 MCP**: Library documentation lookup
-- **VAPI MCP**: Voice agent configuration
+- **Retell AI**: Voice agent call orchestration
+- **ElevenLabs MCP**: Voice synthesis and cloning
 - **Telnyx MCP**: Phone numbers, messaging, calls
-- **ElevenLabs MCP**: Voice synthesis
 - **Playwright MCP**: Browser automation and testing
 - **Sentry MCP**: Error tracking and monitoring
 - **Firecrawl MCP**: Web scraping and search

package/framework/skills/ship/SKILL.md

@@ -21,7 +21,7 @@ Reference `.planning/PROJECT.md` and `.planning/STATE.md` for project config. If
 Detect project type from codebase signals:
 
 - **agent**: Has AI provider imports (`openai`, `anthropic`, `@ai-sdk`), webhook handlers, agent logic
-- **voice**: Has VAPI/Retell/Telnyx/ElevenLabs imports, voice webhook handlers, `x-vapi-signature`
+- **voice**: Has Retell/ElevenLabs/Telnyx imports, voice webhook handlers, `x-retell-signature`
 - **website**: Has `app/page.tsx` or `pages/index.tsx`, no AI provider imports, primarily UI components
 - **edge-functions**: Has `supabase/functions/` directory, no frontend
 
@@ -29,7 +29,7 @@ If ambiguous, ask user. If pure edge functions, skip tsc/eslint quality gates.
 
 ## Shipping Checklist Gate
 
-Before deploying, load the relevant shipping checklist from `~/.claude/qualia-engine/references/completion-checklists.md`:
+Before deploying, load the relevant shipping checklist from `~/.claude/qualia-framework/references/completion-checklists.md`:
 
 - **website** → "Website-Specific Checklist" + "Universal Checklist"
 - **agent** → "AI Agent Checklist" + "Universal Checklist"
@@ -53,7 +53,12 @@ Include the checklist results in the final deploy report (Step 8).
 
 ### 2. Quality Gates
 
-Run in sequence, stop on failure:
+Run in sequence. **If any gate fails, DO NOT dump raw errors to the employee.** Instead:
+
+1. Summarize what failed in plain language
+2. Auto-fix the issues
+3. Re-run the gate
+4. If auto-fix works, continue. If not, tell the employee what's happening.
 
 ```bash
 npx tsc --noEmit        # TypeScript check — skip if no tsconfig or pure edge functions
@@ -61,6 +66,21 @@ npx eslint . --max-warnings 0   # Lint check — skip if no eslint config
 npm run build            # Build verification — skip if pure edge functions
 ```
 
+**On TypeScript failure:**
+> "Found {N} code errors. Fixing them now..."
+> Fix the errors, then re-run `npx tsc --noEmit`.
+> If still failing after 2 attempts: "Some errors need your input. Here's what's wrong: {plain language summary}. Tell me how to proceed."
+
+**On ESLint failure:**
+> "Found {N} code quality issues. Fixing them now..."
+> Run `npx eslint . --fix` first, then re-check.
+> If still failing: "Some lint issues can't be auto-fixed: {summary}. Fixing manually..."
+
+**On build failure:**
+> "The build failed. Investigating..."
+> Read the error, diagnose, fix, and retry.
+> If still failing: "Build is failing because {plain language reason}. This needs investigation — try `/qualia-debug` or escalate to Fawzi."
+
 ### 2a. Run Tests
 
 If test infrastructure exists (per `~/.claude/skills/test-runner/SKILL.md` detection):
@@ -70,7 +90,10 @@ npm test 2>&1 | tail -30     # Unit/Integration
 npx playwright test 2>&1      # E2E (if configured)
 ```
 
-If tests fail: STOP. Report failures. Do not proceed to deploy.
+**On test failure:**
+> "Tests are failing. Fixing now..."
+> Attempt to fix failing tests. Re-run.
+> If still failing after 2 attempts: "{N} tests still failing. Here's the summary: {plain language}. Fix these before deploying, or say 'ship anyway' to skip tests."
 If no test infrastructure: skip silently.
 
 ### 2b. Review Gate
@@ -101,7 +124,7 @@ Based on detected or specified type:
 
 #### If voice (Voice Agent):
 
-- **Webhook signature verification** — Grep for signature check (`x-vapi-signature`, `signature`, `hmac`, `verify`). Report: PASS/WARN
+- **Webhook signature verification** — Grep for signature check (`x-retell-signature`, `signature`, `hmac`, `verify`). Report: PASS/WARN
 - **Edge function latency note** — First-response latency target: < 500ms. After deploy, test with: `curl -w "%{time_total}" -X POST <webhook-url>`
 
 #### If website (Website):
@@ -199,4 +222,7 @@ If production issues detected:
 - **Supabase migrations**: Create reverse migration
 - **Emergency**: Vercel dashboard manual rollback
 
-If ANY quality gate or safety check FAILS: stop, fix the issue, then re-run `/ship`.
+If ANY quality gate or safety check FAILS: attempt to auto-fix. If auto-fix fails after 2 attempts, explain the issue in plain language and suggest next steps. Never dump raw error output without a plain-language summary first.
+
+---
+> Stuck? Type `/qualia-idk` · Lost? Type `/qualia-help`