viepilot 2.41.0 → 2.45.2

package/CHANGELOG.md

@@ -7,6 +7,99 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.45.2] - 2026-04-25
+
+### Enhanced
+- **ENH-077**: crystallize Step 1D.14 now offers AUQ post-export handoff —
+  after design.md exports to project root, prompts "Sync tokens to stylesheets via
+  /vp-design --sync?" with Run now / Skip options; silent skip when no stylesheet
+  target detected (tailwind.config.js / .css / .scss absent) (ENH-077)
+
+## [2.45.1] - 2026-04-25
+
+### Enhanced
+- **ENH-076.5**: Architect workspace adds `design.html` page when design.md or design tokens
+  are present — visual color swatches grid, typography scale table, spacing grid, border-radius
+  samples, component token table; bidirectional sync with notes.md `## design_tokens`;
+  hub nav link added to `index.html` (ENH-076)
+
+## [2.45.0] - 2026-04-25
+
+### Added
+- **ENH-076.4**: New skill `vp-design` — manage Design.MD design system files:
+  `--init` (Q&A from scratch or awesome-design-md import from 55+ brands),
+  `--sync` (tokens → Tailwind / CSS custom properties / SCSS auto-detected),
+  `--audit` (compliance report with ❌/⚠️/✅ severity levels),
+  `--import [brand]` (community template picker with Apply/Customize/Reference modes) (ENH-076)
+
+## [2.44.1] - 2026-04-25
+
+### Enhanced
+- **ENH-076.3**: vp-auto Preflight 5.5 — Design.MD TOKEN_MAP injection for UI tasks:
+  Level 1 silent context injection, Level 2 checklist items (UI ACs), Level 3 post-task
+  audit with auto-fix; backend-only tasks skip injection; monorepo nearest-file rule (ENH-076)
+
+## [2.44.0] - 2026-04-25
+
+### Enhanced
+- **ENH-076.1**: vp-brainstorm `--ui` mode now auto-extracts design tokens → generates
+  `design.md` (Design.MD v1 spec) in session directory alongside `index.html`; `notes.md`
+  gets `## design_tokens` YAML section with `design_md_path` pointer (ENH-076)
+- **ENH-076.2**: vp-crystallize Step 1D.14 — mandatory-acknowledge gate for design.md:
+  export to project root + `ARCHITECTURE.md ## Design System` + `PROJECT-CONTEXT.md` flag;
+  idempotent skip writes `design_md_status: skipped`; conflict handling: Override/Merge/Keep/Diff (ENH-076)
+
+## [2.43.2] - 2026-04-25
+
+### Fixed
+- **BUG-023**: vp-brainstorm session-transition/next-steps prompt ("What would you like to
+  do next?" — crystallize / update UI artifacts / continue discussing) now uses
+  `AskUserQuestion` on Claude Code terminal; `workflows/brainstorm.md` +
+  `skills/vp-brainstorm/SKILL.md` updated (distinct from BUG-022 Q&A content choices)
+
+## [2.43.1] - 2026-04-24
+
+### Fixed
+- **vp-brainstorm**: mid-session structured decision questions now use `AskUserQuestion`
+  on Claude Code terminal when ≥2 discrete named options are available; free-form
+  open questions remain conversational plain text; SKILL.md "Prompts using AUQ" list
+  updated (BUG-022)
+
+## [2.43.0] - 2026-04-24
+
+### Enhanced
+- **vp-rollback**: AUQ checkpoint selection with pagination — structured `AskUserQuestion`
+  prompt replaces plain-text table; "Show N more →" option pages through older checkpoints;
+  `--limit N` flag controls page size (default: 10); `--list` flag unchanged; ENH-059
+  ToolSearch preload applied; text fallback on non-Claude Code adapters (ENH-075)
+
+## [2.42.0] - 2026-04-24
+
+### Added
+- **ENH-073**: vp-persona — fully automated cross-project persona system (no wizard)
+  - `lib/viepilot-persona.cjs`: `inferPersona()` detects domain from project files + git shortlog (no setup required)
+  - Auto-switch persona on `$PWD` change; auto-merge when 2+ domain signals detected in same project
+  - `team_size` inferred from `git shortlog -sn`; `output_style` defaults lean, self-learned from calibration traces
+  - 3-layer resolution: project-override > context-map > global active persona
+  - `lib/viepilot-calibrate.cjs`: always-on adaptive calibration via Reflexion pattern
+    - Session traces written async to `~/.viepilot/traces/` after every session
+    - 🟢 low-risk changes (topic_skip, stack_add) auto-applied silently
+    - 🟡 medium-risk changes (output_style, phase_default) auto-applied + logged to `pending-review.md`
+    - 🔴 high-risk changes blocked (caller decides to prompt, max once per session)
+    - `guardrail_journal` prevents re-proposing rejected patterns
+    - JSON Patch RFC 6902 workflow overlays — base workflows never modified
+  - 5 built-in domain packs: `web-saas`, `data-science`, `mobile`, `devops`, `ai-product`
+    - Each: `topic_priority`, `extra_topics` with Q&A, `phase_template`, `architect_pages`, `stacks_hint`
+  - `vp-tools persona` subcommand: `get`/`infer`/`list`/`set`/`auto-switch`/`context`
+  - `skills/vp-persona/SKILL.md`: new skill for persona inspection and optional correction (`--refine`)
+  - `<persona_context>` block injected into all 19 `vp-*` SKILL.md files (including vp-persona itself)
+  - `workflows/brainstorm.md`: domain pack topic injection (Step 0B)
+  - `workflows/autonomous.md`: persona context injected per task
+  - `workflows/crystallize.md`: `output_style` adaptation (lean/balanced/enterprise)
+  - `workflows/evolve.md`: `phase_template` suggestion from domain pack
+  - `bin/viepilot.cjs`: `install-domain <pack-name>` subcommand for community packs
+  - 35 unit tests (phase108); full suite: 1618 tests pass
+
 ## [2.41.0] - 2026-04-24
 
 ### Added

package/bin/viepilot.cjs

@@ -567,6 +567,38 @@ async function main() {
     }
   }
 
+  if (command === 'install-domain') {
+    const packName = rest[0];
+    if (!packName) {
+      console.error('Usage: viepilot install-domain <pack-name>');
+      console.error('Example: viepilot install-domain fintech');
+      process.exit(1);
+    }
+    const npmPkg = `viepilot-domain-${packName}`;
+    const { execSync } = require('child_process');
+    const path = require('path');
+    const fs = require('fs');
+    try {
+      console.log(`Installing ${npmPkg}...`);
+      execSync(`npm install ${npmPkg}`, { stdio: 'inherit' });
+      // Copy domain-pack.json from installed package to lib/domain-packs/
+      const pkgRoot = path.dirname(require.resolve(`${npmPkg}/package.json`));
+      const packFile = path.join(pkgRoot, 'domain-pack.json');
+      if (fs.existsSync(packFile)) {
+        const dest = path.join(__dirname, '..', 'lib', 'domain-packs', `${packName}.json`);
+        fs.mkdirSync(path.dirname(dest), { recursive: true });
+        fs.copyFileSync(packFile, dest);
+        console.log(`Domain pack '${packName}' installed → lib/domain-packs/${packName}.json`);
+      } else {
+        console.warn(`Installed ${npmPkg} but no domain-pack.json found.`);
+      }
+      process.exit(0);
+    } catch (err) {
+      console.error(`Failed to install ${npmPkg}: ${err.message}`);
+      process.exit(1);
+    }
+  }
+
   if (command !== 'install' && command !== 'uninstall') {
     console.error(`Unknown command: ${command}`);
     printHelp();

package/bin/vp-tools.cjs

@@ -1203,6 +1203,80 @@ ${colors.cyan}Examples:${colors.reset}
       });
   },
 
+  /**
+   * ENH-073: Manage cross-project personas.
+   * persona get            → print active persona JSON
+   * persona infer [dir]    → run inferPersona, print result, update context-map
+   * persona list           → list all ~/.viepilot/personas/*.json
+   * persona set <name>     → set active persona by name
+   * persona auto-switch    → auto-detect and switch for cwd (called at skill start)
+   * persona context [dir]  → print persona-context.md content
+   */
+  'persona': (args) => {
+    const {
+      inferPersona, resolvePersona, generatePersonaContext,
+      readActivePersona, writePersona, setActivePersona, listPersonas,
+      updateContextMap, autoSwitch,
+    } = require('../lib/viepilot-persona.cjs');
+
+    const op = args[0] || 'get';
+    const dir = args[1] ? require('path').resolve(args[1]) : process.cwd();
+
+    if (op === 'get') {
+      const persona = readActivePersona();
+      if (!persona) { process.stdout.write('No active persona\n'); process.exit(0); }
+      process.stdout.write(JSON.stringify(persona, null, 2) + '\n');
+      process.exit(0);
+    }
+
+    if (op === 'list') {
+      const personas = listPersonas();
+      if (!personas.length) { process.stdout.write('No personas saved\n'); process.exit(0); }
+      for (const p of personas) {
+        const marker = p.active ? '[active] ' : '         ';
+        process.stdout.write(`${marker}${p.name}  domain:${p.domain}  confidence:${p.confidence}\n`);
+      }
+      process.exit(0);
+    }
+
+    if (op === 'set') {
+      const name = args[1];
+      if (!name) { process.stderr.write('Usage: persona set <name>\n'); process.exit(1); }
+      setActivePersona(name);
+      process.stdout.write(`Active persona set to: ${name}\n`);
+      process.exit(0);
+    }
+
+    if (op === 'infer') {
+      inferPersona(dir).then(persona => {
+        writePersona(persona.name, persona);
+        setActivePersona(persona.name);
+        updateContextMap(dir, persona.name);
+        process.stdout.write(JSON.stringify(persona, null, 2) + '\n');
+        process.exit(0);
+      }).catch(() => process.exit(0));
+      return;
+    }
+
+    if (op === 'auto-switch') {
+      autoSwitch(dir).then(() => process.exit(0)).catch(() => process.exit(0));
+      return;
+    }
+
+    if (op === 'context') {
+      (async () => {
+        let persona = resolvePersona(dir);
+        if (!persona) persona = await inferPersona(dir);
+        process.stdout.write(generatePersonaContext(persona) + '\n');
+        process.exit(0);
+      })().catch(() => process.exit(0));
+      return;
+    }
+
+    process.stderr.write(`Unknown persona op: ${op}\nUsage: persona get|infer|list|set|auto-switch|context\n`);
+    process.exit(1);
+  },
+
   /**
    * Scan installed skills and rebuild ~/.viepilot/skill-registry.json (BUG-019)
    */
@@ -1330,6 +1404,26 @@ ${colors.cyan}Examples:${colors.reset}
           'vp-tools check-update --force',
         ],
       },
+      'persona': {
+        usage: 'vp-tools persona <op> [dir]',
+        description: 'Manage cross-project personas (ENH-073)',
+        options: [
+          'get          Show active persona JSON',
+          'infer [dir]  Infer persona from project files + git',
+          'list         List all saved personas',
+          'set <name>   Set active persona by name',
+          'auto-switch  Auto-detect and switch persona for current directory',
+          'context [dir] Print persona-context.md content for current project',
+        ],
+        examples: [
+          'vp-tools persona get',
+          'vp-tools persona infer .',
+          'vp-tools persona list',
+          'vp-tools persona set auto-web-saas',
+          'vp-tools persona auto-switch',
+          'vp-tools persona context',
+        ],
+      },
       update: {
         usage: 'vp-tools update [--dry-run] [--yes] [--global]',
         description: 'Update viepilot to npm latest (local dependency, global install, or explicit --global)',
@@ -1391,6 +1485,7 @@ ${colors.cyan}Commands:${colors.reset}
   ${colors.bold}get-registry${colors.reset} [--id <id>] Output global skill registry as JSON
   ${colors.bold}scan-skills${colors.reset}               Scan installed skills → ~/.viepilot/skill-registry.json
   ${colors.bold}check-update${colors.reset} [--silent]   Check for latest ViePilot version on npm (24h cached)
+  ${colors.bold}persona${colors.reset} <op>              Manage user personas (get|infer|list|set|auto-switch|context)
   ${colors.bold}help${colors.reset} [command]           Show help (optionally for specific command)
 
 ${colors.cyan}Examples:${colors.reset}

package/docs/brainstorm/session-2026-04-24.md

@@ -0,0 +1,131 @@
+# Brainstorm Session — 2026-04-24
+
+## Session Info
+- **Date**: 2026-04-24
+- **Topic**: vp-persona — ViePilot Workflow Customization Skill
+- **Status**: Completed
+- **workflow_version**: 2.41.0
+
+## Core Idea
+
+A new skill `/vp-persona` that creates a **user-level, cross-project identity** for ViePilot.
+Lets users customize ALL ViePilot workflows to fit their domain, profession, and interests —
+without re-declaring context per project.
+
+## Problem Statement
+
+ViePilot is currently a general-purpose framework. Multi-domain professionals ("kiêm nhiệm")
+working across Web SaaS, Embedded, Data Science, Mobile face:
+- Brainstorm topics irrelevant to their domain
+- Wrong phase templates
+- No cross-project user identity
+- Must re-declare stack/context for every project
+
+## Key Design Decisions
+
+### 1. Multi-Persona architecture (not single profile)
+- `~/.viepilot/personas/` — named persona files
+- `~/.viepilot/persona.json` — active persona pointer
+- `~/.viepilot/context-map.json` — directory → persona bindings
+
+### 2. Layered resolution (3 layers)
+```
+Priority: project > session > global
+1. .viepilot/persona-override.json   ← per-project explicit
+2. context-map.json pattern match    ← directory-based auto
+3. ~/.viepilot/persona.json (active) ← global default
+```
+
+### 3. Switch + Merge both supported
+- **Switch**: bind project dir to a named persona, change with 1 command
+- **Merge**: create hybrid persona from multiple domains (e.g. IoT Full-stack = web-saas + embedded-iot)
+- Analogy: git branch (switch) + git merge (merge)
+
+### 4. Auto-detection from project files
+| Signal file | Detected domain |
+|------------|-----------------|
+| `package.json` + `prisma/` | web-saas |
+| `CMakeLists.txt` + `sdkconfig` | embedded |
+| `requirements.txt` + `notebooks/` | data-science |
+| `pubspec.yaml` / `*.xcodeproj` | mobile |
+| `Dockerfile` + `terraform/` | devops |
+| `pyproject.toml` + `langchain` | ai-product |
+
+### 5. Persona schema
+```json
+{
+  "name": "Web SaaS Dev",
+  "domain": "web-saas",
+  "role": "full-stack",
+  "stacks": ["nextjs", "nestjs", "postgresql"],
+  "team_size": "solo",
+  "output_style": "lean",
+  "brainstorm": {
+    "topic_priority": ["auth", "user-data", "api", "admin"],
+    "topic_skip": ["embedded", "content-mgmt"]
+  },
+  "phase_template": "lean-startup",
+  "interests": ["ai-integration", "saas", "startup"]
+}
+```
+
+### 6. Domain Packs (5 built-in + community)
+| Pack | Extra topics | Phase template | Extra architect pages |
+|------|-------------|----------------|----------------------|
+| `web-saas` | Billing, Multi-tenant, Onboarding | Auth→Core→Monetize→Scale | billing.html, tenant.html |
+| `data-science` | Dataset mgmt, Model versioning, Drift monitoring | Data→EDA→Train→Serve→Monitor | ml-pipeline.html |
+| `mobile` | Push, Offline sync, Store submit | Auth→Core→Offline→Submit | mobile-flow.html |
+| `devops` | IaC, CI/CD, SLO, Incident | Infra→CI/CD→Observe→Runbooks | infra-topology.html |
+| `ai-product` | LLM integration, RAG, Eval/feedback | Wrapper→Prompt→RAG→Eval→UX | llm-arch.html |
+
+### 7. vp-persona commands
+```
+/vp-persona                      → Show active persona
+/vp-persona --create web-saas    → Create new persona (wizard)
+/vp-persona --switch embedded    → Switch active persona
+/vp-persona --list               → List all personas
+/vp-persona --bind . web-saas    → Bind current dir to persona
+/vp-persona --auto               → Enable auto-detect
+/vp-persona --merge web embedded → Create hybrid persona
+/vp-persona --export / --import  → Backup/share personas
+```
+
+### 8. Workflow adaptations when persona active
+- **vp-brainstorm**: topic order reordered by priority; skipped topics hidden; domain pack topics injected
+- **vp-auto**: stack preflight uses persona stacks automatically; persona-context.md injected per task
+- **vp-crystallize**: output_style "lean" → shorter docs; "enterprise" → full docs + compliance
+- **vp-evolve**: new phase suggestions follow persona's phase_template
+
+## Phases
+
+### Phase 1 — Foundation
+- `vp-persona` skill + wizard (5-question Q&A)
+- `~/.viepilot/personas/` multi-file support
+- `persona-context.md` injection into all skills
+
+### Phase 2 — Multi-context
+- `context-map.json` + directory binding (`--bind`)
+- Auto-detection from project files
+- Session-start smart prompt for multi-domain users
+
+### Phase 3 — Domain Packs
+- 5 built-in domain packs (web-saas, data-science, mobile, devops, ai-product)
+- Domain pack schema + community extensibility (npm install viepilot-domain-*)
+
+### Phase 4 — Merge + Advanced
+- `/vp-persona --merge` hybrid personas
+- Interest-based proactive hints in brainstorm
+- Per-project `persona-override.json`
+
+## Open Questions
+- Should domain packs be separate npm packages or bundled?
+- How to handle conflicts when merge produces duplicate topics?
+- Should `persona-context.md` be injected as a system-prompt prefix or as a workflow step?
+
+## Project meta intake (FEAT-009)
+- Profile binding: skipped (this is ViePilot framework repo itself)
+
+## Background extracted ideas
+- Interest-based proactive suggestions (e.g. "ai-integration" interest → proactive LLM arch hints)
+- Community domain pack registry (viepilot-domain-fintech, viepilot-domain-healthcare...)
+- Persona export/import for team sharing (onboard new dev with same persona)

package/docs/brainstorm/session-2026-04-25.md

@@ -0,0 +1,109 @@
+# Brainstorm Session — 2026-04-25
+
+## Meta
+- **Session ID**: session-2026-04-25
+- **Topic**: Design.MD × ViePilot Integration (ENH-076)
+- **Status**: Completed
+- **workflow_version**: 2.43.2
+- **Participants**: User + AI
+
+## Summary
+Research session trên tiêu chuẩn Design.MD (Google Labs, April 2026) và brainstorm
+cách tích hợp nó toàn diện vào ViePilot workflow — từ brainstorm → crystallize → auto.
+
+## Research: Design.MD Standard
+
+Design.MD là file specification từ Google Labs (21/04/2026, Apache 2.0) — Markdown + YAML
+front matter mô tả visual design system để AI coding agents hiểu brand identity.
+
+- **Creator**: Google Labs / Google Stitch 2.0
+- **Format**: YAML front matter (tokens) + Markdown sections (rationale)
+- **Adopted by**: Claude Code, Cursor, Windsurf, Kiro
+- **Community**: awesome-design-md — 55+ brand examples
+
+### Standard sections
+- `colors`: semantic palette (primary, surface, accent, error, success, warning)
+- `typography`: fontFamily, fontSize, fontWeight, lineHeight
+- `spacing`: base unit + scale
+- `rounded`: corner radius tokens
+- `components`: component-specific tokens
+
+---
+
+## Decisions
+
+### D1: Scope — 5 integration points across ViePilot
+1. **vp-brainstorm**: auto-extract design tokens → generate design.md in session dir
+2. **vp-crystallize**: mandatory-acknowledge gate + export to project root
+3. **vp-auto**: preflight reads design.md, injects TOKEN_MAP into UI tasks
+4. **new skill vp-design**: init/sync/audit/import commands
+5. **Architect workspace**: design.html visual page
+
+### D2: vp-brainstorm token extraction
+- Triggered when `--ui` flag OR ≥2 design keywords detected
+- tokens extracted to `notes.md ## design_tokens` YAML section
+- design.md written to `.viepilot/ui-direction/{session-id}/design.md`
+
+### D3: vp-crystallize gate — mandatory-acknowledge (not hard block)
+- Trigger: design.md exists OR design_tokens in notes.md OR ≥3 design keywords
+- AUQ with 3 options: Export (recommended) / Finalize & export / Skip with note
+- Skip writes `design_md_status: skipped` (idempotent — won't re-ask same session)
+- Export path: Step 1D.14 — after existing coverage exports
+- Output: project root design.md + ARCHITECTURE.md ## Design System + PROJECT-CONTEXT.md flag
+
+### D4: vp-auto — 3 injection levels
+- Level 1: Silent context injection (always for UI tasks)
+- Level 2: Checklist items (when task has explicit UI acceptance criteria)
+- Level 3: Post-task compliance audit (when task output is HTML file)
+- UI keyword detection: html/css/style/component/tailwind/layout/button/card/form/page etc.
+- Edge cases: backend-only tasks skip, monorepo nearest-design.md wins
+
+### D5: vp-design skill commands
+- `--init`: Q&A from scratch OR import from awesome-design-md (55+ brands)
+- `--sync`: tokens → Tailwind config / CSS variables / SCSS
+- `--audit`: scan implementation vs spec, report deviations
+- `--import [brand]`: fetch community template (Linear, Notion, Stripe...)
+
+### D6: ARCHITECTURE.md Design System section format
+- Token summary table (colors/typography/spacing/rounded)
+- Design principles from design.md ## Overview
+- Reference to design.md at project root
+
+---
+
+## Open Questions
+
+- Q1: Should design.md be committed to git by default? (Yes — it's a project artifact like ARCHITECTURE.md)
+- Q2: For vp-design --sync with Tailwind: CSS custom properties or direct tailwind.config.js extension?
+  → Probably both, detected by project structure
+- Q3: awesome-design-md catalog integration — fetch at runtime vs. bundle with ViePilot?
+  → Fetch at runtime (keep ViePilot lean)
+
+---
+
+## Phases
+
+### Phase 1 (ENH-076 core)
+- 76.1: vp-brainstorm design token extraction + design.md generation
+- 76.2: vp-crystallize Step 1D.14 mandatory gate + export pipeline
+- 76.3: vp-auto preflight 5.5 + TOKEN_MAP injection + post-task audit
+- 76.4: new skill vp-design (SKILL.md + workflows/design.md)
+- 76.5: Architect workspace design.html page
+
+### Phase 2 (polish)
+- 76.6: awesome-design-md runtime catalog integration
+- 76.7: vp-design --sync multi-target (Tailwind + CSS vars + SCSS)
+- 76.8: vp-design --audit full HTML/CSS scan
+
+---
+
+## Action Items
+- [ ] Log ENH-076 via /vp-request
+- [ ] Plan phases via /vp-evolve
+- [ ] Execute via /vp-auto
+
+---
+
+## Project Meta Intake (FEAT-009)
+- Profile already bound — skip intake.
+

package/lib/domain-packs/ai-product.json

@@ -0,0 +1,33 @@
+{
+  "id": "ai-product",
+  "label": "AI Product / LLM Application",
+  "topic_priority": ["llm-integration", "rag-pipeline", "prompt-mgmt", "eval", "ux", "guardrails"],
+  "extra_topics": [
+    {
+      "id": "llm-integration",
+      "label": "LLM Integration",
+      "questions": ["LLM provider (OpenAI/Anthropic/Gemini/local)?", "Model selection strategy (cost vs quality)?", "Streaming vs batch response?", "Fallback chain if primary model fails?"]
+    },
+    {
+      "id": "rag-pipeline",
+      "label": "RAG Pipeline",
+      "questions": ["Document ingestion format (PDF/HTML/Markdown)?", "Chunking strategy (fixed/semantic/hierarchical)?", "Vector DB (Pinecone/Qdrant/pgvector/Chroma)?", "Embedding model?", "Retrieval method (semantic/hybrid/BM25)?"]
+    },
+    {
+      "id": "prompt-mgmt",
+      "label": "Prompt Management",
+      "questions": ["Prompt versioning strategy?", "Prompt storage (DB/Git/Langfuse)?", "System prompt vs user prompt separation?", "Prompt injection protection?"]
+    },
+    {
+      "id": "eval-feedback",
+      "label": "Eval & Feedback Loop",
+      "questions": ["Eval framework (RAGAS/DeepEval/custom)?", "Human feedback collection (thumbs up/down/rubric)?", "Evals in CI/CD pipeline?", "Latency + cost tracking per request?"]
+    }
+  ],
+  "phase_template": {
+    "name": "ai-product",
+    "phases": ["LLM Wrapper & Auth", "Prompt Engineering & RAG", "Eval Pipeline", "UX & Feedback Loop", "Guardrails & Cost Control"]
+  },
+  "architect_pages": ["llm-arch.html", "rag-flow.html"],
+  "stacks_hint": ["langchain", "openai", "anthropic", "pgvector", "fastapi", "nextjs", "redis"]
+}

package/lib/domain-packs/data-science.json

@@ -0,0 +1,33 @@
+{
+  "id": "data-science",
+  "label": "Data Science / ML",
+  "topic_priority": ["dataset", "eda", "model-training", "evaluation", "serving", "monitoring"],
+  "extra_topics": [
+    {
+      "id": "dataset",
+      "label": "Dataset Management",
+      "questions": ["Data sources (structured/unstructured/streaming)?", "Data versioning strategy (DVC/Delta Lake/LakeFS)?", "PII/sensitive data handling?", "Train/val/test split strategy?"]
+    },
+    {
+      "id": "model-versioning",
+      "label": "Model Versioning",
+      "questions": ["Model registry (MLflow/W&B/SageMaker)?", "Experiment tracking metadata?", "Artifact storage (S3/GCS/local)?"]
+    },
+    {
+      "id": "drift-monitoring",
+      "label": "Drift & Quality Monitoring",
+      "questions": ["Data drift detection (Evidently/WhyLogs/custom)?", "Model performance degradation alerts?", "Retraining trigger strategy?"]
+    },
+    {
+      "id": "eval-pipeline",
+      "label": "Evaluation Pipeline",
+      "questions": ["Offline eval metrics (AUC/F1/BLEU/ROUGE)?", "Human eval process?", "A/B testing framework for model versions?"]
+    }
+  ],
+  "phase_template": {
+    "name": "ml-pipeline",
+    "phases": ["Data Ingestion & EDA", "Feature Engineering & Training", "Evaluation & Registry", "Serving & API", "Monitoring & Retraining"]
+  },
+  "architect_pages": ["ml-pipeline.html", "data-lineage.html"],
+  "stacks_hint": ["python", "pandas", "pytorch", "fastapi", "mlflow", "postgresql", "redis"]
+}

package/lib/domain-packs/devops.json

@@ -0,0 +1,33 @@
+{
+  "id": "devops",
+  "label": "DevOps / Platform Engineering",
+  "topic_priority": ["infra", "ci-cd", "observability", "slo", "incident-mgmt", "security"],
+  "extra_topics": [
+    {
+      "id": "iac",
+      "label": "Infrastructure as Code",
+      "questions": ["IaC tool (Terraform/Pulumi/CloudFormation/CDK)?", "Cloud provider (AWS/GCP/Azure/multi)?", "State backend (S3/GCS/Terraform Cloud)?", "Module/stack organization strategy?"]
+    },
+    {
+      "id": "ci-cd",
+      "label": "CI/CD Pipeline",
+      "questions": ["CI platform (GitHub Actions/GitLab CI/CircleCI/Jenkins)?", "Deploy strategy (blue-green/canary/rolling)?", "Secrets management (Vault/AWS SSM/GitHub Secrets)?", "PR-level preview environments?"]
+    },
+    {
+      "id": "slo-sla",
+      "label": "SLO / SLA",
+      "questions": ["Availability target (99.9%/99.99%)?", "Latency SLOs (p95/p99)?", "Error budget policy?", "SLO monitoring tool (Datadog/Prometheus/Grafana)?"]
+    },
+    {
+      "id": "incident-mgmt",
+      "label": "Incident Management",
+      "questions": ["On-call rotation tool (PagerDuty/OpsGenie/Rootly)?", "Runbook format and storage?", "Post-mortem process?", "Alert fatigue mitigation strategy?"]
+    }
+  ],
+  "phase_template": {
+    "name": "infra-ops",
+    "phases": ["Infrastructure Foundation", "CI/CD & Automation", "Observability & Alerting", "Runbooks & Incident Response"]
+  },
+  "architect_pages": ["infra-topology.html", "slo.html"],
+  "stacks_hint": ["terraform", "docker", "kubernetes", "prometheus", "grafana", "github-actions"]
+}

package/lib/domain-packs/mobile.json

@@ -0,0 +1,33 @@
+{
+  "id": "mobile",
+  "label": "Mobile App",
+  "topic_priority": ["auth", "core-features", "offline-sync", "push-notifications", "app-store", "deep-links"],
+  "extra_topics": [
+    {
+      "id": "push-notifications",
+      "label": "Push Notifications",
+      "questions": ["Push provider (FCM/APNs/OneSignal/Expo)?", "Notification categories and opt-in flow?", "Deep link handling from notification tap?", "Background/foreground handling?"]
+    },
+    {
+      "id": "offline-sync",
+      "label": "Offline Sync",
+      "questions": ["Offline-first or online-required?", "Conflict resolution strategy (last-write-wins/CRDT/manual)?", "Local storage (SQLite/Realm/AsyncStorage/Core Data)?", "Sync trigger (background/explicit/realtime)?"]
+    },
+    {
+      "id": "app-store",
+      "label": "App Store Submission",
+      "questions": ["Target platforms (iOS/Android/both)?", "App review checklist (privacy policy, ATT prompt, entitlements)?", "CI/CD for store deployment (Fastlane/EAS/Bitrise)?"]
+    },
+    {
+      "id": "deep-links",
+      "label": "Deep Links & Universal Links",
+      "questions": ["URL scheme vs universal links?", "Deferred deep linking (install → open specific screen)?", "Attribution provider (Branch/AppsFlyer/Adjust)?"]
+    }
+  ],
+  "phase_template": {
+    "name": "mobile-launch",
+    "phases": ["Auth & Navigation", "Core Features", "Offline & Sync", "Store Submission & Launch"]
+  },
+  "architect_pages": ["mobile-flow.html", "push.html"],
+  "stacks_hint": ["react-native", "expo", "flutter", "firebase", "postgresql"]
+}

package/lib/domain-packs/web-saas.json

@@ -0,0 +1,33 @@
+{
+  "id": "web-saas",
+  "label": "Web SaaS",
+  "topic_priority": ["auth", "user-data", "api", "billing", "admin", "onboarding", "content-mgmt"],
+  "extra_topics": [
+    {
+      "id": "billing",
+      "label": "Billing & Subscriptions",
+      "questions": ["Payment provider (Stripe/Paddle/LemonSqueezy)?", "Pricing model (flat/usage/per-seat)?", "Free trial or freemium tier?", "Proration on plan change?"]
+    },
+    {
+      "id": "multi-tenant",
+      "label": "Multi-tenancy",
+      "questions": ["Tenant isolation: row-level, schema-per-tenant, or separate DB?", "How are tenants identified (subdomain/slug/org)?", "Cross-tenant data visibility rules?"]
+    },
+    {
+      "id": "onboarding",
+      "label": "User Onboarding",
+      "questions": ["Onboarding flow steps (email verify → profile → invite team)?", "Guided setup wizard?", "Empty-state design for new accounts?"]
+    },
+    {
+      "id": "trial-freemium",
+      "label": "Trial / Freemium",
+      "questions": ["Trial duration?", "Feature gating strategy (usage caps vs feature flags)?", "Upgrade CTA placement?"]
+    }
+  ],
+  "phase_template": {
+    "name": "lean-startup",
+    "phases": ["Auth & Identity", "Core Features", "Monetization", "Scale & Ops"]
+  },
+  "architect_pages": ["billing.html", "tenant.html"],
+  "stacks_hint": ["nextjs", "nestjs", "postgresql", "stripe", "redis", "tailwind"]
+}