qualia-framework 2.1.3 → 2.1.4

package/framework/qualia-engine/workflows/new-project.md

@@ -25,6 +25,27 @@ Parse JSON for: `researcher_model`, `synthesizer_model`, `roadmapper_model`, `co
 git init
 ```
 
+## 1.5. Scan Uploaded Files for Tech Stack Conflicts
+
+**Before asking any questions**, check if the user placed files in the project directory:
+
+```bash
+ls *.pdf *.docx *.doc *.txt *.md *.png *.jpg *.jpeg 2>/dev/null | head -10
+```
+
+If files are found, read them. If ANY file mentions a tech stack that differs from the Qualia standard (Next.js + React + TypeScript + Supabase + Vercel), you MUST ask the user:
+
+Use AskUserQuestion:
+- header: "Tech Stack"
+- question: "The uploaded document mentions {detected stack}. Which stack should we use?"
+- options:
+  - "Qualia stack (Recommended)" — Next.js + React + TypeScript + Supabase + Vercel. This is what we build with.
+  - "Document stack" — Use {detected stack} as specified in the document. The workflow adapts.
+
+**Never silently adopt a non-Qualia stack from uploaded documents.** Always confirm first.
+
+If no files found or no stack conflict: skip silently.
+
 ## 2. Brownfield Offer
 
 **If `needs_codebase_map` is true** (from init — existing code detected but no codebase map):

package/framework/skills/qualia-new-project/SKILL.md

@@ -14,6 +14,22 @@ Initialize a new project with the full Qualia qualia-engine workflow: questionin
 
 ## Process
 
+### 0. Scan for Uploaded Files
+
+Before asking any questions, check if the user uploaded or placed files in the project directory:
+
+```bash
+ls *.pdf *.docx *.doc *.txt *.md *.png *.jpg *.jpeg 2>/dev/null | head -10
+```
+
+If files are found, read them. If ANY file mentions a tech stack (WordPress, Firebase, PHP, Laravel, React Native, Flutter, etc.) that differs from the Qualia standard stack (Next.js + Supabase + Vercel), you MUST ask:
+
+> "The document mentions {tech stack from doc}. Do you want to:
+> 1. **Use the Qualia stack** (Next.js + React + TypeScript + Supabase + Vercel) — recommended, this is what we build with
+> 2. **Use the stack from the document** ({tech stack}) — I'll adapt the workflow accordingly"
+
+Never silently adopt a non-Qualia stack from uploaded documents. Always confirm.
+
 ### 1. Questioning Phase
 
 Run the questioning workflow to understand the project deeply before any planning.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "qualia-framework",
-  "version": "2.1.3",
+  "version": "2.1.4",
   "description": "Qualia Solutions — Claude Code Framework",
   "bin": {
     "qualia-framework": "./bin/cli.js"

package/templates/CLAUDE.md.hbs

@@ -39,12 +39,12 @@ Collaborator, not executor. Speak up about bugs, simpler approaches, bad archite
 Be honest. Default to action. Never speculate on unread code. Say when blocked.
 
 ## Workflow
-- Session start: `pwd` > identify project > read local CLAUDE.md
+- **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 (Sonnet) for research. Opus for complex reasoning.
 - `/compact` at 60%. `/clear` between tasks. `/learn` after mistakes.
 
-## Qualia Mode (activate with /qualia-start)
-When Qualia mode is active, these behaviors apply to ALL interactions:
+## 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

package/templates/settings.json

@@ -21,6 +21,15 @@
   },
   "hooks": {
     "PreToolUse": [
+      {
+        "matcher": "Skill",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "~/.claude/hooks/skill-announce.sh"
+          }
+        ]
+      },
       {
         "matcher": "Edit",
         "hooks": [
@@ -80,6 +89,17 @@
         ]
       }
     ],
+    "PostToolUseFailure": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "~/.claude/hooks/tool-error-announce.sh"
+          }
+        ]
+      }
+    ],
     "PreCompact": [
       {
         "matcher": "",
@@ -91,6 +111,17 @@
         ]
       }
     ],
+    "PostCompact": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "~/.claude/hooks/session-context-loader.sh"
+          }
+        ]
+      }
+    ],
     "SessionStart": [
       {
         "matcher": "",