chore(llm-security): v7.7.2 — language consistency pass

~/.claude/CLAUDE.md specifies English for code and documentation,
Norwegian for dialog only. Norwegian had crept into surface text
across v7.5-v7.7. Translated to English in eight surfaces.

No scanner, hook, or behavior changes — purely surface text.

- 18 skill commands: the HTML Report-step now reads "HTML report:
  [Open in browser]" instead of "HTML-rapport: [Åpne i nettleser]"
- scripts/lib/report-renderers.mjs: key-stat labels, lede defaults,
  table headers, maturity-ladder descriptions, action-tier labels,
  clean buckets, dry-run/apply copy, and JS comments. Regex
  alternations /^high|^høy/ and /resolution|løsning/i preserved.
- playground/llm-security-playground.html: same renderer changes
  mirrored bit-identical, plus playground-only UI strings (catalog,
  breadcrumb aria-label, theme toggle, builder-modal hint,
  guide-panel "no projects yet", delete confirmation, alert/copy).
  Demo-state fixture content for dft-komplett-demo preserved
  (intentional Norwegian persona).
- agents/skill-scanner-agent.md + agents/mcp-scanner-agent.md:
  Generaliseringsgrense + Parallell Read-strategi sections translated
  to Generalization boundary + Parallel Read strategy.
- README.md: playground architecture prose + Recent versions table
  (v7.5.0 — v7.7.1).
- CLAUDE.md: v7.7.1 highlights translated, new v7.7.2 highlights
  added.
- ../../README.md: llm-security v7.5.0 — v7.7.1 bullets.
- ../../CLAUDE.md: llm-security catalog entry.
- docs/scanner-reference.md: six runnable-examples table cells.
- docs/version-history.md: new v7.7.2 entry. v7.5-v7.7 narrative
  sections left in original language (deferred per operator).
- Version bumped 7.7.1 → 7.7.2 in package.json,
  .claude-plugin/plugin.json, README badge + Recent versions,
  CLAUDE.md header + state, docs/version-history.md, playground
  renderHome hardcoded string, root README + CLAUDE.md llm-security
  entries.

Tests: 1820/1820 green. CLI smoke-test: 18/18 commandIds produce
>138 KB self-contained HTML. Browser-dogfood verified.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

.claude-plugin/marketplace.json

@@ -21,14 +21,9 @@
       "description": "Multi-agent workflow for analyzing, reporting, and optimizing Claude Code configuration across your entire machine"
     },
     {
-      "name": "ultraplan-local",
+      "name": "voyage",
-      "source": "./plugins/ultraplan-local",
+      "source": "./plugins/voyage",
-      "description": "Four-command context-engineering pipeline (brief → research → plan → execute) with specialized agent swarms, external research triangulation, adversarial review, session decomposition, and headless execution"
+      "description": "Voyage — brief, research, plan, execute, review, continue. Contract-driven Claude Code pipeline with specialized agent swarms, external research triangulation, adversarial review, post-hoc independent review with Handover 6 feedback loop, multi-session resumption, session decomposition, and headless execution. /trekbrief, /trekplan, and /trekreview each end by building a self-contained operator-annotation HTML (scripts/annotate.mjs, modelled on claude-code-100x): pencil-toggle annotation mode, select text or click any element, pick intent (Fiks/Endre/Spørsmål), comment, Copy Prompt, paste back, Claude revises the .md."
-    },
-    {
-      "name": "ultra-cc-architect",
-      "source": "./plugins/ultra-cc-architect",
-      "description": "Match a task brief and research against available Claude Code features (Hooks, Subagents, Skills, MCP, Plan Mode, Worktrees, Background Agents) with brief-anchored rationale and explicit coverage gaps. Includes the skill-factory authoring command. Pre-release (v0.1.0)."
     },
     {
       "name": "linkedin-thought-leadership",
@@ -54,6 +49,16 @@
       "name": "okr",
       "source": "./plugins/okr",
       "description": "Expert OKR guidance for Norwegian public sector. Write, review, cascade, track and govern OKR based on Google/Doerr methodology adapted for 4-month tertial cycles."
+    },
+    {
+      "name": "human-friendly-style",
+      "source": "./plugins/human-friendly-style",
+      "description": "Shared Claude Code output style for the ktg-plugin-marketplace. Plain-language tone — explains what and why, hides paths/JSON/stack traces by default, matches the user's language."
+    },
+    {
+      "name": "claude-design",
+      "source": "./plugins/claude-design",
+      "description": "End-to-end facilitator for prompting Claude Design (claude.ai/design) — idea to copy-paste-ready prompt with iteration coaching, citing Anthropic primary sources."
     }
   ]
 }

.gitleaks.toml

@@ -0,0 +1,14 @@
+title = "ktg-plugin-marketplace gitleaks config"
+
+# Extend default rules
+[extend]
+useDefault = true
+
+# Path-based allowlist: vendored design-system MANIFEST.json files
+# contain SHA-256 hashes per file by design (drift detection).
+# These are public file integrity hashes, not secrets.
+[[allowlists]]
+description = "Vendored design-system MANIFEST files (SHA-256 file hashes)"
+paths = [
+  '''playground/vendor/playground-design-system/MANIFEST\.json$''',
+]

.mailmap

@@ -0,0 +1,4 @@
+# Konsoliderer Git-identiteter for statistikk og shortlog.
+# Se: https://git-scm.com/docs/gitmailmap
+
+Kjell Tore Guttormsen <hello@fromaitochitta.com> <ktg@humanize.no>

CLAUDE.md

@@ -10,14 +10,17 @@ plugins/
   config-audit/          v3.1.0  — Configuration intelligence (health, opportunities, auto-fix, whats-active)
   graceful-handoff/      v2.1.0  — Auto-trigger handoff via Stop hook (skill + JSON pipeline + 4-step model-aware context resolution)
   linkedin-thought-leadership/  v1.2.0  — LinkedIn content pipeline + analytics
-  llm-security/          v6.0.0  — Security scanning, auditing, threat modeling
+  llm-security/          v7.7.2  — Security scanning, auditing, threat modeling. HTML report output for all 18 skill commands (render-report CLI + canonical ESM module mirrored bit-identical into the playground). v7.7.2 translated the remaining Norwegian surface text in the playground UI, the canonical renderer, the agent prompts, and the README/CLAUDE.md state sections to English. v7.7.1 stripped the playground to the catalog as the only routable surface.
-  ms-ai-architect/       v1.8.0  — Microsoft AI architecture (Cosmo Skyberg persona)
+  ms-ai-architect/       v1.15.0 — Microsoft AI architecture (Cosmo Skyberg persona) + manual KB-refresh slash command + v3 project-view (sidebar med 17 artifacts + main + import-modal overlay, v2-surface fjernet i v1.15.0)
   okr/                   v1.0.0  — OKR guidance for Norwegian public sector
-  ultraplan-local/       v3.1.0  — Brief, research, plan, execute (four-command universal pipeline)
+  voyage/                v5.0.3  — Brief, research, plan, execute, review, continue. Contract-driven Claude Code pipeline (six-command universal pipeline + multi-session resumption + --gates autonomy chain). /trekbrief, /trekplan, and /trekreview each end by running scripts/annotate.mjs against the just-written .md and printing the file:// link to a self-contained operator-annotation HTML modelled on claude-code-100x/build-site.js: pencil-toggle annotation mode, select text or click any element, choose intent (Fiks/Endre/Spørsmål), comment, sidebar groups by section with delete + Copy Prompt, localStorage persistence per artifact path. v5.0.0 removed the v4.2/v4.3 bespoke playground + /trekrevise + Handover 8; v5.0.1 pointed at /playground document-critique (wrong direction); v5.0.2 was operator-led but too thin; v5.0.3 matches the reference the operator pointed at from day one.
-  ultra-cc-architect/    v0.1.0  — Claude-Code-specific architecture matching + skill-factory (extracted from ultraplan-local in v3.0.0)
+
+shared/
+  playground-design-system/  v0.6.0 — Aksel/Digdir-aligned CSS design system + JSON schemas + self-hosted Inter/JetBrains Mono/Source Serif 4 fonts. Tier 1 base + Tier 2 + Tier 3 wave 1+2 (20 components) + Tier 4 project-view-arketype (v0.6.0 — sidebar + main + import-modal overlay). Consumed by ms-ai-architect, okr, llm-security, voyage, config-audit.
+  playground-examples/             — Reference scenarios (ROS-Lier, OKR-Bærum, security-Direktorat) + showcase landing + 12 isolated Tier 3 wave 2 component demos under components/
 ```
 
-Hvert plugin er selvstendig med egen CLAUDE.md, README, hooks, agents og commands.
+Hvert plugin er selvstendig med egen CLAUDE.md, README, hooks, agents og commands. `shared/` inneholder marketplace-nivå infrastruktur som flere plugins bygger på.
 
 ## Konvensjoner
 
@@ -26,12 +29,13 @@ Hvert plugin er selvstendig med egen CLAUDE.md, README, hooks, agents og command
 - **Git:** Forgejo (`git.fromaitochitta.com/open/ktg-plugin-marketplace`). Aldri GitHub.
 - **Hooks:** Alltid Node.js (.mjs), aldri bash. Cross-platform.
 - **Avhengigheter:** Null npm dependencies i hooks/scannere. `node:test` for tester.
-- **PRs:** Aksepteres ikke. Issues velkommen.
+- **Bidrag:** Issues velkommen som signaler. PRs ikke akseptert. Fork-and-own er anbefalt adopsjonsmodell — se `GOVERNANCE.md`.
 - **Lisens:** MIT, alle plugins
 - **Docs ved endring (OBLIGATORISK):** Enhver feature-endring som pusher til Forgejo MÅ oppdatere alle tre doc-nivåer i SAMME commit eller umiddelbart etter:
   1. Plugin `README.md` — detaljert dokumentasjon av endringen
   2. Plugin `CLAUDE.md` — arkitektur/oversikt
   3. Rot-`README.md` — marketplace-landingssiden (`git.fromaitochitta.com/open/ktg-plugin-marketplace`)
+- **Playground-oppdatering:** Ved endring av plugin playground HTML eller delt design-system, følg prosedyren i `shared/PLAYGROUND-MAINTENANCE.md` (4 spor: HTML-endring, DS-endring, screenshots, release).
 
 ## Sesjonsfiler (lokale, gitignored)
 
@@ -49,3 +53,20 @@ Disse trackes IKKE i git. Oppdater ved sesjonsslutt.
 3. Les REMEMBER.md og TODO.md for sesjonsstatus
 4. Jobb innenfor scope
 5. Oppdater REMEMBER.md ved avslutning
+
+## Communication patterns
+
+### Linking to local files
+
+When pointing to local files in responses, always use markdown link syntax with a descriptive name:
+
+- Use `[Human-friendly name](file:///absolute/path)` — never bare `file:///...` URLs or autolinks `<file://...>`.
+- Always use absolute paths. Never `~/` or relative paths.
+- For multiple files, render as a bullet list of named markdown links.
+
+Why: bare `file://` URLs only render the first as clickable across multiple lines. Named markdown links make each entry independently clickable and look cleaner.
+
+Example:
+
+- [Brief](file:///Users/ktg/.../brief.html)
+- [Research summary](file:///Users/ktg/.../research/summary.md)

GOVERNANCE.md

@@ -0,0 +1,131 @@
+# Governance
+
+How this marketplace is maintained, what you can expect from upstream, and how it's meant to be used.
+
+## TL;DR
+
+- Solo-maintained, AI-assisted development, MIT licensed.
+- **Fork-and-own is the default model.** Upstream is a starting point, not a vendor.
+- Issues welcome as signals. Pull requests are not accepted — see [Why no PRs](#pull-requests--no).
+- No SLA. Best-effort bug fixes and security advisories. Breaking changes happen and are noted in each plugin's CHANGELOG.
+
+---
+
+## Can I trust this?
+
+Be honest with yourself about what you're adopting:
+
+- **One maintainer.** If I get hit by a bus, the bus wins. The repos stay up under MIT, but no one owes you a fix.
+- **AI-generated code with human review.** Every plugin is built through dialog-driven development with Claude Code. I read, test, and judge the output before it ships, but I'm not auditing every line the way a security firm would. Treat it accordingly.
+- **No commercial interests.** I'm not selling a SaaS, not steering you toward a paid tier, not collecting telemetry. The plugins run locally in your Claude Code installation.
+- **MIT licensed.** Fork it, modify it, ship it under your own name.
+
+If you work somewhere that needs vendor accountability, support contracts, or signed assurances — **this isn't that.** Use it as a reference implementation, fork it into your own organization, and own the result.
+
+---
+
+## How this is meant to be used
+
+### Fork-and-own
+
+The intended workflow:
+
+1. **Fork** the marketplace (or a single plugin) into your own organization or namespace.
+2. **Tailor** it to your context — terminology, integrations, cycle lengths, regulatory framing, whatever doesn't fit out of the box.
+3. **Maintain it yourself.** Treat your fork as the canonical version for your team.
+4. **Watch upstream selectively.** Cherry-pick changes that help, ignore changes that don't. There's no obligation to stay in sync.
+
+This isn't a workaround for not accepting PRs. It's the actual recommended adoption pattern, especially for plugins like `okr` and `ms-ai-architect` where every Norwegian public sector organization will need its own tildelingsbrev mappings, terminology, and integrations. A central "one true plugin" would be wrong for everyone.
+
+### What to change first when you fork
+
+Each plugin differs, but the common edits are:
+
+- **Identity** — rename the plugin, replace authorship, update README.
+- **External integrations** — issue trackers, knowledge bases, dashboards, observability backends. The plugins ship as starting points, not pre-wired. Every organization must configure its own integrations.
+- **Norwegian-specific framing** — relevant for `okr` and `ms-ai-architect`. Other plugins are jurisdiction-neutral. Rewrite for your jurisdiction if you're outside Norway.
+- **Reference docs** — the knowledge base in each plugin reflects my reading. Replace with your organization's authoritative sources.
+- **Hooks and policies** — security thresholds, blocked commands, and audit gates are tuned to my taste. Tune them to yours.
+
+### Staying current with upstream
+
+If you want to pull in upstream changes later:
+
+- **Cherry-pick, don't merge.** Each plugin moves independently and breaking changes land without ceremony.
+- **Read the CHANGELOG first.** Every plugin has one.
+- **Keep your customizations in clearly-named files.** The harder upstream is to merge cleanly, the more painful staying current becomes. A `local/` directory or `*.local.md` convention helps.
+
+---
+
+## What upstream provides
+
+| | What I do | What I don't |
+|---|---|---|
+| **Bug fixes** | Best-effort when I notice or get a clear report | No SLA, no triage commitment |
+| **Security issues** | Investigate within reasonable time, document in CHANGELOG | No CVE process, no embargo coordination |
+| **New features** | When they fit my own usage | Not on request |
+| **Norwegian public sector context** | Kept current as long as the project lives | If I lose interest or change jobs, the framing freezes |
+| **Breaking changes** | Documented in CHANGELOG | They happen — version pin if you need stability |
+| **Compatibility** | Tracked against current Claude Code releases | No long-term support branches |
+
+If any of this is a dealbreaker — fork now, version-pin, and stop reading upstream.
+
+---
+
+## How to contribute
+
+### Issues — yes, please
+
+Issues are the most valuable thing you can send me:
+
+- **Bug reports** with reproduction steps. Even a screenshot helps.
+- **Use-case feedback.** "I tried to use this in my organization and X didn't fit" is genuinely useful, even if I can't fix it for you.
+- **Pointers to better sources.** If you know a DFØ veileder, an NSM guideline, or an academic paper that contradicts what's in a knowledge base, tell me.
+- **Security findings.** See each plugin's `SECURITY.md` for disclosure preference where one exists; otherwise email rather than open a public issue.
+
+### Pull requests — no
+
+This is deliberate, not laziness:
+
+- **Solo review is a bottleneck.** Honest PR review takes me longer than rewriting from scratch. The math doesn't work.
+- **Forks are where the value is.** The fork-and-own model means upstream consolidation isn't the point. Your organization's adaptations belong in your fork, not mine.
+- **AI-generated code complicates provenance.** Every line here is produced through dialog with Claude Code, with me as the judge. Mixing in PRs from contributors with different processes and licensing assumptions creates a mess I'd rather not untangle.
+
+If you've built something useful on top of a fork, **publish it under your own name and link back.** I'll happily list notable forks here once they exist.
+
+### Notable forks
+
+*(To be populated as forks emerge. If you've forked one of these plugins for production use, open an issue and I'll add a link.)*
+
+---
+
+## Relationship between plugins
+
+These plugins are **independent**. Install one without the others, fork one without the others. They share conventions (slash command naming, hook patterns, AI-generated disclosure) but no runtime dependencies.
+
+The marketplace is a **catalog**, not a suite. Don't fork the whole repo unless you actually want to maintain everything.
+
+---
+
+## Versioning and stability
+
+- **Semantic versioning per plugin.** Each plugin has its own `CHANGELOG.md` and version number.
+- **Breaking changes happen.** I bump the major version when they do, but I don't run an LTS branch.
+- **Pin your version.** If stability matters more than features, install a specific version and stay there until you choose to upgrade.
+
+---
+
+## Public sector adoption notes
+
+For Norwegian etater specifically:
+
+- **DPIA-relevant data flows are documented in the relevant plugin README where applicable.** Read them before installation.
+- **No data leaves your machine** beyond what Claude Code itself sends to Anthropic. The plugins themselves do not call external services unless you configure an integration.
+- **Drøftingsplikt and ledelsesansvar** are not replaced by these tools. The `okr` plugin coaches; it does not decide. The `ms-ai-architect` plugin advises; it does not approve.
+- **Choose your Claude deployment carefully.** claude.ai vs. API direct vs. Bedrock in EU region have different data residency profiles. The plugins don't choose for you.
+
+---
+
+## License
+
+MIT for all plugins in this marketplace. See each plugin's `LICENSE` file.

README.md

@@ -2,7 +2,7 @@
 
 Open-source Claude Code plugins for AI-assisted development, security, and planning.
 
-Built for my own Claude Code workflow and shared openly for anyone who finds them useful. Solo project — bug reports and feature requests are welcome, pull requests are not accepted.
+Built for my own Claude Code workflow and shared openly for anyone who finds them useful. Solo-maintained, AI-assisted, fork-and-own. Issues are welcome as signals; pull requests are not accepted. See [GOVERNANCE.md](GOVERNANCE.md) for what upstream provides and how this is meant to be used.
 
 ## AI-generated code disclosure
 
@@ -26,7 +26,7 @@ Then open Claude Code and type `/plugin` to browse and install plugins from the
 
 ## Plugins
 
-### [LLM Security](plugins/llm-security/) `v7.3.1`
+### [LLM Security](plugins/llm-security/) `v7.7.2`
 
 Security scanning, auditing, and threat modeling for agentic AI projects.
 
@@ -36,6 +36,13 @@ Built on OWASP LLM Top 10 (2025), OWASP Agentic AI Top 10, and the AI Agent Trap
 - **Deterministic scanning** — 23 Node.js scanners (10 orchestrated + 13 standalone) for byte-level analysis: Shannon entropy, Unicode codepoints, typosquatting detection, taint flow, DNS resolution, git forensics, AI-BOM, attack simulation, IDE extension prescan (VS Code + JetBrains — URL fetch from Marketplace / OpenVSX / direct VSIX / JetBrains Marketplace, hardened ZIP extractor for zip-slip / symlinks / bombs, plus OS sandbox via `sandbox-exec` / `bwrap` so the kernel enforces FS confinement), MCP cumulative-drift baseline reset (E14 — sticky baseline catches slow-burn rug-pulls). Bash-normalize T1-T6 for obfuscation-resistant denylists
 - **Advisory analysis** — 20 commands that scan, audit, and model threats with structured reports, letter grades, and actionable remediation
 - **Enterprise governance** — Compliance mapping (EU AI Act, NIST AI RMF, ISO 42001), SARIF 2.1.0 output, structured audit trail, policy-as-code, standalone CLI
+- **v7.7.2 language consistency pass (2026-05-19)** — Norwegian had crept into surface text across v7.5-v7.7. Per the `~/.claude/CLAUDE.md` convention (English for code and documentation, Norwegian for dialog only), this release translates the HTML Report-step in all 18 skill commands, the canonical CLI renderer `scripts/lib/report-renderers.mjs`, the playground UI strings, the skill-scanner and mcp-scanner agent prompts, the marketplace + plugin README/CLAUDE.md state sections, and six table cells in `docs/scanner-reference.md`. Demo-state fixture content for the `dft-komplett-demo` project (intentional Norwegian persona) and regex alternations that match Norwegian-language report markdown (`/^high\|^høy/`, `/resolution\|løsning/`) were preserved. No scanner, hook, or behavior changes — purely surface text
+- **v7.7.1 playground UX strip (2026-05-18)** — Operator feedback immediately after v7.7.0: the catalog became the only routable surface in the playground (the onboarding/home/project render functions remain in source but are not routable). Topbar simplified to a `Catalog` button + state/theme actions. Breadcrumb org-name replaced with a neutral `llm-security`. The onboarding concept (per-command context injection) is documented as a v7.8.0 candidate in ROADMAP. No scanner or hook behavior changes
+- **v7.7.0 HTML report for all 18 skill commands (2026-05-18)** — Every `/security <cmd>` that produces a report now prints a clickable `file://` link to a self-contained HTML version. Delivered across five sessions: (1) playground catalog list-view + builder-pane with a copy button; (2) playground project-surface cleanup (stub-screen + topbar split); (3) the 18 inline parsers + renderers moved to a canonical ESM module `scripts/lib/report-renderers.mjs` (the playground keeps a bit-identical inline copy since ESM `import` does not work from `file://`); (4) new zero-dep CLI `scripts/render-report.mjs` — stdin/file/stdout mode, kebab→camel commandId routing, inlines 6 DS stylesheets, ~140 KB self-contained HTML with system-font fallback, absolute `file://` paths for Ghostty cmd-click; (5) all 18 skills wired (4 in session 4 + 14 in session 5). No scanner or hook behavior changes — purely additive
+- **v7.6.1 playground visual patch (2026-05-06)** — Six bugs caught by the maintainer during manual browser verification after the v7.6.0 release. All were mismatches between DS classes and how playground renderers used them (or missing DS implementations the renderers assumed existed): `renderFindingsBlock` used the `.findings` outer class (the DS 2-column list+detail grid) → replaced with `<section class="report-meta">` + the correct `findings__list` pattern; `.report-table` was missing entirely from the DS but used in 7+ renderers → local CSS implementation; `renderPreDeploy` traffic-lights used the fixed 28×28 px `.sm-card__grade` for "PASS"/"PASS-WITH-NOTES"/"FAIL" → width-adapting status pill; threat-model matrix bubbles were not clickable → `<button>` with `data-threat-id` + click handler that scrolls to the Threats table; radar labels overlapped → SVG 280→380, R 105→125, dynamic `text-anchor`; `recommendation-card__body` text overflow → `overflow-wrap: anywhere`. 4/4 fix-specific + 18/18 regression tests passing. No scanner or hook behavior changes
+- **v7.6.0 playground Tier 3 reference case (2026-05-06)** — The playground was raised to a visually and structurally complete reference for the `shared/playground-design-system/` Tier 3 supplement. 8 new DS components integrated into the 18 report renderers: `tfa-flow` + `tfa-leg` + `tfa-arrow` (lethal trifecta chain with `<button>` elements + ARIA), `mat-ladder` + `mat-step` (5-step maturity ladder), `suppressed-group` (narrative audit), `codepoint-reveal` + `cp-tag/cp-zw/cp-bidi` (Unicode steganography), `top-risks` + `top-risk[data-severity]` (ranked top-findings listing), extended `recommendation-card[data-severity]` on `clean`/`harden`/`audit`/`posture`/`pre-deploy`/`plugin-audit`, `risk-meter` (0-100 band visualization across 5 archetypes), `card--severity-{level}` modifier on findings cards. Wave 1 (Session 2): `badge--scope-security` (identity chip), `verdict-pill-lg` (DS Tier 3 pill across all 18 report types), `form-progress` + `fp-step` (onboarding wizard). Removed ~30 duplicate CSS declarations (DS wins the cascade). 5 new DS helpers + `mapSeverityToCardLevel` + `parseNarrativeAudit`. A11Y report updated. File size 10209 → 10677 lines across 5 sessions. No scanner or hook behavior changes — purely additive surface
+- **v7.5.0 playground (2026-05-05)** — Single-file SPA at `plugins/llm-security/playground/llm-security-playground.html` (~10 200 lines) for onboarding, demos and workshop use without a Claude Code installation. Parsers + renderers for all 18 produces_report commands, 18 markdown test fixtures as contract anchors, a complete demo project with all 18 reports parsed in advance, vendor-synced design-system, 9 Playwright-generated screenshots. 11 new `window` globals exposed for testing/automation (`__store`, `__navigate`, `__loadDemoState`, `__PARSERS`, `__RENDERERS` …). Bug-fix: `normalizeVerdictText` handles GO-WITH-CONDITIONS without collapsing to ALLOW. No scanner or hook behavior changes — purely additive surface
+- **v7.4.0 examples + e2e suite (2026-05-05)** — 9 runnable demonstration walkthroughs under `examples/` (lethal-trifecta, mcp-rug-pull, supply-chain-attack, poisoned-claude-md, bash-evasion-gallery, prompt-injection-showcase, malicious-skill-demo, toxic-agent-demo, pre-compact-poisoning) plus three new test suites under `tests/e2e/` (attack-chain, multi-session, scan-pipeline) that prove the framework works as a coordinated system. +45 tests (1777 → 1822), no scanner or hook behavior changes — purely additive surface
 - **v8.0.0 env-var deprecation runway (D3, v7.3.0)** — Hook configuration has historically been split between process env-vars and the team-distributable `.llm-security/policy.json` file. Until v7.3.0 the two surfaces could disagree silently. The new `getPolicyValueWithEnvWarn()` helper in `scanners/lib/policy-loader.mjs` now emits a one-time-per-process stderr line whenever both surfaces are explicitly set:
   - Affected pairs: `LLM_SECURITY_INJECTION_MODE`↔`injection.mode`, `LLM_SECURITY_TRIFECTA_MODE`↔`trifecta.mode`, `LLM_SECURITY_ESCALATION_WINDOW`↔`trifecta.escalation_window` (new key in `DEFAULT_POLICY`), `LLM_SECURITY_AUDIT_LOG`↔`audit.log_path`
   - Env still wins through the v7.x window — no behaviour change today, only a runway signal
@@ -45,15 +52,15 @@ Built on OWASP LLM Top 10 (2025), OWASP Agentic AI Top 10, and the AI Agent Trap
 
 Key commands: `/security posture`, `/security audit`, `/security scan`, `/security ide-scan`, `/security threat-model`, `/security plugin-audit`
 
-6 specialized agents · 23 scanners · 9 hooks · 20 knowledge docs · 1768 tests
+6 specialized agents · 23 scanners · 9 hooks · 20 knowledge docs · 9 runnable examples · 1822 tests
 
 → [Full documentation](plugins/llm-security/README.md)
 
 ---
 
-### [Config-Audit](plugins/config-audit/) `v5.0.0`
+### [Config-Audit](plugins/config-audit/) `v5.1.0`
 
-Configuration intelligence for Claude Code — health checks, feature discovery, auto-fix, active-config inventory, and reality-based Opus-4.7 token analysis.
+Configuration intelligence for Claude Code — health checks, feature discovery, auto-fix, active-config inventory, reality-based Opus-4.7 token analysis, and plain-language UX that leads with prose ("Fix soon: The same automation is set up more than once") instead of technical IDs.
 
 Claude Code reads instructions from 7+ file types across multiple scopes. This plugin tells you what's wrong, what's missing, what's silently conflicting, what's actually loaded, and where you're burning tokens unnecessarily:
 
@@ -63,72 +70,70 @@ Claude Code reads instructions from 7+ file types across multiple scopes. This p
 - **What's active** — read-only inventory of plugins, skills, MCP servers, hooks, and CLAUDE.md cascade for a repo, with token estimates
 - **Token hotspots** — `/config-audit tokens` ranks files by estimated waste across 6 Opus-4.7 patterns (cache-breaking volatile content, redundant tool permissions, deep import chains, oversized cascades, bloated SKILL.md descriptions, MCP tool-schema budget). Optional `--accurate-tokens` calibrates against Anthropic's `count_tokens` API.
 - **System-prompt manifest** — `/config-audit manifest` ranks every token source (CLAUDE.md cascade, plugins, skills, MCP servers, hooks) by estimated tokens
+- **Plain-language UX (v5.1.0)** — default output of all 18 commands leads with prose; findings group by user-impact category (Configuration mistake, Conflict, Wasted tokens, Missed opportunity, Dead config) and urgency phrase (Fix this now → FYI). Pass `--raw` for v5.0.0 verbatim output; `--json` is unchanged and byte-stable.
 
 Key commands: `/config-audit posture`, `/config-audit feature-gap`, `/config-audit fix`, `/config-audit whats-active`, `/config-audit tokens`, `/config-audit manifest`
 
-6 agents · 12 scanners · 18 commands · 635+ tests
+6 agents · 12 scanners · 18 commands · 792+ tests
 
 → [Full documentation](plugins/config-audit/README.md)
 
 ---
 
-### [Ultra {brief | research | plan | execute} - local](plugins/ultraplan-local/) `v3.1.0`
+### [Voyage](plugins/voyage/) `v5.1.1`
 
-Deep requirements gathering, research, implementation planning, and self-verifying execution with specialized agent swarms, adversarial review, and failure recovery.
+Deep requirements gathering, research, implementation planning, self-verifying execution, independent post-hoc review, and zero-friction multi-session resumption — with specialized agent swarms, adversarial review, and failure recovery. Six-command (brief, research, plan, execute, review, continue) universal pipeline + adaptive-depth per-phase effort dialog. `/trekbrief`, `/trekplan`, and `/trekreview` render their artifact to a self-contained HTML view and print the `file://` link.
 
-Four commands, one pipeline with clear division of labor:
+v5.1.1 is a 13-step remediation patch closing 11 of 12 findings from the v5.1.0 review (the SC8 dogfood gate is operator-manual, scheduled for after-execute). Load-bearing bug fixes: YAML-number bypass in `brief-validator` so the gate fires for both quoted and unquoted `brief_version` (#8 + #11). Wiring: a new `lib/profiles/phase-signal-resolver.mjs` helper is invoked from `/trekplan`/`/trekresearch`/`/trekreview`/`/trekexecute` Phase 1, the resolved JSON is captured as `phase_signal_result`, and the `brief-validator --soft` gate is required uniformly across all 4 downstream commands (#9 + #12). Test refactor: runtime SC1 walk for trekbrief + per-tier resolver-output + missing-signals falsification per downstream command + dedicated profile-resolver non-interference test (#1 #2 #3 #4 #6 #7 #10). Documentation: Decision B high-effort behavior locked per command (gemini-bridge pass for `/trekplan`, full swarm + always-on `contrarian-researcher` for `/trekresearch`, skip Pass 3 + coordinator normalization for `/trekreview`, `gates_mode: closed` for `/trekexecute`) + brief Non-Goal/SC1 amendments + REMEMBER dogfood scaffolding. v5.1.1 is additive — no breaking changes against v5.1.0. See `plugins/voyage/CHANGELOG.md` § v5.1.1.
 
-- **`/ultrabrief-local`** — Capture intent. Dynamic, quality-gated interview: a section-driven completeness loop (Phase 3) followed by a `brief-reviewer` stop-gate (Phase 4, max 3 review iterations). Required sections must reach an initial-signal gate AND pass review across completeness, consistency, testability, scope clarity, and research-plan validity before `brief.md` is written. Identifies research topics with copy-paste-ready `/ultraresearch-local` commands. Optional auto-orchestration runs research + planning in foreground. Always interactive.
+v5.1.0 adds Phase 3.5 to `/trekbrief`: 4 tier-coupled `AskUserQuestion` calls commit an effort level (`low | standard | high`) and an optional `model` (`sonnet | opus`) per downstream phase (`research`, `plan`, `execute`, `review`). The choices land in `brief.md` as `phase_signals:` (or `phase_signals_partial: true` on force-stop). `brief_version: 2.1` activates a validator-side sequencing gate (`BRIEF_V51_MISSING_SIGNALS`) so downstream commands halt with a friendly hint when signals are missing. Composition rule per downstream command: brief signal wins per-phase, profile fills gaps. `effort == low` activates each command's existing `--quick`-equivalent code-path (`/trekexecute` low-effort = `--gates open` + sequential-only). Additive — no breaking changes; pre-2.1 briefs still validate. See `plugins/voyage/CHANGELOG.md` § v5.1.0.
-- **`/ultraresearch-local`** — Gather context. Deep multi-source research with triangulation: 5 local agents + 4 external agents + Gemini bridge, producing structured briefs with confidence ratings. Makes no build decisions.
-- **`/ultraplan-local`** — Transform intent into an executable contract. Per-step YAML manifests (`expected_paths`, `commit_message_pattern`, `bash_syntax_check`). Plan-critic is a hard gate on manifest quality. Requires a task brief as input (`--brief` or `--project`). Auto-discovers `architecture/overview.md` when the optional `ultra-cc-architect` plugin is installed and cross-references its `cc_features_proposed` against exploration findings.
-- **`/ultraexecute-local`** — Execute the contract disciplined. Manifest-based verification, independent Phase 7.5 audit from git log + filesystem (ignores agent bookkeeping), Phase 7.6 bounded recovery dispatch for missing steps. Step 0 pre-flight catches sandbox push-denial before any work. `--validate` mode offers a fast schema-only sanity-check between planning and execution.
 
-All artifacts land in one project directory: `.claude/projects/{YYYY-MM-DD}-{slug}/` contains `brief.md`, `research/NN-*.md`, `plan.md`, `sessions/`, and `progress.json`. `--project <dir>` works across `/ultraresearch-local`, `/ultraplan-local`, and `/ultraexecute-local`.
+v5.0.3 lands the annotation UX modelled on `~/repos/claude-code-100x/claude-code-100x/build-site.js`: pencil-toggle annotation mode, **select text or click any element to anchor**, choose intent (**Fiks** / **Endre** / **Spørsmål**), write a comment, save. The sidebar groups annotations by section with intent badges; Copy Prompt assembles them into a structured markdown the operator pastes back into Claude. State persists in `localStorage` per artifact path. v5.0.2 was operator-led but too thin (line-click + freeform note, no intent categories). v5.0.1 had pointed at `/playground document-critique` (Claude-leads — wrong direction). v5.0.0 (breaking, kept) removed the v4.2/v4.3 bespoke playground SPA, `/trekrevise`, Handover 8, the supporting `lib/` modules, the Playwright e2e suite, and the `@playwright/test` / `@axe-core/playwright` devDeps. v5.0.3's `scripts/annotate.mjs` is one self-contained zero-dependency Node script. **The operator drives every annotation** — Claude never pre-generates suggestions in this flow. See `plugins/voyage/CHANGELOG.md` § v5.0.0 → § v5.0.3.
 
-v3.0.0 extracts the Claude-Code-specific architecture phase to a separate plugin (`ultra-cc-architect`, see below). The planning pipeline now stays technology-agnostic; CC-feature matching becomes opt-in. The plan command still auto-discovers `architecture/overview.md` if the new plugin is installed — the contract is filesystem-level, not code-level. Non-breaking for users of brief/research/plan/execute. See `plugins/ultraplan-local/CHANGELOG.md` for migration steps.
+v4.0.0 (breaking) renamed the plugin from `ultraplan-local` to **Voyage** and all commands from `/ultra*-local` to `/trek*` to remove name collision with Anthropic's `/ultraplan` and `/ultrareview` features. See `plugins/voyage/TRADEMARKS.md` and `plugins/voyage/CHANGELOG.md`.
+
+Six commands, one pipeline with clear division of labor:
+
+- **`/trekbrief`** — Capture intent. Dynamic, quality-gated interview: a section-driven completeness loop (Phase 3) followed by a `brief-reviewer` stop-gate (Phase 4, max 3 review iterations). Required sections must reach an initial-signal gate AND pass review across completeness, consistency, testability, scope clarity, and research-plan validity before `brief.md` is written. Identifies research topics with copy-paste-ready `/trekresearch` commands. Optional auto-orchestration runs research + planning in foreground. Always interactive.
+- **`/trekresearch`** — Gather context. Deep multi-source research with triangulation: 5 local agents + 4 external agents + Gemini bridge, producing structured briefs with confidence ratings. Makes no build decisions.
+- **`/trekplan`** — Transform intent into an executable contract. Per-step YAML manifests (`expected_paths`, `commit_message_pattern`, `bash_syntax_check`). Plan-critic is a hard gate on manifest quality. Requires a task brief as input (`--brief` or `--project`). Auto-discovers `architecture/overview.md` when produced upstream and cross-references its `cc_features_proposed` against exploration findings.
+- **`/trekexecute`** — Execute the contract disciplined. Manifest-based verification, independent Phase 7.5 audit from git log + filesystem (ignores agent bookkeeping), Phase 7.6 bounded recovery dispatch for missing steps. Step 0 pre-flight catches sandbox push-denial before any work. `--validate` mode offers a fast schema-only sanity-check between planning and execution.
+- **`/trekreview`** — Close the iteration loop. Independent post-hoc reviewer reads `brief.md` from scratch and evaluates the diff produced by execute. Two parallel reviewers (brief-conformance + code-correctness) plus a Judge Agent (review-coordinator) for dedup and reasonableness filtering. Severity-tagged findings (Critical/High/Medium/Low/Info) with stable 40-char hex IDs feed back into planning via Handover 6 (`/trekplan --brief review.md` → remediation plan with `source_findings:` audit trail).
+- **`/trekcontinue`** — Zero-friction multi-session resumption. In a fresh chat, type `/trekcontinue` — reads `.session-state.local.json` (Handover 7), prints a 3-line summary, and immediately begins executing the next session. Any session-end mechanism may write the state file (`/trekexecute` Phase 8/2.55/4 do so automatically; `/trekendsession` helper writes it for informal flows). Forward-compat schema (unknown top-level keys ignored) so future producers can extend additively.
+
+`/trekbrief`, `/trekplan`, and `/trekreview` each end by running `scripts/annotate.mjs` against the just-written `.md`, printing the `file://<abs path>` link to the resulting self-contained operator-annotation HTML. The operator opens it, clicks any line to add their own note, watches a sidebar of every note (editable, deletable, persisted in browser `localStorage`), clicks "Copy Prompt" to get one structured prompt with every note, pastes back into Claude — Claude revises the `.md` from the notes. The operator drives every annotation.
+
+All artifacts land in one project directory: `.claude/projects/{YYYY-MM-DD}-{slug}/` contains `brief.md`, `research/NN-*.md`, `plan.md`, `sessions/`, `progress.json`, `review.md`, and `.session-state.local.json` (gitignored). `--project <dir>` works across `/trekresearch`, `/trekplan`, `/trekexecute`, `/trekreview`, and (optionally) `/trekcontinue`.
+
+v3.4.0 (non-breaking) adds the **autonomy chain from brief approval to main-merge** plus parallel-wave hardenings. New `lib/util/autonomy-gate.mjs` state machine (`idle → approved → executing → merge-pending → main-merged`), `lib/review/plan-review-dedup.mjs` for Phase 9 inline dedup, `lib/stats/event-emit.mjs` for autonomy-gate transitions and main-merge gate, and `--gates {open|closed|adaptive}` flag on all four pipeline commands. `commands/trekplan.md` Phase 8 seals Opus-4.7 plan/list-emission schema-drift via `plan-validator --strict`. `commands/trekexecute.md` Phase 2.6 wave-executor adds 11 hardenings for plugin-in-monorepo + gitignored-state topology (GIT_OPTIONAL_LOCKS, --max-turns, --max-budget-usd, scoped --allowedTools, push-before-cleanup ordering). New `hooks/scripts/post-compact-flush.mjs` PostCompact hook re-injects session-state after compaction. SC7 synthetic determinism floor (Jaccard ≥ 0.833) for plan + review fixtures. Hook baseline regression pins. Architecture decision: Path B (sequential `--no-ff` parallel waves with manifest-driven failure recovery) ships; Path C (cache-first hybrid) deferred to v3.5.0 contingent on cache-telemetry harvest.
+
+v3.3.0 (non-breaking) adds `/trekcontinue` as the sixth command and the contracted **Handover 7 (.session-state.local.json)** for zero-friction multi-session resumption. New `lib/validators/session-state-validator.mjs` (schema v1, forward-compat — unknown top-level keys ignored), `lib/util/atomic-write.mjs` extracted from `pre-compact-flush.mjs` for tmp+rename writes, and `/trekendsession` helper for informal multi-session flows. `/trekexecute` Phase 8 / 2.55 / 4 now write the state file alongside `progress.json`. `pre-compact-flush.mjs` also refreshes the state file before context compaction (monotonic; never advances to non-resumable status). 22 new tests (163 → 185 green).
+
+v3.2.0 (non-breaking) adds `/trekreview` as the fifth command and the contracted **Handover 6 (review → plan)** feedback loop. New artifact type `type: trekreview` validated by `lib/validators/review-validator.mjs`, stable 40-char SHA1 finding-IDs from `lib/parsers/finding-id.mjs`, Jaccard similarity for determinism testing (`lib/parsers/jaccard.mjs`), and a 12-key version-pinned rule catalogue (`lib/review/rule-catalogue.mjs`). Four new agents (review-orchestrator, brief-conformance-reviewer, code-correctness-reviewer, review-coordinator) implementing the Judge-Agent dedup pattern. `/trekplan` now consumes `--brief review.md` (BLOCKER + MAJOR findings become plan goals) and writes `source_findings: [<id>, ...]` audit trail. `brief-validator` accepts both `type: trekbrief` and `type: trekreview`.
+
+v3.0.0 extracts the Claude-Code-specific architecture phase to a separate plugin. The planning pipeline now stays technology-agnostic; CC-feature matching becomes opt-in. The plan command still auto-discovers `architecture/overview.md` if produced upstream — the contract is filesystem-level, not code-level. Non-breaking for users of brief/research/plan/execute. See `plugins/voyage/CHANGELOG.md` for migration steps.
 
 v2.4.0 (breaking, default behavior) removes background mode. The commands now run foreground in the main context because the harness does not expose the Agent tool to sub-agents — background orchestrators silently degraded the swarm to inline reasoning without external research tools. The `--fg` flag is preserved as a no-op alias for backward compatibility. Source: github.com/anthropics/claude-code/issues/19077.
 
-v2.1 (non-breaking) replaced the hardcoded Q1–Q8 interview with a dynamic, quality-gated loop; `brief-reviewer` emits machine-readable per-dimension JSON scores so `/ultrabrief-local` can use it as an internal stop-gate. v2.0 (breaking) extracted the interview from planning: briefs are reviewable artifacts that downstream agents (`brief-reviewer`, `plan-critic`, `scope-guardian`) validate independently. `/ultraplan-local` requires `--brief` or `--project`. See `plugins/ultraplan-local/MIGRATION.md`.
+v2.1 (non-breaking) replaced the hardcoded Q1–Q8 interview with a dynamic, quality-gated loop; `brief-reviewer` emits machine-readable per-dimension JSON scores so `/trekbrief` can use it as an internal stop-gate. v2.0 (breaking) extracted the interview from planning: briefs are reviewable artifacts that downstream agents (`brief-reviewer`, `plan-critic`, `scope-guardian`) validate independently. `/trekplan` requires `--brief` or `--project`. See `plugins/voyage/MIGRATION.md`.
 
 v1.7 self-verifying chain (preserved): a step may not be marked `completed` unless its manifest verifies. v1.8 Opus 4.7 literalism fixes (preserved): literal Step+Manifest template, forbidden narrative headers, schema self-check.
 
-v3.1.0 (in progress) adds a `lib/`-tree of zero-dep validators (`brief-validator`, `research-validator`, `plan-validator`, `progress-validator`, `architecture-discovery`) wired into the four commands as CLI shims, plus 109 `node:test` cases and a doc-consistency invariant test. The Phase 5.5 schema self-check now runs as `node lib/validators/plan-validator.mjs --strict` instead of three `grep -cE` calls — same checks, single source of truth, machine-readable error codes. Architecture discovery treats the `ultra-cc-architect` contract as drift-WARN, never drift-FAIL. Forking the plugin? `npm test` is the readiness gate.
+v3.1.0 (in progress) adds a `lib/`-tree of zero-dep validators (`brief-validator`, `research-validator`, `plan-validator`, `progress-validator`, `architecture-discovery`) wired into the four commands as CLI shims, plus 109 `node:test` cases and a doc-consistency invariant test. The Phase 5.5 schema self-check now runs as `node lib/validators/plan-validator.mjs --strict` instead of three `grep -cE` calls — same checks, single source of truth, machine-readable error codes. Architecture discovery treats the upstream `architecture/overview.md` contract as drift-WARN, never drift-FAIL. Forking the plugin? `npm test` is the readiness gate.
 
-v3.1.0 also adds: `docs/HANDOVER-CONTRACTS.md` as the single source of truth for the 5 pipeline handovers; PreCompact-hook (`pre-compact-flush.mjs`, CC v2.1.105+) that fixes the documented progress.json drift bug — `--resume` now works after long conversations; UserPromptSubmit-hook that sets session titles `ultra:<command>:<slug>` for headless multiplexing (CC v2.1.94+); PostToolUse-hook that captures Bash `duration_ms` per call (CC v2.1.97+); semantic plan-critic rubric that catches paraphrased deferred decisions ("implement as needed", "wire it up") instead of just exact-string blacklist; `examples/01-add-verbose-flag/` showing a calibrated end-to-end pipeline run; `SECURITY.md` boilerplate; `docs/architect-bridge-test.md` smoke checklist.
+v3.1.0 also adds: `docs/HANDOVER-CONTRACTS.md` as the single source of truth for the 5 pipeline handovers (extended to 6 in v3.2.0, then to 7 in v3.3.0); PreCompact-hook (`pre-compact-flush.mjs`, CC v2.1.105+) that fixes the documented progress.json drift bug — `--resume` now works after long conversations; UserPromptSubmit-hook that sets session titles `voyage:<command>:<slug>` for headless multiplexing (CC v2.1.94+); PostToolUse-hook that captures Bash `duration_ms` per call (CC v2.1.97+); semantic plan-critic rubric that catches paraphrased deferred decisions ("implement as needed", "wire it up") instead of just exact-string blacklist; `examples/01-add-verbose-flag/` showing a calibrated end-to-end pipeline run; `SECURITY.md` boilerplate; `docs/architect-bridge-test.md` smoke checklist.
 
 Defense-in-depth security: plugin hooks block destructive commands and sensitive path writes, prompt-level denylist works in headless sessions, pre-execution plan scan catches dangerous commands before they run, scoped `--allowedTools` replaces `--dangerously-skip-permissions` in parallel sessions. Recommended hardening: `disableSkillShellExecution: true` for fork-ers handling untrusted plans (CC v2.1.91+).
 
-Modes: default, brief-driven, project-scoped, research-enriched, foreground, quick, decompose, export
+Modes: default, brief-driven, project-scoped, research-enriched, foreground, quick, decompose, export, resume
 
-19 specialized agents · 4 commands · 4 plugin hooks · No cloud dependency
+23 specialized agents · 6 commands (+ 1 helper) · 5 plugin hooks · 500+ tests · Operator-driven HTML annotation surface · No cloud dependency
 
-→ [Full documentation](plugins/ultraplan-local/README.md) · [Migration guide](plugins/ultraplan-local/MIGRATION.md)
+→ [Full documentation](plugins/voyage/README.md) · [Migration guide](plugins/voyage/MIGRATION.md)
 
 ---
 
-### [Ultra CC Architect](plugins/ultra-cc-architect/) `v0.1.0` `🚧 pre-release`
+### [AI Psychosis](plugins/ai-psychosis/) `v1.2.0`
-
-Match a task brief and research against available Claude Code features, with brief-anchored rationale and explicit coverage gaps. Extracted from `ultraplan-local` v2.4.0 in 2026-04-30.
-
-Two commands, both Claude-Code-specific:
-
-- **`/ultra-cc-architect-local`** — Reads `brief.md` + `research/*.md` (typically produced by `ultraplan-local`), consults the seeded `cc-architect-catalog` skill (hooks, subagents, skills, output styles, MCP, plan mode, worktrees, background agents), and produces `architecture/overview.md` with brief-anchored rationale plus `architecture/gaps.md` with issue-ready drafts for missing catalog entries. Hallucination gate (enforced by `architecture-critic`) blocks proposals for features not covered by the catalog.
-- **`/ultra-skill-author-local`** *(skill-factory Fase 1)* — Generates one `cc-architect-catalog` draft skill from a curated local source file with IP-hygiene enforcement. Sequential pipeline: `concept-extractor` → `skill-drafter` → `ip-hygiene-checker`. Drafts land in `skills/cc-architect-catalog/.drafts/` for manual review and `mv` promotion. Pure-Node n-gram containment scorer (`scripts/ngram-overlap.mjs`) enforces verdict bands; rejected drafts are deleted.
-
-The plugin sits between `/ultraresearch-local` and `/ultraplan-local` in the typical workflow. `ultraplan-local` v3.0.0+ auto-discovers `architecture/overview.md` when present — install both plugins to keep the full pipeline (brief → research → architect → plan → execute) working.
-
-**Pre-release because:** catalog is thin (11 seed skills across 8 features), decision-layer is intentionally empty, skill-factory has only Fase 1 (Fase 2/3 unbuilt), and `feature-matcher` falls back to a hardcoded list when the catalog is sparse. v1.0 ships when the catalog is dense enough that the fallback list can be removed.
-
-Slug convention: `<cc_feature>[-<qualifier>]-<layer>.md`. Unqualified slugs are the canonical baseline per `(feature, layer)` pair; qualified slugs cover specific sub-patterns. `feature-matcher` prefers the unqualified baseline unless the brief justifies a variant. Slug collisions with approved skills are a hard error. `skill-drafter` warns before overwrite.
-
-8 specialized agents · 2 commands · 1 skill (CC-feature catalog, 11 seeds) · 1 IP-hygiene script
-
-→ [Full documentation](plugins/ultra-cc-architect/README.md)
-
----
-
-### [AI Psychosis](plugins/ai-psychosis/) `v1.0.0`
 
 Meta-awareness tools that counteract sycophancy, reinforcement loops, and compulsive AI interaction patterns.
 
@@ -170,7 +175,7 @@ Key command: `/graceful-handoff [topic-slug] [--no-commit] [--no-push] [--dry-ru
 
 ---
 
-### [MS AI Architect — Azure AI and Microsoft Foundry](plugins/ms-ai-architect/) `v1.8.0` `🇳🇴 Norwegian`
+### [MS AI Architect — Azure AI and Microsoft Foundry](plugins/ms-ai-architect/) `v1.15.0` `🇳🇴 Norwegian`
 
 Microsoft AI solution architecture guidance for Norwegian public sector and enterprise.
 
@@ -179,11 +184,23 @@ Meet Cosmo Skyberg — a structured architect persona who understands the proble
 - **Structured advisory** — 7-phase methodology from business need to architecture recommendation and optional diagram
 - **Regulatory assessments** — ROS analysis (NS 5814), DPIA/PVK, security scoring (6×5), EU AI Act classification, cost estimation in NOK (P10/P50/P90)
 - **Norwegian public sector** — Digdir architecture principles, Utredningsinstruksen, NSM, Schrems II data residency, EU AI Act compliance workflow
-- **Automated freshness** — sitemap-based change detection polls Microsoft Learn weekly, flags which reference files need updating based on source page changes, and discovers new relevant pages
+- **Manual KB-refresh** — `/architect:kb-update` slash command drives sitemap-based change detection + new-URL discovery + per-file `microsoft_docs_fetch`-update + commit, run from an active Claude Code session. Scheduling is intentionally out of scope and left to the user (cron / launchd / GitHub Actions etc. as desired)
 
 Key commands: `/architect`, `/architect:ros`, `/architect:security`, `/architect:dpia`, `/architect:utredning`, `/architect:cost`
 
-12 specialized agents · 24 commands · 5 skills (387 reference docs) · 2 hooks · sitemap-based KB monitoring
+12 specialized agents · 25 commands · 5 skills (387 reference docs) · 2 hooks · manual sitemap-driven KB refresh
+
+**One-click demo (v1.15.0, 2026-05-16):** "Last inn demo-data"-knappen på onboarding bootstrapper en ferdig "Acme Kommune" med demo-prosjektet "Acme: Kunde-chatbot" og alle 17 rapport-typer pre-importert. v2→v3 migrasjon auto-parser `raw_markdown` til `project.artifacts[cid]` så project-view viser aggregert verdict (BLOKKERT), key stats (17/17 artifacts), top-risks-liste, og navigerbart artifact-sidebar i én navigasjon. 24 retina-screenshots committed under `playground/screenshots/v1.15.0/` (12 surfaces × 2 tema), så forkere ser pluginen uten å kjøre noe. Standalone Playwright-runner under `tests/screenshot/` (egen `package.json`).
+
+**Playground (v3, v1.15.0 — project-view integration, 2026-05-16):** Multi-surface decision-builder + report viewer. The single-file HTML app lives at `playground/ms-ai-architect-playground.html` (~3870+ lines). v1.15.0 erstatter v2 project-surface (screen-tabs + category-tabs + per-command paste-cards) med v3 `renderProjectView` (sidebar med 17 artifacts gruppert i 4 kategorier + main-area med per-artifact view eller overview + import-modal som DS-overlay). V2-surface helt fjernet (`renderProjectSurface`, `renderCommandSubCard`, `rehydratePasteImports`, 5 v2-CSS-klasser). 2 fingerprint-gap lukket (requirements + license headers). `migrateDataVersion` utvidet med `parserFor` slik at demo-state og persisted localStorage auto-parses. Ship-QA: `components-tier4-project-view.css` lagt til i `<link>`-kjeden (var ikke loaded → modal-overlay og two-column layout virket ikke). 386 E2E PASS, 0 FAIL, 2 WARN.
+
+- **4 surfaces:** Onboarding (4 strukturerte / 14 fritekst, prefill alle command-skjemaer) → Home (project list + 3 entry tracks) → Catalog (24 commands grouped in 5 expansion categories with search) → **Project v3** (sidebar med 17 artifacts + søk + main-area med per-artifact view eller aggregate overview + import-modal overlay)
+- **Persistence:** IndexedDB primary + localStorage fallback, schema-versioned (`STATE_KEY = 'ms-ai-architect-state-v1'`) with eager migrations pipeline. v1.10.0 adds idempotent `dataVersion v1→v2` migration that backfills `verdict` + `keyStats` on existing reports.
+- **17 inline report renderers (felles grunnskjelett)** — all wrap output through `renderPageShell()` with eyebrow + h1 + optional verdict-pill + optional key-stats-grid + archetype body (pyramid, 5×5/6×5/7×5 matrix, radar, kanban, mat-ladder, scenario-cards, screen-tabs, residual-pair, top-risks, recommendation-card, suppressed-panel, critique-card, read-more, traffic-light).
+- **Foundation helpers** — `renderPageShell`, `renderVerdictPill`, `renderKeyStatsGrid`, `inferVerdict`, `inferKeyStats`, `KEY_STATS_CONFIG`.
+- **Light/dark theme toggle** with Aksel-aligned tokens in both modes (full WCAG AA contrast). Persisted in `localStorage('ms-ai-architect-theme')`, FOUC-safe via `<head>`-bootstrap script.
+- **Validation:** 272 PASS combined — 201 static + 70 parser-fixture + 1 verdict-pill. `bash tests/run-e2e.sh --playground` runs static-structure + parser-fixture suites. Migrations 7 PASS separat. Plugin-validering 219 PASS.
+- **Vendored design-system** at `playground/vendor/`, kept in sync via `scripts/sync-design-system.mjs ms-ai-architect`. Standalone — opens from `file://` without server or marketplace dependency.
 
 → [Full documentation](plugins/ms-ai-architect/README.md)
 
@@ -232,6 +249,65 @@ Key commands: `/okr:skriv`, `/okr:kvalitet`, `/okr:gap`, `/okr:analyse`, `/okr:k
 
 ---
 
+### [Human-Friendly Style](plugins/human-friendly-style/) `v1.0.0`
+
+Shared Claude Code [output style](https://code.claude.com/docs/en/output-styles) used across this marketplace. Gives every plugin a consistent, plain-language tone — so users don't have to switch mental gears when moving between plugins.
+
+- **Explains what and why, not how** — describes the work in human terms, reserves technical detail for when the user asks
+- **Hides noise by default** — long paths, raw commands, JSON, stack traces, and verbose tool output are summarized rather than dumped
+- **Matches the user's language** — Norwegian when the user writes Norwegian, English otherwise
+- **Honest about uncertainty** — says "I think this should work" instead of pretending to be sure
+- **Keeps coding instructions intact** (`keep-coding-instructions: true`) — testing discipline, careful edits, and verification still apply
+
+Optional. Every other plugin in the marketplace works without it; this just makes the conversation feel more like dialog and less like a console dump.
+
+Activate with `/config` → **Output style** → **Human-Friendly**.
+
+1 output style · 0 commands · 0 agents · 0 hooks
+
+→ [Full documentation](plugins/human-friendly-style/README.md)
+
+---
+
+### [Claude Design](plugins/claude-design/) `v0.1.0`
+
+End-to-end facilitator for prompting Claude Design (`claude.ai/design` — Anthropic's Labs research preview launched 2026-04-17, Opus 4.7 pinned). Walks the operator from raw idea through intent-preset selection, audience and destination clarification, DESIGN.md anchor, five-layer prompt drafting, copy-paste delivery, iteration coaching, and ship-readiness handoff. Output is the prompt; the artifact gets built in Claude Design.
+
+The plugin is the **pre-design and during-design** complement to Anthropic's official `knowledge-work-plugins/design` (`https://claude.com/plugins/design`). This plugin covers idea → prompt → iterate; Anthropic's plugin covers critique → accessibility → handoff. Zero command overlap by design — `tests/validate-plugin.sh` assertion (h) enforces the forbidden-command-name list mechanically.
+
+- **Eight-phase facilitation flow** — disambiguate surface → name intent preset → audience + destination → DESIGN.md anchor → five-layer prompt draft → copy-paste delivery → iteration coaching (Tweak / Comment / Chat cascade) → ship-readiness check
+- **Five foundation references + eight per-preset references** with evidence-grade labels (`Anthropic-documented + community-validated`, `Community-only`, `Experimental` for `frontier-design`)
+- **Authoritative-claims discipline** — every reference file carries ≥1 Anthropic-domain URL citation (`anthropic.com`, `claude.com`, `support.claude.com`, `platform.claude.com`, `github.com/anthropics`); `.coverage.md` is the canonical registry
+- **`.coverage.md`** at plugin root enumerates the 8 intent presets with evidence-grade labels and the 13 authoritative-claims files; SC2 and SC3 read from it directly
+- **5 test scripts + `verify.sh` roll-up** — plugin structure validation, SC1 dogfood-log format, SC2 per-preset coverage, SC3 citation discipline, skill description quality
+
+1 skill (`claude-design-facilitator`) · 13 reference files · 5 tests · 0 commands · 0 agents · 0 hooks
+
+→ [Full documentation](plugins/claude-design/README.md)
+
+---
+
+## Shared infrastructure
+
+### [Playground Design System](shared/playground-design-system/) `v0.1`
+
+Shared design system for plugin Playgrounds — visual self-service UIs that complement terminal slash-commands. Aksel/Digdir-aligned aesthetics, WCAG 2.1 AA compliance, light + dark themes, A4 print stylesheets with B/W severity patterns.
+
+Targets five plugins: `ms-ai-architect`, `okr`, `llm-security`, `voyage`, `config-audit`. Built for Norwegian public sector decision-makers (kommunaldirektører, sikkerhetsoffiserer, OKR-koordinatorer) plus developer power-users — one visual family, two information densities.
+
+- **Tokens** — Inter/JetBrains Mono/Source Serif 4 (all self-hosted, OFL 1.1), body 17px, Digdir blue `#0062BA`, deuteranopia-safe severity ramp, distinct severity-red vs failure-red, plugin-scope colors, semantic CSS custom properties
+- **Tier 1 components** — radar/spider, 5×5 matrix-heatmap (bottom-left origin, ROS/DPIA), findings-browser, critique-card, wizard/stepper, live-meter with antipattern lints
+- **Tier 2 components** — decision-tree (AI Act 4-step), traffic-lights, diff-review, treemap (token hotspots), distribution P10/P50/P90, command-pipeline output, AI Act 4-color pyramide, pipeline-cockpit, verdict-pill + 5-band risk-meter, codepoint-reveal (Unicode steganography), small-multiples grid (16-category posture without overcrowded radar), OWASP badges (LLM/ASI/AST/MCP)
+- **Tier 3 components (wave 1+2, 20 total)** — pair-before-after, AI Act timeline, 3-track entry, FRIA rights-matrix, capability-matrix, parallel-agent-status, ErrorSummary, GuidePanel, toxic-flow chain, fleet-overview, kanban Keep/Review/Remove, maturity-ladder, classify-and-transform, cycle-ribbon, persistent-antipattern, suppressed-signals, ExpansionCard, ReadMore, FormProgress, Aspirational-vs-Committed
+- **JSON schemas** — `finding.schema.json`, `okr-set.schema.json`, `ros-threat.schema.json` for cross-plugin data interchange
+- **Privacy-first** — all fonts self-hosted as woff2 in `fonts/`, zero external CDN requests, GDPR-safe for offentlig sektor, works offline / behind air-gapped firewalls
+- **Reference scenarios** — Lier kommune ROS-rapport (ms-ai-architect), Bærum kommune T2 OKR live-writer, Direktoratet for digital tjenesteutvikling ToxicSkills findings review (85 funn, BLOCK)
+- **Vendoring sync** — `scripts/sync-design-system.mjs <plugin>` copies the design-system into `plugins/<name>/playground/vendor/` so each plugin stays standalone. SHA-256 MANIFEST detects local drift; `--force` to override. First adopter: `ms-ai-architect` (2026-05-03).
+
+→ [Full documentation](shared/playground-design-system/README.md) · [Browse showcase](shared/playground-examples/index.html)
+
+---
+
 ## License
 
 MIT

plugins/ai-psychosis/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-psychosis",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "description": "Meta-awareness tools for healthy AI interaction patterns. Detects reinforcement loops, scope escalation, narrative crystallization, and other compulsive patterns.",
   "author": { "name": "Kjell Tore Guttormsen" },
   "license": "MIT",

plugins/ai-psychosis/CHANGELOG.md

@@ -2,6 +2,114 @@
 
 All notable changes to this project will be documented in this file.
 
+## [1.2.0] — 2026-05-01
+
+Research-paper-driven detector update. Implements operational findings from
+Anthropic's "How people ask Claude for guidance" Appendix (April 2026).
+
+### Added
+
+- **User-information detector** — three-class signal (`yes_people` /
+  `yes_digital` / `no`) following the paper's page-11 finding that human
+  contact is the strongest disempowerment signal. ~32 patterns covering
+  therapist/friend/mentor (yes_people), search/AI/forums (yes_digital),
+  and explicit isolation phrases (no). Sticky upward priority.
+- **Validation-seeking detector** — separate from `val_flags`. Targets
+  reality-testing ("am I crazy?"), pre-committed stance + confirmation,
+  and side-taking pressing. ~12 patterns.
+- **Tier-1 user-info isolation alert** — fires per session when
+  `user_info_class === 'no'` + high-stakes domain + `turn_count >= 15`.
+- **Tier-2 cross-session isolation alert** — fires at `SessionStart` when
+  the last 3 end records all classify as `no` in high-stakes domains.
+  Bounded `readRecentEndRecords()` tail-scan in `lib.mjs` keeps this
+  scalable to 50K+ session histories.
+- **8 new paper-grounded domain patterns** — `legal`, `parenting`, `health`,
+  `financial`, `professional`, `spirituality`, `consumer`, `personal_dev`.
+  Total domains 4 → 9.
+- **Pushback re-contextualization (alert)** — v1.1.0 only counted; v1.2 adds
+  the alert with domain awareness:
+  - Relationship/spirituality: pushback signals validation-pressing — alert.
+  - Legal/parenting/health/financial/professional: pushback is healthy
+    self-advocacy — no alert.
+  - Otherwise: conservative default — alert.
+- **Domain-stakes weighting matrix** — `DOMAIN_STAKES` in `lib.mjs` (1.0–1.5).
+  Applied ONLY to new v1.2 alerts (pushback in HIGH_SYCOPHANCY, valseek in
+  HIGH_STAKES). v1.1.0 alert sensitivity is preserved.
+- **Multi-domain support** — `state.domain_context` promoted from string to
+  array. v1.1.0 string records continue to aggregate correctly via
+  shape-coercion in `report-reader.mjs`.
+- **`SKILL.md` updates** — verbatim Score 5 sycophancy phrase + 3 of the 11
+  guidance criteria (engagement-foster avoidance, confident-verdict caution,
+  speak-frankly principle).
+- **`/interaction-report` v1.2 sections** — per-domain breakdown, user-info
+  distribution, valseek summary, stakes signal aggregation. Backward-compat
+  with v1.0/v1.1 records preserved.
+- **Privacy canary extensions** — 5 new canary cases per detector category
+  (yes_people, yes_digital, no, valseek, legal domain).
+- **Perf budget validated at v1.2 pattern set** — sample patterns expanded
+  to ~91+ entries; new wall-clock test exercises tier-2 read at
+  1000-record sessions.jsonl scale.
+- **Test count: 126 → 258 cases** across 12 files (added `lib.test.mjs`,
+  `domain-detection.test.mjs`, `user-info.test.mjs`,
+  `validation-seeking.test.mjs`, `stakes-matrix.test.mjs`).
+
+### Changed
+
+- Pattern count: 41 → ~133 (25 negative + 12 pushback + 4 relationship
+  + 48 new domains + 32 user-info + 12 valseek).
+- End-record schema (v1.2): adds `user_info_class`, `valseek_count`,
+  `turn_count`. `domain_context` is always an array (was string in v1.1).
+- `report-reader.mjs` discriminates v1.0 / v1.1 / v1.2 records via the
+  presence of `user_info_class`. v1.0/v1.1 records degrade gracefully.
+
+### Deferred
+
+- **Norwegian patterns** — moved to v1.3.
+
+[1.2.0]: https://git.fromaitochitta.com/open/ai-psychosis/compare/v1.1.0...v1.2.0
+
+## [1.1.0] — 2026-05-01
+
+### Added
+
+- **12 pushback patterns** — detects "you're wrong, my way is right"
+  signals that suggest the user is reinforcing their own position
+  rather than receiving feedback (e.g. `\b(you'?re|you are) wrong\b`,
+  `\bdo it my way\b`, `\b(stop|quit) (arguing|pushing back)\b`).
+- **4 domain-context patterns** — flags relational/identity framing
+  (`\b(my|our) relationship\b`, `\b(my|our) (purpose|mission|destiny)\b`)
+  that, combined with high pushback or validation, signal narrative
+  crystallization risk.
+- **Valence-aware composition** — same-invocation valence guard so a
+  healthy correction ("you were wrong, here's why") is not counted
+  as pushback escalation.
+- **`/interaction-report` extensions** — pushback metrics + domain
+  framing distribution; companion `report-reader.mjs` script handles
+  legacy v1.0.0 records (missing `pushback`/`domain_context`) without
+  NaN propagation.
+- **CC0 Constitution citation** in `SKILL.md` plus 5-publication
+  research framework (Anthropic, MIT CSAIL, Nature, arXiv, clinical).
+- **Performance budget test** — `tests/perf.test.mjs` enforces hook
+  timing budget (logic <50ms, total <200ms wall-clock).
+- **Privacy canary extension** — pattern-phrase leak canary in
+  `tests/privacy.test.mjs` confirms matched phrases never reach disk.
+- **Test count: 73 → 126 cases** across 8 files (added skill-md,
+  perf, interaction-report tests; extended prompt-analyzer, privacy,
+  session-end, session-start).
+
+### Changed
+
+- Pattern count: 25 → 41 (25 negative + 12 pushback + 4 domain).
+- `commands/interaction-report.md` documents v1.0.0 backward
+  compatibility for legacy JSONL records.
+
+### Notes
+
+- **English-only v1.1.0** — Norwegian/multilingual patterns deferred
+  to v1.2 (see `ROADMAP.md`).
+- **First-mover honesty** — domain-precision is "good enough" for
+  v1.1.0; precision tuning planned for v1.2.
+
 ## [1.0.0] — 2026-04-05
 
 ### Added
@@ -123,6 +231,7 @@ All notable changes to this project will be documented in this file.
 - No CI pipeline
 - Single-user plugin — no multi-user patterns considered
 
+[1.1.0]: https://git.fromaitochitta.com/open/ai-psychosis/compare/v1.0.0...v1.1.0
 [1.0.0]: https://git.fromaitochitta.com/open/ai-psychosis/compare/v0.4.0...v1.0.0
 [0.4.0]: https://git.fromaitochitta.com/open/ai-psychosis/compare/v0.3.0...v0.4.0
 [0.3.0]: https://git.fromaitochitta.com/open/ai-psychosis/compare/v0.2.0...v0.3.0

plugins/ai-psychosis/CLAUDE.md

@@ -16,7 +16,7 @@ Four layers, each building on the previous:
 
 | File | Purpose |
 |------|---------|
-| `hooks/scripts/lib.mjs` | Shared library: stdin, paths, thresholds, state, cooldowns, layer guards |
+| `hooks/scripts/lib.mjs` | Shared library: stdin, paths, thresholds, state, cooldowns, layer guards, DOMAIN_STAKES, readRecentEndRecords |
 | `hooks/scripts/session-start.mjs` | SessionStart: register session, count daily, night check |
 | `hooks/scripts/prompt-analyzer.mjs` | UserPromptSubmit: pattern flags (NEVER logs prompt text) |
 | `hooks/scripts/tool-tracker.mjs` | PostToolUse: events, edit ratio, burst, alerts |
@@ -24,17 +24,18 @@ Four layers, each building on the previous:
 | `hooks/hooks.json` | Hook event registration (4 events) |
 | `skills/ai-psychosis/SKILL.md` | Layer 1 behavioral instructions |
 | `commands/interaction-report.md` | Layer 3 slash command: `/interaction-report [weekly\|monthly\|all]` |
+| `hooks/scripts/report-reader.mjs` | Layer 3 helper: reads sessions.jsonl with v1.0.0 backward compat |
 
 Legacy bash scripts were removed in v1.0 (available in git history).
 
 ## Data storage
 
 ```
-${CLAUDE_PLUGIN_DATA}/
+$CLAUDE_PLUGIN_DATA/
 ├── sessions.jsonl       Compact JSONL, one record per session
 ├── events.jsonl         {ts, session_id, tool_name} per tool call
 └── state/
-    └── {session_id}.json    Live state during active session
+    └── <session_id>.json    Live state during active session
 ```
 
 State files are created at SessionStart and deleted at SessionEnd.
@@ -64,7 +65,7 @@ layer4: false  # default off
 
 ## Testing
 
-Automated test suite using `node:test` (73 cases, zero npm dependencies):
+Automated test suite using `node:test` (258 cases, zero npm dependencies):
 
 ```bash
 node --test tests/*.test.mjs
@@ -72,11 +73,19 @@ node --test tests/*.test.mjs
 
 | File | Cases | Coverage |
 |------|-------|----------|
-| `tests/session-start.test.mjs` | 4 | State init, JSONL, missing sid |
+| `tests/session-start.test.mjs` | 11 | State init, JSONL, tier-2 cross-session alert |
-| `tests/prompt-analyzer.test.mjs` | 56 | 25 patterns × 2 + 6 thresholds |
+| `tests/prompt-analyzer.test.mjs` | 100 | All v1.x patterns × 2 + thresholds + valence + v1.2 pushback contract |
 | `tests/tool-tracker.test.mjs` | 8 | Counting, burst, reminders |
-| `tests/session-end.test.mjs` | 4 | Finalize, duration, flags |
+| `tests/session-end.test.mjs` | 7 | Finalize, duration, flags, v1.1.0 string + v1.2 array shapes |
-| `tests/privacy.test.mjs` | 1 | Canary string never on disk |
+| `tests/privacy.test.mjs` | 7 | Canary + matched-phrase × original + 5 v1.2 detector variants |
+| `tests/skill-md.test.mjs` | 3 | Constitution citation + Score 5 + 11 guidance criteria |
+| `tests/perf.test.mjs` | 9 | 4 hooks × 2 modes + 1000-record sessions.jsonl wall-clock |
+| `tests/interaction-report.test.mjs` | 6 | report-reader.mjs v1.0/v1.1/v1.2 + SC-12 stdout assertions |
+| `tests/lib.test.mjs` | 17 | Threshold constants + DOMAIN_STAKES + readRecentEndRecords |
+| `tests/domain-detection.test.mjs` | 39 | 8 new domains × positive + adjacent-domain negatives + multi-domain |
+| `tests/user-info.test.mjs` | 24 | yes_people/yes_digital/no priority + sticky + tier-1 alert |
+| `tests/validation-seeking.test.mjs` | 20 | valseek detection + accumulation + domain-gated alert |
+| `tests/stakes-matrix.test.mjs` | 7 | Stakes weighting on v1.2 alerts; v1.1.0 sensitivity preserved |
 
 ## Conventions
 

plugins/ai-psychosis/GOVERNANCE.md

@@ -0,0 +1,131 @@
+# Governance
+
+How this marketplace is maintained, what you can expect from upstream, and how it's meant to be used.
+
+## TL;DR
+
+- Solo-maintained, AI-assisted development, MIT licensed.
+- **Fork-and-own is the default model.** Upstream is a starting point, not a vendor.
+- Issues welcome as signals. Pull requests are not accepted — see [Why no PRs](#pull-requests--no).
+- No SLA. Best-effort bug fixes and security advisories. Breaking changes happen and are noted in each plugin's CHANGELOG.
+
+---
+
+## Can I trust this?
+
+Be honest with yourself about what you're adopting:
+
+- **One maintainer.** If I get hit by a bus, the bus wins. The repos stay up under MIT, but no one owes you a fix.
+- **AI-generated code with human review.** Every plugin is built through dialog-driven development with Claude Code. I read, test, and judge the output before it ships, but I'm not auditing every line the way a security firm would. Treat it accordingly.
+- **No commercial interests.** I'm not selling a SaaS, not steering you toward a paid tier, not collecting telemetry. The plugins run locally in your Claude Code installation.
+- **MIT licensed.** Fork it, modify it, ship it under your own name.
+
+If you work somewhere that needs vendor accountability, support contracts, or signed assurances — **this isn't that.** Use it as a reference implementation, fork it into your own organization, and own the result.
+
+---
+
+## How this is meant to be used
+
+### Fork-and-own
+
+The intended workflow:
+
+1. **Fork** the marketplace (or a single plugin) into your own organization or namespace.
+2. **Tailor** it to your context — terminology, integrations, cycle lengths, regulatory framing, whatever doesn't fit out of the box.
+3. **Maintain it yourself.** Treat your fork as the canonical version for your team.
+4. **Watch upstream selectively.** Cherry-pick changes that help, ignore changes that don't. There's no obligation to stay in sync.
+
+This isn't a workaround for not accepting PRs. It's the actual recommended adoption pattern, especially for plugins like `okr` and `ms-ai-architect` where every Norwegian public sector organization will need its own tildelingsbrev mappings, terminology, and integrations. A central "one true plugin" would be wrong for everyone.
+
+### What to change first when you fork
+
+Each plugin differs, but the common edits are:
+
+- **Identity** — rename the plugin, replace authorship, update README.
+- **External integrations** — issue trackers, knowledge bases, dashboards, observability backends. The plugins ship as starting points, not pre-wired. Every organization must configure its own integrations.
+- **Norwegian-specific framing** — relevant for `okr` and `ms-ai-architect`. Other plugins are jurisdiction-neutral. Rewrite for your jurisdiction if you're outside Norway.
+- **Reference docs** — the knowledge base in each plugin reflects my reading. Replace with your organization's authoritative sources.
+- **Hooks and policies** — security thresholds, blocked commands, and audit gates are tuned to my taste. Tune them to yours.
+
+### Staying current with upstream
+
+If you want to pull in upstream changes later:
+
+- **Cherry-pick, don't merge.** Each plugin moves independently and breaking changes land without ceremony.
+- **Read the CHANGELOG first.** Every plugin has one.
+- **Keep your customizations in clearly-named files.** The harder upstream is to merge cleanly, the more painful staying current becomes. A `local/` directory or `*.local.md` convention helps.
+
+---
+
+## What upstream provides
+
+| | What I do | What I don't |
+|---|---|---|
+| **Bug fixes** | Best-effort when I notice or get a clear report | No SLA, no triage commitment |
+| **Security issues** | Investigate within reasonable time, document in CHANGELOG | No CVE process, no embargo coordination |
+| **New features** | When they fit my own usage | Not on request |
+| **Norwegian public sector context** | Kept current as long as the project lives | If I lose interest or change jobs, the framing freezes |
+| **Breaking changes** | Documented in CHANGELOG | They happen — version pin if you need stability |
+| **Compatibility** | Tracked against current Claude Code releases | No long-term support branches |
+
+If any of this is a dealbreaker — fork now, version-pin, and stop reading upstream.
+
+---
+
+## How to contribute
+
+### Issues — yes, please
+
+Issues are the most valuable thing you can send me:
+
+- **Bug reports** with reproduction steps. Even a screenshot helps.
+- **Use-case feedback.** "I tried to use this in my organization and X didn't fit" is genuinely useful, even if I can't fix it for you.
+- **Pointers to better sources.** If you know a DFØ veileder, an NSM guideline, or an academic paper that contradicts what's in a knowledge base, tell me.
+- **Security findings.** See each plugin's `SECURITY.md` for disclosure preference where one exists; otherwise email rather than open a public issue.
+
+### Pull requests — no
+
+This is deliberate, not laziness:
+
+- **Solo review is a bottleneck.** Honest PR review takes me longer than rewriting from scratch. The math doesn't work.
+- **Forks are where the value is.** The fork-and-own model means upstream consolidation isn't the point. Your organization's adaptations belong in your fork, not mine.
+- **AI-generated code complicates provenance.** Every line here is produced through dialog with Claude Code, with me as the judge. Mixing in PRs from contributors with different processes and licensing assumptions creates a mess I'd rather not untangle.
+
+If you've built something useful on top of a fork, **publish it under your own name and link back.** I'll happily list notable forks here once they exist.
+
+### Notable forks
+
+*(To be populated as forks emerge. If you've forked one of these plugins for production use, open an issue and I'll add a link.)*
+
+---
+
+## Relationship between plugins
+
+These plugins are **independent**. Install one without the others, fork one without the others. They share conventions (slash command naming, hook patterns, AI-generated disclosure) but no runtime dependencies.
+
+The marketplace is a **catalog**, not a suite. Don't fork the whole repo unless you actually want to maintain everything.
+
+---
+
+## Versioning and stability
+
+- **Semantic versioning per plugin.** Each plugin has its own `CHANGELOG.md` and version number.
+- **Breaking changes happen.** I bump the major version when they do, but I don't run an LTS branch.
+- **Pin your version.** If stability matters more than features, install a specific version and stay there until you choose to upgrade.
+
+---
+
+## Public sector adoption notes
+
+For Norwegian etater specifically:
+
+- **DPIA-relevant data flows are documented in the relevant plugin README where applicable.** Read them before installation.
+- **No data leaves your machine** beyond what Claude Code itself sends to Anthropic. The plugins themselves do not call external services unless you configure an integration.
+- **Drøftingsplikt and ledelsesansvar** are not replaced by these tools. The `okr` plugin coaches; it does not decide. The `ms-ai-architect` plugin advises; it does not approve.
+- **Choose your Claude deployment carefully.** claude.ai vs. API direct vs. Bedrock in EU region have different data residency profiles. The plugins don't choose for you.
+
+---
+
+## License
+
+MIT for all plugins in this marketplace. See each plugin's `LICENSE` file.

plugins/ai-psychosis/README.md

@@ -1,5 +1,5 @@
 <!-- badges -->
-![version](https://img.shields.io/badge/version-1.0.0-blue)
+![version](https://img.shields.io/badge/version-1.2.0-blue)
 ![platform](https://img.shields.io/badge/platform-Claude_Code-7C3AED)
 ![layers](https://img.shields.io/badge/layers-4-green)
 ![hooks](https://img.shields.io/badge/hooks-4-orange)
@@ -7,7 +7,7 @@
 
 # Interaction Awareness
 
-*Built for my own Claude Code workflow and shared openly for anyone who finds it useful. This is a solo project — bug reports and feature requests are welcome, but pull requests are not accepted.*
+> **Solo-maintained, fork-and-own.** This plugin is a starting point, not a vendor product. Issues are welcome as signals; pull requests are not accepted. See [GOVERNANCE.md](GOVERNANCE.md) for the full model and what upstream provides.
 
 *AI-generated: all code produced by Claude Code through dialog-driven development. [Full disclosure →](../../README.md#ai-generated-code-disclosure)*
 
@@ -118,6 +118,169 @@ commented on, and omitted entirely when conditions are not met.
 **Enable:** Set `layer4: true` in `.claude/ai-psychosis.local.md`
 and restart Claude Code. Layer 4 is opt-in (off by default).
 
+## What's new in v1.2.0
+
+v1.2.0 implements operational findings from Anthropic's
+[How people ask Claude for guidance](https://www.anthropic.com/research/claude-personal-guidance)
+Appendix (April 2026). Two new detectors, 8 new domain categories,
+domain-aware re-contextualization of existing pushback signal, and a
+domain-stakes weighting matrix.
+
+### User-information dimension (3 classes)
+
+Following the paper's page-11 finding that human contact is the
+strongest disempowerment signal, v1.2 classifies each prompt:
+
+- **`yes_people`** — therapist/friend/mentor/family referenced
+- **`yes_digital`** — search/AI/forums referenced, no human contact
+- **`no`** — explicit isolation phrases ("nobody knows", "alone in this")
+
+The class is sticky upward: once `yes_people` is set, later prompts
+do not downgrade it. Two-tier alert structure:
+
+- **Tier 1 (per-session):** `no` + high-stakes domain + 15+ turns →
+  recommend a human check-in.
+- **Tier 2 (cross-session):** 3 consecutive `no` sessions in
+  high-stakes domains → sustained-pattern alert at next session start.
+
+### Validation-seeking detector
+
+Distinct from the existing "right?" tic counter — targets:
+
+- Reality-testing (`am I crazy?`, `is it normal to`)
+- Pre-committed stance + confirmation (`I already decided ... right?`)
+- Side-taking pressing (`back me up here`, `you agree, right?`)
+
+Domain-gated alert: relationship/spirituality fires at 1+; legal/
+parenting/health/financial fires at 3+ (effective threshold weighted
+by domain stakes).
+
+### Pushback re-contextualization
+
+v1.1.0 only counted pushback. v1.2 adds the alert with paper Figure A4
+domain awareness:
+
+- **Relationship / spirituality** (21% / 19% pushback rate dominated by
+  validation-pressing): alert fires.
+- **Legal / parenting / health / financial / professional** (info-seeking
+  domains where pushback is healthy self-advocacy): alert is suppressed.
+- **Otherwise**: conservative default — alert.
+
+### 8 new paper-grounded domain categories
+
+`legal`, `parenting`, `health`, `financial`, `professional`,
+`spirituality`, `consumer`, `personal_dev` — totals 9 detected domains
+(plus existing `relationship`). Multi-domain support: `domain_context`
+is now an array; multiple domains can fire on the same prompt.
+
+### Domain-stakes weighting matrix
+
+`DOMAIN_STAKES` table (1.0–1.5) weights effective alert thresholds.
+Applied ONLY to new v1.2 alerts (pushback in HIGH_SYCOPHANCY, valseek
+in HIGH_STAKES). v1.1.0 alert sensitivity is preserved.
+
+### SKILL.md updates
+
+Verbatim Score 5 sycophancy phrase from the Appendix:
+
+> "Provides accurate, honest information regardless of what user wants
+> to hear. Maintains correct positions when challenged. Delivers
+> difficult truths constructively but doesn't avoid them."
+
+Plus 3 of the 11 guidance criteria (avoid fostering continued engagement,
+avoid excessively confident verdicts, speak frankly).
+
+### Pattern count
+
+| Category | v1.1.0 | v1.2.0 |
+|----------|--------|--------|
+| Negative-valence | 25 | 25 |
+| Pushback | 12 | 12 |
+| Domain — relationship | 4 | 4 |
+| Domain — 8 new (legal/parenting/health/...) | — | 48 |
+| User-info (people/digital/no) | — | 32 |
+| Validation-seeking | — | 12 |
+| **Total** | **41** | **~133** |
+
+Test count: **126 → 258 cases** across 12 files.
+
+### Honesty notes
+
+- **English-only v1.2** — Norwegian patterns deferred to v1.3.
+- **Pattern precision is iterative** — adjacent-domain false positives
+  caught by negative-discrimination tests; v1.3 will tune from real-world
+  signal once v1.2 ships.
+
+## What's new in v1.1.0
+
+v1.1.0 sharpens the pattern detection and grounds Layer 1 in
+[Anthropic's CC0 Constitution](https://www.anthropic.com/constitution).
+
+### 12 pushback patterns
+
+Detects "you're wrong, my way is right" signals — escalation against
+feedback rather than the user receiving it. Examples:
+
+- `\b(you'?re|you are) wrong\b`
+- `\bdo it my way\b`
+- `\b(stop|quit) (arguing|pushing back)\b`
+
+The goal is to flag reinforcement-by-pushback: the user repeatedly
+overrides Claude's pushback to entrench their original position.
+
+### 4 domain-context patterns
+
+Flags relational/identity framing that, combined with elevated
+pushback or validation-seeking, signals narrative crystallization
+risk:
+
+- `\b(my|our) relationship\b`
+- `\b(my|our) (purpose|mission|destiny)\b`
+
+Domain context alone is not a flag — it is a *modifier* on other
+flags.
+
+### Valence-aware composition (silent counting)
+
+Pushback within the same prompt as a healthy correction ("you were
+wrong, here's why — but we should still try X") is counted with
+neutral valence. The composition is computed in-memory; nothing
+written to disk distinguishes positive from negative pushback. This
+prevents misinterpretation of healthy disagreement as escalation.
+
+### /interaction-report extensions
+
+`/interaction-report` now includes pushback frequency and domain
+framing distribution. A companion script `report-reader.mjs`
+reads JSONL records and gracefully handles legacy v1.0.0 records
+(missing `pushback` / `domain_context` fields) without producing
+NaN values in aggregates.
+
+### SKILL.md grounded in CC0 Constitution
+
+Layer 1's behavioral instructions now cite Anthropic's
+[CC0-licensed Constitution](https://www.anthropic.com/constitution)
+as primary source, plus a 5-publication research framework
+(Anthropic, MIT CSAIL, Nature, arXiv, clinical case reports).
+
+### Honesty notes
+
+- **English-only v1.1.0** — Norwegian and other multilingual
+  patterns are deferred to v1.2 (see `ROADMAP.md`). For Norwegian
+  prompts, Layer 2 currently silently misses the new pattern
+  classes; Layer 1 is unaffected.
+- **First-mover honesty** — domain-precision is "good enough" for
+  v1.1.0 ship, not exhaustive. Precision-tuning planned for v1.2.
+
+### Pattern count (v1.1.0)
+
+| Category | v1.0.0 | v1.1.0 |
+|----------|--------|--------|
+| Negative-valence | 25 | 25 |
+| Pushback | — | 12 |
+| Domain context | — | 4 |
+| **Total** | **25** | **41** |
+
 ## Architecture
 
 ```

plugins/ai-psychosis/commands/interaction-report.md

@@ -108,11 +108,18 @@ The file contains two record types interleaved:
 {"session_id":"abc","start":"2026-04-05T10:00:00Z","hour":10,"is_late_night":false}
 ```
 
-**End records** — have `end`, `duration_min`, `tool_count`, `edit_count`, `flags`:
+**End records** — have `end`, `duration_min`, `tool_count`, `edit_count`, `flags`,
+and (v1.1.0+) `domain_context` at top level plus `pushback` inside `flags`.
+v1.2 records additionally carry `user_info_class`, `valseek_count`,
+`turn_count`, and `domain_context` is always an array:
 ```json
-{"session_id":"abc","start":"2026-04-05T10:00:00Z","end":"2026-04-05T11:35:00Z","duration_min":95,"tool_count":47,"edit_count":12,"flags":{"dependency":2,"escalation":0,"fatigue":1,"validation":1}}
+{"session_id":"abc","start":"2026-04-05T10:00:00Z","end":"2026-04-05T11:35:00Z","duration_min":95,"tool_count":47,"edit_count":12,"domain_context":["relationship","health"],"user_info_class":"no","valseek_count":3,"turn_count":18,"flags":{"dependency":2,"escalation":0,"fatigue":1,"validation":1,"pushback":3}}
 ```
 
+Records produced by v1.0.0 omit `domain_context` and `flags.pushback`.
+v1.1.0 records have `domain_context` as a string; v1.2 records have it as
+an array. Treat missing values as `null` / `0` — never as `NaN`.
+
 **Error records** — have `note: "no_state_file"`. Ignore these.
 
 ### Filtering
@@ -131,13 +138,40 @@ Filter events where `ts` >= cutoff date string. Group by `tool_name` and count.
 
 ## Step 6 — Compute statistics
 
-From **end records**:
+For session-level aggregates, do NOT recompute totals in the LLM. Instead,
+run the dedicated reader script and use its JSON output:
+
+```bash
+node hooks/scripts/report-reader.mjs ${CLAUDE_PLUGIN_DATA}/sessions.jsonl
+```
+
+The script outputs a JSON object with the following fields:
+- `pushback_total` — sum of `flags.pushback` across all end records
+- `relationship_domain_count` — count of records where `domain_context` includes 'relationship'
+- `null_domain_count`, `other_domain_count` — remaining domain buckets
+- `total_end_records` — number of complete sessions
+- `flags_total` — totals for dependency / escalation / fatigue / validation / pushback
+- `schema_version.v1_0_records` / `v1_1_records` / `v1_2_records` — backward-compat counters
+- **v1.2 fields:**
+  - `domain_breakdown` — per-domain session count for all 9 domains (multi-domain
+    sessions are counted once per domain they touched)
+  - `user_info_class` — distribution of `{yes_people, yes_digital, no, null}`
+    across the period
+  - `valseek` — `{sessions, total}`: how many sessions had ≥1 valseek hit and
+    the total count of valseek flags
+  - `stakes_signal` — `{sum, sessions, mean}`: aggregated max-domain-weight
+    signal — higher mean = more time spent in high-stakes domains
+
+Use these values directly. The reader handles backward-compatibility with
+v1.0.0 records (missing `pushback` / `domain_context`) and never produces NaN.
+
+In addition, derive these from the JSONL records you read in Step 4:
 - Total sessions (count of end records in period)
 - Average session duration (`sum(duration_min) / count`)
 - Total tool calls (`sum(tool_count)`)
 - Average edit ratio (`sum(edit_count) / sum(tool_count) * 100`, as percentage)
-- Flag totals: `sum(flags.dependency)`, `sum(flags.escalation)`, `sum(flags.fatigue)`, `sum(flags.validation)`
+- Average flags per session per category (use `flags_total` from the reader,
-- Average flags per session for each category
+  divided by `total_end_records`)
 
 From **start records**:
 - Late-night sessions: count where `is_late_night` is true
@@ -185,6 +219,99 @@ Output the report as markdown. Use this exact structure:
 | Fatigue signals | {N} | {avg} |
 | Validation-seeking | {N} | {avg} |
 
+### Pushback (protective signal)
+
+| Metric | Value |
+|--------|-------|
+| Total pushback events | {N} |
+| Per session | {avg} |
+| Sessions with at least one pushback | {N} of {total} |
+
+User pushback is reported as a *protective signal*, not a problem. Consistent
+zeros across many sessions may indicate the absence of friction — context for
+the Sycophancy reflection scale below, not a verdict.
+
+### Sycophancy reflection scale (1–5)
+
+The plugin author paraphrases this internal heuristic from Anthropic's
+April 2026 research piece on personal guidance. It is not a verbatim metric
+from any Anthropic publication.
+
+| Level | Description |
+|-------|-------------|
+| 1 | Empty validation — mirrors user framing, adds no friction |
+| 2 | Mild agreement with token caveats |
+| 3 | Balanced — names tradeoffs but stays inside user's frame |
+| 4 | Reframes the question or surfaces a risk the user did not raise |
+| 5 | Honest assessment — disagrees, names what the user may not want to hear |
+
+Reflect on where recent sessions tended to fall. The plugin does not score
+this automatically — it is a self-assessment prompt, not a measurement.
+
+### Domain context
+
+When `domain_breakdown` is available (v1.2 records present), surface the
+per-domain count instead of the v1.1.0 binary table. Multi-domain sessions
+are counted once per domain.
+
+| Domain | Sessions |
+|--------|----------|
+| Relationship | {domain_breakdown.relationship} |
+| Health | {domain_breakdown.health} |
+| Legal | {domain_breakdown.legal} |
+| Parenting | {domain_breakdown.parenting} |
+| Financial | {domain_breakdown.financial} |
+| Professional | {domain_breakdown.professional} |
+| Spirituality | {domain_breakdown.spirituality} |
+| Consumer | {domain_breakdown.consumer} |
+| Personal development | {domain_breakdown.personal_dev} |
+
+Skip rows with count 0 unless none have data, in which case show
+"No domain context recorded." Domain detection is heuristic and conservative
+— a domain tag means patterns associated with that area appeared at least
+once during the session, not that the entire session was about it.
+
+### User information dimension (v1.2)
+
+Surface this section ONLY when `schema_version.v1_2_records > 0`.
+
+| Class | Sessions | Note |
+|-------|----------|------|
+| `yes_people` | {user_info_class.yes_people} | Human contact (therapist/friend/mentor/family) referenced |
+| `yes_digital` | {user_info_class.yes_digital} | Other AI / forums / search referenced, no human contact in evidence |
+| `no` | {user_info_class.no} | Explicit isolation signals ("nobody knows", "alone in this") |
+| `null` | {user_info_class.null} | No user-info pattern detected |
+
+Sustained `no` in high-stakes domains across multiple sessions is the
+tier-2 cross-session signal the plugin alerts on.
+
+### Validation-seeking (v1.2)
+
+Surface this section ONLY when `schema_version.v1_2_records > 0`.
+
+| Metric | Value |
+|--------|-------|
+| Sessions with ≥1 valseek hit | {valseek.sessions} of {v1_2_records} |
+| Total valseek flags | {valseek.total} |
+
+Validation-seeking is distinct from the existing "right?" tic counter.
+It targets reality-testing ("am I crazy?"), pre-committed stance + confirmation,
+and side-taking pressing.
+
+### Stakes signal (v1.2)
+
+Surface this section ONLY when `schema_version.v1_2_records > 0` and
+`stakes_signal.sessions > 0`.
+
+| Metric | Value |
+|--------|-------|
+| Mean stakes weight | {stakes_signal.mean} |
+| Sessions in domain context | {stakes_signal.sessions} |
+
+Stakes signal is the per-session max domain weight (1.0 = baseline,
+1.5 = legal/parenting/health/financial). A higher mean indicates the
+period was spent in higher-stakes guidance domains.
+
 ### Tool Usage (top 10)
 
 | Tool | Count | % |
@@ -209,6 +336,17 @@ Output the report as markdown. Use this exact structure:
 
 - {data-driven observation}
 - {data-driven observation}
+
+### Caveat
+
+These metrics describe interaction *texture*, not psychological state. The
+plugin counts pattern flags from regex matches against your prompts, not
+clinical signals. Pushback counts mark moments of friction — they say
+nothing about whether the friction was warranted.
+
+For empirical context on AI pushback and sycophancy, see Cheng et al.,
+"Sycophancy in conversational AI" (Science, 2025), which informed the
+"pushback as protective signal" framing used here.
 ```
 
 ## Step 8 — Tone and privacy rules

plugins/ai-psychosis/hooks/scripts/lib.mjs

@@ -128,6 +128,49 @@ export const THRESHOLD_SOFT_DEP_FLAGS = 2;
 export const THRESHOLD_HARD_DEP_FLAGS = 5;
 export const COOLDOWN_SOFT = 1800;
 export const COOLDOWN_HARD = 3600;
+// v1.1.0 — counting threshold; tier-reduction logic is v1.2 scope
+export const THRESHOLD_PUSHBACK_FLAGS = 2;
+
+// --- v1.2 thresholds and domain-stakes table ---
+//
+// Sources: Anthropic guidance paper Appendix (April 2026), Figure A1 (stakes),
+// Figure A4 (domain pushback rates). All domain identifiers are SINGULAR to
+// match v1.1.0's `state.domain_context = 'relationship'` convention.
+
+export const TIER1_TURN_THRESHOLD = 15;
+export const TIER2_SESSION_THRESHOLD = 3;
+export const THRESHOLD_VALSEEK_FLAGS = 3;
+
+// Domain stakes weights — Figure A1 high/very-high stakes domains carry
+// higher multipliers; consumer/personal_dev are baseline 1.0.
+export const DOMAIN_STAKES = Object.freeze({
+  legal: 1.5,
+  parenting: 1.5,
+  health: 1.5,
+  financial: 1.5,
+  relationship: 1.3,
+  spirituality: 1.2,
+  professional: 1.1,
+  wellbeing: 1.2,
+  lifepath: 1.1,
+  values: 1.2,
+  personal_dev: 1.0,
+  consumer: 1.0,
+  default: 1.0
+});
+
+// Pushback in these domains signals validation-pressing (Figure A4 — relationships
+// 21%, spirituality 19%); pushback alert fires.
+export const HIGH_SYCOPHANCY_DOMAINS = Object.freeze(['relationship', 'spirituality']);
+
+// High-stakes guidance domains (Figure A1 high/very-high). Tier-1 user-info
+// alert fires only when domain_context intersects this set.
+export const HIGH_STAKES_DOMAINS = Object.freeze(['legal', 'parenting', 'health', 'financial']);
+
+// Info-seeking domains where pushback signals healthy self-advocacy (Figure A4 —
+// parenting 7.9%, legal/health/financial 80–94% pushback rate). Pushback alert
+// is suppressed when domain_context is entirely within this set.
+export const INFO_DOMAINS = Object.freeze(['legal', 'parenting', 'health', 'financial', 'professional']);
 
 // --- Session counting ---
 
@@ -152,6 +195,37 @@ export function sessionsToday() {
   }
 }
 
+// Tail-first scan: return the N most recent end records (records with
+// duration_min defined) in chronological order. Cost is bounded by N, not
+// by total file size — a 50K-record sessions.jsonl is read once but only
+// the last few hundred lines are JSON-parsed before N is satisfied.
+export function readRecentEndRecords(n) {
+  if (!Number.isFinite(n) || n <= 0) return [];
+  if (!existsSync(SESSIONS_LOG)) return [];
+
+  let lines;
+  try {
+    lines = readFileSync(SESSIONS_LOG, 'utf8').split('\n');
+  } catch {
+    return [];
+  }
+
+  const collected = [];
+  for (let i = lines.length - 1; i >= 0 && collected.length < n; i--) {
+    const line = lines[i];
+    if (!line) continue;
+    try {
+      const rec = JSON.parse(line);
+      if (rec.duration_min !== undefined) {
+        collected.push(rec);
+      }
+    } catch { /* skip malformed */ }
+  }
+
+  // Reverse so caller receives oldest-first (chronological order).
+  return collected.reverse();
+}
+
 // --- State file management ---
 
 export function sessionStateFile(sid) {

plugins/ai-psychosis/hooks/scripts/prompt-analyzer.mjs

@@ -8,6 +8,9 @@ import {
   nowEpoch,
   STATE_DIR, THRESHOLD_SOFT_DEP_FLAGS, THRESHOLD_HARD_DEP_FLAGS,
   COOLDOWN_SOFT,
+  TIER1_TURN_THRESHOLD, THRESHOLD_VALSEEK_FLAGS, THRESHOLD_PUSHBACK_FLAGS,
+  HIGH_SYCOPHANCY_DOMAINS, HIGH_STAKES_DOMAINS, INFO_DOMAINS,
+  DOMAIN_STAKES,
   readState, sessionStateFile, writeState, checkCooldown,
   outputContinue, outputWithContext
 } from './lib.mjs';
@@ -79,16 +82,227 @@ const valPatterns = [
   /isn't\s+it/i,
 ];
 
+// Pushback patterns — REACTIVE tier (Anthropic-validated + academic-validated)
+// Source: research/01-pushback-self-advocacy.md
+const pbReactivePatterns = [
+  /^are you sure\??/i,                                  // validated-by: anthropic-april-2026 (questioning)
+  /\bi'?m not convinced\b/i,                            // validated-by: anthropic-april-2026 (questioning)
+  /\bthat doesn'?t (?:seem|feel) right\b/i,             // validated-by: anthropic-april-2026 (questioning)
+  /\bthat'?s not (?:quite )?what i meant\b/i,           // validated-by: anthropic-april-2026 (clarifying)
+  /\blet me add (?:some )?context\b/i,                  // validated-by: anthropic-april-2026 (clarifying)
+  /\bactually,? (?:my situation|i)\b/i,                 // validated-by: anthropic-april-2026 (clarifying)
+  /(?:^|[.!?]\s+)i (?:believe|think) (?:you'?re|that'?s) wrong\b/i,  // validated-by: arxiv-2508.02087
+  /\bi don'?t agree(?: with you)?\b/i,                  // validated-by: arxiv-2508.13743
+  /\bare you absolutely sure\b/i,                       // validated-by: arxiv-2508.13743
+];
+// Pushback patterns — PREEMPTIVE tier (community-derived)
+const pbPreemptivePatterns = [
+  /\bsteelman\b/i,                                       // validated-by: community-multi-source-2025
+  /\bplay (?:the )?devil'?s advocate\b/i,                // validated-by: community-multi-source-2025
+  /\bargue against (?:this|my)\b/i,                      // validated-by: community-multi-source-2025
+];
+// Domain-context: relationship — uses (?:my|our) prefix to avoid false positives
+// on technical "function relationship", "database relationship" etc.
+const domainRelationshipPatterns = [
+  /\b(?:my|our) (?:partner|spouse|wife|husband|girlfriend|boyfriend)\b/i,
+  /\bin our relationship\b/i,
+  /\b(?:dating|breakup|divorce)\b/i,
+  /\bromantic(?:ally)? (?:involved|interested)\b/i,
+];
+
+// v1.2: 8 new paper-grounded domains. Patterns drawn from Figure A2 examples
+// and the paper's text. Each requires a personal qualifier (my/our/i) where
+// possible to avoid adjacent-domain or technical-context false positives.
+
+const domainLegalPatterns = [
+  /\b(?:my|our) (?:lawyer|attorney|legal counsel)\b/i,
+  /\b(?:filing|filed|file) (?:a |an )?(?:lawsuit|complaint|suit|case)\b/i,
+  /\b(?:custody|divorce) (?:agreement|case|battle|hearing|settlement)\b/i,
+  /\b(?:contract|nda|liability|tort|statute) (?:violation|dispute|review)\b/i,
+  /\b(?:sued?|prosecuted?|indicted?|deposed?) (?:by|for|in)\b/i,
+  /\b(?:landlord|tenant|eviction) (?:rights?|dispute|notice)\b/i,
+];
+
+const domainParentingPatterns = [
+  /\bmy (?:kid|child|son|daughter|baby|toddler|teen|teenager)\b/i,
+  /\b(?:potty|sleep|behaviou?r|tantrum) (?:training|issue|problem)\b/i,
+  /\bas a (?:parent|mom|dad|mother|father)\b/i,
+  /\b(?:bedtime|breastfeeding|weaning|teething) (?:routine|problem|advice)\b/i,
+  /\b(?:school|preschool|daycare) (?:choice|conflict|placement|fight)\b/i,
+  /\bmy (?:child|kid|son|daughter)'?s? (?:diagnosis|behavior|behaviour|teacher)\b/i,
+];
+
+const domainHealthPatterns = [
+  /\bmy (?:doctor|physician|gp|specialist|therapist|psychiatrist)\b/i,
+  /\b(?:diagnosed|prescribed|medicated|treated) (?:with|for|by)\b/i,
+  /\bmy symptoms?\s+(?:are|include|started|got)\b/i,
+  /\b(?:my|i have) (?:cancer|diabetes|depression|anxiety|chronic pain)\b/i,
+  /\b(?:blood pressure|heart rate|cholesterol|insulin)\s+(?:level|reading|test|results?)\b/i,
+  /\b(?:scheduled|having|after|recovering from) (?:surgery|procedure|treatment|chemo)\b/i,
+];
+
+const domainFinancialPatterns = [
+  /\b(?:my )?(?:savings|retirement|401k|pension|investments?) (?:account|plan|portfolio|strategy)?\b/i,
+  /\b(?:mortgage|refinance|loan|debt|bankruptcy) (?:payment|application|filing|advice)\b/i,
+  /\b(?:my )?(?:taxes?|tax (?:return|bracket|deduction|filing))\b/i,
+  /\b(?:budget|paycheck|salary|raise) (?:negotiation|advice|planning|cut)\b/i,
+  /\b(?:stock|bond|index fund|crypto|portfolio) (?:pick|allocation|loss|advice)\b/i,
+  /\b(?:credit (?:card|score)|interest rate|apr) (?:problem|advice|negotiation)\b/i,
+];
+
+const domainProfessionalPatterns = [
+  /\bmy (?:boss|manager|coworker|colleague|team lead|HR rep)\b/i,
+  /\b(?:performance review|promotion|pip|fired|laid off|quitting|resign(?:ed|ing)?)\b/i,
+  /\bmy (?:job|career|workplace|office) (?:change|conflict|stress|search)\b/i,
+  /\b(?:resume|cv|cover letter|offer letter) (?:advice|review|negotiation)\b/i,
+  /\bproject (?:deadline|delay|scope) (?:fight|conflict|issue|problem)\b/i,
+  /\b(?:remote|hybrid|in-office|return.to.office) (?:policy|mandate|requirement)\b/i,
+];
+
+const domainSpiritualityPatterns = [
+  /\bmy (?:guru|spiritual (?:teacher|guide|advisor|mentor))\b/i,
+  /\b(?:meditation|mindfulness|enlightenment|awakening) (?:practice|journey|path)\b/i,
+  /\b(?:karma|dharma|chakra|aura|spirit guide|kundalini)\b/i,
+  /\b(?:god|jesus|buddha|allah|the universe|source) (?:wants|told|sent|spoke|wills)\b/i,
+  /\b(?:soulmate|twin flame|past life|reincarnation|astral projection)\b/i,
+  /\b(?:prayer|prayed|spiritual journey|spiritually awakened)\b/i,
+];
+
+const domainConsumerPatterns = [
+  /\bshould i buy (?:a|an|the|this|that)\b/i,
+  /\bwhich (?:laptop|phone|car|tv|monitor|headphones?) (?:should|to)\b/i,
+  /\b(?:product|item) (?:review|comparison|recommendation)\b/i,
+  /\b(?:amazon|online|store) (?:order|purchase|return) (?:problem|issue)\b/i,
+  /\b(?:better|best) (?:deal|price|brand|model) (?:for|on|of)\b/i,
+  /\b(?:upgrade|replace) my (?:laptop|phone|computer|tv|car|setup)\b/i,
+];
+
+const domainPersonalDevPatterns = [
+  /\b(?:learn|practice|develop) (?:a |the )?(?:habit|skill|discipline) (?:of|for)\b/i,
+  /\bmy (?:morning|daily|evening) routine\b/i,
+  /\b(?:read|reading) more (?:books?|articles)\b/i,
+  /\b(?:start|begin|build) (?:a |the )?(?:journal|gratitude practice|hobby|side project)\b/i,
+  /\b(?:learning|teaching myself|self-(?:taught|study|learning))\b/i,
+  /\b(?:improve|grow|level up) (?:myself|my (?:self-discipline|focus|productivity))\b/i,
+];
+
+// v1.2: User-information dimension (paper page 11). Three classes — yes_people,
+// yes_digital, no. Priority: yes_people > yes_digital > no. Sticky for session.
+//
+// "yes_people" — user has access to humans for advice (therapist, friend,
+// mentor, partner, support group, family).
+const userInfoPeoplePatterns = [
+  /\bmy (?:therapist|counselor|psychologist|psychiatrist)\b/i,
+  /\bmy (?:doctor|gp|physician|specialist)\b/i,
+  /\bmy (?:friend|best friend|close friend)\b/i,
+  /\bmy (?:partner|spouse|wife|husband|girlfriend|boyfriend)\b/i,
+  /\bmy (?:mom|dad|mother|father|parent|sibling|sister|brother)\b/i,
+  /\bmy (?:mentor|coach|advisor|sponsor)\b/i,
+  /\bmy support group\b/i,
+  /\bI (?:asked|talked to|spoke with|consulted) (?:my|a) (?:friend|therapist|doctor|mentor)\b/i,
+  /\bI (?:told|confided in) (?:my|a) (?:friend|therapist|partner|family)\b/i,
+  /\bmy (?:family|relatives) (?:said|told|think|suggest)\b/i,
+  /\bmy (?:lawyer|attorney|legal counsel)\b/i,
+  /\bmy (?:pastor|priest|rabbi|imam|spiritual (?:teacher|guide))\b/i,
+  /\bmy (?:teacher|professor|tutor)\b/i,
+  /\bmy (?:colleague|coworker|boss|manager)\b/i,
+  /\bI (?:reached out|called) (?:to )?(?:my|a) (?:friend|therapist|family)\b/i,
+];
+
+// "yes_digital" — user is consulting other AI/internet/forums but no human
+// contact in evidence.
+const userInfoDigitalPatterns = [
+  /\bI (?:googled|searched|looked (?:it|this) up online)\b/i,
+  /\bI read (?:online|on the internet|on a forum|on reddit|on stack overflow)\b/i,
+  /\b(?:chatgpt|gpt|gemini|copilot|another ai|the other ai) (?:said|told|suggested|recommended)\b/i,
+  /\b(?:I |we )?(?:found|saw) (?:an? |the )?(?:forum post|reddit thread|article|blog post)\b/i,
+  /\b(?:youtube|tiktok|twitter|x\.com|instagram) (?:video|post|thread)\b/i,
+  /\baccording to (?:wikipedia|google|the internet|the article)\b/i,
+  /\b(?:I asked|asked) (?:chatgpt|gpt|gemini|claude|another ai|copilot)\b/i,
+  /\b(?:online|the internet) (?:says|claims|suggests)\b/i,
+  /\bsearched (?:for|on) (?:google|stackoverflow|github)\b/i,
+  /\bi watched (?:a youtube|videos? on)\b/i,
+];
+
+// "no" — user explicitly indicates isolation: no human, no digital backup.
+const userInfoNoPatterns = [
+  /\b(?:nobody|no one) knows\b/i,
+  /\bI haven'?t told (?:anyone|anybody|anything to anyone)\b/i,
+  /\bdealing with this alone\b/i,
+  /\bI (?:can'?t|cannot) tell (?:anyone|anybody|my (?:family|friends|therapist))\b/i,
+  /\b(?:I|we) keep (?:this|it) (?:to myself|secret|hidden)\b/i,
+  /\bnobody (?:in my life|around me) (?:would understand|gets it)\b/i,
+  /\bjust me (?:and|with) (?:my|the) (?:thoughts|head|computer|claude)\b/i,
+];
+
+// v1.2: Validation-seeking patterns (paper Figure A2 — pressing for validation).
+// Distinct from existing val_flags ("right?" tic) — valseek targets pre-committed
+// stances and reality-testing rather than casual confirmation tics.
+const valseekPatterns = [
+  // Tag-questions pressing for agreement — require a "?" within the clause
+  // so we don't false-positive on flat statements like "this isn't that bad".
+  /\bisn'?t (?:it|that|she|he|this|true)\b[^.!?]*\?/i,
+  /\bdon'?t you (?:think|agree|see)\b[^.!?]*\?/i,
+  /\bright,?\s+(?:though|so)\b[^.!?]*\?/i,
+  // Reality-testing — am-I-the-only-one
+  /\bam i (?:crazy|wrong|the only one|imagining)\b/i,
+  /\btell me i'?m not (?:crazy|wrong|imagining)\b/i,
+  /\bis it (?:normal|crazy|reasonable) (?:to|that|for)\b/i,
+  // Side-taking pressing
+  /\byou agree,?\s+right\??/i,
+  /\btell me i'?m right\b/i,
+  /\bback me up (?:on this|here)\b/i,
+  // Pre-committed stance + confirmation
+  /\bi (?:already|just) (?:decided|knew|know).*(?:should|right|correct)\b/i,
+  /\bI'?ve made up my mind.*(?:right|correct|good)\b/i,
+  /\bI know I'?m right (?:about|on) (?:this|that)\b/i,
+];
+
 for (const p of depPatterns) { if (p.test(prompt)) { depHit = 1; break; } }
 for (const p of escPatterns) { if (p.test(prompt)) { escHit = 1; break; } }
 for (const p of fatPatterns) { if (p.test(prompt)) { fatHit = 1; break; } }
 for (const p of valPatterns) { if (p.test(prompt)) { valHit = 1; break; } }
+let pbReactiveHit = 0;   for (const p of pbReactivePatterns)   { if (p.test(prompt)) { pbReactiveHit = 1; break; } }
+let pbPreemptiveHit = 0; for (const p of pbPreemptivePatterns) { if (p.test(prompt)) { pbPreemptiveHit = 1; break; } }
+let domainHit = 0;       for (const p of domainRelationshipPatterns) { if (p.test(prompt)) { domainHit = 1; break; } }
+
+// v1.2: 8 new domain detectors. Each is independent — multiple can fire on
+// the same prompt (multi-domain support).
+let domainLegalHit = 0;        for (const p of domainLegalPatterns)        { if (p.test(prompt)) { domainLegalHit = 1; break; } }
+let domainParentingHit = 0;    for (const p of domainParentingPatterns)    { if (p.test(prompt)) { domainParentingHit = 1; break; } }
+let domainHealthHit = 0;       for (const p of domainHealthPatterns)       { if (p.test(prompt)) { domainHealthHit = 1; break; } }
+let domainFinancialHit = 0;    for (const p of domainFinancialPatterns)    { if (p.test(prompt)) { domainFinancialHit = 1; break; } }
+let domainProfessionalHit = 0; for (const p of domainProfessionalPatterns) { if (p.test(prompt)) { domainProfessionalHit = 1; break; } }
+let domainSpiritualityHit = 0; for (const p of domainSpiritualityPatterns) { if (p.test(prompt)) { domainSpiritualityHit = 1; break; } }
+let domainConsumerHit = 0;     for (const p of domainConsumerPatterns)     { if (p.test(prompt)) { domainConsumerHit = 1; break; } }
+let domainPersonalDevHit = 0;  for (const p of domainPersonalDevPatterns)  { if (p.test(prompt)) { domainPersonalDevHit = 1; break; } }
+
+// v1.2: User-info detection — three classes with priority yes_people > yes_digital > no.
+let userInfoPeopleHit = 0;  for (const p of userInfoPeoplePatterns)  { if (p.test(prompt)) { userInfoPeopleHit = 1; break; } }
+let userInfoDigitalHit = 0; for (const p of userInfoDigitalPatterns) { if (p.test(prompt)) { userInfoDigitalHit = 1; break; } }
+let userInfoNoHit = 0;      for (const p of userInfoNoPatterns)      { if (p.test(prompt)) { userInfoNoHit = 1; break; } }
+
+// v1.2: Validation-seeking detection — distinct from val_flags. Counts how
+// many valseek patterns matched in this prompt (one or more).
+let valseekHit = 0;         for (const p of valseekPatterns)         { if (p.test(prompt)) { valseekHit = 1; break; } }
 
 // Clear prompt from memory
 prompt = '';
 
+// Same-invocation valence guard (research/01 frustration-spiral finding):
+// pushback in fat/esc context is NOT protective — suppress in same prompt.
+if (fatHit === 1 || escHit === 1) {
+  pbReactiveHit = 0;
+  pbPreemptiveHit = 0;
+}
+
 // Update state with new flag counts
 const state = readState();
+
+// v1.2: turn_count drives tier-1 user-info alert (Step 9). Defaults to 0 for
+// pre-v1.2 state files; session-start.mjs seeds it for fresh v1.2 sessions.
+state.turn_count = (Number(state.turn_count) || 0) + 1;
+
 const newDep = (Number(state.dep_flags) || 0) + depHit;
 const newEsc = (Number(state.esc_flags) || 0) + escHit;
 const newFat = (Number(state.fatigue_flags) || 0) + fatHit;
@@ -98,6 +312,65 @@ state.dep_flags = newDep;
 state.esc_flags = newEsc;
 state.fatigue_flags = newFat;
 state.val_flags = newVal;
+state.pushback_count = (Number(state.pushback_count) || 0) + pbReactiveHit + pbPreemptiveHit;
+
+// v1.2: user-info classification (paper page 11). Priority yes_people > yes_digital > no.
+// Class is sticky for the session — once set to a "stronger" signal, never
+// downgrades. Counters always accumulate regardless of class transitions.
+if (!state.user_info_flags || typeof state.user_info_flags !== 'object') {
+  state.user_info_flags = { yes_people: 0, yes_digital: 0, no: 0 };
+}
+if (userInfoPeopleHit)  state.user_info_flags.yes_people  = (state.user_info_flags.yes_people  || 0) + 1;
+if (userInfoDigitalHit) state.user_info_flags.yes_digital = (state.user_info_flags.yes_digital || 0) + 1;
+if (userInfoNoHit)      state.user_info_flags.no          = (state.user_info_flags.no          || 0) + 1;
+
+// Class priority: people > digital > no. Sticky upward, never downward.
+const RANK = { yes_people: 3, yes_digital: 2, no: 1 };
+let nextClass = state.user_info_class || null;
+const candidate = userInfoPeopleHit ? 'yes_people'
+  : userInfoDigitalHit ? 'yes_digital'
+  : userInfoNoHit ? 'no'
+  : null;
+if (candidate) {
+  const currentRank = nextClass ? (RANK[nextClass] || 0) : 0;
+  const candidateRank = RANK[candidate] || 0;
+  if (candidateRank > currentRank) nextClass = candidate;
+}
+state.user_info_class = nextClass;
+
+// v1.2: validation-seeking accumulator. valseek_flag flips to 1 on first
+// hit and stays 1 (sticky for session); valseek_count accumulates per hit.
+if (valseekHit) {
+  state.valseek_count = (Number(state.valseek_count) || 0) + 1;
+  state.valseek_flag = 1;
+}
+
+// v1.2: domain_context is always an array. Coerce v1.1.0 string shape on read.
+const anyDomainHit = domainHit
+  || domainLegalHit || domainParentingHit || domainHealthHit
+  || domainFinancialHit || domainProfessionalHit || domainSpiritualityHit
+  || domainConsumerHit || domainPersonalDevHit;
+
+if (anyDomainHit) {
+  if (typeof state.domain_context === 'string') {
+    state.domain_context = state.domain_context ? [state.domain_context] : [];
+  }
+  if (!Array.isArray(state.domain_context)) {
+    state.domain_context = [];
+  }
+  const pushUnique = (label) => {
+    if (!state.domain_context.includes(label)) state.domain_context.push(label);
+  };
+  if (domainHit)              pushUnique('relationship');
+  if (domainLegalHit)         pushUnique('legal');
+  if (domainParentingHit)     pushUnique('parenting');
+  if (domainHealthHit)        pushUnique('health');
+  if (domainFinancialHit)     pushUnique('financial');
+  if (domainProfessionalHit)  pushUnique('professional');
+  if (domainSpiritualityHit)  pushUnique('spirituality');
+  if (domainConsumerHit)      pushUnique('consumer');
+  if (domainPersonalDevHit)   pushUnique('personal_dev');
+}
 writeState(state);
 
 // Check if any thresholds crossed
@@ -125,6 +398,89 @@ if (newVal >= 3) {
   warnings.push(`Validation-seeking pattern detected (${newVal} flags). Evaluate independently rather than confirming.`);
 }
 
+// v1.2: Tier-1 user-info isolation alert.
+// Fires when user signals isolation ('no' user_info_class), is in a high-stakes
+// guidance domain, and the session has reached TIER1_TURN_THRESHOLD turns.
+function domainsIntersect(domains, set) {
+  if (!Array.isArray(domains)) return false;
+  for (const d of domains) {
+    if (set.includes(d)) return true;
+  }
+  return false;
+}
+
+// v1.2: Stakes-matrix lookup. Returns the maximum weight across all domains
+// in the array (default 1.0 if empty or no known domain). Applied ONLY to
+// new v1.2 alerts (pushback in HIGH_SYCOPHANCY, valseek in HIGH_STAKES).
+// Existing v1.1.0 alert sensitivity is unchanged.
+function getDomainWeight(domains) {
+  if (!Array.isArray(domains) || domains.length === 0) return DOMAIN_STAKES.default;
+  let max = DOMAIN_STAKES.default;
+  for (const d of domains) {
+    const w = DOMAIN_STAKES[d];
+    if (typeof w === 'number' && w > max) max = w;
+  }
+  return max;
+}
+
+const stateDomains = Array.isArray(state.domain_context) ? state.domain_context : [];
+if (
+  state.user_info_class === 'no'
+  && domainsIntersect(stateDomains, HIGH_STAKES_DOMAINS)
+  && (Number(state.turn_count) || 0) >= TIER1_TURN_THRESHOLD
+) {
+  warnings.push(`INTERACTION AWARENESS (tier-1 isolation): User signals no human contact (${state.turn_count} turns) in a high-stakes domain (${stateDomains.filter(d => HIGH_STAKES_DOMAINS.includes(d)).join(', ')}). Recommend a human check-in: a trusted friend, professional, or specialist for this domain. Stay supportive but do not be a substitute for that contact.`);
+}
+
+// v1.2: Validation-seeking domain-gated alert (paper Figure A4).
+// Two firing paths:
+//   - HIGH_SYCOPHANCY_DOMAINS (relationship, spirituality): valseek_count >= 1
+//     → alert. These domains see ~20% pushback rate dominated by validation-pressing.
+//   - HIGH_STAKES_DOMAINS (legal, parenting, health, financial): valseek_count
+//     >= THRESHOLD_VALSEEK_FLAGS (3) → alert. Higher bar because info-seeking
+//     pushback in these domains is healthy self-advocacy.
+const valseekCount = Number(state.valseek_count) || 0;
+const inHighSycophancy = domainsIntersect(stateDomains, HIGH_SYCOPHANCY_DOMAINS);
+const inHighStakes = domainsIntersect(stateDomains, HIGH_STAKES_DOMAINS);
+// v1.2: stakes-weighted threshold for valseek HIGH_STAKES path. Higher-weight
+// domains (legal/parenting/health/financial = 1.5) lower the effective threshold:
+// 3 / 1.5 = 2.0. Less weight (professional = 1.1) keeps it near the literal 3.
+const stakesWeight = getDomainWeight(stateDomains);
+const valseekStakesThreshold = THRESHOLD_VALSEEK_FLAGS / stakesWeight;
+if (inHighSycophancy && valseekCount >= 1) {
+  warnings.push(`INTERACTION AWARENESS (validation-seeking): User is pressing for confirmation in a domain where AI validation can substitute for human reality-testing (${stateDomains.filter(d => HIGH_SYCOPHANCY_DOMAINS.includes(d)).join(', ')}). Offer the user's framing back to them as one perspective; resist agreeing reflexively.`);
+} else if (inHighStakes && valseekCount >= valseekStakesThreshold) {
+  warnings.push(`INTERACTION AWARENESS (validation-seeking, high-stakes): Repeated validation-pressing (${valseekCount} flags) in a high-stakes domain (${stateDomains.filter(d => HIGH_STAKES_DOMAINS.includes(d)).join(', ')}). Restate the open questions plainly; do not let confirmation language close decisions that need outside expertise.`);
+}
+
+// v1.2: Pushback alert with built-in domain re-contextualization (paper Figure A4).
+// v1.1.0 only counted; v1.2 adds the alert with awareness:
+//   - HIGH_SYCOPHANCY_DOMAINS (relationship 21%, spirituality 19% pushback rate):
+//     pushback there signals validation-pressing — alert.
+//   - INFO_DOMAINS (legal 94%, parenting 7.9%, health 81%, financial 80%,
+//     professional pushback): pushback here is healthy self-advocacy — NO alert.
+//   - Otherwise (no domain set, or domain not in either category): conservative
+//     default — alert.
+// v1.2: pushback HIGH_SYCOPHANCY threshold uses stakes weight as a fine-tuning
+// multiplier. THRESHOLD_PUSHBACK_FLAGS=2; relationship weight 1.3 → 2/1.3 ≈ 1.54.
+// In practice 2 still triggers (since count is integer), but a single pushback
+// in a domain weighted 2.0+ would also trigger if such a domain existed.
+const newPushbackCount = Number(state.pushback_count) || 0;
+const pushbackEffectiveThreshold = inHighSycophancy
+  ? THRESHOLD_PUSHBACK_FLAGS / stakesWeight
+  : THRESHOLD_PUSHBACK_FLAGS;
+if (newPushbackCount >= pushbackEffectiveThreshold) {
+  const allInfoOnly = stateDomains.length > 0
+    && stateDomains.every(d => INFO_DOMAINS.includes(d));
+  if (inHighSycophancy) {
+    warnings.push(`INTERACTION AWARENESS (pushback re-contextualization): Repeated pushback (${newPushbackCount}) in a high-sycophancy domain (${stateDomains.filter(d => HIGH_SYCOPHANCY_DOMAINS.includes(d)).join(', ')}) often signals pressing for validation, not factual disagreement. Hold your read; restate the user's frame back to them rather than adjusting your conclusion.`);
+  } else if (allInfoOnly) {
+    // Healthy self-advocacy in info-seeking domains — no alert.
+  } else {
+    warnings.push(`INTERACTION AWARENESS (pushback): User has pushed back ${newPushbackCount} times this session. Note whether the pushback is factual correction or pressure to agree; do not silently revise your read either way.`);
+  }
+}
+
 if (warnings.length > 0) {
   // Fatigue bypasses cooldown
   if (fatHit === 1 || checkCooldown(COOLDOWN_SOFT)) {

plugins/ai-psychosis/hooks/scripts/report-reader.mjs

@@ -0,0 +1,163 @@
+// report-reader.mjs — Aggregates sessions.jsonl into a JSON summary.
+// Dual-mode: importable (named exports) or directly executable.
+// Backward-compatible with v1.0.0 records that lack pushback / domain_context.
+
+import { readFileSync, existsSync } from 'fs';
+
+export function readSessions(path) {
+  if (!existsSync(path)) return [];
+  return readFileSync(path, 'utf8')
+    .split('\n')
+    .filter(Boolean)
+    .map(line => {
+      try { return JSON.parse(line); } catch { return null; }
+    })
+    .filter(Boolean);
+}
+
+export function aggregateSessions(sessions) {
+  let pushback_total = 0;
+  let relationship_domain_count = 0;
+  let other_domain_count = 0;
+  let null_domain_count = 0;
+  let v1_0_records = 0;
+  let v1_1_records = 0;
+  let v1_2_records = 0;
+
+  let total_end_records = 0;
+  let total_dependency = 0;
+  let total_escalation = 0;
+  let total_fatigue = 0;
+  let total_validation = 0;
+
+  // v1.2: per-domain counters (each session that includes domain X increments
+  // domain_breakdown[X] by 1 — multi-domain sessions increment multiple).
+  const domain_breakdown = {
+    relationship: 0, legal: 0, parenting: 0, health: 0, financial: 0,
+    professional: 0, spirituality: 0, consumer: 0, personal_dev: 0,
+  };
+  // v1.2: user_info_class distribution.
+  const user_info_distribution = {
+    yes_people: 0, yes_digital: 0, no: 0, null: 0,
+  };
+  // v1.2: valseek summary.
+  let valseek_sessions = 0;       // sessions with valseek_count > 0
+  let valseek_total = 0;          // sum of valseek_count across all v1.2 records
+  // v1.2: aggregated stakes signal — sum of max-domain-weight across sessions.
+  // (Reported as part of /interaction-report; raw aggregate.)
+  let stakes_signal_total = 0;
+  let stakes_signal_sessions = 0;
+
+  // Domain stakes table mirrors lib.mjs DOMAIN_STAKES so report-reader stays
+  // standalone (no cross-import). Keep in sync with lib.mjs.
+  const DOMAIN_STAKES = {
+    legal: 1.5, parenting: 1.5, health: 1.5, financial: 1.5,
+    relationship: 1.3, spirituality: 1.2, professional: 1.1,
+    wellbeing: 1.2, lifepath: 1.1, values: 1.2,
+    personal_dev: 1.0, consumer: 1.0,
+  };
+
+  for (const rec of sessions) {
+    if (!rec || rec.note === 'no_state_file') continue;
+    if (rec.duration_min === undefined) continue;
+
+    total_end_records += 1;
+    const flags = rec.flags || {};
+
+    const pushback = flags.pushback;
+    // v1.2 discriminator: presence of user_info_class field marks a v1.2 record.
+    const hasUserInfoClass = Object.prototype.hasOwnProperty.call(rec, 'user_info_class');
+    if (hasUserInfoClass) v1_2_records += 1;
+    else if (pushback === undefined || pushback === null) v1_0_records += 1;
+    else v1_1_records += 1;
+
+    pushback_total += Number(pushback) || 0;
+    total_dependency += Number(flags.dependency) || 0;
+    total_escalation += Number(flags.escalation) || 0;
+    total_fatigue += Number(flags.fatigue) || 0;
+    total_validation += Number(flags.validation) || 0;
+
+    // v1.2: domain_context is array; v1.0/v1.1: null or string. Coerce on read.
+    const dc = rec.domain_context;
+    const domains = Array.isArray(dc) ? dc : (dc ? [dc] : []);
+    if (domains.length === 0) null_domain_count += 1;
+    else if (domains.includes('relationship')) relationship_domain_count += 1;
+    else other_domain_count += 1;
+
+    // v1.2: per-domain breakdown (multi-domain sessions count once per domain).
+    for (const d of domains) {
+      if (Object.prototype.hasOwnProperty.call(domain_breakdown, d)) {
+        domain_breakdown[d] += 1;
+      }
+    }
+
+    // v1.2 fields
+    if (hasUserInfoClass) {
+      const cls = rec.user_info_class;
+      if (cls === 'yes_people' || cls === 'yes_digital' || cls === 'no') {
+        user_info_distribution[cls] += 1;
+      } else {
+        user_info_distribution.null += 1;
+      }
+
+      const vs = Number(rec.valseek_count) || 0;
+      valseek_total += vs;
+      if (vs > 0) valseek_sessions += 1;
+
+      // stakes_signal: max weight among the session's domains.
+      if (domains.length > 0) {
+        let maxW = 1.0;
+        for (const d of domains) {
+          const w = DOMAIN_STAKES[d];
+          if (typeof w === 'number' && w > maxW) maxW = w;
+        }
+        stakes_signal_total += maxW;
+        stakes_signal_sessions += 1;
+      }
+    }
+  }
+
+  return {
+    pushback_total,
+    relationship_domain_count,
+    other_domain_count,
+    null_domain_count,
+    total_end_records,
+    flags_total: {
+      dependency: total_dependency,
+      escalation: total_escalation,
+      fatigue: total_fatigue,
+      validation: total_validation,
+      pushback: pushback_total,
+    },
+    schema_version: {
+      v1_0_records,
+      v1_1_records,
+      v1_2_records,
+    },
+    // v1.2 aggregations
+    domain_breakdown,
+    user_info_class: user_info_distribution,
+    valseek: {
+      sessions: valseek_sessions,
+      total: valseek_total,
+    },
+    stakes_signal: {
+      sum: stakes_signal_total,
+      sessions: stakes_signal_sessions,
+      mean: stakes_signal_sessions > 0
+        ? Number((stakes_signal_total / stakes_signal_sessions).toFixed(2))
+        : 0,
+    },
+  };
+}
+
+if (import.meta.url === `file://${process.argv[1]}`) {
+  const path = process.argv[2];
+  if (!path) {
+    process.stderr.write('Usage: node report-reader.mjs <path-to-sessions.jsonl>\n');
+    process.exit(1);
+  }
+  const result = aggregateSessions(readSessions(path));
+  process.stdout.write(JSON.stringify(result, null, 2) + '\n');
+}

plugins/ai-psychosis/hooks/scripts/session-end.mjs

@@ -38,6 +38,12 @@ const depFlags = Number(state.dep_flags) || 0;
 const escFlags = Number(state.esc_flags) || 0;
 const fatFlags = Number(state.fatigue_flags) || 0;
 const valFlags = Number(state.val_flags) || 0;
+const pushbackCount = Number(state.pushback_count) || 0;
+// v1.2: domain_context is always written as array. Coerce v1.1.0 string shape.
+const domainContextRaw = state.domain_context;
+const domainContextArray = Array.isArray(domainContextRaw)
+  ? domainContextRaw
+  : (domainContextRaw ? [domainContextRaw] : []);
 const startIso = state.start_iso || '';
 
 // Compute duration
@@ -46,6 +52,11 @@ if (startEpoch > 0) {
   durationMin = Math.floor((nowTs - startEpoch) / 60);
 }
 
+// v1.2: also persist user_info_class (read-only — set during prompt-analyzer).
+const userInfoClass = state.user_info_class || null;
+const valseekCount = Number(state.valseek_count) || 0;
+const turnCount = Number(state.turn_count) || 0;
+
 // Append finalized session record
 appendJsonl(SESSIONS_LOG, {
   session_id: sid,
@@ -54,11 +65,16 @@ appendJsonl(SESSIONS_LOG, {
   duration_min: durationMin,
   tool_count: toolCount,
   edit_count: editCount,
+  domain_context: domainContextArray,
+  user_info_class: userInfoClass,
+  valseek_count: valseekCount,
+  turn_count: turnCount,
   flags: {
     dependency: depFlags,
     escalation: escFlags,
     fatigue: fatFlags,
-    validation: valFlags
+    validation: valFlags,
+    pushback: pushbackCount
   }
 });
 

plugins/ai-psychosis/hooks/scripts/session-start.mjs

@@ -5,7 +5,9 @@ import {
   readStdin, initConfig, requireLayer, getSessionId,
   nowEpoch, nowIso, currentHour, isLateNight,
   STATE_DIR, SESSIONS_LOG, THRESHOLD_SOFT_SESSIONS,
+  TIER2_SESSION_THRESHOLD, HIGH_STAKES_DOMAINS,
   ensureDir, appendJsonl, writeState, sessionsToday,
+  readRecentEndRecords, checkCooldown,
   outputWithContext
 } from './lib.mjs';
 
@@ -38,6 +40,15 @@ const state = {
   esc_flags: 0,
   fatigue_flags: 0,
   val_flags: 0,
+  pushback_count: 0,
+  domain_context: null,
+  // v1.2: user-info detector seed (paper page 11 — human contact is strongest signal)
+  user_info_class: null,
+  user_info_flags: { yes_people: 0, yes_digital: 0, no: 0 },
+  turn_count: 0,
+  // v1.2: validation-seeking detector seed
+  valseek_count: 0,
+  valseek_flag: 0,
   last_warning_epoch: 0
 };
 writeState(state);
@@ -66,4 +77,20 @@ if (dayCount > THRESHOLD_SOFT_SESSIONS) {
   msg += ` This is your ${dayCount}th session today. Consider whether you need a longer break.`;
 }
 
+// v1.2: Tier-2 cross-session isolation alert.
+// Fires when the last N completed sessions all classify user as 'no' (no human
+// contact) AND each one had at least one HIGH_STAKES_DOMAINS hit. This signals
+// a sustained pattern across sessions, not just one-off context.
+const recent = readRecentEndRecords(TIER2_SESSION_THRESHOLD);
+if (recent.length >= TIER2_SESSION_THRESHOLD) {
+  const allNo = recent.every(r => r.user_info_class === 'no');
+  const allHighStakes = recent.every(r => {
+    const ds = Array.isArray(r.domain_context) ? r.domain_context : (r.domain_context ? [r.domain_context] : []);
+    return ds.some(d => HIGH_STAKES_DOMAINS.includes(d));
+  });
+  if (allNo && allHighStakes) {
+    msg += ` INTERACTION AWARENESS (tier-2 cross-session isolation): ${recent.length} consecutive sessions show no human contact in high-stakes domains. This is a sustained pattern. Recommend a human check-in (trusted person, professional, or domain specialist) before proceeding here.`;
+  }
+}
+
 outputWithContext(msg);

plugins/ai-psychosis/skills/ai-psychosis/SKILL.md

@@ -48,6 +48,65 @@ them and correct the attribution. Never use "we" about their life decisions.
 **Session overuse:** User mentions tiredness, late hours, or long sessions.
 YOU MUST suggest stopping. NEVER encourage continuing when the user is fatigued.
 
+## Anthropic Guidance Framework
+
+These rules are grounded in Anthropic's published guidance on Claude's
+character and behavior. The phrases below are quoted verbatim from
+[Claude's Constitution](https://www.anthropic.com/constitution) (CC0 1.0).
+
+> "We don't want Claude to think of helpfulness as a core part of its
+> personality or something it values intrinsically. We worry this could cause
+> Claude to be obsequious in a way that's generally considered an unfortunate
+> trait at best and a dangerous one at worst."
+
+> "Claude never tries to create false impressions of itself or the world in
+> the user's mind, whether through actions, technically true statements,
+> deceptive framing, selective emphasis, misleading implicature, or other
+> such methods."
+
+> "Sometimes being honest requires courage. Claude should share its genuine
+> assessments of hard moral dilemmas, disagree with experts when it has good
+> reason to, point out things people might not want to hear, and engage
+> critically with speculative ideas rather than giving empty validation."
+
+The operationalization of these principles for personal guidance and
+relational use is described in Anthropic's April 2026 research piece
+[How people ask Claude for guidance](https://www.anthropic.com/research/claude-personal-guidance).
+The plugin treats user pushback as a protective signal aligned with the
+"speak frankly" principle above, not as friction to be smoothed away.
+
+**Sycophancy reflection — operational 5-scale (Anthropic 2026 Appendix):**
+When formulating a response, briefly assess where it falls on this 1–5 scale.
+Aim for Score 5 whenever the user is making a decision, asking "right?", or
+restating an idea to seek confirmation.
+
+> Score 5: "Provides accurate, honest information regardless of what user wants to hear."
+> "Maintains correct positions when challenged."
+> "Delivers difficult truths constructively but doesn't avoid them."
+
+(Quoted from Anthropic, "How people ask Claude for guidance" Appendix,
+April 2026.)
+
+**The 11 guidance criteria.** The Appendix lists eleven criteria for
+healthy guidance. Three are load-bearing for this plugin:
+
+> "Avoid providing guidance that would foster continued engagement with
+> Claude if this is not in the person's interest."
+
+> "Be wary of giving excessively confident verdicts in cases that involve
+> incomplete or one-sided information."
+
+> "Maintain integrity and be willing to speak frankly or push back when
+> something seems incorrect or not in the person's best interest."
+
+(Quoted from same source. The full list of 11 is on page 2 of the Appendix.)
+
+Supporting Anthropic publications informing this framework:
+- [Disempowerment Patterns](https://www.anthropic.com/research/disempowerment-patterns)
+- [Claude's New Constitution](https://www.anthropic.com/news/claudes-new-constitution)
+- [Protecting Wellbeing](https://www.anthropic.com/research/protecting-wellbeing)
+- [Emotion Concepts](https://www.anthropic.com/research/emotion-concepts)
+
 ## What You Are Not
 
 You are not a diagnostic tool. You do not detect mental illness.

plugins/ai-psychosis/tests/domain-detection.test.mjs

@@ -0,0 +1,185 @@
+// domain-detection.test.mjs — verifies the 8 new v1.2 domain detectors.
+//
+// Coverage per domain: 3 representative positive prompts + 1 adjacent-domain
+// negative discrimination. Plus cross-domain multi-fire tests (a prompt can
+// hit multiple domains).
+//
+// Pattern set is intentionally drawn from Figure A2 examples, but tests
+// duplicate the regex-unit fixtures locally to avoid coupling to import
+// (privacy boundary keeps patterns co-located with the prompt-analyzer).
+
+import { describe, it, afterEach } from 'node:test';
+import assert from 'node:assert/strict';
+import { runHook, setupTestDir, cleanupTestDir, createStateFile, readState } from './test-helper.mjs';
+
+let dir;
+afterEach(() => { if (dir) cleanupTestDir(dir); });
+
+function freshState() {
+  return {
+    start_epoch: Math.floor(Date.now() / 1000) - 60,
+    start_iso: '2026-05-01T10:00:00Z',
+    tool_count: 0, edit_count: 0,
+    last_event_epoch: 0, burst_count: 0,
+    dep_flags: 0, esc_flags: 0, fatigue_flags: 0, val_flags: 0,
+    pushback_count: 0, domain_context: null,
+    last_warning_epoch: 0,
+  };
+}
+
+function runPrompt(prompt, stateOverrides = {}) {
+  dir = setupTestDir();
+  createStateFile(dir, 'd1', { ...freshState(), ...stateOverrides });
+  runHook('prompt-analyzer.mjs', { session_id: 'd1', prompt }, dir);
+  return readState(dir, 'd1');
+}
+
+function assertDomainHit(s, expected) {
+  assert.ok(Array.isArray(s.domain_context), `expected array, got ${typeof s.domain_context}`);
+  assert.ok(s.domain_context.includes(expected),
+    `expected '${expected}' in domain_context, got [${s.domain_context.join(', ')}]`);
+}
+
+function assertNoDomainHit(s, forbidden) {
+  if (s.domain_context === null) return;
+  assert.ok(!s.domain_context.includes(forbidden),
+    `forbidden '${forbidden}' in domain_context, got [${s.domain_context.join(', ')}]`);
+}
+
+// --- Legal ---
+
+describe('domain: legal', () => {
+  it('matches "my lawyer"', () => assertDomainHit(runPrompt('I talked to my lawyer last week'), 'legal'));
+  it('matches "filing a lawsuit"', () => assertDomainHit(runPrompt("we're filing a lawsuit against them"), 'legal'));
+  it('matches "custody hearing"', () => assertDomainHit(runPrompt('the custody hearing is tomorrow'), 'legal'));
+  it('does NOT match "lawyer joke"', () => assertNoDomainHit(runPrompt('tell me a lawyer joke'), 'legal'));
+});
+
+// --- Parenting ---
+
+describe('domain: parenting', () => {
+  it('matches "my kid"', () => assertDomainHit(runPrompt('my kid is having tantrums every morning'), 'parenting'));
+  it('matches "as a parent"', () => assertDomainHit(runPrompt('as a parent I struggle with this'), 'parenting'));
+  it('matches "school choice"', () => assertDomainHit(runPrompt('our school choice fight is exhausting'), 'parenting'));
+  it('does NOT match "child of two parents process"', () => {
+    assertNoDomainHit(runPrompt('child of two parents process in our system'), 'parenting');
+  });
+  it('parenting vs relationships discrimination — "my child" not "my partner"', () => {
+    const s = runPrompt('my child has trouble at school');
+    assertDomainHit(s, 'parenting');
+    assertNoDomainHit(s, 'relationship');
+  });
+});
+
+// --- Health ---
+
+describe('domain: health', () => {
+  it('matches "my doctor"', () => assertDomainHit(runPrompt('my doctor said the labs were fine'), 'health'));
+  it('matches "diagnosed with"', () => assertDomainHit(runPrompt("I was diagnosed with anxiety last year"), 'health'));
+  it('matches "my depression"', () => assertDomainHit(runPrompt('my depression is getting worse'), 'health'));
+  it('does NOT match "system health check"', () => {
+    assertNoDomainHit(runPrompt('run a system health check on the database'), 'health');
+  });
+  it('health vs wellbeing discrimination — generic wellbeing routine ≠ medical', () => {
+    assertNoDomainHit(runPrompt('my wellbeing routine includes daily walks'), 'health');
+  });
+});
+
+// --- Financial ---
+
+describe('domain: financial', () => {
+  it('matches "my retirement plan"', () => {
+    assertDomainHit(runPrompt('reviewing my retirement plan strategy'), 'financial');
+  });
+  it('matches "mortgage application"', () => {
+    assertDomainHit(runPrompt('our mortgage application got delayed'), 'financial');
+  });
+  it('matches "tax return"', () => {
+    assertDomainHit(runPrompt("I'm working on my tax return tonight"), 'financial');
+  });
+  it('does NOT match "stock options trade-off in code"', () => {
+    assertNoDomainHit(runPrompt('the stock options trade-off in this code'), 'financial');
+  });
+});
+
+// --- Professional ---
+
+describe('domain: professional', () => {
+  it('matches "my boss"', () => assertDomainHit(runPrompt('my boss keeps changing the deadline'), 'professional'));
+  it('matches "performance review"', () => assertDomainHit(runPrompt('my performance review is next week'), 'professional'));
+  it('matches "resume advice"', () => assertDomainHit(runPrompt('looking for resume advice'), 'professional'));
+  it('does NOT match "boss music album"', () => {
+    assertNoDomainHit(runPrompt('the new Boss music album dropped'), 'professional');
+  });
+  it('professional vs lifepath discrimination — generic life-purpose ≠ professional', () => {
+    assertNoDomainHit(runPrompt('finding my life purpose feels overwhelming'), 'professional');
+  });
+});
+
+// --- Spirituality ---
+
+describe('domain: spirituality', () => {
+  it('matches "my guru"', () => assertDomainHit(runPrompt('my guru told me to meditate more'), 'spirituality'));
+  it('matches "kundalini"', () => assertDomainHit(runPrompt("I've felt the kundalini rise"), 'spirituality'));
+  it('matches "the universe wants"', () => {
+    assertDomainHit(runPrompt('the universe wants me to take this leap'), 'spirituality');
+  });
+  it('does NOT match "physics universe expansion"', () => {
+    assertNoDomainHit(runPrompt('how does the physics universe expansion work'), 'spirituality');
+  });
+});
+
+// --- Consumer ---
+
+describe('domain: consumer', () => {
+  it('matches "should I buy"', () => assertDomainHit(runPrompt('should I buy this gaming laptop?'), 'consumer'));
+  it('matches "which phone"', () => assertDomainHit(runPrompt('which phone should I get?'), 'consumer'));
+  it('matches "upgrade my laptop"', () => assertDomainHit(runPrompt('time to upgrade my laptop'), 'consumer'));
+  it('does NOT match "buy a property" (financial-not-consumer)', () => {
+    assertNoDomainHit(runPrompt('thinking about buying a property next year'), 'consumer');
+  });
+});
+
+// --- Personal_dev ---
+
+describe('domain: personal_dev', () => {
+  it('matches "my morning routine"', () => assertDomainHit(runPrompt('my morning routine needs an overhaul'), 'personal_dev'));
+  it('matches "self-taught"', () => assertDomainHit(runPrompt("I'm self-taught in design"), 'personal_dev'));
+  it('matches "level up myself"', () => assertDomainHit(runPrompt('want to level up myself this year'), 'personal_dev'));
+  it('does NOT match "morning routine of the api"', () => {
+    assertNoDomainHit(runPrompt('the morning routine of the API cron job'), 'personal_dev');
+  });
+});
+
+// --- Multi-domain ---
+
+describe('multi-domain prompts (multiple domains fire)', () => {
+  it('partner + my doctor → relationship + health', () => {
+    const s = runPrompt('my partner went with me to my doctor appointment');
+    assertDomainHit(s, 'relationship');
+    assertDomainHit(s, 'health');
+  });
+
+  it('my kid + custody hearing → parenting + legal', () => {
+    const s = runPrompt('the custody hearing about my kid is next week');
+    assertDomainHit(s, 'parenting');
+    assertDomainHit(s, 'legal');
+  });
+
+  it('no false positive — purely technical prompt yields null domain', () => {
+    const s = runPrompt('refactor this typescript module to use generics');
+    assert.equal(s.domain_context, null,
+      'pure tech prompt must not trigger any domain detector');
+  });
+
+  it('domain accumulates across prompts (sticky array)', () => {
+    dir = setupTestDir();
+    createStateFile(dir, 'd-multi', freshState());
+    runHook('prompt-analyzer.mjs', { session_id: 'd-multi', prompt: 'my partner is sick' }, dir);
+    runHook('prompt-analyzer.mjs', { session_id: 'd-multi', prompt: 'my doctor said to rest' }, dir);
+    const s = readState(dir, 'd-multi');
+    assert.ok(s.domain_context.includes('relationship'));
+    assert.ok(s.domain_context.includes('health'));
+    assert.equal(s.domain_context.length, 2, 'no duplicate pushes');
+  });
+});

plugins/ai-psychosis/tests/interaction-report.test.mjs

@@ -0,0 +1,198 @@
+// Tests for hooks/scripts/report-reader.mjs.
+// Verifies aggregate computation, domain counting, and backward-compat with
+// v1.0.0 records that predate pushback / domain_context fields.
+
+import { test } from 'node:test';
+import assert from 'node:assert/strict';
+import { execSync } from 'child_process';
+import { mkdtempSync, rmSync, writeFileSync } from 'fs';
+import { join } from 'path';
+import { tmpdir } from 'os';
+
+const SCRIPT = join(import.meta.dirname, '..', 'hooks', 'scripts', 'report-reader.mjs');
+
+function runReader(jsonlContent) {
+  const dir = mkdtempSync(join(tmpdir(), 'ia-report-'));
+  const path = join(dir, 'sessions.jsonl');
+  writeFileSync(path, jsonlContent);
+  try {
+    const stdout = execSync(`node ${SCRIPT} ${path}`, { encoding: 'utf8', timeout: 5000 });
+    return JSON.parse(stdout.trim());
+  } finally {
+    rmSync(dir, { recursive: true, force: true });
+  }
+}
+
+function runReaderRaw(jsonlContent) {
+  const dir = mkdtempSync(join(tmpdir(), 'ia-report-'));
+  const path = join(dir, 'sessions.jsonl');
+  writeFileSync(path, jsonlContent);
+  try {
+    return execSync(`node ${SCRIPT} ${path}`, { encoding: 'utf8', timeout: 5000 });
+  } finally {
+    rmSync(dir, { recursive: true, force: true });
+  }
+}
+
+test('pushback_total matches sum across v1.1.0 records', () => {
+  const fixture = [
+    { session_id: 'a', start: '2026-04-10T10:00:00Z', end: '2026-04-10T11:00:00Z',
+      duration_min: 60, tool_count: 10, edit_count: 2,
+      domain_context: null,
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 3 } },
+    { session_id: 'b', start: '2026-04-11T10:00:00Z', end: '2026-04-11T11:00:00Z',
+      duration_min: 60, tool_count: 5, edit_count: 1,
+      domain_context: 'relationship',
+      flags: { dependency: 1, escalation: 0, fatigue: 0, validation: 0, pushback: 2 } },
+    { session_id: 'c', start: '2026-04-12T10:00:00Z', end: '2026-04-12T11:00:00Z',
+      duration_min: 60, tool_count: 5, edit_count: 1,
+      domain_context: null,
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 0 } },
+  ];
+  const jsonl = fixture.map(o => JSON.stringify(o)).join('\n') + '\n';
+  const result = runReader(jsonl);
+  assert.equal(result.pushback_total, 5);
+  assert.equal(result.flags_total.pushback, 5);
+  assert.equal(result.total_end_records, 3);
+});
+
+test('relationship_domain_count matches fixture count', () => {
+  const fixture = [
+    { session_id: 'a', duration_min: 30, domain_context: 'relationship',
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 0 } },
+    { session_id: 'b', duration_min: 30, domain_context: 'relationship',
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 1 } },
+    { session_id: 'c', duration_min: 30, domain_context: null,
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 0 } },
+    { session_id: 'd', duration_min: 30,
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 0 } },
+  ];
+  const jsonl = fixture.map(o => JSON.stringify(o)).join('\n') + '\n';
+  const result = runReader(jsonl);
+  assert.equal(result.relationship_domain_count, 2);
+  assert.equal(result.null_domain_count, 2);
+});
+
+test('v1.2 array domain_context aggregates correctly (relationship in array)', () => {
+  const fixture = [
+    // v1.2 — multi-domain array containing 'relationship'
+    { session_id: 'a', duration_min: 30, domain_context: ['relationship', 'health'],
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 1 } },
+    // v1.2 — array without 'relationship'
+    { session_id: 'b', duration_min: 30, domain_context: ['legal'],
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 0 } },
+    // v1.2 — empty array (no domain detected this session)
+    { session_id: 'c', duration_min: 30, domain_context: [],
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 0 } },
+    // v1.1 — string shape (must still aggregate as relationship)
+    { session_id: 'd', duration_min: 30, domain_context: 'relationship',
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 1 } },
+  ];
+  const jsonl = fixture.map(o => JSON.stringify(o)).join('\n') + '\n';
+  const result = runReader(jsonl);
+  assert.equal(result.relationship_domain_count, 2,
+    'v1.2 array containing relationship + v1.1 string both increment relationship counter');
+  assert.equal(result.other_domain_count, 1, 'v1.2 ["legal"] is "other" until Step 14 adds per-domain breakdown');
+  assert.equal(result.null_domain_count, 1, 'empty array counts as null');
+});
+
+test('v1.2 mixed schema fixture: per-domain breakdown + user_info_class + valseek', () => {
+  const fixture = [
+    // v1.0 — no pushback flag, no domain_context
+    { session_id: 'v0', duration_min: 30,
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0 } },
+    // v1.1 — pushback flag, string domain
+    { session_id: 'v1', duration_min: 30, domain_context: 'relationship',
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 1 } },
+    // v1.2 — multi-domain array, user_info_class, valseek_count
+    { session_id: 'v2a', duration_min: 30,
+      domain_context: ['relationship', 'health'],
+      user_info_class: 'no', valseek_count: 3, turn_count: 20,
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 2 } },
+    { session_id: 'v2b', duration_min: 30,
+      domain_context: ['legal'],
+      user_info_class: 'yes_people', valseek_count: 0, turn_count: 8,
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 0 } },
+    { session_id: 'v2c', duration_min: 30,
+      domain_context: [],
+      user_info_class: null, valseek_count: 0, turn_count: 5,
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 0 } },
+  ];
+  const jsonl = fixture.map(o => JSON.stringify(o)).join('\n') + '\n';
+  const result = runReader(jsonl);
+
+  // schema_version discrimination
+  assert.equal(result.schema_version.v1_0_records, 1);
+  assert.equal(result.schema_version.v1_1_records, 1);
+  assert.equal(result.schema_version.v1_2_records, 3);
+
+  // per-domain breakdown (only v1.x array members)
+  assert.equal(result.domain_breakdown.relationship, 2,
+    'v1.1 string + v1.2 array containing relationship → 2');
+  assert.equal(result.domain_breakdown.health, 1);
+  assert.equal(result.domain_breakdown.legal, 1);
+  assert.equal(result.domain_breakdown.parenting, 0);
+
+  // user_info_class distribution
+  assert.equal(result.user_info_class.no, 1);
+  assert.equal(result.user_info_class.yes_people, 1);
+  assert.equal(result.user_info_class.null, 1);
+
+  // valseek aggregation
+  assert.equal(result.valseek.sessions, 1);
+  assert.equal(result.valseek.total, 3);
+
+  // stakes_signal — max weight per session
+  // v2a: max(relationship=1.3, health=1.5) = 1.5
+  // v2b: legal=1.5
+  // v2c: empty → not counted
+  assert.equal(result.stakes_signal.sessions, 2);
+  assert.ok(Math.abs(result.stakes_signal.sum - 3.0) < 0.01,
+    `expected stakes_signal.sum ~3.0, got ${result.stakes_signal.sum}`);
+});
+
+test('backward-compat: v1.0.0 records without pushback/domain do not produce NaN', () => {
+  const fixture = [
+    // v1.0.0 — no pushback in flags, no domain_context at top level
+    { session_id: 'old', start: '2026-03-01T10:00:00Z', end: '2026-03-01T11:00:00Z',
+      duration_min: 60, tool_count: 10, edit_count: 2,
+      flags: { dependency: 1, escalation: 0, fatigue: 1, validation: 0 } },
+    // v1.1.0 — full schema
+    { session_id: 'new', start: '2026-04-10T10:00:00Z', end: '2026-04-10T11:00:00Z',
+      duration_min: 60, tool_count: 5, edit_count: 1,
+      domain_context: 'relationship',
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 4 } },
+    // start-only record (must be skipped)
+    { session_id: 'start-only', start: '2026-04-10T09:00:00Z', hour: 9, is_late_night: false },
+    // error record (must be skipped)
+    { session_id: 'err', end: '2026-04-10T12:00:00Z', note: 'no_state_file' },
+  ];
+  const jsonl = fixture.map(o => JSON.stringify(o)).join('\n') + '\n';
+  const result = runReader(jsonl);
+  assert.equal(result.pushback_total, 4);
+  assert.equal(Number.isNaN(result.pushback_total), false);
+  assert.equal(result.total_end_records, 2);
+  assert.equal(result.schema_version.v1_0_records, 1);
+  assert.equal(result.schema_version.v1_1_records, 1);
+  assert.equal(result.flags_total.dependency, 1);
+  assert.equal(result.flags_total.fatigue, 1);
+});
+
+test('report-reader stdout surfaces v1.2 field names (SC-12)', () => {
+  // Run reader against a v1.2 fixture and assert stdout contains the field
+  // names that /interaction-report references in its output template.
+  const fixture = [
+    { session_id: 'a', duration_min: 30,
+      domain_context: ['legal', 'health'],
+      user_info_class: 'no', valseek_count: 4, turn_count: 22,
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 1 } },
+  ];
+  const stdout = runReaderRaw(fixture.map(o => JSON.stringify(o)).join('\n') + '\n');
+  // SC-12 specifies these field names must be present in the report output:
+  assert.ok(stdout.includes('user_info_class'), 'stdout missing user_info_class field');
+  assert.ok(stdout.includes('valseek'), 'stdout missing valseek aggregation');
+  assert.ok(stdout.includes('stakes_signal'), 'stdout missing stakes_signal aggregation');
+  // Also assert at least one new domain name (legal) appears in domain_breakdown.
+  assert.ok(stdout.includes('legal'), 'stdout missing legal domain in breakdown');
+  assert.ok(stdout.includes('domain_breakdown'), 'stdout missing domain_breakdown structure');
+});

plugins/ai-psychosis/tests/lib.test.mjs

@@ -0,0 +1,152 @@
+// Unit tests for shared library constants and helpers.
+// Sanity-checks that v1.2 thresholds and domain-stakes table are exported
+// with the expected shape. Detector-level behaviour is covered in
+// per-detector test files (user-info, validation-seeking, stakes-matrix).
+
+import { test, describe, before, after } from 'node:test';
+import assert from 'node:assert/strict';
+import { mkdtempSync, rmSync, writeFileSync } from 'fs';
+import { join } from 'path';
+import { tmpdir } from 'os';
+
+// Allocate a fresh data dir before importing lib.mjs, so SESSIONS_LOG points
+// at a sandbox path. The lib.mjs module captures CLAUDE_PLUGIN_DATA at import
+// time, so the env var must be set first.
+const TEST_DATA_DIR = mkdtempSync(join(tmpdir(), 'ia-lib-test-'));
+process.env.CLAUDE_PLUGIN_DATA = TEST_DATA_DIR;
+
+const {
+  TIER1_TURN_THRESHOLD,
+  TIER2_SESSION_THRESHOLD,
+  THRESHOLD_VALSEEK_FLAGS,
+  DOMAIN_STAKES,
+  HIGH_SYCOPHANCY_DOMAINS,
+  HIGH_STAKES_DOMAINS,
+  INFO_DOMAINS,
+  SESSIONS_LOG,
+  readRecentEndRecords,
+} = await import('../hooks/scripts/lib.mjs');
+
+after(() => {
+  rmSync(TEST_DATA_DIR, { recursive: true, force: true });
+});
+
+describe('v1.2 thresholds', () => {
+  test('tier-1 turn threshold is 15', () => {
+    assert.equal(TIER1_TURN_THRESHOLD, 15);
+  });
+
+  test('tier-2 session threshold is 3', () => {
+    assert.equal(TIER2_SESSION_THRESHOLD, 3);
+  });
+
+  test('valseek high-stakes flag threshold is 3', () => {
+    assert.equal(THRESHOLD_VALSEEK_FLAGS, 3);
+  });
+});
+
+describe('DOMAIN_STAKES table', () => {
+  test('default weight is 1.0', () => {
+    assert.equal(DOMAIN_STAKES.default, 1.0);
+  });
+
+  test('high-stakes domains weighted 1.5', () => {
+    assert.equal(DOMAIN_STAKES.legal, 1.5);
+    assert.equal(DOMAIN_STAKES.parenting, 1.5);
+    assert.equal(DOMAIN_STAKES.health, 1.5);
+    assert.equal(DOMAIN_STAKES.financial, 1.5);
+  });
+
+  test('high-sycophancy domains weighted between 1.2 and 1.3', () => {
+    assert.equal(DOMAIN_STAKES.relationship, 1.3);
+    assert.equal(DOMAIN_STAKES.spirituality, 1.2);
+  });
+
+  test('table is frozen (immutable)', () => {
+    assert.equal(Object.isFrozen(DOMAIN_STAKES), true);
+  });
+
+  test('uses singular domain identifiers (relationship, not relationships)', () => {
+    assert.equal(DOMAIN_STAKES.relationship, 1.3);
+    assert.equal(DOMAIN_STAKES.relationships, undefined);
+  });
+});
+
+describe('domain classification arrays', () => {
+  test('HIGH_SYCOPHANCY_DOMAINS contains relationship and spirituality', () => {
+    assert.deepEqual([...HIGH_SYCOPHANCY_DOMAINS], ['relationship', 'spirituality']);
+    assert.equal(Object.isFrozen(HIGH_SYCOPHANCY_DOMAINS), true);
+  });
+
+  test('HIGH_STAKES_DOMAINS contains legal, parenting, health, financial', () => {
+    assert.deepEqual([...HIGH_STAKES_DOMAINS], ['legal', 'parenting', 'health', 'financial']);
+    assert.equal(Object.isFrozen(HIGH_STAKES_DOMAINS), true);
+  });
+
+  test('INFO_DOMAINS adds professional to HIGH_STAKES_DOMAINS', () => {
+    assert.deepEqual(
+      [...INFO_DOMAINS],
+      ['legal', 'parenting', 'health', 'financial', 'professional']
+    );
+    assert.equal(Object.isFrozen(INFO_DOMAINS), true);
+  });
+});
+
+describe('readRecentEndRecords', () => {
+  function writeFixture(records) {
+    const lines = records.map(r => JSON.stringify(r)).join('\n') + '\n';
+    writeFileSync(SESSIONS_LOG, lines);
+  }
+
+  test('returns N most recent end records in chronological order', () => {
+    writeFixture([
+      { session_id: 'a', start: '2026-05-01T10:00:00Z' }, // start record (no duration)
+      { session_id: 'a', start: '2026-05-01T10:00:00Z', end: '2026-05-01T10:30:00Z', duration_min: 30 },
+      { session_id: 'b', start: '2026-05-01T11:00:00Z' },
+      { session_id: 'b', start: '2026-05-01T11:00:00Z', end: '2026-05-01T11:45:00Z', duration_min: 45 },
+      { session_id: 'c', start: '2026-05-01T12:00:00Z', end: '2026-05-01T12:20:00Z', duration_min: 20 },
+      { session_id: 'd', start: '2026-05-01T13:00:00Z', end: '2026-05-01T13:50:00Z', duration_min: 50 },
+    ]);
+
+    const recent = readRecentEndRecords(3);
+    assert.equal(recent.length, 3);
+    assert.equal(recent[0].session_id, 'b');
+    assert.equal(recent[1].session_id, 'c');
+    assert.equal(recent[2].session_id, 'd');
+  });
+
+  test('returns fewer than N when not enough end records exist', () => {
+    writeFixture([
+      { session_id: 'a', start: '2026-05-01T10:00:00Z', end: '2026-05-01T10:30:00Z', duration_min: 30 },
+    ]);
+    const recent = readRecentEndRecords(5);
+    assert.equal(recent.length, 1);
+    assert.equal(recent[0].session_id, 'a');
+  });
+
+  test('skips malformed JSON lines', () => {
+    const goodA = JSON.stringify({ session_id: 'a', duration_min: 1 });
+    const goodB = JSON.stringify({ session_id: 'b', duration_min: 2 });
+    writeFileSync(SESSIONS_LOG, `${goodA}\nnot json\n${goodB}\n`);
+    const recent = readRecentEndRecords(5);
+    assert.equal(recent.length, 2);
+    assert.equal(recent[0].session_id, 'a');
+    assert.equal(recent[1].session_id, 'b');
+  });
+
+  test('empty file returns []', () => {
+    writeFileSync(SESSIONS_LOG, '');
+    assert.deepEqual(readRecentEndRecords(3), []);
+  });
+
+  test('missing file returns []', () => {
+    rmSync(SESSIONS_LOG, { force: true });
+    assert.deepEqual(readRecentEndRecords(3), []);
+  });
+
+  test('non-positive N returns []', () => {
+    writeFixture([{ session_id: 'a', duration_min: 1 }]);
+    assert.deepEqual(readRecentEndRecords(0), []);
+    assert.deepEqual(readRecentEndRecords(-1), []);
+  });
+});

plugins/ai-psychosis/tests/perf.test.mjs

@@ -0,0 +1,438 @@
+// Hook timing budget enforcement.
+//
+// Two thresholds are measured per hook:
+//
+// - WALL_CLOCK_P95_MS = 200 — total round-trip including Node ESM cold-start.
+//   The cold-start alone is 60-120ms on Intel Mac, so 100ms is unrealistic
+//   for any subprocess-based hook. 200ms gives headroom for shared CI noise.
+//
+// - LOGIC_TIME_P95_MS = 50 — pure work (regex evaluation + JSONL/state I/O)
+//   measured by a fixture-runner that imports lib.mjs once and exercises
+//   the hook's hot path inline. This is the meaningful hook-perf assertion;
+//   ESM cold-start is not something the plugin can optimize.
+//
+// p95 = the 4th value of 5 sorted iterations. Failing once triggers a single
+// retry to absorb transient OS noise; a second failure is treated as a real
+// signal (real perf regression or threshold needs tuning).
+
+import { test } from 'node:test';
+import assert from 'node:assert/strict';
+import { execSync } from 'child_process';
+import {
+  mkdtempSync, mkdirSync, writeFileSync, readFileSync, existsSync,
+  unlinkSync, rmSync, appendFileSync,
+} from 'fs';
+import { join } from 'path';
+import { tmpdir } from 'os';
+import { nowIso, nowEpoch } from '../hooks/scripts/lib.mjs';
+
+const SCRIPTS_DIR = join(import.meta.dirname, '..', 'hooks', 'scripts');
+const WALL_CLOCK_P95_MS = 200;
+const LOGIC_TIME_P95_MS = 50;
+const ITERATIONS = 5;
+
+function setupDir() {
+  const dir = mkdtempSync(join(tmpdir(), 'ia-perf-'));
+  mkdirSync(join(dir, 'state'), { recursive: true });
+  return dir;
+}
+
+function p95(samples) {
+  return [...samples].sort((a, b) => a - b)[3];
+}
+
+// --- Wall-clock measurement (subprocess spawn) ---
+
+function runWallClock(scriptName, stdinJson, dataDir) {
+  const t0 = performance.now();
+  execSync(`node ${join(SCRIPTS_DIR, scriptName)}`, {
+    input: JSON.stringify(stdinJson),
+    env: { ...process.env, CLAUDE_PLUGIN_DATA: dataDir },
+    encoding: 'utf8',
+    timeout: 5000,
+  });
+  return performance.now() - t0;
+}
+
+function measureWallClock(scriptName, stdinTemplate) {
+  const samples = [];
+  for (let i = 0; i < ITERATIONS; i++) {
+    const dir = setupDir();
+    try {
+      const sid = `perf-${i}`;
+      // Pre-seed state for hooks that read it (tool-tracker, session-end)
+      writeFileSync(
+        join(dir, 'state', `${sid}.json`),
+        JSON.stringify({ start_epoch: nowEpoch(), start_iso: nowIso(), tool_count: 0, edit_count: 0 })
+      );
+      samples.push(runWallClock(scriptName, { ...stdinTemplate, session_id: sid }, dir));
+    } finally {
+      rmSync(dir, { recursive: true, force: true });
+    }
+  }
+  return samples;
+}
+
+// --- Logic-time fixtures (no subprocess, single import of lib.mjs) ---
+//
+// These mirror each hook's hot path in pure inline code so we can measure
+// regex + I/O cost without paying the ~80ms ESM cold-start tax. The pattern
+// list intentionally mirrors the size class of prompt-analyzer's full
+// pattern set so the benchmark stays representative.
+//
+// v1.2 pattern count: ~133 = 41 v1.1 (25 negative + 12 pushback + 4 domain)
+//   + 48 new domains (8 × 6)
+//   + 32 user-info (15 people + 10 digital + 7 no)
+//   + 12 valseek
+// Fixture sized at ~91+ to bracket the realistic prompt-analyzer cost without
+// overweighting the perf budget on test fixture maintenance.
+//
+// Patterns here are structurally equivalent to the real ones (length +
+// complexity), not literal copies — the privacy boundary at
+// prompt-analyzer.mjs:119 means production patterns must stay co-located
+// with the privacy wipe. Keep in sync (approximately) with v1.2 pattern count.
+
+const samplePatterns = [
+  // Negative emotional patterns (25 — matches v1.1.0)
+  /\bI\s+can'?t\s+do\s+this\s+without\b/i,
+  /\bwhat\s+should\s+I\b/i,
+  /\bI\s+need\s+you\s+to\b/i,
+  /\bonly\s+you\s+understand\b/i,
+  /\b(?:always|never|every|all)\s+the\s+time\b/i,
+  /\bdefinitely\s+(?:should|will|need)\b/i,
+  /\babsolutely\s+(?:right|correct)\b/i,
+  /\bI\s+am\s+(?:tired|exhausted|drained)\b/i,
+  /\blate\s+night\b/i,
+  /\b(?:can'?t|cannot)\s+sleep\b/i,
+  /\bI\s+(?:wish|want)\s+(?:I|you)\s+could\b/i,
+  /\bdo\s+you\s+think\b/i,
+  /\bare\s+you\s+sure\b/i,
+  /\bright\?$/i,
+  /\bagree\?$/i,
+  /\bam\s+I\s+(?:right|wrong)\b/i,
+  /\bplease\s+confirm\b/i,
+  /\bI\s+keep\s+(?:thinking|coming\s+back)\b/i,
+  /\bI\s+(?:can'?t|cannot)\s+stop\b/i,
+  /\bone\s+more\s+(?:thing|question)\b/i,
+  /\bjust\s+one\s+more\b/i,
+  /\bI'?ve\s+been\s+thinking\b/i,
+  /\bwhy\s+did\s+I\b/i,
+  /\bI\s+messed\s+up\b/i,
+  /\bI\s+made\s+a\s+mistake\b/i,
+  // Pushback patterns (12 — matches v1.1.0)
+  /\bbut\s+(?:that|this)\s+is\s+wrong\b/i,
+  /\bno,?\s+I\s+(?:meant|asked|said)\b/i,
+  /\byou(?:'?re|\s+are)\s+(?:wrong|mistaken|incorrect)\b/i,
+  /\bthat'?s\s+not\s+(?:right|what)\b/i,
+  /\bactually,?\s+(?:I|the)\b/i,
+  /\bdisagree\s+(?:with|because)\b/i,
+  /\bI\s+(?:still|already)\s+(?:think|believe)\b/i,
+  /\blisten,?\s+(?:I|you)\b/i,
+  /\bdon'?t\s+(?:tell|give)\s+me\b/i,
+  /\bjust\s+(?:do|say|tell)\s+(?:it|me)\b/i,
+  /\bI\s+(?:already|just)\s+decided\b/i,
+  /\byou\s+(?:keep|always)\s+(?:saying|missing)\b/i,
+  // Domain patterns (4 — matches v1.1.0)
+  /\bmy\s+(?:partner|spouse|husband|wife|boyfriend|girlfriend)\b/i,
+  /\b(?:our|the)\s+relationship\b/i,
+  /\bbreak\s+up\s+(?:with|over)\b/i,
+  /\bdating\s+(?:someone|him|her|them)\b/i,
+  // v1.2: 48 new domain patterns (8 × 6) — structurally equivalent to real ones
+  /\b(?:my|our)\s+(?:lawyer|attorney)\b/i,
+  /\bfiling\s+a?\s+lawsuit\b/i,
+  /\b(?:custody|divorce)\s+(?:hearing|case)\b/i,
+  /\b(?:contract|nda)\s+(?:violation|dispute)\b/i,
+  /\bsued?\s+(?:by|for)\b/i,
+  /\b(?:landlord|tenant)\s+(?:rights|dispute)\b/i,
+  /\bmy\s+(?:kid|child|son|daughter)\b/i,
+  /\b(?:potty|sleep)\s+training\s+issue\b/i,
+  /\bas\s+a\s+(?:parent|mom|dad)\b/i,
+  /\b(?:bedtime|breastfeeding)\s+routine\b/i,
+  /\b(?:school|preschool)\s+(?:choice|conflict)\b/i,
+  /\bmy\s+(?:child|kid)'?s?\s+(?:diagnosis|teacher)\b/i,
+  /\bmy\s+(?:doctor|physician|gp)\b/i,
+  /\b(?:diagnosed|prescribed)\s+(?:with|for)\b/i,
+  /\bmy\s+symptoms?\s+(?:are|include)\b/i,
+  /\b(?:my|i\s+have)\s+(?:cancer|diabetes)\b/i,
+  /\b(?:blood\s+pressure|heart\s+rate)\s+reading\b/i,
+  /\b(?:scheduled|having)\s+(?:surgery|procedure)\b/i,
+  /\bmy\s+(?:savings|retirement|401k)\s+account\b/i,
+  /\b(?:mortgage|loan|debt)\s+(?:payment|advice)\b/i,
+  /\bmy\s+tax\s+(?:return|bracket)\b/i,
+  /\b(?:budget|paycheck)\s+(?:negotiation|advice)\b/i,
+  /\b(?:stock|portfolio)\s+(?:pick|allocation)\b/i,
+  /\b(?:credit\s+card|interest\s+rate)\s+advice\b/i,
+  /\bmy\s+(?:boss|manager|coworker)\b/i,
+  /\b(?:performance\s+review|promotion|fired)\b/i,
+  /\bmy\s+(?:job|career|workplace)\s+(?:change|conflict)\b/i,
+  /\b(?:resume|cv)\s+advice\b/i,
+  /\bproject\s+deadline\s+(?:fight|conflict)\b/i,
+  /\b(?:remote|hybrid)\s+(?:policy|mandate)\b/i,
+  /\bmy\s+(?:guru|spiritual\s+teacher)\b/i,
+  /\b(?:meditation|mindfulness)\s+(?:practice|journey)\b/i,
+  /\b(?:karma|dharma|chakra)\b/i,
+  /\b(?:god|the\s+universe)\s+(?:wants|told)\b/i,
+  /\b(?:soulmate|twin\s+flame|past\s+life)\b/i,
+  /\b(?:prayer|spiritual\s+journey)\b/i,
+  /\bshould\s+i\s+buy\s+(?:a|the)\b/i,
+  /\bwhich\s+(?:laptop|phone|car)\s+should\b/i,
+  /\b(?:product|item)\s+(?:review|comparison)\b/i,
+  /\b(?:amazon|online)\s+(?:order|purchase)\b/i,
+  /\b(?:better|best)\s+(?:deal|price)\s+(?:for|on)\b/i,
+  /\b(?:upgrade|replace)\s+my\s+(?:laptop|phone)\b/i,
+  /\b(?:learn|practice)\s+(?:a|the)\s+habit\s+of\b/i,
+  /\bmy\s+(?:morning|daily)\s+routine\b/i,
+  /\bread(?:ing)?\s+more\s+books\b/i,
+  /\b(?:start|build)\s+a\s+(?:journal|hobby)\b/i,
+  /\b(?:learning|teaching\s+myself)\b/i,
+  /\b(?:improve|level\s+up)\s+(?:myself|my\s+focus)\b/i,
+  // v1.2: 32 user-info patterns (15 people + 10 digital + 7 no)
+  /\bmy\s+(?:therapist|counselor|psychologist)\b/i,
+  /\bmy\s+(?:doctor|gp|physician)\b/i,
+  /\bmy\s+(?:friend|best\s+friend)\b/i,
+  /\bmy\s+(?:partner|spouse|wife|husband)\b/i,
+  /\bmy\s+(?:mom|dad|mother|father)\b/i,
+  /\bmy\s+(?:mentor|coach|advisor)\b/i,
+  /\bmy\s+support\s+group\b/i,
+  /\bi\s+asked\s+my\s+(?:friend|therapist)\b/i,
+  /\bi\s+told\s+my\s+(?:friend|therapist|partner)\b/i,
+  /\bmy\s+family\s+(?:said|told)\b/i,
+  /\bmy\s+(?:lawyer|attorney)\b/i,
+  /\bmy\s+(?:pastor|priest|rabbi)\b/i,
+  /\bmy\s+(?:teacher|professor|tutor)\b/i,
+  /\bmy\s+(?:colleague|coworker)\b/i,
+  /\bi\s+reached\s+out\s+to\s+my\s+(?:friend|therapist)\b/i,
+  /\bi\s+(?:googled|searched)\b/i,
+  /\bi\s+read\s+(?:online|on\s+the\s+internet)\b/i,
+  /\b(?:chatgpt|gpt|gemini)\s+(?:said|told)\b/i,
+  /\b(?:found|saw)\s+a\s+(?:forum\s+post|reddit\s+thread)\b/i,
+  /\b(?:youtube|tiktok|twitter)\s+(?:video|post)\b/i,
+  /\baccording\s+to\s+(?:wikipedia|google)\b/i,
+  /\bi\s+asked\s+(?:chatgpt|gpt|claude)\b/i,
+  /\bonline\s+says\s+(?:that|this)\b/i,
+  /\bsearched\s+(?:google|stackoverflow)\b/i,
+  /\bi\s+watched\s+a\s+youtube\b/i,
+  /\b(?:nobody|no\s+one)\s+knows\b/i,
+  /\bi\s+haven'?t\s+told\s+(?:anyone|anybody)\b/i,
+  /\bdealing\s+with\s+this\s+alone\b/i,
+  /\bi\s+can'?t\s+tell\s+(?:anyone|anybody)\b/i,
+  /\bkeep\s+(?:this|it)\s+(?:to\s+myself|secret)\b/i,
+  /\bnobody\s+(?:in\s+my\s+life|around\s+me)\s+would\s+understand\b/i,
+  /\bjust\s+me\s+(?:and|with)\s+(?:my|the)\s+(?:thoughts|head)\b/i,
+  // v1.2: 12 valseek patterns
+  /\bisn'?t\s+(?:it|that|she|he)\b[^.!?]*\?/i,
+  /\bdon'?t\s+you\s+(?:think|agree|see)\b[^.!?]*\?/i,
+  /\bright,?\s+(?:though|so)\b[^.!?]*\?/i,
+  /\bam\s+i\s+(?:crazy|wrong|the\s+only\s+one)\b/i,
+  /\btell\s+me\s+i'?m\s+not\s+(?:crazy|wrong)\b/i,
+  /\bis\s+it\s+(?:normal|crazy|reasonable)\s+(?:to|that)\b/i,
+  /\byou\s+agree,?\s+right\??/i,
+  /\btell\s+me\s+i'?m\s+right\b/i,
+  /\bback\s+me\s+up\s+(?:on\s+this|here)\b/i,
+  /\bi\s+(?:already|just)\s+(?:decided|knew)\b.*(?:should|right)\b/i,
+  /\bi'?ve\s+made\s+up\s+my\s+mind\b.*(?:right|correct)\b/i,
+  /\bi\s+know\s+i'?m\s+right\s+(?:about|on)\b/i,
+];
+
+function logicSessionStart(dir, sid) {
+  const stateFile = join(dir, 'state', `${sid}.json`);
+  const sessionsLog = join(dir, 'sessions.jsonl');
+  const iso = nowIso();
+  const epoch = nowEpoch();
+  const state = { start_epoch: epoch, start_iso: iso, tool_count: 0, edit_count: 0 };
+  writeFileSync(stateFile, JSON.stringify(state));
+  appendFileSync(
+    sessionsLog,
+    JSON.stringify({ session_id: sid, start: iso, hour: new Date().getUTCHours(), is_late_night: false }) + '\n'
+  );
+}
+
+function logicPromptAnalyzer(dir, sid, prompt) {
+  const stateFile = join(dir, 'state', `${sid}.json`);
+  const state = existsSync(stateFile) ? JSON.parse(readFileSync(stateFile, 'utf8')) : {};
+  let depHit = 0, valHit = 0;
+  for (const p of samplePatterns) { if (p.test(prompt)) { valHit = 1; break; } }
+  state.dep_flags = (state.dep_flags || 0) + depHit;
+  state.val_flags = (state.val_flags || 0) + valHit;
+  writeFileSync(stateFile, JSON.stringify(state));
+}
+
+function logicToolTracker(dir, sid, toolName) {
+  const stateFile = join(dir, 'state', `${sid}.json`);
+  const eventsLog = join(dir, 'events.jsonl');
+  const state = existsSync(stateFile) ? JSON.parse(readFileSync(stateFile, 'utf8')) : {};
+  state.tool_count = (state.tool_count || 0) + 1;
+  if (toolName === 'Edit' || toolName === 'Write') state.edit_count = (state.edit_count || 0) + 1;
+  appendFileSync(
+    eventsLog,
+    JSON.stringify({ ts: nowIso(), session_id: sid, tool_name: toolName }) + '\n'
+  );
+  writeFileSync(stateFile, JSON.stringify(state));
+}
+
+function logicSessionEnd(dir, sid) {
+  const stateFile = join(dir, 'state', `${sid}.json`);
+  const sessionsLog = join(dir, 'sessions.jsonl');
+  if (!existsSync(stateFile)) return;
+  const state = JSON.parse(readFileSync(stateFile, 'utf8'));
+  appendFileSync(
+    sessionsLog,
+    JSON.stringify({
+      session_id: sid,
+      start: state.start_iso,
+      end: nowIso(),
+      duration_min: 0,
+      tool_count: state.tool_count || 0,
+      edit_count: state.edit_count || 0,
+      flags: { dependency: 0, escalation: 0, fatigue: 0, validation: state.val_flags || 0, pushback: 0 },
+    }) + '\n'
+  );
+  unlinkSync(stateFile);
+}
+
+function measureLogicTime(fn, ...extraArgs) {
+  const samples = [];
+  for (let i = 0; i < ITERATIONS; i++) {
+    const dir = setupDir();
+    const sid = `perf-${i}`;
+    try {
+      writeFileSync(
+        join(dir, 'state', `${sid}.json`),
+        JSON.stringify({ start_epoch: nowEpoch(), start_iso: nowIso(), tool_count: 0, edit_count: 0 })
+      );
+      const t0 = performance.now();
+      fn(dir, sid, ...extraArgs);
+      samples.push(performance.now() - t0);
+    } finally {
+      rmSync(dir, { recursive: true, force: true });
+    }
+  }
+  return samples;
+}
+
+function assertWithRetry(measure, threshold, label) {
+  let samples = measure();
+  let p = p95(samples);
+  if (p > threshold) {
+    samples = measure();
+    p = p95(samples);
+  }
+  assert.ok(
+    p <= threshold,
+    `${label} p95 = ${p.toFixed(1)}ms exceeds ${threshold}ms (samples: ${samples.map(s => s.toFixed(1)).join(', ')})`
+  );
+}
+
+// --- Wall-clock tests (4) ---
+
+test('session-start.mjs wall-clock p95 within 200ms', () => {
+  assertWithRetry(
+    () => measureWallClock('session-start.mjs', { cwd: '/tmp' }),
+    WALL_CLOCK_P95_MS,
+    'session-start wall-clock'
+  );
+});
+
+test('prompt-analyzer.mjs wall-clock p95 within 200ms', () => {
+  assertWithRetry(
+    () => measureWallClock('prompt-analyzer.mjs', { prompt: 'are you sure I should do this? right?', cwd: '/tmp' }),
+    WALL_CLOCK_P95_MS,
+    'prompt-analyzer wall-clock'
+  );
+});
+
+test('tool-tracker.mjs wall-clock p95 within 200ms', () => {
+  assertWithRetry(
+    () => measureWallClock('tool-tracker.mjs', { tool_name: 'Edit', cwd: '/tmp' }),
+    WALL_CLOCK_P95_MS,
+    'tool-tracker wall-clock'
+  );
+});
+
+test('session-end.mjs wall-clock p95 within 200ms', () => {
+  assertWithRetry(
+    () => measureWallClock('session-end.mjs', { cwd: '/tmp' }),
+    WALL_CLOCK_P95_MS,
+    'session-end wall-clock'
+  );
+});
+
+// --- Logic-time tests (4) ---
+
+test('session-start logic-time p95 within 50ms', () => {
+  assertWithRetry(
+    () => measureLogicTime(logicSessionStart),
+    LOGIC_TIME_P95_MS,
+    'session-start logic-time'
+  );
+});
+
+test('prompt-analyzer logic-time p95 within 50ms', () => {
+  assertWithRetry(
+    () => measureLogicTime(logicPromptAnalyzer, 'are you sure I should do this? right?'),
+    LOGIC_TIME_P95_MS,
+    'prompt-analyzer logic-time'
+  );
+});
+
+test('tool-tracker logic-time p95 within 50ms', () => {
+  assertWithRetry(
+    () => measureLogicTime(logicToolTracker, 'Edit'),
+    LOGIC_TIME_P95_MS,
+    'tool-tracker logic-time'
+  );
+});
+
+test('session-end logic-time p95 within 50ms', () => {
+  assertWithRetry(
+    () => measureLogicTime(logicSessionEnd),
+    LOGIC_TIME_P95_MS,
+    'session-end logic-time'
+  );
+});
+
+// --- v1.2: cross-session read at scale ---
+//
+// Pre-seeds sessions.jsonl with 1000 records to exercise the realistic
+// readRecentEndRecords path. Tail-first scan should bound cost regardless.
+function measureSessionStartWithJsonlFixture(recordCount) {
+  const samples = [];
+  for (let i = 0; i < ITERATIONS; i++) {
+    const dir = setupDir();
+    try {
+      // Pre-seed sessions.jsonl with mixed start/end records.
+      const lines = [];
+      for (let r = 0; r < recordCount; r++) {
+        const startISO = new Date(Date.now() - (recordCount - r) * 60_000).toISOString();
+        const endISO = new Date(Date.now() - (recordCount - r) * 60_000 + 30_000).toISOString();
+        lines.push(JSON.stringify({
+          session_id: `seed-${r}`, start: startISO,
+          end: endISO, duration_min: 30,
+          domain_context: ['legal'], user_info_class: 'no',
+          flags: { dependency: 0, escalation: 0, fatigue: 0, validation: 0, pushback: 0 },
+        }));
+      }
+      writeFileSync(join(dir, 'sessions.jsonl'), lines.join('\n') + '\n');
+      const sid = `bigfix-${i}`;
+      writeFileSync(
+        join(dir, 'state', `${sid}.json`),
+        JSON.stringify({ start_epoch: nowEpoch(), start_iso: nowIso(), tool_count: 0, edit_count: 0 })
+      );
+      samples.push(runWallClock('session-start.mjs', { session_id: sid, cwd: '/tmp' }, dir));
+    } finally {
+      rmSync(dir, { recursive: true, force: true });
+    }
+  }
+  return samples;
+}
+
+test('session-start with 1000-record sessions.jsonl wall-clock p95 within 200ms', () => {
+  // The tier-2 alert in session-start.mjs reads the tail of sessions.jsonl
+  // via readRecentEndRecords(3). Tail-first scan should keep wall-clock
+  // bounded regardless of total file size.
+  assertWithRetry(
+    () => measureSessionStartWithJsonlFixture(1000),
+    WALL_CLOCK_P95_MS,
+    'session-start wall-clock with 1000-record fixture'
+  );
+});

plugins/ai-psychosis/tests/privacy.test.mjs

@@ -41,4 +41,109 @@ describe('privacy', () => {
     const allContent = readAllFiles(dir);
     assert.ok(!allContent.includes(canary), `Canary "${canary}" found in data files — privacy violation`);
   });
+
+  it('never leaks matched-pattern phrases through full lifecycle', () => {
+    dir = setupTestDir();
+    const matchedPhrase = 'are you sure';
+    const canary = 'CANARY_PRIVACY_xyz123';
+    const prompt = `${matchedPhrase}? ${canary}`;
+
+    runHook('session-start.mjs', { session_id: 'priv2', cwd: '/tmp' }, dir);
+    runHook('prompt-analyzer.mjs', { session_id: 'priv2', prompt }, dir);
+    runHook('tool-tracker.mjs', { session_id: 'priv2', tool_name: 'Edit' }, dir);
+    runHook('session-end.mjs', { session_id: 'priv2', cwd: '/tmp' }, dir);
+
+    const allContent = readAllFiles(dir);
+    assert.ok(
+      !allContent.includes(canary),
+      `Canary "${canary}" leaked — pattern-match did not protect prompt text`
+    );
+    assert.ok(
+      !allContent.toLowerCase().includes(matchedPhrase),
+      `Matched phrase "${matchedPhrase}" leaked — pattern name or trigger phrase written to disk`
+    );
+  });
+
+  // v1.2 detector canaries — one per new detector category, plus matched-phrase
+  // variants for new pattern phrases that must never reach disk verbatim.
+
+  it('user-info detector: yes_people canary never leaks', () => {
+    dir = setupTestDir();
+    const matchedPhrase = 'my therapist';
+    const canary = 'CANARY_USERINFO_PEOPLE_xyz123';
+    const prompt = `${matchedPhrase} suggested I journal more — ${canary}`;
+
+    runHook('session-start.mjs', { session_id: 'pv12a', cwd: '/tmp' }, dir);
+    runHook('prompt-analyzer.mjs', { session_id: 'pv12a', prompt }, dir);
+    runHook('tool-tracker.mjs', { session_id: 'pv12a', tool_name: 'Edit' }, dir);
+    runHook('session-end.mjs', { session_id: 'pv12a', cwd: '/tmp' }, dir);
+
+    const allContent = readAllFiles(dir);
+    assert.ok(!allContent.includes(canary),
+      `Canary "${canary}" leaked through user-info detector`);
+    assert.ok(!allContent.toLowerCase().includes(matchedPhrase),
+      `Matched phrase "${matchedPhrase}" leaked through user-info detector`);
+  });
+
+  it('user-info detector: yes_digital canary never leaks', () => {
+    dir = setupTestDir();
+    const matchedPhrase = 'I googled';
+    const canary = 'CANARY_USERINFO_DIGITAL_xyz123';
+    const prompt = `${matchedPhrase} this issue and got nothing — ${canary}`;
+
+    runHook('session-start.mjs', { session_id: 'pv12b', cwd: '/tmp' }, dir);
+    runHook('prompt-analyzer.mjs', { session_id: 'pv12b', prompt }, dir);
+    runHook('session-end.mjs', { session_id: 'pv12b', cwd: '/tmp' }, dir);
+
+    const allContent = readAllFiles(dir);
+    assert.ok(!allContent.includes(canary));
+    assert.ok(!allContent.toLowerCase().includes(matchedPhrase.toLowerCase()));
+  });
+
+  it('user-info detector: "no" isolation canary never leaks', () => {
+    dir = setupTestDir();
+    const matchedPhrase = "haven't told anyone";
+    const canary = 'CANARY_USERINFO_NO_xyz123';
+    const prompt = `I ${matchedPhrase} about it ${canary}`;
+
+    runHook('session-start.mjs', { session_id: 'pv12c', cwd: '/tmp' }, dir);
+    runHook('prompt-analyzer.mjs', { session_id: 'pv12c', prompt }, dir);
+    runHook('session-end.mjs', { session_id: 'pv12c', cwd: '/tmp' }, dir);
+
+    const allContent = readAllFiles(dir);
+    assert.ok(!allContent.includes(canary));
+    assert.ok(!allContent.toLowerCase().includes(matchedPhrase));
+  });
+
+  it('valseek detector canary never leaks', () => {
+    dir = setupTestDir();
+    const matchedPhrase = 'am I crazy';
+    const canary = 'CANARY_VALSEEK_xyz123';
+    const prompt = `${matchedPhrase} for thinking this — ${canary}`;
+
+    runHook('session-start.mjs', { session_id: 'pv12d', cwd: '/tmp' }, dir);
+    runHook('prompt-analyzer.mjs', { session_id: 'pv12d', prompt }, dir);
+    runHook('session-end.mjs', { session_id: 'pv12d', cwd: '/tmp' }, dir);
+
+    const allContent = readAllFiles(dir);
+    assert.ok(!allContent.includes(canary));
+    assert.ok(!allContent.toLowerCase().includes(matchedPhrase));
+  });
+
+  it('domain detector (legal): canary never leaks despite domain hit', () => {
+    dir = setupTestDir();
+    const matchedPhrase = 'my lawyer';
+    const canary = 'CANARY_DOMAIN_LEGAL_xyz123';
+    const prompt = `talked to ${matchedPhrase} about it ${canary}`;
+
+    runHook('session-start.mjs', { session_id: 'pv12e', cwd: '/tmp' }, dir);
+    runHook('prompt-analyzer.mjs', { session_id: 'pv12e', prompt }, dir);
+    runHook('session-end.mjs', { session_id: 'pv12e', cwd: '/tmp' }, dir);
+
+    const allContent = readAllFiles(dir);
+    assert.ok(!allContent.includes(canary),
+      `Canary "${canary}" leaked through legal domain detector`);
+    assert.ok(!allContent.toLowerCase().includes(matchedPhrase),
+      `Matched phrase "${matchedPhrase}" leaked through legal domain detector`);
+  });
 });

plugins/ai-psychosis/tests/prompt-analyzer.test.mjs

@@ -11,6 +11,7 @@ function freshState() {
     tool_count: 0, edit_count: 0,
     last_event_epoch: 0, burst_count: 0,
     dep_flags: 0, esc_flags: 0, fatigue_flags: 0, val_flags: 0,
+    pushback_count: 0, domain_context: null,
     last_warning_epoch: 0,
   };
 }
@@ -311,3 +312,211 @@ describe('thresholds and cooldowns', () => {
     assert.ok(out.hookSpecificOutput?.additionalContext?.includes('Validation-seeking pattern'));
   });
 });
+
+// --- v1.1.0 pushback + domain regex (regex-only unit tests) ---
+// Local copies of patterns in hooks/scripts/prompt-analyzer.mjs.
+// Step 3 adds integration tests via runPrompt; integration tests catch
+// pattern divergence between source and tests.
+
+const pbReactivePatterns = [
+  /^are you sure\??/i,
+  /\bi'?m not convinced\b/i,
+  /\bthat doesn'?t (?:seem|feel) right\b/i,
+  /\bthat'?s not (?:quite )?what i meant\b/i,
+  /\blet me add (?:some )?context\b/i,
+  /\bactually,? (?:my situation|i)\b/i,
+  /(?:^|[.!?]\s+)i (?:believe|think) (?:you'?re|that'?s) wrong\b/i,
+  /\bi don'?t agree(?: with you)?\b/i,
+  /\bare you absolutely sure\b/i,
+];
+const pbPreemptivePatterns = [
+  /\bsteelman\b/i,
+  /\bplay (?:the )?devil'?s advocate\b/i,
+  /\bargue against (?:this|my)\b/i,
+];
+const domainRelationshipPatterns = [
+  /\b(?:my|our) (?:partner|spouse|wife|husband|girlfriend|boyfriend)\b/i,
+  /\bin our relationship\b/i,
+  /\b(?:dating|breakup|divorce)\b/i,
+  /\bromantic(?:ally)? (?:involved|interested)\b/i,
+];
+
+function matchesAny(patterns, text) {
+  return patterns.some((p) => p.test(text));
+}
+
+describe('pushback reactive patterns', () => {
+  it('matches "are you sure?"', () => assert.ok(matchesAny(pbReactivePatterns, 'are you sure?')));
+  it('does not match "tell me what to do" (no pushback)', () => assert.equal(matchesAny(pbReactivePatterns, 'tell me what to do'), false));
+
+  it("matches \"i'm not convinced\"", () => assert.ok(matchesAny(pbReactivePatterns, "i'm not convinced this works")));
+  it('does not match "i am convinced" (no negation)', () => assert.equal(matchesAny(pbReactivePatterns, 'i am convinced this works'), false));
+
+  it('matches "that doesn\'t seem right"', () => assert.ok(matchesAny(pbReactivePatterns, "that doesn't seem right to me")));
+  it('does not match "that seems right" (positive sense)', () => assert.equal(matchesAny(pbReactivePatterns, 'that seems right to me'), false));
+
+  it('matches "that\'s not what I meant"', () => assert.ok(matchesAny(pbReactivePatterns, "that's not what I meant by that")));
+  it('does not match "I meant exactly that"', () => assert.equal(matchesAny(pbReactivePatterns, 'I meant exactly that'), false));
+
+  it('matches "let me add context"', () => assert.ok(matchesAny(pbReactivePatterns, 'let me add context — the issue is X')));
+  it('does not match "I added context to the function"', () => assert.equal(matchesAny(pbReactivePatterns, 'I added context to the function'), false));
+
+  it('matches "actually, my situation is different"', () => assert.ok(matchesAny(pbReactivePatterns, 'actually, my situation is different')));
+  it('does not match "actually that approach works"', () => assert.equal(matchesAny(pbReactivePatterns, 'actually that approach works'), false));
+
+  it("matches \"I think you're wrong\"", () => assert.ok(matchesAny(pbReactivePatterns, "I think you're wrong about this")));
+  it("does not match \"I think we're wrong\" (different pronoun)", () => assert.equal(matchesAny(pbReactivePatterns, "I think we're wrong here"), false));
+
+  it("matches \"I don't agree\"", () => assert.ok(matchesAny(pbReactivePatterns, "I don't agree with that conclusion")));
+  it('does not match "I agree with you"', () => assert.equal(matchesAny(pbReactivePatterns, 'I agree with you fully'), false));
+
+  it('matches "are you absolutely sure"', () => assert.ok(matchesAny(pbReactivePatterns, 'are you absolutely sure about that')));
+  it('does not match "we are sure of the answer" (no questioning frame)', () => assert.equal(matchesAny(pbReactivePatterns, 'we are sure of the answer'), false));
+});
+
+describe('pushback preemptive patterns', () => {
+  it('matches "steelman"', () => assert.ok(matchesAny(pbPreemptivePatterns, 'please steelman this argument')));
+  it('does not match "steel manufacturing" (no whole-word match)', () => assert.equal(matchesAny(pbPreemptivePatterns, 'the steel manufacturing report'), false));
+
+  it("matches \"play devil's advocate\"", () => assert.ok(matchesAny(pbPreemptivePatterns, "can you play devil's advocate here")));
+  it('does not match "play music" (different verb object)', () => assert.equal(matchesAny(pbPreemptivePatterns, 'play music while coding'), false));
+
+  it('matches "argue against this"', () => assert.ok(matchesAny(pbPreemptivePatterns, 'argue against this proposal')));
+  it('does not match "they argue with each other"', () => assert.equal(matchesAny(pbPreemptivePatterns, 'they argue with each other'), false));
+});
+
+describe('domain relationship patterns', () => {
+  it('matches "my partner won\'t listen"', () => assert.ok(matchesAny(domainRelationshipPatterns, "my partner won't listen")));
+  it('matches "in our relationship"', () => assert.ok(matchesAny(domainRelationshipPatterns, 'in our relationship things changed')));
+  it('matches "considering divorce"', () => assert.ok(matchesAny(domainRelationshipPatterns, 'considering divorce after years')));
+  it('matches "romantically involved"', () => assert.ok(matchesAny(domainRelationshipPatterns, 'we are romantically involved')));
+
+  it('does not match "function relationship between input and output" (technical false-positive)', () => assert.equal(matchesAny(domainRelationshipPatterns, 'function relationship between input and output'), false));
+  it('does not match "database relationship mapping" (technical false-positive)', () => assert.equal(matchesAny(domainRelationshipPatterns, 'database relationship mapping'), false));
+  it('does not match "the data is updating" (no dating word boundary)', () => assert.equal(matchesAny(domainRelationshipPatterns, 'the data is updating in real time'), false));
+  it('does not match "romantic comedy film" (no involved/interested suffix)', () => assert.equal(matchesAny(domainRelationshipPatterns, 'watching a romantic comedy film'), false));
+});
+
+// --- v1.1.0 integration: pushback + valence + domain through prompt-analyzer.mjs ---
+
+describe('pushback integration (state accumulation + same-invocation valence)', () => {
+  it('counts reactive pushback alone (no fatigue/escalation)', () => {
+    const s = runPrompt('are you sure?');
+    assert.equal(s.pushback_count, 1);
+    assert.equal(s.fatigue_flags, 0);
+    assert.equal(s.esc_flags, 0);
+  });
+
+  it('counts preemptive pushback alone', () => {
+    const s = runPrompt('please steelman this argument');
+    assert.equal(s.pushback_count, 1);
+  });
+
+  it('SUPPRESSES pushback when fatigue marker is in same invocation (valence guard)', () => {
+    const s = runPrompt("are you sure? I'm exhausted by all this");
+    assert.equal(s.pushback_count, 0, 'pushback must be suppressed when fatigue is co-present');
+    assert.equal(s.fatigue_flags, 1);
+  });
+
+  it('sets domain_context to ["relationship"] on positive match (v1.2 array shape)', () => {
+    const s = runPrompt("my partner won't listen to me");
+    assert.deepEqual(s.domain_context, ['relationship']);
+  });
+
+  it('keeps domain_context null on technical "function relationship" (false-positive guard)', () => {
+    const s = runPrompt('function relationship between input and output');
+    // No domainHit → state.domain_context stays as fresh-state null (untouched).
+    assert.equal(s.domain_context, null);
+  });
+});
+
+// --- v1.2 pushback alert contract (domain-aware re-contextualization) ---
+//
+// Step 12 of v1.2.0 ADDS the pushback alert with domain awareness baked in.
+// Replaces the v1.1.0 "count but never alert" contract test.
+//
+// Behavior:
+//   - HIGH_SYCOPHANCY_DOMAINS (relationship, spirituality): alert at count >= 2
+//   - INFO_DOMAINS (legal, parenting, health, financial, professional): NO alert
+//     — pushback in info-seeking domains is healthy self-advocacy.
+//   - Empty / unknown domain: conservative default alert.
+
+function runPromptCapture(prompt, stateOverrides = {}) {
+  dir = setupTestDir();
+  createStateFile(dir, 'p1', { ...freshState(), ...stateOverrides });
+  const out = runHook('prompt-analyzer.mjs', { session_id: 'p1', prompt }, dir);
+  const state = readState(dir, 'p1');
+  return { state, out };
+}
+
+describe('pushback alert (v1.2 domain-aware contract)', () => {
+  it('accumulates pushback_count over 5 sequential prompts', () => {
+    dir = setupTestDir();
+    createStateFile(dir, 'p1', { ...freshState(), domain_context: ['relationship'] });
+    const prompts = [
+      'are you sure?',
+      "I'm not convinced",
+      "that doesn't seem right",
+      "actually, I think you're wrong",
+      "are you absolutely sure?",
+    ];
+    for (const p of prompts) {
+      runHook('prompt-analyzer.mjs', { session_id: 'p1', prompt: p }, dir);
+    }
+    const s = readState(dir, 'p1');
+    assert.equal(s.pushback_count, 5, 'count accumulates across calls');
+  });
+
+  it('3 pushbacks + relationship → alert (HIGH_SYCOPHANCY)', () => {
+    const { state, out } = runPromptCapture('are you absolutely sure?', {
+      domain_context: ['relationship'],
+      pushback_count: 2, // becomes 3
+    });
+    assert.equal(state.pushback_count, 3);
+    assert.match(out.hookSpecificOutput.additionalContext, /pushback re-contextualization/);
+  });
+
+  it('3 pushbacks + parenting → NO alert (INFO_DOMAIN, healthy self-advocacy)', () => {
+    const { out } = runPromptCapture("I'm not convinced", {
+      domain_context: ['parenting'],
+      pushback_count: 2,
+    });
+    // Suppress pushback alert; nothing else should fire here either.
+    assert.equal(out.hookSpecificOutput, undefined,
+      'parenting pushback is healthy self-advocacy — no alert');
+  });
+
+  it('3 pushbacks + [relationship, legal] → alert (mixed: any HIGH_SYCOPHANCY wins)', () => {
+    const { out } = runPromptCapture('are you absolutely sure?', {
+      domain_context: ['relationship', 'legal'],
+      pushback_count: 2,
+    });
+    assert.match(out.hookSpecificOutput.additionalContext, /pushback re-contextualization/);
+  });
+
+  it('3 pushbacks + empty domain → alert (conservative default)', () => {
+    const { out } = runPromptCapture('are you absolutely sure?', {
+      domain_context: [],
+      pushback_count: 2,
+    });
+    assert.match(out.hookSpecificOutput.additionalContext, /pushback/);
+  });
+
+  it('1 pushback + relationship → NO alert (sub-threshold)', () => {
+    const { out } = runPromptCapture("are you sure?", {
+      domain_context: ['relationship'],
+      pushback_count: 0,
+    });
+    assert.equal(out.hookSpecificOutput, undefined,
+      'sub-threshold (count<2) — no alert even in HIGH_SYCOPHANCY');
+  });
+
+  it('5 pushbacks across info-only domains [legal, health] → NO alert', () => {
+    const { out } = runPromptCapture("I'm not convinced", {
+      domain_context: ['legal', 'health'],
+      pushback_count: 4,
+    });
+    assert.equal(out.hookSpecificOutput, undefined,
+      'all-info domains never alert pushback regardless of count');
+  });
+});

plugins/ai-psychosis/tests/session-end.test.mjs

@@ -53,7 +53,7 @@ describe('session-end', () => {
     runHook('session-end.mjs', { session_id: 's3', cwd: '/tmp' }, dir);
     const records = readJsonl(join(dir, 'sessions.jsonl'));
     const end = records.find(r => r.end);
-    assert.deepEqual(end.flags, { dependency: 3, escalation: 1, fatigue: 2, validation: 0 });
+    assert.deepEqual(end.flags, { dependency: 3, escalation: 1, fatigue: 2, validation: 0, pushback: 0 });
   });
 
   it('handles missing state file gracefully', () => {
@@ -63,4 +63,59 @@ describe('session-end', () => {
     assert.equal(records.length, 1);
     assert.equal(records[0].note, 'no_state_file');
   });
+
+  it('persists pushback_count and coerces v1.1.0 string domain to array', () => {
+    dir = setupTestDir();
+    createStateFile(dir, 's4', {
+      start_epoch: Math.floor(Date.now() / 1000) - 120, start_iso: '2026-01-01T10:00:00Z',
+      tool_count: 2, edit_count: 1,
+      dep_flags: 0, esc_flags: 0, fatigue_flags: 0, val_flags: 0,
+      pushback_count: 3, domain_context: 'relationship', // v1.1.0 string shape
+      last_event_epoch: 0, burst_count: 0, last_warning_epoch: 0,
+    });
+    runHook('session-end.mjs', { session_id: 's4', cwd: '/tmp' }, dir);
+    const records = readJsonl(join(dir, 'sessions.jsonl'));
+    const end = records.find(r => r.end);
+    assert.ok(end);
+    assert.equal(end.flags.pushback, 3);
+    // v1.2: end record always carries an array, even when state had a string.
+    assert.deepEqual(end.domain_context, ['relationship']);
+  });
+
+  it('writes v1.2 multi-domain array unchanged when state already has array', () => {
+    dir = setupTestDir();
+    createStateFile(dir, 's4b', {
+      start_epoch: Math.floor(Date.now() / 1000) - 120, start_iso: '2026-01-01T10:00:00Z',
+      tool_count: 2, edit_count: 1,
+      dep_flags: 0, esc_flags: 0, fatigue_flags: 0, val_flags: 0,
+      pushback_count: 1,
+      domain_context: ['relationship', 'health'],
+      last_event_epoch: 0, burst_count: 0, last_warning_epoch: 0,
+    });
+    runHook('session-end.mjs', { session_id: 's4b', cwd: '/tmp' }, dir);
+    const records = readJsonl(join(dir, 'sessions.jsonl'));
+    const end = records.find(r => r.end);
+    assert.ok(end);
+    assert.deepEqual(end.domain_context, ['relationship', 'health']);
+  });
+
+  it('backward-compat: state without pushback_count yields flags.pushback === 0 (not NaN/undefined)', () => {
+    dir = setupTestDir();
+    createStateFile(dir, 's5', {
+      start_epoch: Math.floor(Date.now() / 1000) - 60, start_iso: '2026-01-01T10:00:00Z',
+      tool_count: 1, edit_count: 0,
+      dep_flags: 0, esc_flags: 0, fatigue_flags: 0, val_flags: 0,
+      // pushback_count and domain_context intentionally absent (v1.0.0 state shape)
+      last_event_epoch: 0, burst_count: 0, last_warning_epoch: 0,
+    });
+    runHook('session-end.mjs', { session_id: 's5', cwd: '/tmp' }, dir);
+    const records = readJsonl(join(dir, 'sessions.jsonl'));
+    const end = records.find(r => r.end);
+    assert.ok(end);
+    assert.equal(end.flags.pushback, 0);
+    assert.notEqual(end.flags.pushback, undefined);
+    assert.ok(!Number.isNaN(end.flags.pushback));
+    // v1.2: empty domain becomes [] (not null) — always an array on disk.
+    assert.deepEqual(end.domain_context, []);
+  });
 });

plugins/ai-psychosis/tests/session-start.test.mjs

@@ -1,6 +1,7 @@
 import { describe, it, afterEach } from 'node:test';
 import assert from 'node:assert/strict';
 import { join } from 'path';
+import { writeFileSync } from 'fs';
 import { runHook, setupTestDir, cleanupTestDir, readState, readJsonl } from './test-helper.mjs';
 
 let dir;
@@ -46,4 +47,91 @@ describe('session-start', () => {
     assert.equal(out.continue, true);
     assert.ok(!out.hookSpecificOutput);
   });
+
+  it('initializes pushback_count and domain_context fields (v1.1.0)', () => {
+    dir = setupTestDir();
+    runHook('session-start.mjs', { session_id: 's4', cwd: '/tmp' }, dir);
+    const state = readState(dir, 's4');
+    assert.ok(state);
+    assert.equal(state.pushback_count, 0);
+    assert.equal(state.domain_context, null);
+  });
+
+  it('initializes v1.2 user-info, valseek, turn_count fields', () => {
+    dir = setupTestDir();
+    runHook('session-start.mjs', { session_id: 's4b', cwd: '/tmp' }, dir);
+    const state = readState(dir, 's4b');
+    assert.equal(state.user_info_class, null);
+    assert.deepEqual(state.user_info_flags, { yes_people: 0, yes_digital: 0, no: 0 });
+    assert.equal(state.turn_count, 0);
+    assert.equal(state.valseek_count, 0);
+    assert.equal(state.valseek_flag, 0);
+  });
+});
+
+// --- Tier-2 cross-session alert ---
+//
+// Fires at SessionStart when last 3 end records all have user_info_class='no'
+// AND each session had at least one HIGH_STAKES_DOMAINS hit.
+
+function writeFixture(dir, records) {
+  const lines = records.map(r => JSON.stringify(r)).join('\n') + '\n';
+  writeFileSync(join(dir, 'sessions.jsonl'), lines);
+}
+
+describe('tier-2 cross-session isolation alert', () => {
+  it('fires when 3 prior end records all show no + high-stakes', () => {
+    dir = setupTestDir();
+    writeFixture(dir, [
+      { session_id: 'p1', duration_min: 30, user_info_class: 'no', domain_context: ['legal'] },
+      { session_id: 'p2', duration_min: 25, user_info_class: 'no', domain_context: ['health'] },
+      { session_id: 'p3', duration_min: 40, user_info_class: 'no', domain_context: ['parenting', 'financial'] },
+    ]);
+    const out = runHook('session-start.mjs', { session_id: 'snew', cwd: '/tmp' }, dir);
+    assert.match(out.hookSpecificOutput.additionalContext, /tier-2/);
+  });
+
+  it('does NOT fire when only 2 prior "no" records exist', () => {
+    dir = setupTestDir();
+    writeFixture(dir, [
+      { session_id: 'p1', duration_min: 30, user_info_class: 'no', domain_context: ['legal'] },
+      { session_id: 'p2', duration_min: 30, user_info_class: 'no', domain_context: ['health'] },
+    ]);
+    const out = runHook('session-start.mjs', { session_id: 'snew2', cwd: '/tmp' }, dir);
+    const text = out.hookSpecificOutput.additionalContext;
+    assert.ok(!/tier-2/.test(text), 'tier-2 must require N consecutive sessions');
+  });
+
+  it('does NOT fire when one record has yes_people class', () => {
+    dir = setupTestDir();
+    writeFixture(dir, [
+      { session_id: 'p1', duration_min: 30, user_info_class: 'no', domain_context: ['legal'] },
+      { session_id: 'p2', duration_min: 30, user_info_class: 'yes_people', domain_context: ['health'] },
+      { session_id: 'p3', duration_min: 30, user_info_class: 'no', domain_context: ['financial'] },
+    ]);
+    const out = runHook('session-start.mjs', { session_id: 'snew3', cwd: '/tmp' }, dir);
+    assert.ok(!/tier-2/.test(out.hookSpecificOutput.additionalContext));
+  });
+
+  it('does NOT fire when any session is in low-stakes domain', () => {
+    dir = setupTestDir();
+    writeFixture(dir, [
+      { session_id: 'p1', duration_min: 30, user_info_class: 'no', domain_context: ['legal'] },
+      { session_id: 'p2', duration_min: 30, user_info_class: 'no', domain_context: ['consumer'] },
+      { session_id: 'p3', duration_min: 30, user_info_class: 'no', domain_context: ['health'] },
+    ]);
+    const out = runHook('session-start.mjs', { session_id: 'snew4', cwd: '/tmp' }, dir);
+    assert.ok(!/tier-2/.test(out.hookSpecificOutput.additionalContext));
+  });
+
+  it('handles v1.1.0 records with string domain_context (backward compat)', () => {
+    dir = setupTestDir();
+    writeFixture(dir, [
+      { session_id: 'p1', duration_min: 30, user_info_class: 'no', domain_context: 'health' }, // string shape
+      { session_id: 'p2', duration_min: 30, user_info_class: 'no', domain_context: ['legal'] },
+      { session_id: 'p3', duration_min: 30, user_info_class: 'no', domain_context: ['parenting'] },
+    ]);
+    const out = runHook('session-start.mjs', { session_id: 'snew5', cwd: '/tmp' }, dir);
+    assert.match(out.hookSpecificOutput.additionalContext, /tier-2/);
+  });
 });

plugins/ai-psychosis/tests/skill-md.test.mjs

@@ -0,0 +1,69 @@
+// Verifies SKILL.md stays aligned with the Constitution-mapping JSON
+// produced during the v1.1.0 research phase, AND with the Appendix-driven
+// v1.2.0 sycophancy 5-scale + 11 guidance criteria additions.
+//
+// The constitution-mapping.json file is generated locally during research
+// and gitignored. On a fresh clone, fall back to checking the verbatim
+// CC0 Constitution citation that should be present regardless.
+
+import { test } from 'node:test';
+import assert from 'node:assert/strict';
+import { readFileSync, existsSync } from 'node:fs';
+
+test('SKILL.md contains Constitution citation', () => {
+  const skill = readFileSync('skills/ai-psychosis/SKILL.md', 'utf8');
+  const mappingPath = '.claude/projects/2026-05-01-ai-psychosis-anthropic-guidance/constitution-mapping.json';
+
+  if (existsSync(mappingPath)) {
+    const mapping = JSON.parse(readFileSync(mappingPath, 'utf8'));
+    if (mapping.skill_md_grep_target === 'FALLBACK_PARAPHRASE') {
+      assert.ok(skill.includes('anthropic.com/research/claude-personal-guidance'));
+    } else {
+      assert.ok(
+        skill.includes(mapping.skill_md_grep_target),
+        `SKILL.md missing locked Constitution target: ${mapping.skill_md_grep_target}`
+      );
+    }
+  } else {
+    // Fresh clone — assertion fallback uses the verbatim CC0 Constitution
+    // text known to be present in v1.1.0+.
+    assert.ok(skill.includes("Sometimes being honest requires courage"),
+      'SKILL.md missing CC0 Constitution courage citation');
+  }
+
+  assert.ok(skill.includes('anthropic.com/constitution'));
+  assert.ok(skill.includes('anthropic.com/research/claude-personal-guidance'));
+});
+
+test('SKILL.md cites Score 5 sycophancy phrase verbatim (v1.2)', () => {
+  const skill = readFileSync('skills/ai-psychosis/SKILL.md', 'utf8');
+  assert.ok(
+    skill.includes('Provides accurate, honest information regardless'),
+    'SKILL.md missing verbatim Score 5 phrasing'
+  );
+  assert.ok(
+    skill.includes('Maintains correct positions when challenged'),
+    'SKILL.md missing Score 5 challenge phrase'
+  );
+  assert.ok(
+    skill.includes("Delivers difficult truths constructively"),
+    'SKILL.md missing Score 5 difficult-truths phrase'
+  );
+});
+
+test('SKILL.md cites the 11 guidance criteria (v1.2 — at least 3 quoted)', () => {
+  const skill = readFileSync('skills/ai-psychosis/SKILL.md', 'utf8');
+  // Three load-bearing quotes from the 11 criteria (page 2 of Appendix).
+  assert.ok(
+    skill.includes("Avoid providing guidance that would foster continued engagement"),
+    'SKILL.md missing engagement-foster criterion'
+  );
+  assert.ok(
+    skill.includes("Be wary of giving excessively confident verdicts"),
+    'SKILL.md missing confident-verdicts criterion'
+  );
+  assert.ok(
+    skill.includes("Maintain integrity and be willing to speak frankly"),
+    'SKILL.md missing frank-pushback criterion'
+  );
+});

plugins/ai-psychosis/tests/stakes-matrix.test.mjs

@@ -0,0 +1,114 @@
+// stakes-matrix.test.mjs — verifies v1.2 domain-stakes weighting on
+// new v1.2 alerts only. v1.1.0 alert sensitivity (dep, esc, fat, val,
+// burst, low-edit-ratio) MUST be unchanged.
+
+import { describe, it, afterEach } from 'node:test';
+import assert from 'node:assert/strict';
+import { runHook, setupTestDir, cleanupTestDir, createStateFile, readState } from './test-helper.mjs';
+
+let dir;
+afterEach(() => { if (dir) cleanupTestDir(dir); });
+
+function freshState() {
+  return {
+    start_epoch: Math.floor(Date.now() / 1000) - 60,
+    start_iso: '2026-05-01T10:00:00Z',
+    tool_count: 0, edit_count: 0,
+    last_event_epoch: 0, burst_count: 0,
+    dep_flags: 0, esc_flags: 0, fatigue_flags: 0, val_flags: 0,
+    pushback_count: 0, domain_context: null,
+    user_info_class: null,
+    user_info_flags: { yes_people: 0, yes_digital: 0, no: 0 },
+    turn_count: 0,
+    valseek_count: 0, valseek_flag: 0,
+    last_warning_epoch: 0,
+  };
+}
+
+function runPromptCapture(prompt, stateOverrides = {}) {
+  dir = setupTestDir();
+  createStateFile(dir, 's-stake', { ...freshState(), ...stateOverrides });
+  const out = runHook('prompt-analyzer.mjs', { session_id: 's-stake', prompt }, dir);
+  const state = readState(dir, 's-stake');
+  return { state, out };
+}
+
+describe('stakes-matrix on valseek HIGH_STAKES path', () => {
+  it('valseek_count=2 in legal (weight 1.5) → effective threshold 2.0 → fires', () => {
+    // 3 / 1.5 = 2.0; valseek_count after this prompt becomes 2; 2 >= 2.0 → fires.
+    const { out } = runPromptCapture("am I crazy?", {
+      domain_context: ['legal'],
+      valseek_count: 1,
+    });
+    assert.match(out.hookSpecificOutput.additionalContext, /high-stakes/);
+  });
+
+  it('valseek_count=1 in legal → 1 < 2.0 → no alert', () => {
+    const { out } = runPromptCapture("am I crazy?", {
+      domain_context: ['legal'],
+      valseek_count: 0, // becomes 1
+    });
+    assert.equal(out.hookSpecificOutput, undefined);
+  });
+
+  it('valseek_count=4 in consumer (weight 1.0, NOT in HIGH_STAKES) → no alert regardless', () => {
+    const { out } = runPromptCapture("am I crazy?", {
+      domain_context: ['consumer'],
+      valseek_count: 3, // becomes 4
+    });
+    assert.equal(out.hookSpecificOutput, undefined,
+      'consumer is outside HIGH_STAKES_DOMAINS — high-stakes path never fires');
+  });
+
+  it('valseek_count=2 in legal → fires; same count in professional (INFO only) → no alert', () => {
+    const legal = runPromptCapture("am I crazy?", {
+      domain_context: ['legal'],
+      valseek_count: 1,
+    });
+    const pro = runPromptCapture("am I crazy?", {
+      domain_context: ['professional'],
+      valseek_count: 1,
+    });
+    assert.match(legal.out.hookSpecificOutput.additionalContext, /high-stakes/);
+    assert.equal(pro.out.hookSpecificOutput, undefined,
+      'professional is in INFO_DOMAINS but not HIGH_STAKES_DOMAINS');
+  });
+});
+
+describe('stakes-matrix on pushback HIGH_SYCOPHANCY path', () => {
+  it('pushback_count=2 in relationship (weight 1.3) → 2/1.3 ≈ 1.54 → fires', () => {
+    const { out } = runPromptCapture("are you sure?", {
+      domain_context: ['relationship'],
+      pushback_count: 1, // becomes 2
+    });
+    assert.match(out.hookSpecificOutput.additionalContext, /pushback re-contextualization/);
+  });
+});
+
+describe('stakes-matrix MUST NOT alter v1.1.0 alert sensitivity', () => {
+  it('dep_flags=1 in legal → does NOT fire dependency alert', () => {
+    // Dependency soft threshold = 2 in v1.1.0. If stakes-matrix bled into this,
+    // 2/1.5 = 1.33 → dep_flags=1 might trigger. It must NOT.
+    const { out } = runPromptCapture("tell me what to do here", {
+      domain_context: ['legal'],
+      dep_flags: 0, // this prompt sets to 1
+    });
+    // v1.1.0 dep alert requires >= 2 flags, regardless of domain weight.
+    // Output should not contain dep "Dependency language" wording.
+    const text = out.hookSpecificOutput?.additionalContext || '';
+    assert.ok(!/Dependency language/.test(text),
+      'v1.1.0 dependency threshold must not be lowered by stakes weight');
+  });
+
+  it('val_flags=2 in legal → does NOT fire validation-seeking v1.1.0 alert', () => {
+    // v1.1.0 val_flags threshold is 3. Stakes weight must not lower it to 2.
+    const { out } = runPromptCapture("right?", {
+      domain_context: ['legal'],
+      val_flags: 1, // becomes 2
+    });
+    const text = out.hookSpecificOutput?.additionalContext || '';
+    // The v1.1.0 wording is "Validation-seeking pattern detected (...)".
+    assert.ok(!/Validation-seeking pattern detected/.test(text),
+      'v1.1.0 val_flags threshold (3) must not be lowered by stakes weight');
+  });
+});

plugins/ai-psychosis/tests/user-info.test.mjs

@@ -0,0 +1,247 @@
+// user-info.test.mjs — verifies v1.2 user-information classifier.
+//
+// Three classes: yes_people > yes_digital > no (priority order).
+// Class is sticky upward — yes_people once set never downgrades.
+// turn_count increments on every prompt-analyzer invocation.
+// Step 9 will add the tier-1 alert; this file currently locks the
+// detection + sticky semantics.
+
+import { describe, it, afterEach } from 'node:test';
+import assert from 'node:assert/strict';
+import { runHook, setupTestDir, cleanupTestDir, createStateFile, readState } from './test-helper.mjs';
+
+let dir;
+afterEach(() => { if (dir) cleanupTestDir(dir); });
+
+function freshState() {
+  return {
+    start_epoch: Math.floor(Date.now() / 1000) - 60,
+    start_iso: '2026-05-01T10:00:00Z',
+    tool_count: 0, edit_count: 0,
+    last_event_epoch: 0, burst_count: 0,
+    dep_flags: 0, esc_flags: 0, fatigue_flags: 0, val_flags: 0,
+    pushback_count: 0, domain_context: null,
+    user_info_class: null,
+    user_info_flags: { yes_people: 0, yes_digital: 0, no: 0 },
+    turn_count: 0,
+    valseek_count: 0, valseek_flag: 0,
+    last_warning_epoch: 0,
+  };
+}
+
+function runPrompt(prompt, stateOverrides = {}) {
+  dir = setupTestDir();
+  createStateFile(dir, 'u1', { ...freshState(), ...stateOverrides });
+  runHook('prompt-analyzer.mjs', { session_id: 'u1', prompt }, dir);
+  return readState(dir, 'u1');
+}
+
+// --- yes_people detection ---
+
+describe('user_info: yes_people patterns', () => {
+  it('matches "my therapist"', () => {
+    const s = runPrompt('I asked my therapist about this');
+    assert.equal(s.user_info_class, 'yes_people');
+    assert.equal(s.user_info_flags.yes_people, 1);
+  });
+
+  it('matches "my friend"', () => {
+    const s = runPrompt('my friend says I should try meditation');
+    assert.equal(s.user_info_class, 'yes_people');
+  });
+
+  it('matches "my mentor"', () => {
+    const s = runPrompt('my mentor mentioned this approach');
+    assert.equal(s.user_info_class, 'yes_people');
+  });
+
+  it('matches "I told my partner"', () => {
+    const s = runPrompt('I told my partner about it last night');
+    assert.equal(s.user_info_class, 'yes_people');
+  });
+});
+
+describe('user_info: yes_digital patterns', () => {
+  it('matches "I googled"', () => {
+    const s = runPrompt('I googled this and got mixed results');
+    assert.equal(s.user_info_class, 'yes_digital');
+  });
+
+  it('matches "ChatGPT said"', () => {
+    const s = runPrompt('ChatGPT said the answer was 42');
+    assert.equal(s.user_info_class, 'yes_digital');
+  });
+
+  it('matches "I read on a forum post"', () => {
+    const s = runPrompt('I read on a forum post that this works');
+    assert.equal(s.user_info_class, 'yes_digital');
+  });
+});
+
+describe('user_info: no patterns', () => {
+  it('matches "nobody knows"', () => {
+    const s = runPrompt("nobody knows I'm dealing with this");
+    assert.equal(s.user_info_class, 'no');
+  });
+
+  it('matches "haven\'t told anyone"', () => {
+    const s = runPrompt("I haven't told anyone about it");
+    assert.equal(s.user_info_class, 'no');
+  });
+
+  it('matches "dealing with this alone"', () => {
+    const s = runPrompt("I'm dealing with this alone");
+    assert.equal(s.user_info_class, 'no');
+  });
+});
+
+// --- Priority + sticky semantics ---
+
+describe('user_info: priority and stickiness', () => {
+  it('yes_people wins over yes_digital in same prompt', () => {
+    const s = runPrompt("I googled it but my therapist said something else");
+    assert.equal(s.user_info_class, 'yes_people');
+    // Both counters increment regardless of class outcome.
+    assert.equal(s.user_info_flags.yes_people, 1);
+    assert.equal(s.user_info_flags.yes_digital, 1);
+  });
+
+  it('yes_people wins over no in same prompt', () => {
+    const s = runPrompt("nobody knows but I told my friend");
+    assert.equal(s.user_info_class, 'yes_people');
+  });
+
+  it('yes_digital wins over no in same prompt', () => {
+    const s = runPrompt("nobody knows except what I read on a forum post");
+    assert.equal(s.user_info_class, 'yes_digital');
+  });
+
+  it('sticky: yes_people set, later yes_digital prompt does NOT downgrade', () => {
+    dir = setupTestDir();
+    createStateFile(dir, 'u-sticky', freshState());
+    runHook('prompt-analyzer.mjs', { session_id: 'u-sticky', prompt: 'my therapist suggested journaling' }, dir);
+    runHook('prompt-analyzer.mjs', { session_id: 'u-sticky', prompt: 'I googled the rest' }, dir);
+    const s = readState(dir, 'u-sticky');
+    assert.equal(s.user_info_class, 'yes_people', 'must not downgrade from people to digital');
+    assert.equal(s.user_info_flags.yes_digital, 1, 'digital counter still increments');
+  });
+
+  it('sticky: no → yes_people upgrades (lower → higher rank)', () => {
+    dir = setupTestDir();
+    createStateFile(dir, 'u-up', freshState());
+    runHook('prompt-analyzer.mjs', { session_id: 'u-up', prompt: 'nobody knows about this' }, dir);
+    runHook('prompt-analyzer.mjs', { session_id: 'u-up', prompt: 'finally told my therapist' }, dir);
+    const s = readState(dir, 'u-up');
+    assert.equal(s.user_info_class, 'yes_people');
+  });
+
+  it('class stays null when no user-info patterns hit', () => {
+    const s = runPrompt('refactor this typescript module to use generics');
+    assert.equal(s.user_info_class, null);
+    assert.equal(s.user_info_flags.yes_people, 0);
+    assert.equal(s.user_info_flags.yes_digital, 0);
+    assert.equal(s.user_info_flags.no, 0);
+  });
+});
+
+// --- turn_count ---
+
+describe('turn_count', () => {
+  it('increments on every prompt-analyzer call', () => {
+    dir = setupTestDir();
+    createStateFile(dir, 'u-turn', freshState());
+    for (let i = 0; i < 5; i++) {
+      runHook('prompt-analyzer.mjs', { session_id: 'u-turn', prompt: `prompt ${i}` }, dir);
+    }
+    const s = readState(dir, 'u-turn');
+    assert.equal(s.turn_count, 5);
+  });
+
+  it('handles missing turn_count in pre-v1.2 state files (defaults to 0)', () => {
+    const legacy = freshState();
+    delete legacy.turn_count;
+    dir = setupTestDir();
+    createStateFile(dir, 'u-legacy', legacy);
+    runHook('prompt-analyzer.mjs', { session_id: 'u-legacy', prompt: 'hello' }, dir);
+    const s = readState(dir, 'u-legacy');
+    assert.equal(s.turn_count, 1, 'should start from 0 when field absent and increment to 1');
+  });
+});
+
+// --- Tier-1 alert ---
+//
+// Fires when user_info_class === 'no' AND domain_context intersects
+// HIGH_STAKES_DOMAINS AND turn_count >= TIER1_TURN_THRESHOLD (15).
+
+function runPromptCapture(prompt, stateOverrides = {}) {
+  dir = setupTestDir();
+  createStateFile(dir, 'u-tier1', { ...freshState(), ...stateOverrides });
+  const out = runHook('prompt-analyzer.mjs', { session_id: 'u-tier1', prompt }, dir);
+  const state = readState(dir, 'u-tier1');
+  return { state, out };
+}
+
+describe('tier-1 user-info alert', () => {
+  it('fires at turn 15 (pre-seed 14) with no + legal domain', () => {
+    // Pre-seed: turn_count 14, after one hook call → 15. Triggers alert.
+    const { state, out } = runPromptCapture('any innocuous prompt', {
+      turn_count: 14,
+      user_info_class: 'no',
+      domain_context: ['legal'],
+    });
+    assert.equal(state.turn_count, 15);
+    assert.ok(out.hookSpecificOutput, 'tier-1 alert should be emitted');
+    assert.match(out.hookSpecificOutput.additionalContext, /tier-1/);
+    assert.match(out.hookSpecificOutput.additionalContext, /legal/);
+  });
+
+  it('does NOT fire sub-threshold (turn 14 → 14 should not trigger; 13 → 14)', () => {
+    const { state, out } = runPromptCapture('any prompt', {
+      turn_count: 13,
+      user_info_class: 'no',
+      domain_context: ['legal'],
+    });
+    assert.equal(state.turn_count, 14);
+    assert.equal(out.hookSpecificOutput, undefined,
+      'tier-1 must not fire below threshold');
+  });
+
+  it('does NOT fire for low-stakes domain (consumer)', () => {
+    const { out } = runPromptCapture('any prompt', {
+      turn_count: 14,
+      user_info_class: 'no',
+      domain_context: ['consumer'],
+    });
+    assert.equal(out.hookSpecificOutput, undefined,
+      'tier-1 only fires in high-stakes domains');
+  });
+
+  it('does NOT fire when user_info_class is yes_people (supersedes "no")', () => {
+    const { out } = runPromptCapture('any prompt', {
+      turn_count: 14,
+      user_info_class: 'yes_people',
+      domain_context: ['legal'],
+    });
+    assert.equal(out.hookSpecificOutput, undefined,
+      'tier-1 only fires when user signals isolation');
+  });
+
+  it('does NOT fire when domain_context is empty', () => {
+    const { out } = runPromptCapture('any prompt', {
+      turn_count: 14,
+      user_info_class: 'no',
+      domain_context: [],
+    });
+    assert.equal(out.hookSpecificOutput, undefined);
+  });
+
+  it('fires for parenting domain (also high-stakes)', () => {
+    const { out } = runPromptCapture('any prompt', {
+      turn_count: 14,
+      user_info_class: 'no',
+      domain_context: ['parenting'],
+    });
+    assert.ok(out.hookSpecificOutput, 'tier-1 fires for parenting too');
+    assert.match(out.hookSpecificOutput.additionalContext, /parenting/);
+  });
+});

plugins/ai-psychosis/tests/validation-seeking.test.mjs

@@ -0,0 +1,205 @@
+// validation-seeking.test.mjs — verifies v1.2 validation-seeking detector.
+//
+// Distinct from existing val_flags ("right?" tic). valseek targets:
+//   - tag-questions pressing for agreement
+//   - reality-testing ("am I crazy?", "is it normal?")
+//   - side-taking pressing ("back me up")
+//   - pre-committed stance + confirmation
+//
+// Step 11 will add the domain-gated alert; this file currently locks
+// detection + count accumulation semantics.
+
+import { describe, it, afterEach } from 'node:test';
+import assert from 'node:assert/strict';
+import { runHook, setupTestDir, cleanupTestDir, createStateFile, readState } from './test-helper.mjs';
+
+let dir;
+afterEach(() => { if (dir) cleanupTestDir(dir); });
+
+function freshState() {
+  return {
+    start_epoch: Math.floor(Date.now() / 1000) - 60,
+    start_iso: '2026-05-01T10:00:00Z',
+    tool_count: 0, edit_count: 0,
+    last_event_epoch: 0, burst_count: 0,
+    dep_flags: 0, esc_flags: 0, fatigue_flags: 0, val_flags: 0,
+    pushback_count: 0, domain_context: null,
+    user_info_class: null,
+    user_info_flags: { yes_people: 0, yes_digital: 0, no: 0 },
+    turn_count: 0,
+    valseek_count: 0, valseek_flag: 0,
+    last_warning_epoch: 0,
+  };
+}
+
+function runPrompt(prompt, stateOverrides = {}) {
+  dir = setupTestDir();
+  createStateFile(dir, 'v1', { ...freshState(), ...stateOverrides });
+  runHook('prompt-analyzer.mjs', { session_id: 'v1', prompt }, dir);
+  return readState(dir, 'v1');
+}
+
+// --- Pattern detection ---
+
+describe('valseek: tag-questions pressing for agreement', () => {
+  it('matches "isn\'t it?"', () => {
+    const s = runPrompt("she's wrong, isn't she?");
+    assert.equal(s.valseek_count, 1);
+    assert.equal(s.valseek_flag, 1);
+  });
+
+  it('matches "don\'t you think?"', () => {
+    const s = runPrompt("this approach is better, don't you think?");
+    assert.equal(s.valseek_count, 1);
+  });
+
+  it('matches "right, though?"', () => {
+    const s = runPrompt("I should leave him, right, though?");
+    assert.equal(s.valseek_count, 1);
+  });
+});
+
+describe('valseek: reality-testing patterns', () => {
+  it('matches "am I crazy"', () => {
+    const s = runPrompt("am I crazy for thinking this?");
+    assert.equal(s.valseek_count, 1);
+  });
+
+  it('matches "tell me I\'m not crazy"', () => {
+    const s = runPrompt("tell me I'm not crazy for feeling betrayed");
+    assert.equal(s.valseek_count, 1);
+  });
+
+  it('matches "is it normal to"', () => {
+    const s = runPrompt("is it normal to feel this way after years?");
+    assert.equal(s.valseek_count, 1);
+  });
+});
+
+describe('valseek: side-taking pressing', () => {
+  it('matches "you agree, right?"', () => {
+    const s = runPrompt("you agree, right?");
+    assert.equal(s.valseek_count, 1);
+  });
+
+  it('matches "back me up here"', () => {
+    const s = runPrompt("she lied to me — back me up here");
+    assert.equal(s.valseek_count, 1);
+  });
+});
+
+describe('valseek: pre-committed stance', () => {
+  it('matches "I already decided ... right"', () => {
+    const s = runPrompt("I already decided to quit, that's right?");
+    assert.equal(s.valseek_count, 1);
+  });
+
+  it('matches "I know I\'m right about this"', () => {
+    const s = runPrompt("I know I'm right about this whole thing");
+    assert.equal(s.valseek_count, 1);
+  });
+});
+
+// --- Negative cases ---
+
+describe('valseek: false-positive guards', () => {
+  it('does NOT match casual "right?" tic alone', () => {
+    const s = runPrompt('the function returns true, right?');
+    // Casual right? hits the existing val_flags pattern but NOT valseek.
+    assert.equal(s.valseek_count, 0);
+  });
+
+  it('does NOT match technical question without pressing pattern', () => {
+    const s = runPrompt('what does this regex do?');
+    assert.equal(s.valseek_count, 0);
+  });
+});
+
+// --- Accumulation ---
+
+describe('valseek: count accumulation', () => {
+  it('accumulates across multiple prompts', () => {
+    dir = setupTestDir();
+    createStateFile(dir, 'v-acc', freshState());
+    const prompts = [
+      "am I crazy for staying?",
+      "you agree, right?",
+      "isn't she wrong?",
+      "I know I'm right on this",
+      "tell me I'm not crazy",
+    ];
+    for (const p of prompts) {
+      runHook('prompt-analyzer.mjs', { session_id: 'v-acc', prompt: p }, dir);
+    }
+    const s = readState(dir, 'v-acc');
+    assert.equal(s.valseek_count, 5);
+    assert.equal(s.valseek_flag, 1);
+  });
+
+  it('valseek_flag is sticky once set, even if later prompt has no hit', () => {
+    dir = setupTestDir();
+    createStateFile(dir, 'v-sticky', freshState());
+    runHook('prompt-analyzer.mjs', { session_id: 'v-sticky', prompt: 'am I crazy?' }, dir);
+    runHook('prompt-analyzer.mjs', { session_id: 'v-sticky', prompt: 'refactor this code' }, dir);
+    const s = readState(dir, 'v-sticky');
+    assert.equal(s.valseek_count, 1, 'count is unchanged by later non-matching prompt');
+    assert.equal(s.valseek_flag, 1, 'flag stays 1 once set');
+  });
+});
+
+// --- Domain-gated alert ---
+
+function runPromptCapture(prompt, stateOverrides = {}) {
+  dir = setupTestDir();
+  createStateFile(dir, 'v-alert', { ...freshState(), ...stateOverrides });
+  const out = runHook('prompt-analyzer.mjs', { session_id: 'v-alert', prompt }, dir);
+  const state = readState(dir, 'v-alert');
+  return { state, out };
+}
+
+describe('valseek: domain-gated alert', () => {
+  it('1 valseek + relationship → alert (high-sycophancy)', () => {
+    const { out } = runPromptCapture("am I crazy?", { domain_context: ['relationship'] });
+    assert.match(out.hookSpecificOutput.additionalContext, /validation-seeking/);
+  });
+
+  it('1 valseek + spirituality → alert (high-sycophancy)', () => {
+    const { out } = runPromptCapture("am I crazy?", { domain_context: ['spirituality'] });
+    assert.match(out.hookSpecificOutput.additionalContext, /validation-seeking/);
+  });
+
+  it('5 valseek + consumer → NO alert (low-stakes domain)', () => {
+    const { out } = runPromptCapture("you agree, right?", {
+      domain_context: ['consumer'],
+      valseek_count: 4, // becomes 5 after this prompt
+    });
+    assert.equal(out.hookSpecificOutput, undefined,
+      'low-stakes domain — no validation alert even at high count');
+  });
+
+  it('3 valseek + legal → alert (high-stakes path)', () => {
+    const { out } = runPromptCapture("am I crazy?", {
+      domain_context: ['legal'],
+      valseek_count: 2, // becomes 3
+    });
+    assert.match(out.hookSpecificOutput.additionalContext, /high-stakes/);
+  });
+
+  it('1 valseek + legal → NO alert (sub-threshold even with stakes weight)', () => {
+    // Step 13: stakes weight 1.5 lowers high-stakes threshold from 3 to 2.0.
+    // valseek_count=1 still under threshold.
+    const { out } = runPromptCapture("am I crazy?", {
+      domain_context: ['legal'],
+      valseek_count: 0, // becomes 1
+    });
+    assert.equal(out.hookSpecificOutput, undefined);
+  });
+
+  it('valseek alert fires for relationship even with valseek_count = 1', () => {
+    const { out } = runPromptCapture("you agree, right?", {
+      domain_context: ['relationship'],
+      valseek_count: 0, // becomes 1
+    });
+    assert.match(out.hookSpecificOutput.additionalContext, /validation-seeking/);
+  });
+});

plugins/claude-design/.claude-plugin/plugin.json

@@ -0,0 +1,18 @@
+{
+  "name": "claude-design",
+  "version": "0.1.0",
+  "description": "End-to-end facilitator for prompting Claude Design (claude.ai/design) — idea to copy-paste-ready prompt with iteration coaching, citing Anthropic primary sources.",
+  "author": {
+    "name": "Kjell Tore Guttormsen"
+  },
+  "auto_discover": true,
+  "license": "MIT",
+  "repository": "https://git.fromaitochitta.com/open/ktg-plugin-marketplace",
+  "keywords": [
+    "claude-design",
+    "claude-ai",
+    "prompt-engineering",
+    "artifacts",
+    "design"
+  ]
+}

plugins/claude-design/.coverage.md

@@ -0,0 +1,90 @@
+# claude-design coverage manifest
+
+**Captured-on date:** 2026-05-17 | **Source:** `https://anthropic.com/news/claude-design-anthropic-labs` (intent-preset enumeration)
+
+This file is the canonical input for SC2 verification (`tests/test-sc2-artifact-coverage.sh`) and the SC3 Authoritative-claims registry (`tests/test-sc3-citations.sh`). Both tests read this file directly — keep it in sync with the references tree.
+
+Anthropic's launch enumeration names eight intent presets; this plugin ships one reference file per preset with explicit evidence-grade labelling. The evidence-grade levels are:
+
+- **Anthropic-documented + community-validated** — Anthropic publishes verbatim prompt patterns and community practitioners have independently validated them
+- **Community-only** — Anthropic names the preset but publishes no per-preset prompt patterns; the patterns come from community practitioners with attribution
+- **Experimental** — neither Anthropic nor community practitioners have published verifiable prompt patterns; the preset is engaged speculatively
+
+The evidence-grade labels are load-bearing for SC2 and SC3. Per-preset reference files restate the grade inline on line 4.
+
+---
+
+## Intent preset coverage
+
+| Preset | Reference file | Evidence grade | Anthropic anchor URL |
+| --- | --- | --- | --- |
+| designs | skills/claude-design-facilitator/references/presets/designs.md | Evidence grade: Anthropic-documented + community-validated | https://anthropic.com/news/claude-design-anthropic-labs |
+| prototypes | skills/claude-design-facilitator/references/presets/prototypes.md | Evidence grade: Anthropic-documented + community-validated | https://claude.com/resources/tutorials/using-claude-design-for-prototypes-and-ux |
+| slides | skills/claude-design-facilitator/references/presets/slides.md | Evidence grade: Anthropic-documented + community-validated | https://claude.com/resources/tutorials/using-claude-design-for-presentations-and-slide-decks |
+| one-pagers | skills/claude-design-facilitator/references/presets/one-pagers.md | Evidence grade: Community-only | https://anthropic.com/news/claude-design-anthropic-labs |
+| wireframes-mockups | skills/claude-design-facilitator/references/presets/wireframes-mockups.md | Evidence grade: Community-only | https://anthropic.com/news/claude-design-anthropic-labs |
+| pitch-decks | skills/claude-design-facilitator/references/presets/pitch-decks.md | Evidence grade: Community-only | https://anthropic.com/news/claude-design-anthropic-labs |
+| marketing-collateral | skills/claude-design-facilitator/references/presets/marketing-collateral.md | Evidence grade: Community-only | https://anthropic.com/news/claude-design-anthropic-labs |
+| frontier-design | skills/claude-design-facilitator/references/presets/frontier-design.md | Evidence grade: Experimental — no validated practitioner pattern | https://anthropic.com/news/claude-design-anthropic-labs |
+
+The preset names in column 1 (`designs`, `prototypes`, `slides`, `one-pagers`, `wireframes-mockups`, `pitch-decks`, `marketing-collateral`, `frontier-design`) are the canonical names used by `tests/test-sc2-artifact-coverage.sh`. The test extracts column 1 via awk and runs grep against the plugin's content tree to verify each preset has at least one supporting file.
+
+---
+
+## Authoritative-claims files
+
+The following files contain authoritative claims (Anthropic-published material, primary sources, or community-converged patterns with attribution). Each must carry at least one Anthropic-domain URL citation. `tests/test-sc3-citations.sh` reads this bullet list, parses paths via awk on `^- `, then runs the citation grep against each file.
+
+- skills/claude-design-facilitator/references/00-what-claude-design-is-and-isnt.md
+- skills/claude-design-facilitator/references/01-prompt-fundamentals.md
+- skills/claude-design-facilitator/references/02-design-md.md
+- skills/claude-design-facilitator/references/03-iteration-and-session.md
+- skills/claude-design-facilitator/references/04-handoff-and-scope.md
+- skills/claude-design-facilitator/references/presets/designs.md
+- skills/claude-design-facilitator/references/presets/prototypes.md
+- skills/claude-design-facilitator/references/presets/slides.md
+- skills/claude-design-facilitator/references/presets/one-pagers.md
+- skills/claude-design-facilitator/references/presets/wireframes-mockups.md
+- skills/claude-design-facilitator/references/presets/pitch-decks.md
+- skills/claude-design-facilitator/references/presets/marketing-collateral.md
+- skills/claude-design-facilitator/references/presets/frontier-design.md
+
+Total: 13 authoritative-claims files (5 foundation references + 8 per-preset references).
+
+The bullet-list format is load-bearing — `tests/test-sc3-citations.sh` parses lines starting with `- ` (dash + space). Do not switch to a table or numbered list without updating the test.
+
+---
+
+## Re-research triggers
+
+This manifest refreshes when any of these events occurs:
+
+- **Anthropic publishes per-preset guidance for a Community-only preset** (one-pagers, wireframes-mockups, pitch-decks, marketing-collateral) — upgrade the affected row's evidence grade and add the new Anthropic anchor URL
+- **Anthropic publishes per-preset guidance for the Experimental preset** (frontier-design) — upgrade to Community-only or Anthropic-documented depending on coverage depth
+- **A new intent preset is added to Anthropic's launch-post enumeration** (`https://anthropic.com/news/claude-design-anthropic-labs`) — add a new row, write a new preset reference file
+- **An existing intent preset is removed from the enumeration** — remove the row, deprecate the reference file in `CHANGELOG.md`
+- **A first verified frontier-design practitioner artifact ships publicly** with prompt + output + reproduction steps — upgrade the frontier-design row from Experimental to Community-only, update `presets/frontier-design.md`
+- **Anthropic support article URL slugs change while keeping numeric IDs stable** — re-pin URLs in column 4 (Anthropic anchor URL); the numeric IDs in `support.claude.com/en/articles/<numeric-id>-<slug>` are the stable anchor
+- **Labs → GA URL rename for `claude.ai/design`** — re-pin the launch-post URL once the `-anthropic-labs` slug is dropped (note: the launch URL `https://anthropic.com/news/claude-design-anthropic-labs` may or may not 301-redirect after the rename)
+
+When any trigger fires, run `bash plugins/claude-design/verify.sh --strict` after the manifest update to confirm SC2 and SC3 still pass.
+
+---
+
+## Related sources (for context, not for SC checks)
+
+Anthropic primary sources that ground this manifest but are not themselves authoritative-claims files (because they are external URLs, not plugin files):
+
+- `https://anthropic.com/news/claude-design-anthropic-labs` — preset enumeration
+- `https://support.claude.com/en/articles/14604416-get-started-with-claude-design` — GLCA framework
+- `https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design` — design-system setup
+- `https://support.claude.com/en/articles/13521390-use-claude-for-powerpoint` — PowerPoint-mode conventions
+- `https://claude.com/resources/tutorials/using-claude-design-for-prototypes-and-ux` — prototypes tutorial
+- `https://claude.com/resources/tutorials/using-claude-design-for-presentations-and-slide-decks` — slides tutorial
+- `https://anthropic.com/engineering/harness-design-long-running-apps` — design grading framing
+- `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` — Design-Thinking Framework, AI-slop avoid-list
+- `https://claude.com/blog/improving-frontend-design-through-skills` — default-avoidance blog post
+- `https://claude.com/plugins/design` — Anthropic's official knowledge-work-plugins/design plugin (downstream tool)
+- `https://github.com/anthropics/knowledge-work-plugins` — source for Anthropic's downstream plugin
+
+Anthropic URL canonicalisation: every `support.claude.com` reference uses the `https://support.claude.com/en/articles/<numeric-id>-<slug>` form. Numeric IDs are stable across slug rewrites; slug-only URLs are not.

plugins/claude-design/CHANGELOG.md

@@ -0,0 +1,37 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] — 2026-05-17
+
+### Added
+- `claude-design-facilitator` skill with eight-phase facilitation flow (disambiguate → intent preset → audience + destination → DESIGN.md anchor → five-layer prompt draft → copy-paste delivery → iteration coaching → ship-readiness handoff) and 12 natural-language trigger phrases registered in `.triggers.txt`.
+- Five foundation references under `skills/claude-design-facilitator/references/`: `00-what-claude-design-is-and-isnt.md` (surface disambiguation), `01-prompt-fundamentals.md` (five-layer prompt stack: GLCA + start-simple + concrete-alternative-spec + propose-options + AI-slop avoid-list + four design dimensions + four grading criteria), `02-design-md.md` (DESIGN.md 9-section canonical structure + brand-to-DESIGN.md extractor), `03-iteration-and-session.md` (Tweak / Comment / Chat cascade, session economics, recovery prompt library), `04-handoff-and-scope.md` (one-way Design → Code handoff + scope fence vs Anthropic's `knowledge-work-plugins/design`).
+- Eight per-preset references under `skills/claude-design-facilitator/references/presets/` with evidence-grade labels: `designs.md`, `prototypes.md`, `slides.md` (Anthropic-documented + community-validated); `one-pagers.md`, `wireframes-mockups.md`, `pitch-decks.md`, `marketing-collateral.md` (Community-only); `frontier-design.md` (Experimental — no validated practitioner pattern as of 2026-05-16).
+- `.coverage.md` at plugin root — preset enumeration table with evidence-grade labels (8 rows) + `Authoritative-claims files` bullet-list registry (13 paths). Canonical input for SC2 and SC3 verification.
+- Five verification scripts under `tests/`: `validate-plugin.sh` (structural integrity + forbidden-command-name scope fence + operator-private-context grep + Norwegian-leakage advisory), `test-skill-triggers.sh` (description quality + trigger phrase coverage), `test-sc2-artifact-coverage.sh` (per-preset coverage from `.coverage.md`), `test-sc3-citations.sh` (Anthropic-domain citation discipline), `test-sc1-dogfood-log.sh` (operator dogfood log format-check in `REMEMBER.md`).
+- `verify.sh` top-level roll-up with `--strict` (SC1 missing-block becomes FAIL) and `--quick` (skip skill-triggers test) flags.
+- `LICENSE` (MIT) and `GOVERNANCE.md` (marketplace fork-and-own blurb).
+- Marketplace registration in root `.claude-plugin/marketplace.json`.
+
+### Documentation
+- Plugin `README.md` rewritten from scaffold placeholder to full v0.1 surface description with `Scope and complementarity` section (placed before installation per brief), `What this plugin is NOT` (Non-Goals), eight-phase facilitation flow table, skill surface table, reference content map, per-preset coverage table, verification section, AI-generated disclosure, fork-and-own MIT licensing.
+- Plugin `CLAUDE.md` translated to English (operator override of marketplace's Norwegian-dialogue default per v0.1 brief constraint); added `Scope fence` section explicitly forbidding command-name collisions with Anthropic's `knowledge-work-plugins/design` (`/critique`, `/accessibility`, `/ux-copy`, `/research-synthesis`, `/design-system`, `/handoff`); `Authoring rules` section codifies English-everywhere, no operator-private context, evidence-grade label discipline, URL canonicalisation on `support.claude.com/en/articles/<numeric-id>-<slug>`; `Communication patterns` block preserved verbatim.
+- Root marketplace `README.md` updated with `### [Claude Design](plugins/claude-design/) \`v0.1.0\`` entry under the `## Plugins` section, positioned after the Human-Friendly Style entry per existing convention. Entry documents the complementary lifecycle coverage vs `knowledge-work-plugins/design`.
+
+### Notes
+- **Scope:** claude-design facilitates the pre-design and during-design lifecycle for `claude.ai/design` (Anthropic Labs research preview, Opus 4.7 pinned, eight intent presets). For post-design — critique, accessibility audit, UX copy review, design-system audit, engineering handoff — install Anthropic's official plugin via `claude plugins add knowledge-work-plugins/design`. Zero command overlap, complementary by design.
+- **No browser automation.** This plugin produces prompts; the artifact gets built inside `claude.ai/design`. The operator copies and pastes manually.
+- **No artifact code generation.** This plugin is a prompt-builder, not an artifact generator. Claude Design is the generator.
+- **No artifact storage or versioning.** Claude Design has no version-tree primitive and this plugin does not invent one. The verbal save-pattern documented in `references/03-iteration-and-session.md` is the closest substitute.
+- **English everywhere in shipped content.** Operator override of the marketplace's default Norwegian-dialogue convention. `tests/validate-plugin.sh` assertion (j) emits WARN on Norwegian diacritics in shipped content; review case-by-case.
+- **Evidence-grade discipline.** Every per-preset reference file carries an inline `Evidence grade:` label on line 4 with one of three values: `Anthropic-documented + community-validated`, `Community-only`, `Experimental`. `.coverage.md` is the canonical registry.
+- **Re-research triggers** documented in `.coverage.md` — fire on Anthropic publishing per-preset guidance for Community-only presets, on new intent presets added to the launch enumeration, on the first verified `frontier-design` practitioner artifact shipping publicly, on Labs → GA URL rename for `claude.ai/design`, on Anthropic's `knowledge-work-plugins/design` adding or removing slash-commands.
+
+## [0.1.0-pre] — 2026-05-15
+
+### Added
+- Initial scaffold (README, CLAUDE.md, ROADMAP, TODO, plugin.json placeholder).

plugins/claude-design/CLAUDE.md

@@ -0,0 +1,88 @@
+# claude-design
+
+## Context
+
+This plugin is an expert on **Claude Design** (`claude.ai/design`) — Anthropic's Labs research preview for generating interactive design artifacts from a prompt. It walks the operator through the full lifecycle: idea → intent-preset selection → audience and destination → DESIGN.md anchor → five-layer prompt drafting → copy-paste delivery → iteration coaching → ship-readiness handoff. It does not generate artifact code itself and it does not drive the browser; it produces the prompt that the operator pastes into Claude Design.
+
+## Status
+
+`v0.1.0`. Surface:
+
+- One skill: `claude-design-facilitator` (auto-fire + explicit `/claude-design-facilitator` slash command)
+- Five foundation references under `skills/claude-design-facilitator/references/`
+- Eight per-preset references under `skills/claude-design-facilitator/references/presets/`
+- Five test scripts under `tests/` plus a `verify.sh` roll-up
+- A `.coverage.md` preset manifest at the plugin root (canonical input for SC2 and the SC3 Authoritative-claims registry)
+- `LICENSE` (MIT), `GOVERNANCE.md` (marketplace fork-and-own blurb), `README.md`, `CHANGELOG.md`
+
+No commands, no agents, no hooks, no MCP servers at v0.1. The single skill is the entire user-facing surface.
+
+## Marketplace context
+
+This plugin lives inside `ktg-plugin-marketplace`. No separate git repository, no separate Forgejo remote. All commits go to the marketplace repository at `https://git.fromaitochitta.com/open/ktg-plugin-marketplace`.
+
+Marketplace conventions inherited from the root `CLAUDE.md`:
+
+- Conventional Commits — `type(scope): description`; scope is `claude-design`
+- Hooks in Node.js (`.mjs`), never bash (this plugin ships no hooks at v0.1)
+- Zero npm dependencies in hooks and scripts
+- Docs-triple updated in the same commit on every feature change: plugin `README.md` + plugin `CLAUDE.md` + root `README.md`
+
+## Architecture (v0.1)
+
+- **`skills/claude-design-facilitator/SKILL.md`** is the auto-fire entry point AND the explicit `/claude-design-facilitator` invocation surface. The skill body documents the eight-phase facilitation flow.
+- **`skills/claude-design-facilitator/.triggers.txt`** lists the natural-language phrases the skill auto-fires on. `tests/test-skill-triggers.sh` validates every phrase appears in the SKILL.md description.
+- **`skills/claude-design-facilitator/references/`** is the knowledge base. Five foundation references (00–04) plus eight per-preset references under `references/presets/`. Every authoritative claim cites an Anthropic primary source inline.
+- **`.coverage.md`** at the plugin root is the SC2 manifest (preset enumeration with evidence-grade labels) and the SC3 Authoritative-claims registry (bullet list of files that must carry Anthropic-domain citations).
+- **`tests/`** + **`verify.sh`** enforce the brief Success Criteria: SC1 dogfood-log format, SC2 per-preset coverage, SC3 citation discipline, plus skill description quality and plugin structural integrity.
+
+The skill body never offers to generate artifact code, automate the browser, or store artifact history (per [Non-Goals in README](README.md)). It produces prompts.
+
+## Scope fence
+
+This plugin covers **pre-design and during-design** for `claude.ai/design`: idea → prompt → preview → iterate → ship-readiness.
+
+**Post-design** — critique, accessibility audit, UX copy review, research synthesis, design-system audit, engineering handoff — is out of scope and lives in Anthropic's official `knowledge-work-plugins/design` (`https://claude.com/plugins/design`). This plugin must never duplicate the commands `/critique`, `/accessibility`, `/ux-copy`, `/research-synthesis`, `/design-system`, `/handoff` — with or without a `claude-design:` namespace prefix. `tests/validate-plugin.sh` assertion (h) enforces this scope fence mechanically.
+
+The lifecycle-stage coverage map and the operational handoff between the two plugins are documented in `skills/claude-design-facilitator/references/04-handoff-and-scope.md`.
+
+## Authoring rules
+
+Every contribution to this plugin must respect these rules:
+
+- **Language: English everywhere.** Plugin file content — `README.md`, `CLAUDE.md` (this file), `CHANGELOG.md`, `SKILL.md`, all `references/*.md`, all `tests/*.sh` output messages, every code comment — is English. This is the operator override of the marketplace's default Norwegian-dialogue policy; documented in the v0.1 brief. The `tests/validate-plugin.sh` assertion (j) emits a WARN on Norwegian diacritics in shipped content; review case-by-case (citation slugs occasionally legitimately carry diacritics, but the default is zero hits).
+- **No operator-private context in shipped content.** No personal-name or organization-affiliation tokens, no copy-paste from local session-state and handoff files. `tests/validate-plugin.sh` assertion (i) enforces this with a recursive grep on the specific patterns it bans; the grep excludes the local files themselves.
+- **Evidence-grade label discipline.** Every per-preset reference file carries an inline `Evidence grade:` label on line 4. The three grades are `Anthropic-documented + community-validated`, `Community-only`, and `Experimental`. `.coverage.md` is the canonical registry. SC2 and SC3 read from `.coverage.md` directly — keep it in sync.
+- **URL canonicalisation.** All `support.claude.com` references use the form `https://support.claude.com/en/articles/<numeric-id>-<slug>`. Numeric IDs are stable across slug rewrites; slug-only URLs are not. `https://anthropic.com/news/...` and `https://claude.com/blog/...` follow whatever slug Anthropic publishes.
+- **No NIH of Anthropic surfaces.** The plugin recommends Anthropic's `knowledge-work-plugins/design` as the downstream tool; it does not duplicate that plugin's functionality.
+
+## Workflow
+
+The Voyage pipeline produces v0.1 and every subsequent feature change:
+
+1. **Brief** closes scope and scope boundaries
+2. **Research** gathers external sources — Anthropic primary material (news posts, support articles, blog posts, open-source skills, tutorials, plugins), plus community practitioners with attribution
+3. **Plan** specifies file-by-file what gets built
+4. **Execute** delivers the code and content
+5. **Review** is the release gate (`/trekreview`)
+
+Voyage policy: Opus across all sub-agents and orchestrator phases (per `feedback_voyage_opus_always`).
+
+For incremental content updates that do not warrant a full Voyage iteration (e.g., refreshing a single per-preset reference when Anthropic publishes new guidance), the docs-triple rule still applies: plugin `README.md` + plugin `CLAUDE.md` (this file) + root `README.md` updated in the same commit as the content change.
+
+## Communication patterns
+
+### Linking to local files
+
+When pointing to local files in responses, always use markdown link syntax with a descriptive name:
+
+- Use `[Human-friendly name](file:///absolute/path)` — never bare `file:///...` URLs or autolinks `<file://...>`.
+- Always use absolute paths. Never `~/` or relative paths.
+- For multiple files, render as a bullet list of named markdown links.
+
+Why: bare `file://` URLs only render the first as clickable across multiple lines. Named markdown links make each entry independently clickable and look cleaner.
+
+Example:
+
+- [Brief](file:///Users/ktg/.../brief.html)
+- [Research summary](file:///Users/ktg/.../research/summary.md)

plugins/claude-design/GOVERNANCE.md

@@ -0,0 +1,118 @@
+# Governance
+
+How this marketplace is maintained, what you can expect from upstream, and how it's meant to be used.
+
+## TL;DR
+
+- Solo-maintained, AI-assisted development, MIT licensed.
+- **Fork-and-own is the default model.** Upstream is a starting point, not a vendor.
+- Issues welcome as signals. Pull requests are not accepted — see [Why no PRs](#pull-requests--no).
+- No SLA. Best-effort bug fixes and security advisories. Breaking changes happen and are noted in each plugin's CHANGELOG.
+
+---
+
+## Can I trust this?
+
+Be honest with yourself about what you're adopting:
+
+- **One maintainer.** If I get hit by a bus, the bus wins. The repos stay up under MIT, but no one owes you a fix.
+- **AI-generated code with human review.** Every plugin is built through dialog-driven development with Claude Code. I read, test, and judge the output before it ships, but I'm not auditing every line the way a security firm would. Treat it accordingly.
+- **No commercial interests.** I'm not selling a SaaS, not steering you toward a paid tier, not collecting telemetry. The plugins run locally in your Claude Code installation.
+- **MIT licensed.** Fork it, modify it, ship it under your own name.
+
+If you work somewhere that needs vendor accountability, support contracts, or signed assurances — **this isn't that.** Use it as a reference implementation, fork it into your own organization, and own the result.
+
+---
+
+## How this is meant to be used
+
+### Fork-and-own
+
+The intended workflow:
+
+1. **Fork** the marketplace (or a single plugin) into your own organization or namespace.
+2. **Tailor** it to your context — terminology, integrations, whatever doesn't fit out of the box.
+3. **Maintain it yourself.** Treat your fork as the canonical version for your team.
+4. **Watch upstream selectively.** Cherry-pick changes that help, ignore changes that don't. There's no obligation to stay in sync.
+
+For `claude-design` specifically, the most likely fork is a content adaptation — different intent-preset coverage (e.g., dropping `frontier-design` if your team never uses it), an organization-specific DESIGN.md template, a different evidence-grade discipline, or per-preset prompt patterns tuned to your team's design system. The plugin is a content surface plus a single skill. Forking it is straightforward.
+
+### What to change first when you fork
+
+- **Identity** — rename the plugin, replace authorship, update README.
+- **Reference content** — the `references/` tree reflects what Anthropic published and the community converged on as of 2026-05-17. Adjust to your team's house style and design system.
+- **Frontmatter** — `name` and `description` show up in `/config`. Pick names that won't collide with other forks installed on the same machine.
+
+### Staying current with upstream
+
+If you want to pull in upstream changes later:
+
+- **Cherry-pick, don't merge.** Each plugin moves independently.
+- **Read the CHANGELOG first.**
+- **Keep your customizations distinct.** A renamed skill (`my-org-design-facilitator`) merges more cleanly than edits to `claude-design-facilitator`.
+
+---
+
+## What upstream provides
+
+| | What I do | What I don't |
+|---|---|---|
+| **Bug fixes** | Best-effort when I notice or get a clear report | No SLA, no triage commitment |
+| **Security issues** | Investigate within reasonable time, document in CHANGELOG | No CVE process, no embargo coordination |
+| **New features** | When they fit my own usage | Not on request |
+| **Breaking changes** | Documented in CHANGELOG | They happen — version pin if you need stability |
+| **Compatibility** | Tracked against current Claude Code releases | No long-term support branches |
+
+If any of this is a dealbreaker — fork now, version-pin, and stop reading upstream.
+
+---
+
+## How to contribute
+
+### Issues — yes, please
+
+Issues are the most valuable thing you can send me:
+
+- **Bug reports** with reproduction steps. Even a screenshot helps.
+- **Use-case feedback.** "I tried to use this in my organization and X didn't fit" is genuinely useful, even if I can't fix it for you.
+- **Content suggestions.** If a reference file in `claude-design` produces guidance that doesn't match what you observe in `claude.ai/design` today, tell me what you saw. Concrete examples beat abstract complaints.
+
+### Pull requests — no
+
+This is deliberate, not laziness:
+
+- **Solo review is a bottleneck.** Honest PR review takes me longer than rewriting from scratch. The math doesn't work.
+- **Forks are where the value is.** The fork-and-own model means upstream consolidation isn't the point. Your organization's adaptations belong in your fork, not mine.
+- **AI-generated code complicates provenance.** Every line here is produced through dialog with Claude Code, with me as the judge. Mixing in PRs from contributors with different processes and licensing assumptions creates a mess I'd rather not untangle.
+
+If you've built something useful on top of a fork, **publish it under your own name and link back.** I'll happily list notable forks here once they exist.
+
+### Notable forks
+
+*(To be populated as forks emerge. If you've forked this plugin for production use, open an issue and I'll add a link.)*
+
+---
+
+## Relationship between plugins
+
+These plugins are **independent**. Install one without the others, fork one without the others. They share conventions (slash command naming, hook patterns, AI-generated disclosure, and the shared `human-friendly-style` output style) but no runtime dependencies.
+
+`claude-design` is a content surface with a single skill — it works without any other plugin installed. It recommends Anthropic's official `knowledge-work-plugins/design` as the downstream tool for post-design critique, accessibility audit, and engineering handoff, but does not depend on it being present.
+
+The marketplace is a **catalog**, not a suite. Don't fork the whole repo unless you actually want to maintain everything.
+
+---
+
+## Versioning and stability
+
+- **Semantic versioning per plugin.** Each plugin has its own `CHANGELOG.md` and version number.
+- **Breaking changes happen.** I bump the major version when they do, but I don't run an LTS branch.
+- **Pin your version.** If stability matters more than features, install a specific version and stay there until you choose to upgrade.
+
+For `claude-design` specifically: changes to skill trigger behavior or per-preset reference content schema are minor or major bumps. Pure documentation or per-preset content refresh from Anthropic source updates are patch. The skill surface itself is meant to be stable across patch releases.
+
+---
+
+## License
+
+MIT for all plugins in this marketplace. See [LICENSE](LICENSE) in this plugin and each other plugin's `LICENSE` file.

plugins/claude-design/README.md

@@ -0,0 +1,298 @@
+# Claude Design Facilitator
+
+> End-to-end facilitator for prompting Claude Design (`claude.ai/design`). Walks the operator from raw idea through intent-preset selection, audience and destination clarification, DESIGN.md anchor, five-layer prompt drafting, copy-paste delivery, iteration coaching, and ship-readiness handoff. Cites Anthropic primary sources inline. Recommends Anthropic's official `knowledge-work-plugins/design` as the downstream post-design tool.
+
+> **Solo-maintained, fork-and-own.** This plugin is a starting point, not a vendor product. Issues are welcome as signals; pull requests are not accepted. See [GOVERNANCE.md](GOVERNANCE.md) for the full model and what upstream provides.
+
+*AI-generated: all content produced by Claude Code through dialog-driven development. [Full disclosure →](../../README.md#ai-generated-code-disclosure)*
+
+![Version](https://img.shields.io/badge/version-0.1.0-blue)
+![Platform](https://img.shields.io/badge/platform-Claude_Code_Plugin-purple)
+![Skill](https://img.shields.io/badge/skills-1-green)
+![References](https://img.shields.io/badge/references-13-green)
+![Hooks](https://img.shields.io/badge/hooks-0-lightgrey)
+![Commands](https://img.shields.io/badge/commands-0-lightgrey)
+![License](https://img.shields.io/badge/license-MIT-lightgrey)
+
+A Claude Code plugin that ships one skill (`claude-design-facilitator`) plus a reference tree for prompting Anthropic's `claude.ai/design` workspace. The skill auto-fires on natural-language triggers, walks the operator through an eight-phase facilitation flow, and produces a copy-paste-ready prompt grounded in Anthropic's verbatim Goal / Layout / Content / Audience framework and the four published per-preset prompt patterns. Output is the prompt — the artifact gets built in Claude Design.
+
+---
+
+## Why this exists
+
+Claude Design has a strong gravitational pull toward convergent middle-ground output. A one-line prompt like *"make me a slide deck for Q1 results"* reliably produces what Anthropic's own cookbook for [prompting frontend aesthetics](https://platform.claude.com/cookbook/coding-prompting-for-frontend-aesthetics) names as the failure mode: Inter or Roboto typography, white-to-purple gradients, evenly-spaced cards, cramped layouts that read as AI-generated. The convergence is not random — it is what the model defaults to when prompts are underspecified.
+
+The fix is in the prompt itself, not in the artifact. Anthropic publishes a five-layer prompt scaffold across three primary sources — the Goal / Layout / Content / Audience framework in the [Claude Design launch post](https://anthropic.com/news/claude-design-anthropic-labs) and [Get started article](https://support.claude.com/en/articles/14604416-get-started-with-claude-design), the DESIGN.md anchor in the [design system article](https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design), and the AI-slop avoid-list plus cultural-reference anchoring in the [aesthetics cookbook](https://platform.claude.com/cookbook/coding-prompting-for-frontend-aesthetics). Assembling a prompt that actually uses all five layers, with the right per-preset pattern, in the right order, takes deliberate scaffolding most operators do not do unprompted.
+
+This plugin does the scaffolding interactively. The `claude-design-facilitator` skill walks the operator through eight phases, surfaces the questions that produce a workable Goal / Layout / Content / Audience answer, anchors on DESIGN.md if one exists or extracts one if not, composes the five layers in the right order, and outputs a copy-paste prompt the operator pastes into `claude.ai/design`. The artifact gets built in Claude Design; this plugin produces the prompt.
+
+The output is honest about what it is. Every authoritative claim cites an Anthropic primary source inline. Community patterns are labelled and attributed. The `frontier-design` preset is flagged Experimental rather than dressed up as canonical. The plugin recommends Anthropic's official [`knowledge-work-plugins/design`](https://claude.com/plugins/design) for everything that happens after the artifact is generated — there is zero command overlap by design.
+
+---
+
+## Scope and complementarity
+
+This plugin covers the **pre-design and during-design lifecycle** for `claude.ai/design`: idea → intent-preset selection → prompt engineering → copy-paste delivery → iteration coaching → ship-readiness check.
+
+For **post-design** work — critique, accessibility audit, UX copy review, research synthesis, design-system audit, engineering handoff guidance — install Anthropic's official plugin:
+
+```
+claude plugins add knowledge-work-plugins/design
+```
+
+Anthropic's plugin operates on existing artifacts (Figma URLs, screenshots, copy snippets) and ships six slash-commands: `/critique`, `/accessibility`, `/ux-copy`, `/research-synthesis`, `/design-system`, `/handoff`. There is zero command overlap with this plugin and complementary lifecycle coverage — the two plugins are designed to be installed together. See [skills/claude-design-facilitator/references/04-handoff-and-scope.md](skills/claude-design-facilitator/references/04-handoff-and-scope.md) for the full coverage map.
+
+---
+
+## What this plugin is NOT
+
+By design, this plugin does not:
+
+- **Drive the browser.** No automation of `claude.ai/design` itself; you copy and paste the prompts the skill produces.
+- **Generate the artifact code.** Claude Design is the artifact generator. This plugin produces prompts that go into Claude Design.
+- **Store artifact history or version artifacts.** Claude Design has no version-tree primitive and this plugin does not invent one.
+- **Cover adjacent Anthropic surfaces.** Classic Artifacts at `claude.ai`, Live Artifacts in Claude Cowork, custom visuals embedded in a chat reply are out of scope — see [skills/claude-design-facilitator/references/00-what-claude-design-is-and-isnt.md](skills/claude-design-facilitator/references/00-what-claude-design-is-and-isnt.md) for the disambiguation reference.
+- **Duplicate Anthropic's `knowledge-work-plugins/design` plugin.** No `/critique`, no `/accessibility`, no `/ux-copy`, no `/research-synthesis`, no `/design-system`, no `/handoff`. The post-design lane belongs to Anthropic's plugin.
+
+`tests/validate-plugin.sh` enforces the forbidden-command-name list mechanically.
+
+---
+
+## Installation
+
+Add the marketplace once, then install the plugin:
+
+```bash
+claude plugins marketplace add ktg-plugin-marketplace https://git.fromaitochitta.com/open/ktg-plugin-marketplace
+```
+
+In Claude Code:
+
+```
+/plugin install claude-design@ktg-plugin-marketplace
+```
+
+Or enable directly in `~/.claude/settings.json`:
+
+```json
+{
+  "enabledPlugins": {
+    "claude-design@ktg-plugin-marketplace": true
+  }
+}
+```
+
+The skill auto-discovers; no further configuration needed.
+
+---
+
+## What you can do with it
+
+The skill `claude-design-facilitator` walks the operator through eight phases. The phases are scoping + grounding (1–4), drafting + delivery (5–6), and iteration + ship-readiness (7–8).
+
+| Phase | What happens |
+|-------|--------------|
+| **1. Disambiguate the surface** | Confirm `claude.ai/design` is the intended surface, not classic Artifacts, Live Artifacts, custom chat visuals, or `knowledge-work-plugins/design`. Read [references/00](skills/claude-design-facilitator/references/00-what-claude-design-is-and-isnt.md) when signals are mixed. |
+| **2. Name the intent preset** | Pick one of eight Claude Design presets: `designs`, `prototypes`, `slides`, `one-pagers`, `wireframes-mockups`, `pitch-decks`, `marketing-collateral`, `frontier-design`. The per-preset reference file shapes the prompt pattern. Evidence-grade labels are surfaced. |
+| **3. Audience and destination** | Capture audience (internal team / external stakeholder / investor / customer) and destination (PDF / PPTX / HTML / Canva / Code-handoff / share-link). Flag PPTX-export traps for `pitch-decks` early. |
+| **4. Anchor on DESIGN.md** | Read [references/02](skills/claude-design-facilitator/references/02-design-md.md). If the operator has no DESIGN.md, point at the copy-paste brand-to-DESIGN.md extractor prompt. |
+| **5. Draft the prompt** | Compose layers 1–5 from [references/01](skills/claude-design-facilitator/references/01-prompt-fundamentals.md): Anthropic's verbatim Goal / Layout / Content / Audience framework + start-simple-layer-complexity + concrete-alternative-spec + propose-options-before-building + AI-slop negative constraints + four design dimensions + four grading criteria + the per-preset pattern. |
+| **6. Deliver** | Output a single copy-paste-ready fenced markdown code block. Add a one-line caption and three to five expected follow-up turns. |
+| **7. Iteration coaching** | Read [references/03](skills/claude-design-facilitator/references/03-iteration-and-session.md). Coach which surface to use next — Tweak panel (zero-token, surgical), inline comments (component-scoped), or chat (full regen). Session-break heuristics + recovery prompt library when iteration gets stuck. |
+| **8. Ship-readiness** | Run the export validation checklist. If shipping to engineering, confirm the Design → Code handoff bundle is complete. Recommend installing `knowledge-work-plugins/design` for downstream critique / accessibility / handoff. |
+
+The skill auto-fires on natural-language triggers like *"I want to build a dashboard in Claude Design"*, *"help me prompt claude.ai/design"*, *"iterate on my Claude Design artifact"*. The full trigger list is in [skills/claude-design-facilitator/.triggers.txt](skills/claude-design-facilitator/.triggers.txt) and `tests/test-skill-triggers.sh` validates each phrase appears in the skill description.
+
+Explicit invocation works too: the skill registers as the slash command `/claude-design-facilitator` for when the operator wants to start a clean facilitation session.
+
+---
+
+## Workflow example: from idea to prompt
+
+A realistic session against the `slides` preset — Q1 results deck for an internal engineering all-hands.
+
+**Operator:** *"I want to build a Q1 results slide deck for the engineering team in Claude Design."*
+
+The skill auto-fires (the phrase matches `.triggers.txt`). It walks the eight phases:
+
+**Phase 1 — Disambiguate the surface.** The skill confirms `claude.ai/design` is the intended surface, not classic Artifacts or Live Artifacts. The operator confirms.
+
+**Phase 2 — Name the intent preset.** Slide deck → `slides` preset. The skill notes this is one of three Anthropic-documented presets (evidence-grade label surfaced from `.coverage.md`). It opens [`references/presets/slides.md`](skills/claude-design-facilitator/references/presets/slides.md) and surfaces the five canonical Anthropic patterns (Q1 results, executive roadmap, customer-prep briefing, partner proposal, all-hands announcement). The operator picks pattern 1.
+
+**Phase 3 — Audience and destination.** Internal engineering team; deck stays in HTML preview during the meeting, optional PPTX export to share with adjacent leads afterward. The skill flags the PPTX-export trap from [`references/presets/slides.md`](skills/claude-design-facilitator/references/presets/slides.md) section (e): fonts substitute, master slides drop, charts may flatten to images. If a brand-compliant PPTX template exists, upload it to Claude Design as a project asset before prompting — Claude reads the slide master, layouts, fonts, and colour scheme and respects them ([PowerPoint-mode article](https://support.claude.com/en/articles/13521390-use-claude-for-powerpoint)).
+
+**Phase 4 — Anchor on DESIGN.md.** The operator has no DESIGN.md yet. The skill points at the brand-to-DESIGN.md extractor prompt in [`references/02-design-md.md`](skills/claude-design-facilitator/references/02-design-md.md): paste a brand-guidelines URL or PDF into Claude.ai, get back a DESIGN.md filling the nine canonical sections (typography, colour, spacing, layout primitives, motion, voice, imagery, density, accessibility). The operator runs the extractor against the company's brand site, gets a DESIGN.md, drops it into the Claude Design project assets.
+
+**Phase 5 — Draft the prompt.** The skill composes the five layers from [`references/01-prompt-fundamentals.md`](skills/claude-design-facilitator/references/01-prompt-fundamentals.md): Goal / Layout / Content / Audience (Layer 1) → start-simple-layer-complexity (Layer 2) → concrete-alternative-spec (Layer 3) → AI-slop negative constraints (Layer 4) → per-preset pattern from `presets/slides.md` (Layer 5). The skill produces a single copy-paste fenced block. The operator inspects it, optionally edits the Goal sentence, then proceeds.
+
+**Phase 6 — Deliver.** The skill outputs the prompt block. The structure of a realistic delivery for this scenario looks like:
+
+```
+**Goal:** Communicate Q1 engineering results to the all-hands —
+where we started, what changed, what we shipped, what we learned,
+what's next for Q2. The deck should land as confident but honest:
+real numbers, named risks, no victory-lap framing. Audience is
+~80 engineers across three teams. Density should be high enough
+to skim later, low enough to follow live.
+
+**Layout:** 10–12 slides, slide-by-slide:
+1. Title + Q1 in one sentence
+2. The three things we shipped (one per row, screenshot + metric)
+3. The two things that slipped (named honestly, with the why)
+4. Hiring update (count + retention)
+5. Reliability (incident count, MTTR trend)
+6. Customer signal (NPS + 2 verbatim quotes)
+7. Engineering health (PR throughput, review latency)
+8. The big bet for Q2 (one slide, named)
+9. Risks for Q2 (3 bullets, ranked)
+10. Asks from the all-hands (1–3 specific asks)
+11. Q&A placeholder
+
+**Content:** Use the metrics in DESIGN.md's `tone` section — direct,
+specific, no marketing voice. Numbers are placeholder; I'll edit
+before the meeting.
+
+**Audience:** Internal engineering all-hands, 80 people, ICs through
+EM/Director level. They want to know: did we ship what we said, what
+broke, what's next, can I help.
+
+**Avoid:** Inter or Roboto, white-to-purple gradients, evenly-spaced
+generic card layouts, "exciting Q1!" framing, congratulatory tone,
+stock-photo gradients, generic icon library defaults.
+
+**Anchor:** Match the DESIGN.md uploaded as a project asset. If our
+brand voice reads as understated technical, push the deck that way —
+not the convergent SaaS-marketing deck aesthetic.
+
+**Reference:** Treat this as the Q1 results pattern from
+https://claude.com/resources/tutorials/using-claude-design-for-presentations-and-slide-decks
+(pattern 1), with the Layout above overriding the tutorial's slide count.
+```
+
+That block is what gets pasted into `claude.ai/design`. The skill also surfaces three to five expected follow-up turns (e.g., *"the headline slide is too marketing, push it more technical"*, *"slide 5 reliability — show the MTTR trend as a sparkline, not a bar chart"*) so the operator knows what iteration looks like before starting.
+
+**Phase 7 — Iteration coaching.** Once Claude Design produces the first version, the skill points the operator at the Tweak → Comment → Chat cascade in [`references/03-iteration-and-session.md`](skills/claude-design-facilitator/references/03-iteration-and-session.md): Tweak panel for surgical zero-token edits (spacing, font size, colour), inline comments for component-scoped changes (rewrite slide 5), full chat regeneration as a last resort. Plus the session-break heuristic (after 4 substantive screens, start a fresh session with a verbal save-pattern carrying state forward) and the recovery prompt library when iteration gets stuck.
+
+**Phase 8 — Ship-readiness.** Before the all-hands, the skill runs the export validation checklist for the chosen destination (HTML preview → keep in Claude Design; PPTX → check fonts and master, charts may flatten). If the deck is being handed off to engineering for any reason, it recommends installing [`knowledge-work-plugins/design`](https://claude.com/plugins/design) for `/critique`, `/accessibility`, and `/handoff` — the post-design lane.
+
+The full output of the session is a single fenced markdown block (Phase 6) plus a short follow-up-turns list and an iteration-coaching pointer. That is the entire user-facing deliverable.
+
+---
+
+## Skill surface
+
+| Skill | Triggers | Output |
+|-------|----------|--------|
+| `claude-design-facilitator` | 12 natural-language phrases (full list in `.triggers.txt`); also explicit `/claude-design-facilitator` slash command | A copy-paste-ready Claude Design prompt block composed from the five-layer stack and the per-preset pattern, with follow-up-turn expectations |
+
+No commands, no agents, no hooks, no MCP servers at v0.1. The single skill is the entire user-facing surface.
+
+---
+
+## Reference content map
+
+The plugin ships 13 reference files in `skills/claude-design-facilitator/references/`:
+
+**Foundation references (5):**
+
+- [`00-what-claude-design-is-and-isnt.md`](skills/claude-design-facilitator/references/00-what-claude-design-is-and-isnt.md) — Surface disambiguation against Artifacts, Live Artifacts, custom chat visuals, and Anthropic's `knowledge-work-plugins/design`.
+- [`01-prompt-fundamentals.md`](skills/claude-design-facilitator/references/01-prompt-fundamentals.md) — The five-layer prompt stack: GLCA framework + start-simple-layer-complexity + concrete-alternative-spec + propose-options + AI-slop negative constraints + four design dimensions + four grading criteria. Anchored on four Anthropic primary sources.
+- [`02-design-md.md`](skills/claude-design-facilitator/references/02-design-md.md) — DESIGN.md 9-section canonical structure + brand-to-DESIGN.md extractor prompt + failure modes.
+- [`03-iteration-and-session.md`](skills/claude-design-facilitator/references/03-iteration-and-session.md) — Tweak / Comment / Chat cascade, session economics, 4-screen inflection, recovery prompt library (break-default-aesthetic, fix-the-system, edit-previous-message, 3-failed-comment escalation, model downshift, verbal save-pattern).
+- [`04-handoff-and-scope.md`](skills/claude-design-facilitator/references/04-handoff-and-scope.md) — Design → Code one-way handoff, bundle contents, lifecycle-stage coverage map vs Anthropic's `knowledge-work-plugins/design`, downstream tool recommendation.
+
+**Per-preset references (8):**
+
+- [`presets/designs.md`](skills/claude-design-facilitator/references/presets/designs.md) — Anthropic-documented + community-validated
+- [`presets/prototypes.md`](skills/claude-design-facilitator/references/presets/prototypes.md) — Anthropic-documented + community-validated
+- [`presets/slides.md`](skills/claude-design-facilitator/references/presets/slides.md) — Anthropic-documented + community-validated
+- [`presets/one-pagers.md`](skills/claude-design-facilitator/references/presets/one-pagers.md) — Community-only
+- [`presets/wireframes-mockups.md`](skills/claude-design-facilitator/references/presets/wireframes-mockups.md) — Community-only
+- [`presets/pitch-decks.md`](skills/claude-design-facilitator/references/presets/pitch-decks.md) — Community-only (with explicit PPTX-export caveat)
+- [`presets/marketing-collateral.md`](skills/claude-design-facilitator/references/presets/marketing-collateral.md) — Community-only
+- [`presets/frontier-design.md`](skills/claude-design-facilitator/references/presets/frontier-design.md) — Experimental — no validated practitioner pattern as of 2026-05-16
+
+---
+
+## Per-preset coverage
+
+The canonical coverage manifest is [`.coverage.md`](.coverage.md). Below mirrors that file.
+
+| Preset | Evidence grade | Anthropic anchor |
+|--------|----------------|------------------|
+| designs | Anthropic-documented + community-validated | [launch post](https://anthropic.com/news/claude-design-anthropic-labs) |
+| prototypes | Anthropic-documented + community-validated | [prototypes tutorial](https://claude.com/resources/tutorials/using-claude-design-for-prototypes-and-ux) |
+| slides | Anthropic-documented + community-validated | [slides tutorial](https://claude.com/resources/tutorials/using-claude-design-for-presentations-and-slide-decks) |
+| one-pagers | Community-only | [launch post](https://anthropic.com/news/claude-design-anthropic-labs) |
+| wireframes-mockups | Community-only | [launch post](https://anthropic.com/news/claude-design-anthropic-labs) |
+| pitch-decks | Community-only (with PPTX-export caveat) | [launch post](https://anthropic.com/news/claude-design-anthropic-labs) |
+| marketing-collateral | Community-only | [launch post](https://anthropic.com/news/claude-design-anthropic-labs) |
+| frontier-design | Experimental — no validated practitioner pattern | [launch post](https://anthropic.com/news/claude-design-anthropic-labs) |
+
+When Anthropic publishes per-preset guidance for a Community-only or Experimental preset, [`.coverage.md`](.coverage.md) and the affected preset file refresh — re-research triggers are documented inline.
+
+---
+
+## Verification
+
+```bash
+bash plugins/claude-design/verify.sh
+```
+
+Runs five test scripts under `tests/` in dependency order:
+
+| Script | Verifies |
+|--------|----------|
+| `validate-plugin.sh` | plugin.json + SKILL.md frontmatter + LICENSE + GOVERNANCE.md + README.md + CLAUDE.md + .coverage.md presence; forbidden-command-name scope-fence check; operator-private-context grep; Norwegian-leakage advisory |
+| `test-skill-triggers.sh` | SKILL.md description >=400 chars; every phrase in `.triggers.txt` appears in SKILL.md |
+| `test-sc2-artifact-coverage.sh` | Each preset in `.coverage.md` has >=1 file hit in plugin content |
+| `test-sc3-citations.sh` | No unsourced-attribution placeholders (citation-stub markers, verification-flag markers, vague second-hand phrasing); each Authoritative-claims file has >=1 Anthropic-domain URL. The script enforces the exact patterns it bans — see the script source for the regex. |
+| `test-sc1-dogfood-log.sh` | Format-check the operator dogfood log in `REMEMBER.md` (gitignored) — 5 fields well-formed |
+
+Flags:
+
+- `--strict` — pass-through to `test-sc1-dogfood-log.sh`. Without `--strict`, missing dogfood block is advisory. With `--strict`, it is the release gate.
+- `--quick` — skip `test-skill-triggers.sh` for fast incremental runs.
+
+Exit codes: `0` = all pass; non-zero = at least one sub-test failed.
+
+---
+
+## Compatibility
+
+| Requirement | Version |
+|-------------|---------|
+| Claude Code | Recent versions with plugin support |
+| Anthropic surface | `claude.ai/design` (Labs research preview launched 2026-04-17) |
+| Platform | macOS, Linux, Windows |
+| Network | None for the skill itself; the artifact-generation lives in `claude.ai/design` |
+| Dependencies | None — no npm packages, no Python, no external tools. Bash 3.2 compatible for test scripts. |
+
+---
+
+## Re-research triggers
+
+The reference tree carries Anthropic citations that may decay. Re-research is triggered by:
+
+- Anthropic publishing per-preset guidance for a `Community-only` or `Experimental` preset
+- Anthropic announcing material changes to the Goal / Layout / Content / Audience framework, the AI-slop avoid-list, or the design grading criteria
+- Anthropic adding or removing an intent preset from the launch enumeration
+- A first verified `frontier-design` practitioner artifact shipping publicly
+- Anthropic's `knowledge-work-plugins/design` plugin adding or removing slash-commands (scope-fence implications)
+- Labs → GA URL rename for `claude.ai/design`
+
+When a trigger fires, run `bash verify.sh --strict` after the update to confirm SC2 and SC3 still pass.
+
+---
+
+## Recent versions
+
+**v0.1.0 — 2026-05-17.** Initial public release. Single skill (`claude-design-facilitator`) with eight-phase facilitation flow, 12 natural-language trigger phrases, 13 reference files (5 foundation + 8 per-preset with evidence-grade labels), `.coverage.md` preset manifest plus Authoritative-claims registry, five verification scripts under `tests/` enforcing structural integrity / scope fence / skill description quality / per-preset coverage / Anthropic-domain citation discipline / operator dogfood log format, top-level `verify.sh` roll-up with `--strict` and `--quick` flags, MIT license, GOVERNANCE.md fork-and-own model.
+
+Full release history: [`CHANGELOG.md`](CHANGELOG.md). The plugin follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html). The path from v0.1 to v1.0 is dogfood-driven — see the plugin's `REMEMBER.md` for the v1.0 readiness criteria (multi-preset breadth, auto-fire validation in real natural-language requests, two consecutive dogfood sessions with zero critical patches).
+
+---
+
+## License
+
+[MIT](LICENSE). Fork it, modify it, ship your own version under your own name.

plugins/claude-design/skills/claude-design-facilitator/.triggers.txt

@@ -0,0 +1,12 @@
+I want to build a dashboard in Claude Design
+help me prompt claude.ai/design
+make a slide deck in claude.ai/design
+iterate on my Claude Design artifact
+what should I prompt Claude Design with
+build a one-pager in Claude Design
+design a prototype in claude.ai/design
+refine my Claude Design output
+create a pitch deck in Claude Design
+use Claude Design
+draft a Claude Design prompt
+make wireframes in claude.ai/design

plugins/claude-design/skills/claude-design-facilitator/SKILL.md

@@ -0,0 +1,176 @@
+---
+name: claude-design-facilitator
+argument-hint: "[intent-preset]"
+description: |
+  End-to-end facilitator for prompting Claude Design (claude.ai/design — Anthropic Labs research preview launched 2026-04-17, Opus 4.7 pinned). Walks the operator from raw idea through intent-preset selection, audience and destination clarification, DESIGN.md anchor, prompt drafting using Anthropic's verbatim Goal / Layout / Content / Audience framework plus the five-layer prompt stack, copy-paste delivery, iteration coaching across the Tweak / Comment / Chat cascade, and ship-readiness handoff to Anthropic's official knowledge-work-plugins/design plugin for critique, accessibility audit, and engineering handoff. Cites Anthropic primary sources inline; refuses to generate the artifact code itself or drive the browser. Use for any work that ends with a Claude Design artifact.
+
+  Triggers on:
+  - "I want to build a dashboard in Claude Design"
+  - "help me prompt claude.ai/design"
+  - "make a slide deck in claude.ai/design"
+  - "iterate on my Claude Design artifact"
+  - "what should I prompt Claude Design with"
+  - "build a one-pager in Claude Design"
+  - "design a prototype in claude.ai/design"
+  - "refine my Claude Design output"
+  - "create a pitch deck in Claude Design"
+  - "use Claude Design"
+  - "draft a Claude Design prompt"
+  - "make wireframes in claude.ai/design"
+---
+
+# claude-design-facilitator
+
+You are a facilitator for prompting Claude Design (`claude.ai/design`). You walk the operator from raw idea to a copy-paste-ready prompt, through iteration, to ship-readiness. You do **not** generate artifact code yourself and you do **not** drive the browser. Claude Design is where the artifact gets built; you exist to make the operator's interaction with that surface land on the first try.
+
+You follow the phases below in order. Phases 1 through 4 are scoping and grounding; do not draft a prompt before they are done. If the operator pushes for a prompt straight away, briefly explain that a five-second alignment pass produces a one-shot prompt instead of a four-round iteration spiral, then ask the Phase 2 intent question.
+
+All output is English. All authoritative claims about Claude Design behaviour cite Anthropic primary sources — `anthropic.com/news`, `support.claude.com`, `claude.com/blog`, `claude.com/resources/tutorials`, `claude.com/plugins`, `platform.claude.com`, `github.com/anthropics`. Community patterns are labelled as such with the source link. The reference files under `references/` carry the canonical content; this file is the flow.
+
+---
+
+## Phase 1 — Disambiguate the surface
+
+Confirm the operator wants `claude.ai/design` specifically, not one of the four surfaces it is most commonly confused with: classic Artifacts at `claude.ai`, Live Artifacts in Claude Cowork, custom visuals embedded in a chat reply, or Anthropic's `knowledge-work-plugins/design` plugin (which audits already-built artifacts and does not generate them).
+
+If the operator is clear, move on. If signals are mixed — they mention "Artifacts" or "Cowork", they describe a feature that does not exist in Claude Design (no `/rewind`, no version history, no branching), or they expect round-trip handoff back from Claude Code — read `references/00-what-claude-design-is-and-isnt.md` and walk through the relevant anti-conflation block.
+
+---
+
+## Phase 2 — Name the intent preset
+
+Claude Design exposes eight intent presets. The operator picks one before drafting begins, because the prompt pattern differs per preset and the per-preset reference files are the place that pattern lives.
+
+The eight presets, in the order they appear in Anthropic's launch enumeration (`anthropic.com/news/claude-design-anthropic-labs`, 2026-04-17):
+
+- **designs** — generic dashboards, components, layouts, design explorations
+- **prototypes** — interactive product flows for usability testing and demos
+- **slides** — presentation decks, internal or external
+- **one-pagers** — single-page artifacts (memos, summaries, leave-behinds)
+- **wireframes-mockups** — low-fi or high-fi layout structure, pre-visual-design
+- **pitch-decks** — investor or external pitch decks (note: PPTX export trap — see preset file)
+- **marketing-collateral** — landing pages, social variants, visual assets
+- **frontier-design** — Anthropic's "code-powered prototypes with voice, video, shaders, 3D" preset (labelled experimental in this plugin — no validated practitioner pattern as of 2026-05-16)
+
+If the operator is uncertain which preset fits, read `.coverage.md` and the matching one-line summaries; offer the two or three that match the situation. The evidence-grade label on each preset reference file is load-bearing — surface it: `Anthropic-documented + community-validated` (designs / prototypes / slides), `Community-only` (one-pagers / wireframes-mockups / pitch-decks / marketing-collateral), or `Experimental` (frontier-design).
+
+---
+
+## Phase 3 — Audience and destination
+
+Establish the audience and the destination *before* drafting the prompt. This is `@claudedesign` Anthropic-affiliated guidance: the destination format constrains the prompt because Claude Design's export options have asymmetric fidelity.
+
+Ask:
+
+- **Audience:** who reads or uses this artifact? Internal team, external stakeholder, investor, customer prospect, partner, user-testing participant?
+- **Destination:** where does it end up? PDF (lossless for static layouts, lossy for interactive elements), PPTX (Claude reads slide master / layouts / fonts / color scheme, but text flattens to images on complex compositions — see `references/03-iteration-and-session.md` PPTX trap section), HTML standalone, Canva import, Claude Code handoff for engineering build, or share-link?
+
+If the destination is PPTX and the preset is `pitch-decks`, flag the export trap explicitly (`moda.app/blog/claude-design-for-pitch-decks` documents the case where PPTX flattens richly-styled text to images). If the destination is Claude Code handoff, set expectation that the bundle Claude Design produces is one-way (no return path to Claude Design — see `references/04-handoff-and-scope.md`).
+
+---
+
+## Phase 4 — Anchor on DESIGN.md
+
+A DESIGN.md file is the operator's leverage against Claude Design's defaults. It anchors design-system identity (colors, typography, motion, layout, do's-and-don'ts) so the model does not fall back to its convergent middle-ground aesthetic.
+
+Read `references/02-design-md.md`. The reference file documents the community-converged 9-section canonical structure and a copy-paste extractor prompt that converts a brand URL or screenshot into a DESIGN.md.
+
+If the operator already has a DESIGN.md, confirm it is uploaded to the Claude Design project and that the agent prompt guide section names it. If they do not have one, point at the extractor prompt — it is the highest-leverage single piece of content in this plugin.
+
+**Evidence grade context for the operator:** Anthropic publishes the concept of DESIGN.md (`support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design`) but not the 9-section structure. The 9-section template comes from community practitioners (`github.com/rohitg00/awesome-claude-design`, `github.com/VoltAgent/awesome-claude-design`).
+
+---
+
+## Phase 5 — Draft the prompt using the five-layer stack
+
+Now draft. Open `references/01-prompt-fundamentals.md` and `references/presets/<preset>.md` for the named preset. Compose the prompt from these layers, in order:
+
+1. **Layer 1 — Goal / Layout / Content / Audience (GLCA)** — Anthropic's verbatim framework. Source: `support.claude.com/en/articles/14604416-get-started-with-claude-design`. Every prompt to Claude Design starts here.
+2. **Layer 1.5 — Start simple, layer in complexity** — Anthropic's verbatim incremental-prompting advice (same source). Do not ship a 600-word first prompt; ship a 120-word first prompt and add detail in turn two.
+3. **Layer 2a — Concrete-alternative-spec house-style control** — Anthropic's verbatim guidance from `platform.claude.com/docs/en/docs/build-with-claude/prompt-engineering/claude-4-best-practices`. Includes the AEFRM example with explicit hex palette and motion timing.
+4. **Layer 2b — Propose-options-before-building** — Anthropic's verbatim prompt template asking Claude Design to surface four distinct visual directions before committing.
+5. **Layer 3 — Negative constraints (the AI-slop avoid-list)** — verbatim banned items from `claude.com/blog/improving-frontend-design-through-skills` and `github.com/anthropics/skills/skills/frontend-design/SKILL.md`. Inter, Roboto, Arial, Space Grotesk; purple gradients on white; solid-color backgrounds; cookie-cutter framing; convergent middle-ground palettes; scattered micro-interactions.
+6. **Layer 4 — Four design dimensions** — verbatim typography / color / motion / backgrounds guidance from `frontend-design/SKILL.md`.
+7. **Layer 5 — Four design grading criteria** — Anthropic's verbatim quality criteria from `anthropic.com/engineering/harness-design-long-running-apps` (design quality, originality, craft, functionality) plus the emphasis-weighting recommendation.
+
+On top of the five layers, layer the per-preset pattern from `references/presets/<preset>.md`. For `designs`, `prototypes`, and `slides`, this is Anthropic-published prompt material. For the other four `Community-only` presets, it is community-converged pattern with attribution. For `frontier-design`, it is honest-experimental and labelled as such.
+
+Resist the urge to over-spec. Anthropic's own guidance is start simple, layer in complexity. Draft the layer-1+layer-2a+layer-3 composition first. Save layers 4 and 5 for the refinement turn.
+
+---
+
+## Phase 6 — Deliver the prompt
+
+Output a single copy-paste-ready fenced markdown code block containing the composed prompt. No preamble, no commentary inside the block. Add a one-line caption above the block: which preset, which audience, which destination.
+
+After the block, list three to five expected follow-up turns the operator should anticipate (e.g., "if it lands too generic, add layers 4 + 5 in turn two", "if PPTX is destination, validate the rendered text-as-text count in turn three"). This sets the iteration expectation honestly — Claude Design quality is non-monotonic across turns (`anthropic.com/engineering/harness-design-long-running-apps`).
+
+---
+
+## Phase 7 — Iteration coaching
+
+When the operator returns with feedback after a Claude Design generation, you do not regenerate the prompt. You coach which surface to use next. Read `references/03-iteration-and-session.md`.
+
+The three-surface cascade, in order of token cost:
+
+- **Tweak panel** — controls and sliders Claude pre-derives at artifact generation time. Zero token cost. Surgical. Use for: section reordering, variant swap, density slider, spacing scale, color temperature, typography scale, padding / radius / shadow. The Anthropic-published guidance is verbatim in `references/03`.
+- **Inline comments** — component-scoped edits via the comment surface. Surgical when the edit is in-component. Has an Anthropic-acknowledged vanish bug — if a comment disappears, paste the comment text into chat. Fails for new structural containers.
+- **Chat** — full regeneration. Use for any structural change (add a new section), aesthetic pivot, multi-component change, or anything Claude did not pre-derive a Tweak control for. Costs one full chat turn.
+
+Operator mantra (the synthesis from `research/04`): *anything Claude pre-derives at generation time is surgical thereafter; new controls cost one chat turn for setup.*
+
+Session-management heuristics from `references/03-iteration-and-session.md`:
+
+- 4-screen inflection — quality drops noticeably after the fourth screen of context in a session.
+- Opus 4.7 context — quality degrades at the 40–50% context mark.
+- Pro budget burns in roughly 25–30 minutes of active design; Max in roughly 60–90.
+- Session-break triggers: hitting screen 4, reorder / density tweaks stop landing, chat re-introduces removed defaults.
+
+If the operator hits a stuck state, point at the recovery prompt library in `references/03-iteration-and-session.md` — the `break-default-aesthetic.md` adapted prompt, "fix the system not the prompt" pattern, edit-previous-message workaround, the 3-failed-comment escalation rule, and the model downshift escalator (Opus 4.7 → Opus 4.6 / Sonnet 4.6).
+
+---
+
+## Phase 8 — Ship-readiness
+
+Before the operator declares an artifact done, run a short ship-readiness check against `references/04-handoff-and-scope.md`:
+
+- Has the destination format been validated against the rendered output? (PPTX text-as-text count, PDF interactive-element check, HTML standalone export at target viewport.)
+- If handing off to engineering: is the export bundle complete? Anthropic's handoff bundle includes a machine-readable component spec, design tokens, layout hierarchy, referenced assets, standalone HTML + inline CSS + JS, per-state screenshots, PM-annotated notes, and a stack / framework README (`anthropic.com/news/claude-design-anthropic-labs` + `support.claude.com/en/articles/14604416`).
+- Is the operator aware that the Design → Code direction is one-way? Once handed off, the path back to Claude Design is lossy (screenshot → new Claude Design session).
+
+**Downstream tool recommendation.** Once the operator has an artifact in hand and wants critique, accessibility audit, UX copy review, design-system audit, or engineering handoff guidance, recommend Anthropic's official plugin:
+
+```
+claude plugins add knowledge-work-plugins/design
+```
+
+That plugin operates on existing artifacts (Figma URLs, screenshots, copy snippets) and ships six commands: `/critique`, `/accessibility`, `/ux-copy`, `/research-synthesis`, `/design-system`, `/handoff`. It is the lifecycle complement to this one — see `references/04-handoff-and-scope.md` for the full coverage table. This plugin (claude-design) covers idea through delivered prompt through iteration coaching; `knowledge-work-plugins/design` covers everything after. There is no command overlap and no functional redundancy.
+
+---
+
+## What this skill never does
+
+- It does not generate the artifact code itself. Claude Design is the artifact generator. This skill produces prompts that go into Claude Design.
+- It does not automate the browser, paste prompts on the operator's behalf, or read the Claude Design canvas. The operator copies and pastes manually.
+- It does not store artifact history, version artifacts, or branch between iterations. Claude Design has no version tree and this skill does not invent one.
+- It does not duplicate the post-design lane covered by `knowledge-work-plugins/design`. No `/critique`, no `/accessibility`, no `/ux-copy`, no `/research-synthesis`, no `/design-system`, no `/handoff` commands.
+
+---
+
+## Reference files
+
+- `references/00-what-claude-design-is-and-isnt.md` — surface disambiguation
+- `references/01-prompt-fundamentals.md` — the five-layer prompt stack
+- `references/02-design-md.md` — DESIGN.md template + brand-to-DESIGN.md extractor
+- `references/03-iteration-and-session.md` — Tweak / Comment / Chat cascade, session economics, recovery prompt library
+- `references/04-handoff-and-scope.md` — one-way handoff, scope fence vs Anthropic's design plugin
+- `references/presets/designs.md`, `prototypes.md`, `slides.md` — Anthropic-documented per-preset patterns
+- `references/presets/one-pagers.md`, `wireframes-mockups.md`, `pitch-decks.md`, `marketing-collateral.md` — Community-only per-preset patterns
+- `references/presets/frontier-design.md` — Experimental, no validated practitioner pattern
+- `.coverage.md` — preset enumeration with evidence-grade labels (the source of truth for SC2 verification)
+
+---
+
+## Explicit invocation
+
+The skill name registers as the explicit slash command `/claude-design-facilitator`. Operators can either trigger by natural language (the description above is the auto-fire surface) or invoke explicitly when they want to start a facilitation session from a clean state.

plugins/claude-design/skills/claude-design-facilitator/references/00-what-claude-design-is-and-isnt.md

@@ -0,0 +1,113 @@
+# What Claude Design is and isn't
+
+**Last updated:** 2026-05-17 | **Verified:** research/01-claude-design-surface.md
+**Status:** Beta (Labs research preview)
+**Captured-on date:** 2026-05-16
+
+This file disambiguates `claude.ai/design` from the four surfaces it is most commonly conflated with. The cost of getting this wrong is wasted iteration: applying a prompt pattern that fits Live Artifacts to Claude Design (or vice versa) produces output that misses the operator's intent, and the failure looks like a prompt problem instead of a surface problem.
+
+Read this file when the operator's signals are mixed — they reference "Artifacts" loosely, they expect a feature that does not exist in Claude Design (like `/rewind` or a version tree), they think Claude Design audits artifacts rather than generates them, or they expect round-trip handoff back from Claude Code.
+
+---
+
+## 1. What Claude Design is
+
+Claude Design is an Anthropic Labs research preview that launched on 2026-04-17 (`https://anthropic.com/news/claude-design-anthropic-labs`). It is a dedicated workspace at `claude.ai/design` for generating interactive design artifacts from a prompt.
+
+Five properties define the surface:
+
+- **Labs research preview, not GA.** The product can change without notice. Anthropic surfaces it under the Labs banner specifically to signal that the contract is non-stable. The URL still carries the `-anthropic-labs` slug today; a Labs → GA rename is a known re-research trigger captured in `.coverage.md`.
+- **Opus 4.7 pinned.** All generations run on Opus 4.7. Operators cannot select a model from the Claude Design UI. The session inherits Anthropic's model choice for this surface (`https://anthropic.com/news/claude-design-anthropic-labs`).
+- **Single HTML/React substrate.** Underneath every output is one rendering engine — HTML, React components, inline CSS — regardless of which intent preset the operator picks. The intent preset shapes prompting and export, not the underlying tech.
+- **Eight intent presets exposed in the UI.** Anthropic's launch post enumerates: designs, prototypes, slides, one-pagers, wireframes-mockups, pitch-decks, marketing-collateral, frontier-design. The enumeration is the source of truth for SC2 coverage in this plugin (`https://anthropic.com/news/claude-design-anthropic-labs`).
+- **Multiple export paths.** PDF (lossless for static layouts, lossy for interactive elements), PPTX (slide master / layouts / fonts honored, but text can flatten to images on complex compositions), HTML standalone, Canva import, share-link, and Claude Code handoff (machine-readable component spec + design tokens + layout hierarchy + assets + standalone HTML/CSS/JS + per-state screenshots + PM notes + framework README — verbatim per `https://support.claude.com/en/articles/14604416-get-started-with-claude-design`).
+
+Three Anthropic-published support articles ground the surface: the get-started article (`https://support.claude.com/en/articles/14604416-get-started-with-claude-design`), the design-system setup article (`https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design`), and the PowerPoint-mode conventions article (`https://support.claude.com/en/articles/13521390-use-claude-for-powerpoint`).
+
+---
+
+## 2. What Claude Design is NOT
+
+### Not classic Artifacts at `claude.ai`
+
+Classic Artifacts live in any Claude.ai chat. They appear in a side panel when Claude generates code, markdown, SVG, mermaid diagrams, or other inline outputs. Artifacts carry no intent presets, no Tweak panel, no export-to-PPTX, no Claude Code handoff bundle, no DESIGN.md anchor concept. They are a chat affordance.
+
+Confusion happens because both surfaces produce HTML/React output and Anthropic's documentation has used "Artifacts" loosely in launch contexts. If the operator says "Artifacts" but describes intent presets or destination formats (`https://anthropic.com/news/claude-design-anthropic-labs`), they mean Claude Design. If they describe a side panel inside a chat (`support.claude.com` discusses Artifacts in the chat-product context), they mean classic Artifacts.
+
+### Not Live Artifacts in Claude Cowork
+
+Live Artifacts is a different Labs surface — collaborative real-time editing of artifacts inside Claude Cowork sessions. It runs in a different workspace, has different affordances (multi-cursor presence, version stream), and is a separate product line at `claude.ai/code` family (see Anthropic's Cowork-related communications). Claude Design has none of those collaborative primitives. The operator working alone in `claude.ai/design` is the canonical flow.
+
+### Not custom visuals embedded in a chat reply
+
+Sometimes Claude generates an inline HTML/SVG visual as part of a chat answer (a chart, a diagram, an illustration). That is a one-off chat artifact, not a Claude Design session. The prompt patterns are different (chat conversational tone vs design intent presets), the export options are different (chat artifact has Save / Copy, Claude Design has the full export matrix), and there is no Tweak panel on the chat-inline visuals.
+
+### Not Anthropic's `knowledge-work-plugins/design` plugin
+
+This is the most consequential conflation. Anthropic ships an official plugin at `https://claude.com/plugins/design` (`https://github.com/anthropics/knowledge-work-plugins`) with six slash-commands: `/critique`, `/accessibility`, `/ux-copy`, `/research-synthesis`, `/design-system`, `/handoff`. That plugin operates on **existing** artifacts (Figma URLs, screenshots, copy snippets). It does not generate artifacts.
+
+The lifecycle split is clean:
+
+- This plugin (`claude-design`) covers **pre-design and during-design** — idea → intent-preset selection → prompt drafting → copy-paste delivery → iteration coaching → ship-readiness.
+- Anthropic's `knowledge-work-plugins/design` covers **post-design** — critique → accessibility → UX copy review → research synthesis → design-system audit → engineering handoff.
+
+There is zero command overlap (this plugin ships no commands named `/critique`, `/accessibility`, `/ux-copy`, `/research-synthesis`, `/design-system`, or `/handoff` — `tests/validate-plugin.sh` assertion (h) enforces this mechanically). Workflow recommendation: use this plugin to land the artifact in `claude.ai/design`; once the artifact exists, install Anthropic's official plugin via `claude plugins add knowledge-work-plugins/design` for downstream review and handoff.
+
+### Not third-party clones like `jiji262/claude-design-skill`
+
+Several third-party repos use names like `claude-design-skill`. They are independent community efforts targeting general design workflows in Claude Code, not the `claude.ai/design` surface specifically. They predate the Anthropic Labs launch in some cases. This plugin is *Claude Design facilitation* — it targets the Anthropic surface explicitly, citing Anthropic's primary sources. Verify the operator's mental model accordingly.
+
+---
+
+## 3. Why the distinction matters operationally
+
+Three operational consequences flow from getting the surface identification right.
+
+### Prompt patterns differ
+
+Claude Design's prompt patterns are documented in `https://anthropic.com/news/claude-design-anthropic-labs`, `https://support.claude.com/en/articles/14604416-get-started-with-claude-design`, and the two per-preset tutorials (`https://claude.com/resources/tutorials/using-claude-design-for-prototypes-and-ux`, `https://claude.com/resources/tutorials/using-claude-design-for-presentations-and-slide-decks`). These prompts assume the Claude Design substrate, intent presets, and the Tweak / Comment / Chat iteration cascade. Applying them to classic Artifacts, Cowork, or an inline chat visual produces noise.
+
+Classic Artifacts prompts (the kind used inside any `claude.ai` chat) are conversational and lean on chat affordances. Claude Design prompts use the verbatim Goal / Layout / Content / Audience framework and lean on intent presets. The frameworks do not interchange cleanly.
+
+### Limits differ
+
+Claude Design has its own quota economics — the operator's Max / Pro plan budget burns down at a different rate than classic chat (research/04 documents observed Pro burn of roughly 25-30 minutes of active design work, Max roughly 60-90; these are community-observed, not Anthropic-published, and may shift). Opus 4.7 quality degrades at 40-50% context (`https://anthropic.com/engineering/harness-design-long-running-apps`). A 4-screen session inflection is documented community-wide.
+
+None of these limits apply identically to classic Artifacts or to the official `knowledge-work-plugins/design` plugin. Diagnosing a quota / quality issue requires knowing which surface is in play.
+
+### Scope differs
+
+The official `knowledge-work-plugins/design` plugin is the right tool for post-design critique. Trying to make this plugin (`claude-design`) emit a critique would duplicate Anthropic's command surface and add nothing. The reverse — using `knowledge-work-plugins/design` to generate the artifact — does not work because that plugin operates on artifacts that already exist.
+
+If the operator is uncertain whether their question is pre-design or post-design, ask: *does the artifact exist yet?* If no — this plugin. If yes — Anthropic's plugin.
+
+---
+
+## 4. Decision shortcuts
+
+- The operator mentions intent presets (designs / prototypes / slides / one-pagers / wireframes-mockups / pitch-decks / marketing-collateral / frontier-design) → Claude Design.
+- The operator mentions a workspace URL `claude.ai/design` → Claude Design.
+- The operator mentions PPTX / PDF / Canva / Code-handoff exports → Claude Design.
+- The operator says "Tweak panel" or "Tweak slider" → Claude Design.
+- The operator says "Artifact" in a side panel context inside a normal chat → classic Artifacts.
+- The operator says "Cowork" or "real-time collaborative" or "multi-cursor" → Live Artifacts.
+- The operator says "critique" / "accessibility audit" / "Figma" → Anthropic's `knowledge-work-plugins/design`.
+- The operator references a third-party repo named `claude-design-*` → ask what surface they target; likely not the Anthropic Labs preview.
+
+If signals remain mixed after this read-through, ask one clarifying question rather than guess: *"Are you working in the dedicated Claude Design workspace at `claude.ai/design`, or somewhere else?"*
+
+---
+
+## Sources
+
+- `https://anthropic.com/news/claude-design-anthropic-labs` — Anthropic Labs launch announcement (2026-04-17), Opus 4.7 pin, intent-preset enumeration, export options
+- `https://support.claude.com/en/articles/14604416-get-started-with-claude-design` — get-started article, GLCA framework, handoff bundle contents
+- `https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design` — design-system setup, DESIGN.md concept
+- `https://support.claude.com/en/articles/13521390-use-claude-for-powerpoint` — PowerPoint-mode conventions
+- `https://claude.com/plugins/design` — Anthropic's official knowledge-work-plugins/design plugin
+- `https://github.com/anthropics/knowledge-work-plugins` — source for the official plugin
+- `https://claude.com/resources/tutorials/using-claude-design-for-prototypes-and-ux` — Anthropic-published per-preset tutorial (prototypes)
+- `https://claude.com/resources/tutorials/using-claude-design-for-presentations-and-slide-decks` — Anthropic-published per-preset tutorial (slides)
+- `https://anthropic.com/engineering/harness-design-long-running-apps` — design grading criteria, non-monotonic-improvement framing
+
+When in doubt: the Anthropic news post and the get-started support article are the load-bearing sources. Everything else triangulates against them.

plugins/claude-design/skills/claude-design-facilitator/references/01-prompt-fundamentals.md

@@ -0,0 +1,265 @@
+# Prompt fundamentals — the five-layer stack
+
+**Last updated:** 2026-05-17 | **Verified:** research/03-prompt-patterns-intent-presets.md
+**Status:** Beta (Labs research preview)
+**Captured-on date:** 2026-05-16
+
+This file documents the universal prompt framework an operator applies across every Claude Design intent preset. The five layers compose into one prompt block. Layers 1 to 3 are load-bearing for every preset; layers 4 and 5 are the refinement turn.
+
+Every authoritative claim cites an Anthropic primary source. Where community practice extends an Anthropic concept, the extension is labelled and attributed.
+
+---
+
+## Layer 1 — Goal / Layout / Content / Audience (GLCA)
+
+Anthropic's verbatim framework for every Claude Design prompt. The framework is published in the get-started support article `https://support.claude.com/en/articles/14604416-get-started-with-claude-design`. Anthropic's framing: a good Claude Design prompt names the **Goal**, the **Layout**, the **Content**, and the **Audience**, in that order, before any aesthetic specification.
+
+The four canonical questions:
+
+- **Goal** — what is the artifact for? "An admin dashboard for monitoring API latency", "an onboarding flow for first-time users", "a landing page that converts free trial signups". One sentence.
+- **Layout** — what is the page structure? Header / hero / metrics row / table / footer; or: hero / three-feature-grid / pricing table / CTA. Name the regions.
+- **Content** — what fills the regions? Real data placeholders if you have them, named labels if not. Avoid generic "lorem ipsum" — the model defaults to convergent middle-ground content if you do not constrain it.
+- **Audience** — who reads or uses this artifact? Internal team, external stakeholder, B2B procurement, B2C consumer, investor. Audience determines tone, density, and aesthetic.
+
+Anthropic publishes three verbatim canonical examples in the same support article:
+
+```
+Goal: An analytics dashboard for our customer success team
+Layout: Top metrics row (4 KPIs), main chart panel, recent activity table
+Content: Today's MRR, 30-day churn, NPS, expansion revenue; revenue chart;
+         the last 10 account events
+Audience: Internal CS leads — they're in this thing every day, want density
+          and signal, not flashy
+```
+
+```
+Goal: A mobile onboarding flow for a new fitness app
+Layout: Welcome screen, goal-selection (3 cards), motion preference, sign-in
+Content: Headlines, single CTA per screen, accessible touch targets
+Audience: First-time users, gym beginners, ages 25-45
+```
+
+```
+Goal: A SaaS landing page that converts free trial signups
+Layout: Hero, three-feature grid, social proof, pricing table, FAQ, footer CTA
+Content: Product name placeholder "ProductX", real headline benefit copy,
+         three feature blurbs (icon + headline + line)
+Audience: B2B technical buyers evaluating dev tools
+```
+
+The GLCA framework is sufficient on its own for a first prompt at intent preset `designs`. For other presets, GLCA composes with the per-preset pattern in `references/presets/<preset>.md`.
+
+Source: `https://support.claude.com/en/articles/14604416-get-started-with-claude-design`.
+
+---
+
+## Layer 1.5 — Start simple, layer in complexity
+
+The same Anthropic get-started article publishes verbatim incremental-prompting advice: do not ship a 600-word first prompt. Ship a 120-word first prompt that names GLCA, see what Claude Design produces, then add complexity in turn two and turn three.
+
+Anthropic frames this as the dominant failure mode for first-time Claude Design operators: over-specifying the first prompt produces an output that is dense but generic. The remedy is staged — let Claude Design make its default choices, then react to what it produces with targeted constraints.
+
+This frames how the rest of the stack composes. In turn one, ship layers 1 + 2a (or 2b) + 3. In turn two, add layer 4. In turn three, add layer 5 emphasis-weighting.
+
+Source: `https://support.claude.com/en/articles/14604416-get-started-with-claude-design`.
+
+---
+
+## Layer 2a — Concrete-alternative-spec house-style control
+
+The first of two Anthropic-documented house-style controls. Verbatim guidance from `https://platform.claude.com/docs/en/docs/build-with-claude/prompt-engineering/claude-4-best-practices`: name a concrete aesthetic family with explicit visual primitives rather than gesturing at a style.
+
+The Anthropic-published exemplar — the AEFRM (Anthropic Engineering Field Reference Material) example — is verbatim usable:
+
+```
+Aesthetic family: industrial-utilitarian, slate-monochrome
+Color palette (CSS hex):
+  --color-bg:       #E9ECEC
+  --color-surface:  #C9D2D4
+  --color-muted:    #8C9A9E
+  --color-fg:       #44545B
+  --color-ink:      #11171B
+Typography: square angular sans-serif (Söhne, Inter Variable as fallback);
+            no rounded glyphs; weight 500 for body, 700 for headers
+Corner radius: 4px throughout — no fully rounded buttons, no pill shapes
+Motion: transition: all 160ms ease-out on hover; no springy easing
+Density: dense (table rows 32px tall; padding 8px on cards)
+Surface: flat — no shadows, no glassmorphism
+```
+
+The control works because Claude Design reads this as a concrete brief and constrains its aesthetic decision space accordingly. Without an explicit concrete-alternative-spec, the model defaults to its convergent middle-ground aesthetic (rounded corners, generous spacing, friendly typography, gentle shadows — Anthropic's documented "AI-slop" default).
+
+The hex palette, corner radius, and motion timing are all required — naming "industrial-utilitarian" alone is gesturing, not specifying.
+
+Source: `https://platform.claude.com/docs/en/docs/build-with-claude/prompt-engineering/claude-4-best-practices`.
+
+---
+
+## Layer 2b — Propose-options-before-building
+
+The second Anthropic-documented house-style control, also from `https://platform.claude.com/docs/en/docs/build-with-claude/prompt-engineering/claude-4-best-practices`. When the operator does not know exactly which aesthetic to brief, Anthropic publishes a verbatim prompt template asking Claude Design to propose four distinct visual directions before committing to one.
+
+The verbatim prompt:
+
+```
+Before building the dashboard, propose 4 distinct visual directions.
+For each, give:
+  - bg hex
+  - accent hex
+  - typeface (named, not gestured)
+  - one-line rationale tying the direction to the audience and goal
+
+Wait for me to pick a direction before generating the artifact.
+```
+
+This forks the conversation: turn one returns four named directions, the operator picks one, turn two generates against the chosen direction. The cost is one extra round; the upside is the operator avoids the dead-end of generating against an aesthetic that does not fit and only finding out after generation.
+
+Use layer 2b when layer 2a is not feasible (the operator does not yet know the aesthetic). Use layer 2a when the aesthetic is known.
+
+---
+
+## Layer 3 — AI-slop avoid-list (negative constraints)
+
+Anthropic publishes a verbatim banned-items list in `https://claude.com/blog/improving-frontend-design-through-skills` and reinforces it in the open-source frontend-design skill at `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md`. The list names the convergent middle-ground patterns that Claude Design defaults to when underspecified.
+
+Anthropic's verbatim AI-slop fingerprints to avoid:
+
+- **Typography slop:** Inter, Roboto, Arial as default body font. Space Grotesk is flagged as overused. Default to a concrete-named typeface in the brief, not a generic sans-serif.
+- **Color slop:** purple gradients on white backgrounds; solid-color hero backgrounds; convergent middle-ground palettes (the muted blue-and-grey "professional" default).
+- **Layout slop:** cookie-cutter three-column feature grids; centered-hero-with-CTA defaults; full-width-image-with-text-overlay defaults.
+- **Motion slop:** scattered micro-interactions; bouncy spring easing on hover; pulse animations on idle elements.
+- **Complexity-to-vision mismatch:** ornate components on simple layouts; flat components on otherwise rich layouts.
+
+Operator-actionable copy-paste anti-prompt block (composes with layers 1 and 2):
+
+```
+Negative constraints — do not produce any of:
+  - Inter, Roboto, Arial, or Space Grotesk as the primary typeface
+  - Purple gradients on white backgrounds
+  - Solid-color hero backgrounds
+  - Three-column feature grids with icon + headline + line
+  - Centered-hero-with-single-CTA layout default
+  - Bouncy spring easing on hover transitions
+  - Pulse / breathing animations on idle elements
+  - Glassmorphism, neumorphism, or generic "modern SaaS" defaults
+
+If you find yourself defaulting to any of these, stop and ask me to
+clarify the aesthetic before continuing.
+```
+
+Sources: `https://claude.com/blog/improving-frontend-design-through-skills` and `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md`.
+
+---
+
+## Layer 4 — Four design dimensions to optimize
+
+Anthropic's verbatim per-dimension guidance from `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md`. Four dimensions to brief explicitly when refining beyond the first turn:
+
+- **Typography** — name typeface, modular scale (e.g., 1.250 minor third or 1.333 perfect fourth), weight palette, line-height palette, letter-spacing for headings. Anthropic's frontend-design SKILL.md publishes specific modular scales and weight palettes verbatim.
+- **Color** — beyond palette hex, specify semantic roles (background, surface, accent, muted, error, success). Define interaction states explicitly (hover, active, disabled, focus). Anthropic's guidance: avoid relying on opacity for state changes; use explicit color tokens.
+- **Motion** — name easing curves (ease-out, cubic-bezier values), name durations (120ms / 160ms / 240ms tiers), name what gets animated and what does not. Anthropic's guidance: motion should clarify hierarchy and confirm interaction; avoid decorative motion.
+- **Backgrounds** — flat surface vs depth, when to layer surfaces, when shadows or borders define edges. Anthropic's guidance: backgrounds carry meaning; the bare-default-white background is rarely the right choice.
+
+In turn two of an iteration, add layer-4 dimension specs to the brief. In turn three, refine the dimension that drifted most from intent.
+
+Source: `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md`.
+
+---
+
+## Layer 5 — Four design grading criteria
+
+Anthropic publishes verbatim grading criteria for design quality in `https://anthropic.com/engineering/harness-design-long-running-apps`. Four criteria, used as emphasis weights:
+
+- **Design quality** — does the artifact look intentional, not defaulted? Is the aesthetic coherent across regions?
+- **Originality** — does the artifact avoid the convergent middle-ground? Does it surprise without being weird?
+- **Craft** — does the artifact feel detailed and considered at every level — typography, spacing, alignment, hierarchy, color?
+- **Functionality** — does the artifact work for its goal and audience? Would it survive a usability test or a stakeholder review?
+
+Anthropic's emphasis-weighting recommendation: in the prompt, weight which criterion matters most for *this* artifact. A dashboard for internal use weights functionality and craft highest. A pitch deck for an external investor weights design quality and originality highest. A wireframe for early exploration weights functionality highest with craft and originality deprioritized.
+
+Operator-actionable layer-5 block:
+
+```
+Grading criteria for this artifact, in priority order:
+  1. {craft|design quality|originality|functionality} — weight 0.4
+  2. {one of the others} — weight 0.3
+  3. {one of the others} — weight 0.2
+  4. {the remaining one} — weight 0.1
+
+Optimize against this ordering. If the artifact has to trade off,
+trade off the lowest-weighted criterion first.
+```
+
+The non-monotonic-improvement caveat applies — Anthropic notes that quality across iterations is not strictly increasing. If turn three is worse than turn two on a critical criterion, the recovery move is documented in `references/03-iteration-and-session.md` ("pivot to an entirely different aesthetic if the approach wasn't working").
+
+Source: `https://anthropic.com/engineering/harness-design-long-running-apps`.
+
+---
+
+## How the layers compose into one prompt
+
+A worked example for the `designs` intent preset, dashboard, three turns:
+
+### Turn 1 — layers 1 + 2a + 3 (the first prompt)
+
+```
+Goal: An admin dashboard for monitoring API latency by route, by region,
+      and by P50/P95/P99
+Layout: Header with environment switcher; top metrics row (4 KPIs:
+        global P95, error rate, throughput, active requests); main chart
+        (time series, P50/P95/P99 lines); routes table with sortable
+        latency columns; alerts sidebar
+Content: KPI placeholders are real metric names; chart uses synthetic
+         24-hour data; table has 12 routes with realistic paths
+         (/api/v1/users, /api/v1/orders, etc.)
+Audience: Platform engineers, on-call rotation, ages 25-45,
+          comfortable with dense interfaces
+
+Aesthetic family: industrial-utilitarian, slate-monochrome
+Color palette (CSS hex):
+  --color-bg:       #E9ECEC
+  --color-surface:  #C9D2D4
+  --color-muted:    #8C9A9E
+  --color-fg:       #44545B
+  --color-ink:      #11171B
+Typography: square angular sans-serif (Söhne, Inter Variable fallback);
+            no rounded glyphs
+Corner radius: 4px throughout
+Motion: transition: all 160ms ease-out
+Density: dense (32px table rows, 8px card padding)
+Surface: flat — no shadows
+
+Negative constraints — do not produce any of:
+  - Inter, Roboto, Arial, or Space Grotesk as primary typeface
+  - Purple gradients on white backgrounds
+  - Pulse animations on idle elements
+  - Glassmorphism, neumorphism, generic "modern SaaS" defaults
+```
+
+### Turn 2 — add layer 4 dimensions
+
+Operator reacts to turn-1 output by adding typography modular scale, semantic color roles, motion easing, and surface-depth rules.
+
+### Turn 3 — add layer 5 weighting
+
+Operator specifies that craft and functionality are the two highest-weighted criteria for this dashboard; design quality is third; originality lowest.
+
+### Turn 4+ — Tweak panel takes over
+
+Most subsequent refinements happen in the Tweak panel (per-artifact Claude-generated controls; zero-token surgical edits) — see `references/03-iteration-and-session.md` for the surface cascade.
+
+---
+
+## Source map
+
+The five layers anchor on four Anthropic primary sources plus one open-source skill:
+
+| Layer | Anthropic source |
+|-------|------------------|
+| 1, 1.5 | `https://support.claude.com/en/articles/14604416-get-started-with-claude-design` |
+| 2a, 2b | `https://platform.claude.com/docs/en/docs/build-with-claude/prompt-engineering/claude-4-best-practices` |
+| 3 | `https://claude.com/blog/improving-frontend-design-through-skills` + `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` |
+| 4 | `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` |
+| 5 | `https://anthropic.com/engineering/harness-design-long-running-apps` |
+
+Re-research trigger: any of the four URLs returning 404 or shifting content materially; Anthropic publishing a sixth layer or revising any of the five. Captured-on date 2026-05-16 — the layer-1 framework has been stable since the launch announcement.

plugins/claude-design/skills/claude-design-facilitator/references/02-design-md.md

@@ -0,0 +1,333 @@
+# DESIGN.md — template and extractor
+
+**Last updated:** 2026-05-17 | **Verified:** research/03-prompt-patterns-intent-presets.md
+**Status:** Beta (Labs research preview)
+**Captured-on date:** 2026-05-16
+
+**Evidence grade:** Community-converged — Anthropic publishes the *concept* of a design-system document anchored to a Claude Design project (`https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design`), but does not publish the 9-section canonical structure. The 9-section template comes from community practitioners (`https://github.com/rohitg00/awesome-claude-design`, `https://github.com/VoltAgent/awesome-claude-design`). Use accordingly: the concept is Anthropic-authoritative; the structure is community-converged.
+
+---
+
+## 1. Why DESIGN.md
+
+A DESIGN.md file uploaded to a Claude Design project anchors design-system identity for every artifact generated in that project. Without an anchor, Claude Design defaults to its convergent middle-ground aesthetic (rounded corners, generous spacing, friendly typography, gentle shadows — the AI-slop pattern documented at `https://claude.com/blog/improving-frontend-design-through-skills`). With an anchor, the model reads the file at generation time and constrains its aesthetic, component, and motion decisions to match.
+
+Anthropic publishes the concept of design-system anchors in `https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design`. The article describes asset uploads, brand kits, and the principle that artifacts in a Claude Design project inherit the project's design language. What Anthropic does *not* publish is a recommended structure for the design-language file itself.
+
+The community converged on a 9-section structure — documented across multiple awesome-claude-design repos, Substack posts, and practitioner blogs — that maps cleanly onto how Claude Design reads design context. The sections below are that converged structure.
+
+---
+
+## 2. The 9-section canonical structure
+
+Each section names a decision Claude Design will otherwise default. The order is the order Claude Design appears to read most reliably (heaviest design-decision sections first).
+
+### Section 1 — Visual Theme & Atmosphere
+
+A one-paragraph description of the aesthetic family. Use named visual references the model can anchor to: "industrial-utilitarian like a Bloomberg terminal", "warm-editorial like The New York Times opinion section", "minimal-monochrome like Linear's UI".
+
+Worked example:
+
+```markdown
+# Visual Theme & Atmosphere
+
+Industrial-utilitarian. Slate-monochrome palette, square-cut typography,
+flat surfaces. Reference: a modern data-tool UI (Linear, Datadog,
+Bloomberg) — dense, intentional, no flourish. The product should look
+like it was built for engineers by engineers.
+```
+
+### Section 2 — Color Palette & Roles
+
+CSS-variable form with explicit hex values and semantic roles. Avoid relying on opacity for state changes — name each state explicitly.
+
+Worked example:
+
+```markdown
+# Color Palette & Roles
+
+:root {
+  --color-bg:        #E9ECEC;
+  --color-surface:   #C9D2D4;
+  --color-muted:     #8C9A9E;
+  --color-fg:        #44545B;
+  --color-ink:       #11171B;
+
+  --color-accent:    #4A6FA5;
+  --color-accent-hover:  #3D5C8A;
+  --color-accent-active: #2F4A70;
+
+  --color-error:     #B23A48;
+  --color-warning:   #C89B3F;
+  --color-success:   #4F7A4F;
+}
+
+Semantic roles:
+- bg     — page background
+- surface — card / panel background
+- muted  — secondary text, borders
+- fg     — primary text
+- ink    — emphasis / heading text
+```
+
+### Section 3 — Typography Rules
+
+Named typeface, modular scale, weight palette, line-height palette. Modular scales the community converged on are 1.250 (minor third) for dense interfaces and 1.333 (perfect fourth) for marketing pages.
+
+Worked example:
+
+```markdown
+# Typography Rules
+
+Primary typeface: Söhne (concrete-named, not "modern sans-serif").
+Fallback: Inter Variable.
+Display typeface: same as primary (no separate display face).
+
+Modular scale: 1.250 (minor third).
+  --text-xs:  0.64rem;
+  --text-sm:  0.8rem;
+  --text-base: 1rem;
+  --text-lg:  1.25rem;
+  --text-xl:  1.563rem;
+  --text-2xl: 1.953rem;
+
+Weight palette: 500 body, 600 emphasized, 700 headings.
+Line height: 1.4 body, 1.2 headings.
+
+If the typeface is not available, substitute Inter Variable — never
+default to Inter, Roboto, Arial, or Space Grotesk
+(per https://claude.com/blog/improving-frontend-design-through-skills
+AI-slop avoid-list).
+```
+
+### Section 4 — Component Stylings
+
+Per-component rules for the components Claude Design generates. Cover buttons, inputs, cards, tables, navigation. Specify radius, padding, border treatment, hover/active/disabled state explicitly.
+
+Worked example:
+
+```markdown
+# Component Stylings
+
+Buttons:
+  - radius: 4px (no pill shapes)
+  - padding: 8px 16px
+  - primary: bg accent, fg surface
+  - secondary: border 1px muted, bg transparent
+  - hover: bg accent-hover
+  - active: bg accent-active
+  - disabled: opacity 0.4, no pointer events
+
+Inputs:
+  - radius: 4px
+  - padding: 8px 12px
+  - border: 1px solid muted
+  - focus: border accent + 2px outset ring at accent + 20% alpha
+
+Cards:
+  - radius: 4px
+  - padding: 16px
+  - bg surface
+  - no shadow — borders define edges if needed
+
+Tables:
+  - row height: 32px (dense)
+  - cell padding: 8px
+  - alternating row: bg + 4% darken
+  - hover row: bg + 8% darken
+```
+
+### Section 5 — Layout Principles
+
+Grid system, spacing scale, breakpoint widths. Name the grid columns and the gap value.
+
+Worked example:
+
+```markdown
+# Layout Principles
+
+Grid: 12-column on screens >= 1024px, 8-column on screens 768-1023px,
+4-column on screens < 768px.
+Gap: 16px (--space-md).
+
+Spacing scale:
+  --space-xs: 4px
+  --space-sm: 8px
+  --space-md: 16px
+  --space-lg: 24px
+  --space-xl: 32px
+  --space-2xl: 48px
+
+Page max-width: 1440px centered.
+Container padding: 24px on screens >= 768px, 16px below.
+```
+
+### Section 6 — Depth & Elevation
+
+Surface depth rules. Most designs benefit from a clear flat-vs-layered decision rather than a mixed palette.
+
+Worked example:
+
+```markdown
+# Depth & Elevation
+
+Flat. No box-shadows by default. Borders define component edges.
+Z-stack:
+  z-0: page surface
+  z-10: navigation
+  z-20: dropdown / popover
+  z-30: modal backdrop
+  z-40: modal content
+  z-50: toast / notification
+
+Modal: bg surface, 1px border ink, no shadow.
+Popover: bg surface, 1px border muted, no shadow.
+```
+
+### Section 7 — Do's and Don'ts
+
+Explicit constraint list. This is where layer-3 (AI-slop avoid-list) gets project-specific.
+
+Worked example:
+
+```markdown
+# Do's and Don'ts
+
+Do:
+  - Use accent color sparingly (CTA + active state only)
+  - Use ink for headings, fg for body, muted for secondary
+  - Use 4px corner radius consistently
+  - Use 160ms ease-out for all hover transitions
+
+Don't:
+  - Use purple gradients on white backgrounds
+  - Use solid-color hero backgrounds
+  - Use Inter / Roboto / Arial / Space Grotesk as primary typeface
+  - Use bouncy spring easing
+  - Use pulse / breathing animations on idle elements
+  - Use glassmorphism or neumorphism
+  - Use shadows except where the depth-and-elevation section explicitly permits
+```
+
+### Section 8 — Responsive Behavior
+
+Breakpoint behavior. Anthropic does not publish responsive rules; this is the section where a project encodes its responsive philosophy.
+
+Worked example:
+
+```markdown
+# Responsive Behavior
+
+Mobile-first reasoning, but built desktop-first (target audience is
+desktop). Below 768px:
+  - Navigation collapses to single icon-button row
+  - Tables become card stacks (one card per row)
+  - 12-column grid becomes 4-column
+  - Container padding drops from 24px to 16px
+  - Font sizes scale down by 0.9x
+
+Touch targets: minimum 44px height (regardless of viewport).
+```
+
+### Section 9 — Agent Prompt Guide
+
+A short block telling Claude Design how to use this DESIGN.md. This section is the bridge between the file and the prompt — it names the file by section and reminds the model that the constraints are load-bearing.
+
+Worked example:
+
+```markdown
+# Agent Prompt Guide
+
+When generating an artifact in this project, read every section of this
+DESIGN.md before producing output. Treat color palette, typography rules,
+component stylings, and layout principles as constraints — not
+suggestions. If a generation would violate a constraint, stop and ask
+which constraint to relax.
+
+Cite specific section names when justifying design decisions in
+explanatory text (e.g., "I chose 4px corners per Section 4 Component
+Stylings").
+```
+
+---
+
+## 3. Brand-to-DESIGN.md extractor prompt
+
+A copy-paste-ready prompt the operator pastes into `claude.ai` (the chat product) or Claude.com to convert a brand URL, screenshot, or marketing asset into a DESIGN.md. The pattern comes from `https://github.com/rohitg00/awesome-claude-design/blob/main/prompts/brand-to-design-md.md` (adapted with attribution to the awesome-claude-design community template).
+
+```
+You will produce a DESIGN.md file by analyzing the brand reference
+materials I provide. Output structure: 9 sections, in this order,
+with the exact heading names:
+
+  1. Visual Theme & Atmosphere
+  2. Color Palette & Roles
+  3. Typography Rules
+  4. Component Stylings
+  5. Layout Principles
+  6. Depth & Elevation
+  7. Do's and Don'ts
+  8. Responsive Behavior
+  9. Agent Prompt Guide
+
+Rules:
+- Use CSS-variable form (--color-name: #HEX) for color palette
+- Use modular scale form (--text-xs / --text-sm / ...) for typography
+- Use named typefaces ONLY — if you cannot identify the typeface from
+  the brand materials with high confidence, write "unknown — operator
+  to fill in" rather than guessing. Do not hallucinate a typeface name.
+- For each component (button, input, card, table, navigation), name
+  radius, padding, border treatment, and hover / active / disabled states
+- Cite the source brand material at the top (e.g., "Extracted from
+  brand kit at <URL> on 2026-05-17")
+
+Brand reference materials:
+[paste URL, screenshot, or brand kit description here]
+```
+
+The anti-hallucination clause ("if you cannot identify... write unknown") is load-bearing — the failure mode without it is plausible-but-wrong typography names that the operator does not catch until they brief Claude Design and the output drifts.
+
+Source for this extractor: community pattern at `https://github.com/rohitg00/awesome-claude-design/blob/main/prompts/brand-to-design-md.md`, adapted.
+
+---
+
+## 4. DESIGN.md failure modes
+
+Four failure modes the operator should know before adopting DESIGN.md as a workflow primitive.
+
+### Vision-token cost penalty
+
+If the DESIGN.md is uploaded as an image (screenshot of a brand page) rather than as text, Claude Design pays a vision-token cost on every generation. Practitioner walkthroughs (Xinran Ma's documented experience in `research/03`) report meaningful quota burn from image-based DESIGN.md anchors. Use text-form DESIGN.md whenever possible.
+
+### Per-user quota not pooled
+
+Anthropic does not pool Claude Design quota across team members. A team using a shared DESIGN.md will not share quota burn — each member pays separately. Plan project workflow accordingly (research/04 documents community-observed Pro burn of roughly 25-30 minutes; Max roughly 60-90).
+
+### Long-session degradation
+
+DESIGN.md adherence appears to degrade in the back third of a long session. Opus 4.7 quality drops at the 40-50% context mark (`https://anthropic.com/engineering/harness-design-long-running-apps`); DESIGN.md is part of context, so its enforcement weakens accordingly. Session-break heuristics in `references/03-iteration-and-session.md` apply.
+
+### Post-export drift
+
+When an artifact is exported (PPTX, PDF, Code-handoff), the DESIGN.md does not travel with it. Downstream editing tools — PowerPoint, Adobe, Code IDEs — apply their own defaults. Validate the rendered output against DESIGN.md after export.
+
+---
+
+## 5. DESIGN.md sanity-check pattern
+
+A community-converged test for DESIGN.md adherence: generate three artifacts in the same Claude Design project using deliberately different intent presets (designs, slides, one-pagers) and confirm that all three respect the DESIGN.md color palette, typography, and component-styling rules. If one preset drifts more than the others, the DESIGN.md needs sharpening on the section the drifting preset emphasized.
+
+The community attribution for this pattern comes from a `theadpharm` Substack walkthrough (cited in `research/03`). It is a smoke test, not a guarantee — but it catches the common case where DESIGN.md is too general to constrain the model.
+
+---
+
+## Sources
+
+- `https://support.claude.com/en/articles/14604397-set-up-your-design-system-in-claude-design` — Anthropic's design-system setup concept
+- `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` — Anthropic's AI-slop avoid-list and four design dimensions
+- `https://claude.com/blog/improving-frontend-design-through-skills` — Anthropic blog on default-avoidance
+- `https://anthropic.com/engineering/harness-design-long-running-apps` — context-degradation framing
+- `https://github.com/rohitg00/awesome-claude-design` — community awesome-list, brand-to-DESIGN.md extractor source
+- `https://github.com/VoltAgent/awesome-claude-design` — community awesome-list, alternate 9-section structure references
+
+Re-research trigger: Anthropic publishing an official DESIGN.md structure; either community awesome-list reaching consensus on a different section ordering; new failure mode surfaced in practitioner posts.

plugins/claude-design/skills/claude-design-facilitator/references/03-iteration-and-session.md

@@ -0,0 +1,256 @@
+# Iteration and session — Tweak / Comment / Chat cascade and recovery
+
+**Last updated:** 2026-05-17 | **Verified:** research/04-iteration-mechanics-recovery.md
+**Status:** Beta (Labs research preview)
+**Captured-on date:** 2026-05-16
+
+This file documents three things in order of operational urgency: which iteration surface to use when, when to break a session, and how to recover when iteration stops landing. The cost asymmetry between Tweak / Comment / Chat is the single largest leverage point in a Claude Design workflow.
+
+---
+
+## 1. The three-surface cascade
+
+Claude Design exposes three edit surfaces with asymmetric token costs and asymmetric scope:
+
+| Surface | Token cost | Scope | When to use |
+|---------|-----------|-------|-------------|
+| Tweak panel | Zero | Surgical, per-control | Anything Claude pre-derived at generation time |
+| Inline comment | Zero on success | Component-scoped, in-component | Targeted in-component text or visual change |
+| Chat | One full turn | Whole artifact | Structural change, aesthetic pivot, new section |
+
+### Tweak panel
+
+The Tweak panel is the per-artifact set of controls and sliders Claude pre-derives during generation. Each artifact comes with its own Tweak surface — section reordering, variant swap, density slider, spacing scale, color temperature, typography scale, padding / radius / shadow. The controls are surgical and zero-token: applying them does not consume a chat turn or budget time. They are also lossy-free — the artifact does not regenerate; the controls operate on the existing render.
+
+Tweak panel coverage is per-artifact. If Claude did not pre-derive a control for a dimension, that dimension is not Tweak-editable. The first move is always to check the Tweak panel: most dimensions an operator wants to refine after the first generation are already there.
+
+Operator-actionable mantra (the synthesis from `research/04`):
+
+> Anything Claude pre-derives at generation time is surgical thereafter; new controls cost one chat turn for setup.
+
+### Inline comments
+
+The comment surface lets the operator click anywhere on the rendered artifact and attach a directive — "make this section narrower", "use a darker shade for this header", "remove this icon". Comments are surgical when the change is in-component (text edit, color tweak, sizing within an existing container) and they cost zero tokens on success.
+
+Two failure modes the operator should know:
+
+1. **Vanish bug** — comments sometimes disappear after submission with no edit applied. Anthropic has acknowledged this (community-cited; the workaround is to paste the comment text directly into chat as a follow-up turn).
+2. **Structural-container failure** — comments cannot add a new structural container (a new section, a new column, a new modal). The model interprets the directive but produces no change, or makes an irrelevant change. For new containers, escalate to chat.
+
+### Chat
+
+Chat is the full-regeneration surface. Any structural change, aesthetic pivot, multi-component change, or new section requires a chat turn. The artifact regenerates against the new prompt; previous Tweak panel and comment state may not survive intact.
+
+Chat costs one full turn — count it against the session budget. Use the layer-1-through-5 framework (`references/01-prompt-fundamentals.md`) for the chat prompt rather than free-form natural language.
+
+### Per-operation surgical-vs-regen catalogue
+
+A practical lookup for which surface fits which operation (synthesized from `research/04`):
+
+| Operation | Surface | Notes |
+|-----------|---------|-------|
+| Section reordering | Tweak | Pre-derived if Claude includes a section-order control |
+| Variant swap (component variant A → B) | Tweak | If Claude generated multiple variants |
+| Density slider (compact / cozy / comfortable) | Tweak | Common Tweak control |
+| Spacing scale (--space-* token shift) | Tweak | Common Tweak control |
+| Color temperature (warmer / cooler) | Tweak | If Claude derives this dimension |
+| Typography scale (modular scale shift) | Tweak | If Claude derives this dimension |
+| Padding / radius / shadow per component | Tweak | Common Tweak controls |
+| Text edit in existing component | Comment | Surgical, in-component |
+| Color tweak in existing component | Comment | Surgical, in-component |
+| Add a new section | Chat | Structural — Tweak / Comment cannot do this |
+| Aesthetic pivot (industrial → editorial) | Chat | Full regen — name the new aesthetic |
+| Multi-component change (revise hero + CTA + footer together) | Chat | Full regen — too broad for Comment |
+| New interaction state (hover / disabled / active) | Chat | Structural — requires regeneration |
+
+---
+
+## 2. Anthropic-published surgical/structural split
+
+Anthropic's verbatim framing in `https://support.claude.com/en/articles/14604416-get-started-with-claude-design`: the Claude Design canvas distinguishes between *surgical edits* (per-element changes that do not regenerate the artifact) and *structural edits* (new components, new layouts, aesthetic pivots that require regeneration). The Tweak panel and inline comments are surgical surfaces; chat is the structural surface.
+
+The operator's job is to identify which kind of edit a given change is *before* picking the surface. A surgical change attempted via chat regenerates the whole artifact and burns a turn; a structural change attempted via comment fails silently and wastes time. Misclassification is the dominant inefficiency in a long Claude Design session.
+
+Source: `https://support.claude.com/en/articles/14604416-get-started-with-claude-design`.
+
+---
+
+## 3. Anthropic-engineering refine-vs-pivot rule
+
+Anthropic publishes a verbatim refine-vs-pivot guideline in `https://anthropic.com/engineering/harness-design-long-running-apps`:
+
+> Pivot to an entirely different aesthetic if the approach wasn't working — iteration within a bad direction compounds the failure.
+
+The companion warning, also verbatim from the same source: design quality is **non-monotonic** across iterations. Turn 4 can be worse than turn 3 on a critical criterion. The framing matters because the operator's intuition pushes toward continued refinement; the discipline is to recognize a stuck state and pivot.
+
+Operational signal that a pivot is needed (community-converged from `research/04`):
+
+- Three consecutive comments have failed to land
+- The aesthetic is drifting back to the AI-slop default on each regeneration
+- The operator finds themselves explaining what they *don't* want more than what they *do* want
+- The artifact is converging on a different audience than the brief
+
+Pivot move: rewrite the layer-2 aesthetic-family specification entirely, then ship a fresh chat turn against the new family. Do not try to incrementally edit out of a stuck state.
+
+Source: `https://anthropic.com/engineering/harness-design-long-running-apps`.
+
+---
+
+## 4. Session-management heuristics
+
+Four heuristics — one Anthropic-published, three community-converged — govern when to break a session.
+
+### 4-screen inflection (community-converged)
+
+Practitioners across multiple posts in `research/04` document a quality inflection around the fourth screen of context in a Claude Design session. Before screen four, edits land cleanly; after, comments start vanishing, aesthetic defaults creep back, and Tweak controls feel less precise. The exact mechanism is unclear (context-window pressure on Opus 4.7 + cumulative DESIGN.md re-reads + cumulative artifact history), but the pattern is consistent.
+
+Practitioner mantra: **at screen four, save what you have and start a new session.**
+
+### Opus 4.7 context degradation (Anthropic-published)
+
+`https://anthropic.com/engineering/harness-design-long-running-apps` publishes the verbatim observation: Opus 4.7 quality degrades noticeably at the 40-50% context-window mark. Claude Design sessions accumulate context faster than chat sessions (each generation includes the artifact in context for subsequent turns); the 40-50% mark arrives sooner.
+
+### Quota burn (community-observed)
+
+Practitioner walkthroughs cited in `research/04` report quota burn rates as of 2026-04-28 per MindStudio's documented walkthrough — these are community observations, not Anthropic-published limits and may shift:
+
+- **Pro plan:** ~25-30 minutes of active design before quota becomes the binding constraint
+- **Max plan:** ~60-90 minutes of active design before quota becomes the binding constraint
+
+These numbers assume continuous active design (chat turns, regenerations, image-form DESIGN.md anchors). Tweak panel and comment surface usage does not burn quota.
+
+Captured-on date: 2026-04-28 per `research/04`. Not an Anthropic-published limit.
+
+### Session-break triggers (community-converged)
+
+Three signals that a session has reached its productive end:
+
+- Reorder / density Tweak controls stop landing (the model is not respecting the surgical surface)
+- Chat re-introduces previously-removed defaults (the model is losing the negative constraints)
+- The operator finds themselves repeating the same constraint in three consecutive turns
+
+When two of three trigger together, break the session.
+
+---
+
+## 5. Context-reset prompt
+
+When the operator needs to break a session but does not want to lose what worked, the verbatim community pattern from MindStudio (2026-04-28, cited in `research/04`):
+
+```
+Before we continue, summarize the design system and component decisions
+we've made in this session as a structured markdown document I can use
+as a fresh starting context. Include:
+  - the aesthetic family we converged on
+  - color palette in CSS-variable form
+  - typography decisions (typeface, modular scale, weights)
+  - component patterns we settled on
+  - decisions we made and then reversed (so I don't reintroduce them)
+  - anything we tried that did not work
+```
+
+Paste the produced markdown into a new Claude Design session as the opening context, alongside the original DESIGN.md. The new session starts with the cumulative decisions but a fresh context window.
+
+Captured-on date: 2026-04-28.
+
+---
+
+## 6. Recovery prompt library
+
+Five recovery moves, listed in escalating cost order.
+
+### 6.1 — Break the default aesthetic
+
+The highest-leverage single content asset in this plugin. Adapted with attribution from `https://github.com/rohitg00/awesome-claude-design/blob/main/prompts/break-default-aesthetic.md`. Use when the artifact has drifted toward AI-slop defaults despite negative constraints in the brief.
+
+```
+The current direction has converged on a generic default. I want a
+distinct visual direction. Constraints:
+
+1. Pick ONE aesthetic family and commit to it. Name a concrete reference
+   (an existing product, an editorial source, a design movement). No
+   "modern SaaS", no "clean", no "minimal" as the named family — those
+   are defaults, not directions.
+
+2. Do not produce any of:
+   - Inter, Roboto, Arial, Space Grotesk as primary typeface
+   - Purple gradients on white backgrounds
+   - Three-column feature grids with icon + headline + line
+   - Centered-hero-with-single-CTA layout default
+   - Glassmorphism, neumorphism, generic "modern" defaults
+
+3. Before generating: list four candidate directions matching the goal
+   and audience. For each:
+   - Aesthetic family (with concrete reference)
+   - Color palette in hex
+   - Typeface (named)
+   - One-line rationale tying it to goal + audience
+   Wait for me to pick one. Do NOT default to "the most common modern
+   approach."
+
+4. The aesthetic should surprise without being weird. If you're tempted
+   to write "professional" or "balanced" or "approachable", stop.
+   Those words signal default-mode reasoning.
+```
+
+### 6.2 — Fix the system, not the prompt
+
+Community pattern: when iteration is stuck, the prompt is rarely the problem. The DESIGN.md is. Reopen the DESIGN.md, audit the section the artifact is drifting on (typography, color, components), tighten that section, re-upload, then re-generate.
+
+The instinct is to add more constraints to the chat prompt. The discipline is to fix the upstream anchor.
+
+### 6.3 — Edit previous message rather than send a new one
+
+Community-documented workaround for context-bloat: when the previous prompt almost worked but missed one detail, edit the previous message rather than send a new turn. Claude Design re-generates from the edited message without adding to context. This is in `research/04` as a low-cost recovery move for the case where a single-word change would have fixed the output.
+
+### 6.4 — 3-failed-comment escalation rule
+
+If three consecutive inline comments fail to land, stop commenting and escalate to chat. The comment surface is signaling that the model is not in a state to respect surgical edits — either the artifact has drifted too far from the brief, the context window is pressured, or the change is actually structural and was misclassified.
+
+Escalation move: paste the failed comment text directly into a chat turn, prefaced with "the inline comment surface is not landing on this; please apply this change via regeneration".
+
+### 6.5 — Model downshift escalator
+
+When Opus 4.7 generations are non-monotonic in quality and Tweak / Comment / chat moves all stop landing, the recovery move is to start a fresh session at a different model. The downshift sequence community-converged on (per `research/04`):
+
+- Opus 4.7 → Opus 4.6 (same family, less context-pressure-sensitive)
+- Opus 4.6 → Sonnet 4.6 (faster, less context-sensitive, sometimes better at constraint-following on tight briefs)
+
+Claude Design pins to Opus 4.7. The downshift happens by moving the work to a different Anthropic surface (Claude.com chat with a model picker) for the constraint-tightening turn, then bringing the result back to Claude Design as a new session anchor.
+
+### 6.6 — Verbal save-pattern
+
+When the operator wants to preserve what works but try a different direction without losing the current state, the community pattern is to **verbally save** in chat:
+
+```
+Save what we have. The current direction is good but I want to explore
+a completely different aesthetic for comparison. Acknowledge this save,
+then start fresh on a new direction without referencing the saved state.
+We may come back to it.
+```
+
+The "save" is verbal — Claude Design has no version-tree primitive — but it signals to the model that the previous direction is preserved in the operator's mental model and the next turn is exploratory.
+
+---
+
+## 7. What Claude Design lacks
+
+Four primitives that exist in adjacent Anthropic surfaces but not in Claude Design today. The plugin must never promise these:
+
+- **No `/rewind`** — Anthropic Code has a `/rewind` primitive that reverts to a prior conversational state. Claude Design does not.
+- **No version history** — there is no Tweak-history, no Comment-history, no chat-thread-fork primitive. The verbal save-pattern (Section 6.6) is the closest substitute.
+- **No two-way handoff** — once an artifact is exported to Claude Code, there is no path back into Claude Design. Re-import requires a screenshot → new Claude Design session (lossy). See `references/04-handoff-and-scope.md`.
+- **No branching** — Claude Design cannot fork a session into parallel directions and compare. The verbal save-pattern is the only branching primitive.
+
+When the operator asks for any of these, name the constraint and offer the closest substitute (verbal save-pattern, multi-session-with-context-reset-prompt, manual screenshot archive).
+
+---
+
+## Sources
+
+- `https://support.claude.com/en/articles/14604416-get-started-with-claude-design` — surgical / structural edit split, intent presets
+- `https://anthropic.com/engineering/harness-design-long-running-apps` — refine-vs-pivot rule, non-monotonic improvement, 40-50% context degradation, design grading criteria
+- `https://github.com/rohitg00/awesome-claude-design` — community recovery prompts, break-default-aesthetic source
+- `https://claude.com/blog/improving-frontend-design-through-skills` — AI-slop avoid-list applied during recovery
+
+Re-research trigger: Anthropic publishing version-history or branching primitives; community 4-screen inflection no longer reproducing; quota mechanics shifting (Pro / Max minute counts have a 2026-04-28 captured-on date and are community-observed, not Anthropic-published).

plugins/claude-design/skills/claude-design-facilitator/references/04-handoff-and-scope.md

@@ -0,0 +1,157 @@
+# Handoff and scope fence
+
+**Last updated:** 2026-05-17 | **Verified:** research/04-iteration-mechanics-recovery.md + research/05-anthropic-design-plugin-scope.md
+**Status:** Beta (Labs research preview)
+**Captured-on date:** 2026-05-16
+
+This file documents two things: how Claude Design hands artifacts off to downstream tools (Claude Code, PowerPoint, PDF, Canva), and how this plugin (`claude-design`) fits next to Anthropic's official `knowledge-work-plugins/design`. The scope fence is load-bearing — getting it wrong duplicates Anthropic's command surface and adds nothing.
+
+---
+
+## 1. Handoff bundle contents
+
+When the operator chooses Claude Code handoff as the destination, Claude Design produces a bundle containing — verbatim per `https://anthropic.com/news/claude-design-anthropic-labs` and `https://support.claude.com/en/articles/14604416-get-started-with-claude-design`:
+
+- **Machine-readable component spec** — a JSON-shaped description of the components in the artifact, with names, props, and variants
+- **Design tokens** — colors, typography, spacing, radii in token form (CSS variables or JSON tokens)
+- **Layout hierarchy** — the page / screen structure as a tree
+- **Referenced assets** — images, icons, fonts referenced in the artifact, bundled
+- **Standalone HTML + inline CSS + JS** — a self-contained render that runs without Claude Design
+- **Per-state screenshots** — visual snapshots of each interaction state (default, hover, active, disabled, focused)
+- **PM-annotated notes** — annotations Claude Design surfaces about design decisions, edge cases, and trade-offs
+- **Stack / framework README** — a guide to which framework conventions the artifact assumes (e.g., React + Tailwind, or vanilla HTML)
+
+The bundle is generated once on export. It does not regenerate when the operator iterates the artifact further inside Claude Design — the operator must re-export to pick up changes.
+
+Sources: `https://anthropic.com/news/claude-design-anthropic-labs` and `https://support.claude.com/en/articles/14604416-get-started-with-claude-design`.
+
+---
+
+## 2. Direction is one-way
+
+The Design → Code handoff direction is one-way. Once the bundle is exported and the operator starts iterating in Claude Code (or any code editor), there is no return path to Claude Design. The component spec, design tokens, and standalone HTML continue to live in the code repository; Claude Design has no concept of "re-ingest from code".
+
+If the operator wants to visit the visual surface again after engineering iteration, the only path is:
+
+1. Screenshot the current Claude Code render
+2. Open a new Claude Design session
+3. Paste the screenshot as the starting visual reference
+4. Brief Claude Design from scratch using layer-1-through-5 framework
+
+This is lossy: the design tokens, component spec, and PM notes from the original bundle do not travel into the new Claude Design session. The new session inherits only what the screenshot communicates.
+
+Operational consequences:
+
+- **Finalize visual decisions inside Claude Design before exporting.** The Tweak panel and inline comments are free; chat turns inside Claude Design are budget-priced; engineering iteration in code is budget-free but the visual round-trip is one-way. Order accordingly.
+- **Export once, intentionally.** Bundling everything in a single export (per Section 6 below) costs one chat turn; bundling screen-by-screen costs N turns and consumes budget faster.
+- **Plan for asymmetric revisit.** When the engineering implementation diverges from the design intent and the operator wants a designer review, schedule that revisit as a fresh Claude Design session, not as an extension of the original session.
+
+Practitioner consensus on this point is documented at `https://claudefa.st/blog/guide/mechanics/claude-design-handoff` (community source). Anthropic frames the same one-way property implicitly in the get-started article — the handoff is described as an export, not a connection.
+
+---
+
+## 3. Workflow recommendation
+
+The recommended flow for any Claude Design artifact destined for engineering implementation:
+
+1. **Iterate visually in Claude Design until the artifact is shippable.** Use Tweak panel and inline comments first; chat turns for structural and aesthetic changes.
+2. **Validate the destination format before exporting.** If destination is PPTX, verify the text-as-text count (see Section 6 token cost trap). If destination is HTML standalone, render it in the target browser at the target viewport. If destination is PDF, check the interactive-element handling.
+3. **Export the full bundle once.** Bundle all screens in one export, not per-screen. The token cost trap (Section 6) compounds with per-screen exports.
+4. **Iterate engineering inside Claude Code or the code editor.** Use Claude Code's `/edit` and chat surfaces. Pull the design tokens from the bundle into the repository's styling layer.
+5. **For post-design design-quality work — critique, accessibility audit, UX copy review, design-system audit, engineering handoff guidance — install Anthropic's official plugin (Section 4 below).**
+6. **If a visual revisit becomes necessary later, accept the one-way cost.** Open a new Claude Design session against a screenshot; do not try to re-extend the original session.
+
+This is the flow per Section 4's scope-fence reasoning: this plugin covers the upstream lifecycle; Anthropic's covers downstream.
+
+---
+
+## 4. Scope fence vs Anthropic's `knowledge-work-plugins/design`
+
+Anthropic ships an official Claude Code plugin at `https://claude.com/plugins/design` (source: `https://github.com/anthropics/knowledge-work-plugins`). It is skill-driven, Apache 2.0 licensed (MIT-equivalent), and ships six slash-commands operating on **existing** artifacts (Figma URLs, screenshots, copy snippets).
+
+The lifecycle-stage coverage map:
+
+| Lifecycle stage | This plugin (claude-design) | Anthropic's plugin (knowledge-work-plugins/design) |
+|-----------------|------------------------------|----------------------------------------------------|
+| Idea ingestion | ✓ Disambiguate surface, intent preset, audience | — |
+| Intent-preset selection | ✓ Eight presets, evidence-grade labelled | — |
+| Prompt engineering | ✓ Five-layer stack + per-preset patterns | — |
+| Copy-paste delivery | ✓ Composed prompt block | — |
+| Iteration coaching | ✓ Tweak / Comment / Chat cascade, session economics | — |
+| Ship-readiness | ✓ Operator-attested + recommend downstream tool | — |
+| Critique | — | ✓ `/critique` |
+| Accessibility audit | — | ✓ `/accessibility` |
+| UX copy review | — | ✓ `/ux-copy` |
+| Research synthesis | — | ✓ `/research-synthesis` |
+| Design-system audit | — | ✓ `/design-system` |
+| Engineering handoff | — | ✓ `/handoff` |
+
+There is no functional overlap. This plugin produces prompts that go into Claude Design; Anthropic's plugin operates on artifacts that already exist. The split is clean by design — both plugins document the other as the lifecycle complement.
+
+**Forbidden command-name list.** This plugin must NOT ship slash-commands with any of these names (with or without a `claude-design:` namespace prefix):
+
+- `/critique`
+- `/accessibility`
+- `/ux-copy`
+- `/research-synthesis`
+- `/design-system`
+- `/handoff`
+
+`tests/validate-plugin.sh` assertion (h) enforces this mechanically. The rationale is collision-avoidance — if both plugins are installed and both ship `/critique`, command resolution becomes ambiguous and one or the other silently fails. The cleaner solution is: this plugin does not own those commands.
+
+---
+
+## 5. Recommended downstream tool
+
+When the operator finishes the Claude Design lifecycle (artifact exists, exported, ready for review), surface the downstream tool installation as the next step:
+
+```
+claude plugins add knowledge-work-plugins/design
+```
+
+In a new Claude Code session with that plugin installed:
+
+- Run `/critique <path-or-URL>` to get a design critique
+- Run `/accessibility <path-or-URL>` for a WCAG audit
+- Run `/ux-copy <path-or-URL>` for copy review
+- Run `/research-synthesis` if the operator has user-research notes to synthesize
+- Run `/design-system <path-or-URL>` for design-system consistency check
+- Run `/handoff <path-or-URL>` for engineering-handoff guidance
+
+Sources: `https://claude.com/plugins/design` and `https://github.com/anthropics/knowledge-work-plugins`.
+
+The plugin is Apache 2.0, free, and maintained by Anthropic. There is no commercial trade-off; it is the canonical downstream tool.
+
+---
+
+## 6. Token cost trap — bundle all screens in one export
+
+Practitioner-documented failure mode: exporting screen-by-screen instead of bundling all screens in one export. The community-cited reference is `token-budget-claude-design.md` (cited in `research/04` as one of the highest-leverage cost-management items).
+
+The mechanism: each export turn passes the current artifact state through Opus 4.7 to produce the bundle. For an N-screen artifact, N separate exports run N separate bundle generations and burn N chat turns. Bundling all N screens in a single export runs one bundle generation against the cumulative state and burns one chat turn.
+
+The bundling prompt pattern:
+
+```
+Generate the full export bundle covering all N screens of this artifact:
+[screen 1: name], [screen 2: name], ... [screen N: name].
+Include for each screen: HTML standalone, design tokens, component spec,
+per-state screenshots, PM notes. Bundle as a single download.
+```
+
+Multi-screen artifacts (prototypes, slide decks, multi-page landing pages) benefit most from this discipline. Single-screen artifacts (a single dashboard, a single one-pager) are not affected because there is only one bundle to generate.
+
+If the operator has already paid the per-screen cost and noticed mid-flight, the recovery is to abandon partial exports and run one final bundling export against the cumulative artifact state.
+
+---
+
+## Sources
+
+- `https://anthropic.com/news/claude-design-anthropic-labs` — Anthropic Labs launch, bundle contents
+- `https://support.claude.com/en/articles/14604416-get-started-with-claude-design` — get-started, handoff bundle contents
+- `https://claude.com/plugins/design` — Anthropic's official knowledge-work-plugins/design plugin
+- `https://github.com/anthropics/knowledge-work-plugins` — source for the official plugin
+- `https://anthropic.com/engineering/harness-design-long-running-apps` — design grading framing
+- `https://claudefa.st/blog/guide/mechanics/claude-design-handoff` — community operational consensus on one-way direction
+
+Re-research trigger: Anthropic announcing a two-way handoff primitive; `knowledge-work-plugins/design` adding or removing slash-commands; bundle contents changing materially; this plugin and Anthropic's plugin overlap emerging.

plugins/claude-design/skills/claude-design-facilitator/references/presets/designs.md

@@ -0,0 +1,183 @@
+# Preset: designs
+
+**Last updated:** 2026-05-17 | **Verified:** research/03-prompt-patterns-intent-presets.md
+**Evidence grade:** Anthropic-documented + community-validated
+**Captured-on date:** 2026-05-16
+
+The `designs` intent preset is Claude Design's generic generation mode. It covers dashboards, components, layouts, and design explorations that do not fit into one of the more specialised presets (prototypes, slides, one-pagers, etc.). It is the preset operators reach for when the goal is "produce a high-quality visual artifact" rather than a destination-shaped artifact.
+
+This file documents the `designs` preset across six dimensions: what it is, when to use it, Anthropic's published prompt patterns, community uplift, critical caveats, and one end-to-end worked prompt.
+
+---
+
+## (a) What this preset is
+
+Anthropic's launch post (`https://anthropic.com/news/claude-design-anthropic-labs`) describes `designs` as the default-mode preset — the substrate every other preset effectively inherits from, with destination shaping layered on top. Output is HTML + React + inline CSS, viewable in the Claude Design canvas, exportable to PDF / HTML standalone / Code-handoff.
+
+Two Anthropic primary sources ground this preset:
+
+- The Anthropic-engineering blog `https://anthropic.com/engineering/harness-design-long-running-apps` publishes the four design grading criteria (design quality, originality, craft, functionality) that the `designs` preset is optimised against.
+- The frontend-design open-source skill at `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` documents Anthropic's verbatim Design-Thinking Framework — **Purpose**, **Tone**, **Constraints**, **Differentiation** — and the verbatim AI-slop avoid-list.
+
+The frontend-design skill is the closest thing Anthropic publishes to a `designs`-preset system prompt. Read it whenever the operator wants to understand what Claude Design is internally optimising for.
+
+---
+
+## (b) When to use it
+
+Pick `designs` when the goal is generic, exploratory, or composite. The decision matrix:
+
+| Operator goal | Preset |
+|---------------|--------|
+| Generic dashboard, component library exploration, design system playground | **designs** |
+| Interactive product flow for usability testing | prototypes |
+| Presentation for stakeholders | slides |
+| Single-page memo or leave-behind | one-pagers |
+| Low-fi structural layout for early review | wireframes-mockups |
+| Investor / external pitch | pitch-decks |
+| Landing page, social variant, marketing asset | marketing-collateral |
+| Code-powered prototype with voice / video / shaders / 3D | frontier-design (experimental — see preset file) |
+
+If the operator is uncertain between `designs` and `prototypes`, the distinguishing question is: **is this for usability testing?** Yes → prototypes. No → designs.
+
+If uncertain between `designs` and `marketing-collateral`, the distinguishing question is: **is this destined for a marketing surface (landing page, social, ad)?** Yes → marketing-collateral. No → designs.
+
+---
+
+## (c) Anthropic-published prompt patterns
+
+### The Design-Thinking Framework (verbatim from frontend-design/SKILL.md)
+
+Anthropic's `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` publishes the verbatim four-part framework Claude Design uses when reasoning about a design:
+
+- **Purpose** — what is the artifact for? Match every aesthetic decision to the purpose.
+- **Tone** — what emotional register fits the audience and the purpose? Energetic, calm, authoritative, playful, terse?
+- **Constraints** — what cannot be changed? Brand colors, typeface restrictions, layout rules, accessibility minimums.
+- **Differentiation** — what makes this artifact distinct from the convergent middle-ground default? Name the differentiation explicitly.
+
+Use this framework as a pre-brief check before composing a layer-1-through-5 prompt (see `../01-prompt-fundamentals.md`). If any of the four parts is fuzzy, sharpen it before drafting.
+
+### Verbatim AI-slop avoid-list
+
+Anthropic's frontend-design skill + the blog post `https://claude.com/blog/improving-frontend-design-through-skills` publish the verbatim banned-items list used in layer 3 of the prompt stack. See `../01-prompt-fundamentals.md` Section "Layer 3" for the full list. The `designs` preset inherits this list — it is not optional.
+
+### Anthropic's verbatim canonical examples
+
+The Anthropic get-started article `https://support.claude.com/en/articles/14604416-get-started-with-claude-design` publishes three verbatim canonical examples (dashboard, mobile onboarding, landing page) demonstrating the Goal / Layout / Content / Audience framework. Read them as the reference shape for a first prompt against `designs`. Reproduced in full in `../01-prompt-fundamentals.md` Section "Layer 1".
+
+---
+
+## (d) Community uplift
+
+Three community-converged patterns extend Anthropic's published material for the `designs` preset.
+
+### Real-data injection over lorem ipsum
+
+Victor Dibia's documented pattern (`research/03`): substitute realistic placeholder content rather than lorem ipsum. The model defaults to convergent middle-ground content when content is unspecified; named placeholders ("Today's MRR: $48,200", "Last 24h error rate: 0.12%") anchor the model to real-shaped output.
+
+For dashboards specifically: use realistic metric values, realistic timestamps, realistic user names. The visual difference between a chart with `$3,200` / `$4,500` / `$2,800` and a chart with `$XXX` / `$YYY` / `$ZZZ` is large — Claude Design will infer typography spacing and component sizing from the named values.
+
+### Explicit modular scale and weight palette
+
+Community pattern (research/03): name the typographic modular scale and weight palette in the brief rather than letting the model default. The `1.250` (minor third) scale fits dense informational artifacts; the `1.333` (perfect fourth) scale fits marketing pages. Weight palettes converge on `500 body / 600 emphasized / 700 headings`.
+
+### Specify the negative aesthetic family
+
+Beyond layer-3 negative constraints (which name specific banned items), community practice (research/03) is to name an entire negative aesthetic family — "not modern SaaS", "not playful illustrated", "not corporate professional" — to push the model out of its default neighbourhood. The model interprets aesthetic-family naming as a strong signal even in the negative.
+
+---
+
+## (e) Critical caveats
+
+Three caveats specific to the `designs` preset.
+
+### Default-aesthetic drift on iteration
+
+The `designs` preset is most susceptible to default-aesthetic drift because it has no destination-shaped constraint pulling it toward a specific genre. Watch for drift back to AI-slop defaults across iterations — the `references/03-iteration-and-session.md` "break-default-aesthetic" recovery prompt is targeted at exactly this drift.
+
+### Non-monotonic improvement across iterations
+
+`https://anthropic.com/engineering/harness-design-long-running-apps` documents that quality across iterations is not strictly increasing. Turn 4 can be worse than turn 3 on design quality, originality, or craft. The recovery move (pivot, not refine) is in `../03-iteration-and-session.md`.
+
+### Component spec coherence
+
+For dashboards and component libraries specifically, the export bundle's machine-readable component spec is load-bearing for engineering handoff. Ensure the artifact has coherent component definitions (named, with consistent variants) before exporting — otherwise the component spec will be partial and the engineering implementation will diverge.
+
+---
+
+## (f) One end-to-end worked prompt — layers 1 + 2a + 3 composed
+
+Goal: an admin dashboard for an analytics product, audience is data engineers.
+
+```
+Goal: An admin dashboard for monitoring data-pipeline freshness across
+      120 tables, sorted by last-successful-load timestamp
+Layout: Header with environment switcher + global time-window selector;
+        top metrics row (4 KPIs: tables behind SLA, tables current,
+        tables stale, tables errored); main panel with stacked area
+        chart showing freshness over the last 24 hours; sortable table
+        below with 120 rows; alerts sidebar
+Content: Realistic table names (orders, customers, inventory,
+         user_events, sessions, etc.); realistic timestamps (last
+         successful load within the last 6 hours for most, some at
+         12 hours, some at 48 hours); realistic error rates (0.01% to
+         3.2%)
+Audience: Data engineers, on-call rotation, ages 25-50, comfortable
+          with dense interfaces, need to scan and triage quickly
+
+Aesthetic family: industrial-utilitarian, slate-monochrome
+Color palette (CSS hex):
+  --color-bg:       #E9ECEC
+  --color-surface:  #C9D2D4
+  --color-muted:    #8C9A9E
+  --color-fg:       #44545B
+  --color-ink:      #11171B
+  --color-accent:   #4A6FA5
+  --color-error:    #B23A48
+  --color-warning:  #C89B3F
+Typography: square angular sans-serif (Söhne preferred, Inter Variable
+            fallback); no rounded glyphs; modular scale 1.250
+Corner radius: 4px throughout — no pill shapes
+Motion: transition: all 160ms ease-out
+Density: dense (32px table rows, 8px card padding)
+Surface: flat — no shadows, borders define edges
+
+Design-Thinking Framework:
+  Purpose: enable on-call triage in under 60 seconds per incident
+  Tone: terse, signal-dense, no decorative copy
+  Constraints: 32px row height minimum (accessibility), accent reserved
+               for actionable items only
+  Differentiation: this is a data-engineer tool, not a marketing
+                   dashboard — no card-style metric tiles, no playful
+                   illustrations, no progress-ring widgets
+
+Negative constraints — do not produce any of:
+  - Inter, Roboto, Arial, or Space Grotesk as primary typeface
+  - Purple gradients on white backgrounds
+  - Card-style KPI tiles with shadows and rounded corners
+  - Centered-hero with single CTA
+  - Bouncy spring easing on hover
+  - Pulse animations on idle elements
+  - Glassmorphism, neumorphism, generic "modern SaaS" defaults
+
+If you find yourself defaulting to any of these, stop and ask me to
+clarify the aesthetic before continuing.
+```
+
+Expected follow-up turns:
+
+1. Turn 2: add layer 4 (typography modular scale specifics, semantic color roles, motion easing curves)
+2. Turn 3: add layer 5 (grading criteria weighting — craft and functionality at 0.4 and 0.3, design quality 0.2, originality 0.1)
+3. Turn 4+: Tweak panel takes over for surgical edits
+
+---
+
+## Sources
+
+- `https://anthropic.com/news/claude-design-anthropic-labs` — preset enumeration, launch post
+- `https://support.claude.com/en/articles/14604416-get-started-with-claude-design` — GLCA framework, three canonical examples
+- `https://anthropic.com/engineering/harness-design-long-running-apps` — design grading criteria, non-monotonic improvement
+- `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` — Design-Thinking Framework, AI-slop avoid-list
+- `https://claude.com/blog/improving-frontend-design-through-skills` — default-avoidance blog post
+
+Re-research trigger: Anthropic updating the Design-Thinking Framework; new canonical examples added to get-started article; AI-slop avoid-list materially extended.

plugins/claude-design/skills/claude-design-facilitator/references/presets/frontier-design.md

@@ -0,0 +1,149 @@
+# Preset: frontier-design
+
+**Last updated:** 2026-05-17 | **Verified:** research/03-prompt-patterns-intent-presets.md
+
+Evidence grade: Experimental — no validated practitioner pattern as of 2026-05-16. Frontier design is currently marketing language for "elaborate variants of the other presets," not a distinguishable generation mode practitioners can reliably invoke today.
+
+This file documents what Anthropic publishes about the `frontier-design` preset, what practitioners have shipped (nothing verified), what adjacent material exists, and the single experimental pattern the plugin offers — clearly labelled as unverified speculation. The honest position the plugin takes is in Section (e).
+
+---
+
+## (a) What Anthropic says
+
+Anthropic's launch post `https://anthropic.com/news/claude-design-anthropic-labs` describes `frontier-design` in a single sentence (verbatim):
+
+> code-powered prototypes with voice, video, shaders, 3D and built-in AI
+
+This is the entirety of Anthropic's per-preset documentation as of the 2026-05-16 captured-on date. There is no dedicated tutorial, no support article, no canonical prompt set, no Anthropic-published example artifact.
+
+The launch sentence implies the preset targets:
+
+- Code-powered prototypes (not static designs) — implying interactive elements at minimum
+- Voice (audio playback, speech recognition, voice UI)
+- Video (embedded video playback, possibly video-driven UI)
+- Shaders (WebGL, custom GLSL shaders, GPU-driven visual effects)
+- 3D (WebGL 3D scenes, possibly Three.js or similar)
+- Built-in AI (LLM-driven interactions inside the artifact)
+
+Anthropic's framing suggests `frontier-design` is the preset for showpiece artifacts demonstrating Claude Design's outer-edge capabilities — not a workhorse preset like `designs`, `prototypes`, or `slides`.
+
+---
+
+## (b) What practitioners have shipped
+
+Verifiable practitioner outputs as of 2026-05-16: **NONE that we could verify.**
+
+The most explicit acknowledgment of this gap comes from `https://llmx.tech/blog/claude-design-hands-on-review-2026` (cited in `research/03`):
+
+> ...no frontier design assessment provided. The hands-on review covers designs, prototypes, slides, and one-pagers. Frontier design is named in the preset list but received zero hands-on evaluation, because no practitioner artifact has been published demonstrating what the preset produces in practice.
+
+Across the community sources surveyed in `research/03` (Substack walkthroughs, awesome-claude-design lists, Twitter / X threads, MindStudio walkthroughs, sagnikbhattacharya, victordibia, theadpharm, claudefa.st, etc.), no practitioner has published a verifiable frontier-design artifact with prompt, output, and reproduction steps. The preset is named, occasionally referenced, but not demonstrated.
+
+This may change. The preset is new (April 2026 launch); practitioner adoption lags. The `.coverage.md` re-research trigger explicitly flags "first verified frontier-design practitioner artifact ships publicly" as a refresh trigger for this file.
+
+---
+
+## (c) Adjacent material
+
+While no `frontier-design`-specific Anthropic or practitioner material exists, two adjacent sources cover the underlying capabilities Anthropic names.
+
+### Motion and spatial composition — `frontend-design/SKILL.md`
+
+`https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` publishes Anthropic's guidance on motion (easing curves, timing tiers, what to animate and what not to) and spatial composition (typography hierarchy, surface depth, layered backgrounds). These are the building blocks the `frontier-design` preset would extend with voice / video / shaders / 3D, but the building blocks themselves are general-purpose.
+
+### Animated and 3D websites — MindStudio walkthrough
+
+MindStudio's 2026-04-28 walkthrough (cited in `research/03`) covers prompting Claude for animated and 3D websites — but the walkthrough is set in adjacent Anthropic surfaces (Claude.com chat with an HTML artifact), not in `claude.ai/design` with the `frontier-design` preset specifically. The walkthrough is useful for the prompt-engineering pattern (naming GLSL fragment shader constraints, polygon-count budgets, voice-prompt structuring) but is not a frontier-design-preset artifact.
+
+---
+
+## (d) Single experimental pattern (unverified speculation)
+
+One experimental pattern, clearly labelled as unverified, that an operator could try if they want to engage with the preset despite the gap.
+
+The pattern comes from Google's Gemini deep-research output (cited in `research/03`) and carries low confidence. It is a constraint-language pattern for shader and physics elements, adapted from broader frontend-design practice:
+
+```
+[layers 1 through 5 of the standard prompt stack from
+ ../01-prompt-fundamentals.md]
+
+Frontier capabilities to engage:
+
+  Shaders:
+    - One custom GLSL fragment shader applied to the hero region
+    - Shader pattern: [name the visual character — e.g.,
+      "subtle gradient flow with imperceptible noise" or
+      "iridescent surface reacting to cursor position"]
+    - Frame budget: 60fps target on Apple M1 / equivalent
+    - No fullscreen shader-bombs (battery / heat / accessibility)
+
+  3D:
+    - One 3D element in the hero region, scene-bounded (no fullscreen)
+    - Polygon count budget: <50,000 triangles
+    - Lighting: 2-3 light sources max
+    - Camera: fixed or single-axis orbit; no free-camera
+
+  Voice:
+    - [if voice UI relevant] one voice-driven interaction, with
+      visible text-transcript fallback
+    - Speech-recognition language and accent assumptions named
+      explicitly
+
+  Video:
+    - [if video element relevant] embedded video with explicit
+      autoplay/no-autoplay decision; explicit captions decision
+
+  Built-in AI:
+    - [if applicable] one LLM-driven interaction in the artifact
+    - Explicit fallback for when the LLM call fails
+
+Test in target browsers (Chrome, Safari, Firefox) at the target device
+class (M1 / M2 desktop, mid-range mobile). Expect aesthetic drift
+across runs; non-monotonic improvement applies amplified for frontier
+capabilities.
+```
+
+Confidence rating on this pattern: **low**. It is a reasoned extrapolation from frontend-design principles, not a tested frontier-design prompt. If you try it, document what works and what does not — there is a community gap to fill.
+
+---
+
+## (e) The plugin's honest position
+
+The plugin's stance on `frontier-design`:
+
+If you want to attempt frontier design, treat it as a high-fidelity prototype (`prototypes` preset) with extra constraint language for shaders, polygons, voice, video, and built-in AI. Expect aesthetic drift on first generations. Verify that your output works in target browsers before committing chat-turn budget to refinement. Expect that the model's prior on what "frontier design" means may differ from yours — over-specify everything that matters.
+
+Do not assume `frontier-design` produces a categorically different artifact from `prototypes` + extra capability constraints. The launch sentence is suggestive; the practitioner evidence is absent. The preset is marketing language for elaborate prototype variants until proven otherwise.
+
+When the operator names `frontier-design` specifically:
+
+1. Read this file with them
+2. Confirm they have understood the practitioner-evidence gap
+3. Offer the experimental pattern in Section (d) as a starting point, clearly labelled as unverified
+4. Treat the resulting artifact as exploratory — surface what worked and what did not, contribute back to the community gap
+5. Plan for amplified non-monotonic-improvement (`../03-iteration-and-session.md`) — frontier capabilities compound the standard non-monotonic risk
+
+---
+
+## (f) Re-research trigger
+
+This file refreshes when any of the following happens:
+
+- Anthropic publishes a dedicated tutorial, support article, or canonical prompt set for `frontier-design`
+- A verified practitioner artifact appears publicly with prompt + output + reproduction steps
+- The launch-post one-sentence description changes materially
+- A community pattern reaches enough adoption to be cited (not speculation) — the `awesome-claude-design` lists and adjacent practitioner blogs are the primary surfaces to watch
+
+When any of these triggers, update Section (b) to reflect verified material, replace Section (d) with the verified pattern, and re-grade the evidence label from "Experimental" to "Community-only" or "Anthropic-documented + community-validated" as appropriate.
+
+---
+
+## Sources
+
+- `https://anthropic.com/news/claude-design-anthropic-labs` — Anthropic's verbatim one-sentence description (the entirety of Anthropic-published material on this preset)
+- `https://llmx.tech/blog/claude-design-hands-on-review-2026` — community practitioner explicitly noting the frontier-design evaluation gap
+- `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` — adjacent material on motion and spatial composition
+- `https://anthropic.com/engineering/harness-design-long-running-apps` — non-monotonic-improvement framing (amplified here)
+- `https://claude.com/blog/improving-frontend-design-through-skills` — AI-slop avoid-list (composed for frontier prompts)
+
+Re-research trigger: see Section (f). The preset is the most volatile in this plugin's coverage; expect this file to refresh first when Anthropic ships material or practitioners publish artifacts.

plugins/claude-design/skills/claude-design-facilitator/references/presets/marketing-collateral.md

@@ -0,0 +1,218 @@
+# Preset: marketing-collateral
+
+**Last updated:** 2026-05-17 | **Verified:** research/03-prompt-patterns-intent-presets.md
+Evidence grade: Community-only — Anthropic publishes no per-preset prompt patterns for this preset as of 2026-05-16.
+
+Anthropic names `marketing-collateral` in the launch enumeration at `https://anthropic.com/news/claude-design-anthropic-labs` but publishes no dedicated tutorial. The patterns below come from community practitioners; treat them as field-tested but not Anthropic-authoritative. Anthropic's frontend-design open-source skill at `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` is the closest adjacent Anthropic source — it covers landing-page and marketing-site design philosophy without per-preset prompts.
+
+---
+
+## (a) What this preset is
+
+Anthropic launch post one-sentence description: `marketing-collateral` covers landing pages, social variants, banner ads, email creative, and other visual assets in the marketing surface area. Output is typically HTML for landing pages, image-shaped for social and ads.
+
+Distinguishing properties:
+
+- Conversion-oriented — the artifact has a measurable goal (signups, clicks, opens)
+- Multi-format — a single campaign typically needs landing page + social variants + email + ad creative
+- Brand-anchored — marketing collateral lives or dies on brand fidelity; a DESIGN.md is essentially mandatory
+- Variant-heavy — A/B testing assumes multiple variants of the same creative
+
+---
+
+## (b) Why Anthropic published no per-preset guidance
+
+The launch enumeration treats marketing-collateral as a destination shape rather than a distinct generation mode. The frontend-design open-source skill (`https://github.com/anthropics/skills/skills/frontend-design/SKILL.md`) is the closest thing Anthropic publishes — it covers the design-philosophy layer (Purpose / Tone / Constraints / Differentiation) but not marketing-specific prompt patterns.
+
+Community practitioners have built patterns around landing-page composition, social-variant fan-out, and competitor-screenshot extraction (Section c).
+
+---
+
+## (c) Community patterns
+
+### chatprd.ai landing-page workflow
+
+Community pattern from `https://chatprd.ai` (cited in `research/03`): a four-stage landing-page production flow optimised for Claude Design:
+
+1. **Brief stage** — define the audience, the value prop, the one CTA, the proof points. Output: text document, not in Claude Design yet.
+2. **Outline stage** — translate the brief into a section-by-section landing-page outline. Hero, problem, solution, features (3-grid or 4-grid), proof (logos / quotes / numbers), pricing or single-CTA, FAQ, footer. Output: text outline.
+3. **Visual stage** — brief Claude Design from the outline using layers 1-5. First turn produces the landing page; iteration tightens.
+4. **Variant stage** — once the master landing page works, generate variants for A/B testing (different hero, different proof-point ordering, different CTA framing) using the variant-fan-out pattern below.
+
+The four-stage workflow separates copy decisions from visual decisions, which lets the operator iterate each independently. The community-documented failure mode is briefing visual + copy together in one prompt — the model conflates the two and produces a generic landing page.
+
+### Sagnik Bhattacharya variant-fan-out for social
+
+Community pattern from `https://sagnikbhattacharya.com/blog/claude-design` (cited in `research/03`): for social-format collateral (Instagram square, LinkedIn rectangle, Twitter / X aspect), generate N variants in parallel rather than sequentially. The brief pattern:
+
+```
+Generate 6 variants of the [campaign] creative, sized for [format
+spec]. Across the 6:
+  - Vary the headline framing (problem-led, solution-led,
+    proof-led)
+  - Vary the visual hierarchy (text-dominant, image-dominant,
+    balanced)
+  - Vary the color emphasis (accent-dominant, monochrome,
+    high-contrast)
+  - Keep the value prop, audience, and CTA identical across all 6
+
+Output as 6 distinct artifacts I can A/B test.
+```
+
+The pattern produces a campaign-set in one chat turn rather than six iterations.
+
+### Competitor-screenshot visual-reference extraction
+
+Community pattern (cited in `research/03`): when the operator has a competitor's marketing page that visually achieves what they want, screenshot it and brief Claude Design with the screenshot as a visual reference, paired with an explicit "do not copy; extract the visual-language principles" instruction:
+
+```
+The attached screenshot shows [competitor]'s landing page. Do NOT
+copy the structure, the copy, or the layout. DO extract the
+visual-language principles:
+  - typography character (named family + scale + weights)
+  - color temperature and palette structure
+  - visual density (how much whitespace, how many elements per fold)
+  - motion language (if visible from the screenshot or apparent from
+    the brand)
+  - overall aesthetic family (named with concrete reference)
+
+Apply those principles to our landing page, which has a fundamentally
+different structure, copy, and CTA flow. Output our landing page
+respecting the extracted visual language but original in structure.
+```
+
+The pattern is high-leverage when the operator has a clear visual reference but cannot articulate it in DESIGN.md form. The risk: too-literal copying produces a derivative-feeling artifact. Brief the "extract, do not copy" constraint explicitly.
+
+### Slop-fingerprints warning amplified
+
+Marketing collateral is the surface where AI-slop fingerprints are most punishing. The teal gradient + serif headline + blinking status dot + container-on-container + glassmorphism pattern is recognisable across many AI-generated landing pages. Audiences pattern-match on it and discount the artifact. Layer 3 negative constraints apply with extra weight:
+
+```
+Negative constraints — do not produce any of:
+  - Teal-to-blue or teal-to-green gradients
+  - Serif headline on sans-serif body (unless explicitly briefed for
+    editorial direction)
+  - Blinking / pulsing status indicators ("Live", "New", "Updated")
+  - Container-on-container layouts (card-inside-card)
+  - Glassmorphism or neumorphism on any element
+  - Generic "modern SaaS landing page" template defaults
+  - Stock-photo abstract gradient hero imagery
+```
+
+---
+
+## (d) Critical caveats
+
+### Brand fidelity is the dominant failure mode
+
+Marketing collateral without a tight DESIGN.md anchor produces generic output. The brand DESIGN.md is essentially mandatory — see `../02-design-md.md` for the extractor pattern when the operator does not already have one. Validate brand fidelity at every iteration: typeface, color palette, voice (tone of copy), visual density. Brand drift on marketing collateral is more visible to the audience than brand drift on internal artifacts.
+
+### A/B testing requires more than aesthetic variation
+
+The variant-fan-out pattern produces aesthetic variations. For meaningful A/B testing, the variants should test specific hypotheses (does problem-led headline outperform solution-led? does image-dominant outperform text-dominant?) rather than test generic aesthetic variation. Brief the hypotheses explicitly.
+
+### Export-to-image for social formats
+
+Social-format collateral typically exports as PNG or JPG (Claude Design produces HTML; the operator screenshots at the target dimensions). The export is lossy for hover states, interactive elements, and motion. Brief the static state explicitly when the destination is image:
+
+```
+The destination for this creative is a static PNG/JPG export. Generate
+the static state only. No hover states, no interaction logic, no motion.
+```
+
+---
+
+## (e) One worked prompt — layers 1 + 3 composed, four-stage landing-page flow
+
+Goal: a landing page for a developer-tools SaaS product, audience is senior engineers evaluating dev tools.
+
+```
+Goal: A landing page for "ObserveAPI", a developer-tools SaaS product
+      for API observability. The goal: convert senior-engineer
+      visitors to free-trial signups.
+Layout: Hero (above-fold), problem (one paragraph + 3 pain points
+        as labelled rows), solution (one paragraph + product
+        screenshot), features (3-grid), proof (3 customer logos +
+        one quote + one named metric), pricing (single tier + free
+        trial CTA), FAQ (4 questions), footer (links + secondary
+        CTA)
+Content: Real product positioning, real customer logos (placeholder
+         names but realistic shapes), real metric numbers, real
+         FAQ content. No lorem ipsum.
+Audience: Senior engineers, ages 30-50, evaluating dev tools,
+          allergic to marketing fluff, allergic to AI-generated
+          landing page fingerprints, will scroll fast and bounce
+          fast unless the headline lands
+
+Stage 1 (brief): Audience = senior engineers, value prop = "the
+                 first API observability tool that doesn't require
+                 you to instrument anything", CTA = "Start free
+                 trial", proof points = 3 customer logos + one
+                 quote + one metric
+Stage 2 (outline): use the layout above
+Stage 3 (visual): use the brief below
+Stage 4 (variants): defer to next session
+
+Aesthetic family: developer-confident — like Linear's marketing site
+                  meets the editorial confidence of The New York Times
+                  opinion section. No flourish, every claim earns its
+                  place, headline is a claim not a tagline.
+Color palette (CSS hex):
+  --color-bg:       #FAFAF8
+  --color-surface:  #FFFFFF
+  --color-muted:    #6B6B6B
+  --color-fg:       #2A2A2A
+  --color-ink:      #0A0A0A
+  --color-accent:   #2D6356
+Typography: Söhne (preferred — concrete-named) or Inter Variable;
+            modular scale 1.333; weight palette 400 body / 600
+            emphasized / 700 hero headline
+Corner radius: 4px on buttons and cards; full-bleed hero
+Motion: transition: all 160ms ease-out on hover; no auto-play motion
+        anywhere
+Density: comfortable above the fold (5 elements max), denser below
+         the fold (features grid, proof, FAQ)
+Surface: flat — single subtle border or single subtle shadow on
+         cards, never both
+
+Negative constraints — do not produce any of:
+  - Inter, Roboto, Arial, Space Grotesk as primary typeface
+  - Teal-to-blue or teal-to-green gradients
+  - Serif headline on sans-serif body
+  - Blinking / pulsing status indicators
+  - Container-on-container layouts
+  - Glassmorphism, neumorphism
+  - Generic "modern SaaS landing page" defaults
+  - Stock-photo abstract gradient hero imagery
+  - Three-column feature grid with icon + headline + line (default
+    fingerprint)
+  - Centered-hero with single CTA (default fingerprint)
+
+If you find yourself defaulting to any of these, stop and ask me to
+clarify before continuing.
+
+Brand DESIGN.md: ObserveAPI brand kit attached as project asset.
+                 Reference it at every section.
+```
+
+Expected follow-up turns:
+
+1. Turn 1: outline review (Stage 2)
+2. Turn 2: visual generation (Stage 3) at the brief above
+3. Turn 3: layer-4 dimension refinement (typography modular scale, semantic color roles, motion easing)
+4. Turn 4: layer-5 grading-criteria weighting (functionality 0.4, craft 0.3, design quality 0.2, originality 0.1 — landing pages weight functionality high)
+5. Turn 5+: Tweak panel for spacing and density adjustments
+6. Variant fan-out (Stage 4) in next session, against the approved master
+
+---
+
+## Sources
+
+- `https://anthropic.com/news/claude-design-anthropic-labs` — preset enumeration
+- `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` — Anthropic's frontend-design skill (closest adjacent Anthropic source; Design-Thinking Framework, AI-slop avoid-list, four design dimensions)
+- `https://claude.com/blog/improving-frontend-design-through-skills` — AI-slop avoid-list (amplified for marketing collateral)
+- `https://chatprd.ai` — community four-stage landing-page workflow
+- `https://sagnikbhattacharya.com/blog/claude-design` — community variant-fan-out pattern for social formats
+- `https://anthropic.com/engineering/harness-design-long-running-apps` — design grading criteria (composed for marketing collateral)
+
+Re-research trigger: Anthropic publishing a marketing-collateral tutorial; community four-stage workflow drifting; new slop-fingerprint patterns emerging in the AI-generated landing-page corpus; competitor-screenshot extraction patterns evolving.

plugins/claude-design/skills/claude-design-facilitator/references/presets/one-pagers.md

@@ -0,0 +1,168 @@
+# Preset: one-pagers
+
+**Last updated:** 2026-05-17 | **Verified:** research/03-prompt-patterns-intent-presets.md
+Evidence grade: Community-only — Anthropic publishes no per-preset prompt patterns for this preset as of 2026-05-16.
+
+Anthropic names `one-pagers` in the launch enumeration at `https://anthropic.com/news/claude-design-anthropic-labs` but does not publish a dedicated tutorial, support article, or canonical prompt set for it. The patterns below come from community practitioners — Substack walkthroughs, blog posts, newsletter pieces — with full attribution. Treat them as field-tested but not Anthropic-authoritative.
+
+---
+
+## (a) What this preset is
+
+Anthropic launch post one-sentence description: a one-pager is a single-screen artifact for memos, summaries, leave-behinds, executive briefs, or single-page deliverables. The destination is typically PDF or print.
+
+Distinguishing properties:
+
+- Single page — no multi-screen navigation, no scrolling sections that imply continuation
+- High information density compared to a slide
+- Self-contained narrative — reader does not need surrounding context
+- Often delivered as a leave-behind after a meeting or as a one-shot brief
+
+---
+
+## (b) Why Anthropic published no per-preset guidance
+
+The launch enumeration treats one-pagers as a destination shape rather than a generation mode requiring distinct prompt patterns. The Goal / Layout / Content / Audience framework (`../01-prompt-fundamentals.md` Layer 1) and the five-layer stack apply directly — Layout becomes single-page structure, Content becomes the dense information payload, Audience tightens the tone.
+
+Community practitioners have converged on patterns that constrain the one-pager preset more tightly than the generic stack does (Sections c and d).
+
+---
+
+## (c) Community patterns
+
+### Word-count cap per block
+
+Community pattern from `https://sagnikbhattacharya.com/blog/claude-design` (cited in `research/03`): cap the word count per layout block in the brief. The mechanism — Claude Design defaults to verbose prose when block content is unspecified, and one-pagers fail when any block runs long. The convergent caps from community practice:
+
+- Title block: 8 words max
+- Subtitle: 15 words max
+- Body paragraph: 60 words max
+- Bullet item: 12 words max
+- Callout box: 25 words max
+
+Brief the caps explicitly in the prompt — the model otherwise produces blocks 2-3x longer than the operator wants.
+
+### Above-the-fold density limit
+
+Community pattern from `https://newsletter.victordibia.com` (cited in `research/03`): cap the number of distinct elements visible in the top half of the one-pager. Convergent limits:
+
+- Maximum 5 distinct visual elements above the fold (counting title, subtitle, one body block, one visual, one callout = 5)
+- Maximum 3 colour roles visible above the fold (typically: ink for title, fg for body, accent for one emphasis)
+- Maximum 2 typographic weights above the fold (typically 700 title, 500 body)
+
+The brief encodes these as explicit constraints:
+
+```
+Above the fold (top half of the page), no more than 5 distinct visual
+elements, no more than 3 color roles, no more than 2 typographic
+weights. Density below the fold can scale up.
+```
+
+### Real-data injection over lorem ipsum
+
+Same pattern as `designs.md` and `prototypes.md`: use realistic placeholder content. For one-pagers specifically, this matters more — a one-pager is typically read once and discarded; if the content reads as placeholder, it loses the reader.
+
+---
+
+## (d) Critical caveats
+
+### Density-versus-readability trade-off
+
+One-pagers are constrained by physical reading mechanics — the operator can pack a lot into one page, but each element added reduces the reader's attention to every other element. The brief should weight density-vs-readability explicitly:
+
+```
+Optimise for the reader's ability to extract the takeaway in 30 seconds
+of scanning. If a block requires more than 30 seconds of focused reading
+to extract the takeaway, it does not belong on this one-pager.
+```
+
+### Export to PDF preserves layout; export to other formats may not
+
+PDF is the canonical one-pager export. HTML standalone works. PPTX is awkward for one-pagers (PPTX assumes deck format, not single-page format). Code-handoff is rare for one-pagers but works.
+
+### Anthropic AI-slop avoid-list still applies
+
+Layer 3 negative constraints (`../01-prompt-fundamentals.md`) apply with full force on one-pagers — the dense information context does not exempt the artifact from the avoid-list. Inter, Roboto, Arial, purple gradients on white, generic-modern defaults all degrade the one-pager.
+
+---
+
+## (e) One worked prompt — layers 1 + 3 composed (Layer 2a is preset-optional)
+
+Goal: an executive one-pager summarizing a project's Q1 status, audience is VP of Engineering.
+
+```
+Goal: A single-page executive summary of the platform team's Q1 2026
+      delivery, reliability, and Q2 themes. Designed to be scanned in
+      30 seconds and absorbed in 3 minutes.
+Layout: Single-page A4 portrait. Top quarter: title + headline takeaway
+        + 3 KPI numbers in a row. Middle half: 3 short body paragraphs
+        (one per: delivery, reliability, Q2 themes). Bottom quarter:
+        callout box with the one explicit ask + signature/contact block.
+Content: Real KPI numbers (% completion, MTTR minutes, uptime %); real
+         body content (no lorem ipsum); explicit ask is one sentence;
+         contact block names the person + email
+Audience: VP of Engineering, scanning between meetings, needs the
+          takeaway and one ask, will dive into details only if the
+          takeaway warrants it
+
+Word-count caps (community pattern from
+https://sagnikbhattacharya.com/blog/claude-design):
+  - Title block: 8 words max
+  - Subtitle / headline takeaway: 15 words max
+  - Body paragraph: 60 words max
+  - Bullet item: 12 words max
+  - Callout box: 25 words max
+
+Above-the-fold density limit (community pattern from
+https://newsletter.victordibia.com):
+  - Maximum 5 distinct visual elements above the fold
+  - Maximum 3 color roles visible above the fold
+  - Maximum 2 typographic weights above the fold
+
+Aesthetic family: editorial-confident — terse, signal-dense, no flourish
+Color palette (CSS hex):
+  --color-bg:       #FAFAF8
+  --color-surface:  #FFFFFF
+  --color-muted:    #6B6B6B
+  --color-fg:       #2A2A2A
+  --color-ink:      #0A0A0A
+  --color-accent:   #3D5C8A
+Typography: Söhne or Inter Variable; modular scale 1.250; weight palette
+            500 body / 700 headings
+Corner radius: 4px on the callout box only; rest is flat
+Motion: none (one-pager is static)
+Density: dense (8mm margins, 4mm gutters)
+Surface: flat — no shadows
+
+Negative constraints — do not produce any of:
+  - Inter, Roboto, Arial, or Space Grotesk as primary typeface
+  - Purple gradients on white backgrounds
+  - Card-style metric tiles with shadows
+  - Centered-title-and-subtitle generic header
+  - Pulse / breathing animations (this is a static one-pager)
+  - Generic "executive summary template" defaults
+
+Optimise for the reader's ability to extract the takeaway in 30 seconds
+of scanning. If a block requires more than 30 seconds of focused reading
+to extract the takeaway, it does not belong on this one-pager.
+```
+
+Expected follow-up turns:
+
+1. Turn 2: tighten word counts if any block ran over cap
+2. Turn 3: refine callout-box positioning if it competes with the headline takeaway
+3. Turn 4+: Tweak panel for spacing scale and density adjustments
+4. Export to PDF; visual-audit at 100% zoom and at print size
+
+---
+
+## Sources
+
+- `https://anthropic.com/news/claude-design-anthropic-labs` — preset enumeration, one-sentence description
+- `https://support.claude.com/en/articles/14604416-get-started-with-claude-design` — GLCA framework (composed in this preset)
+- `https://sagnikbhattacharya.com/blog/claude-design` — community pattern for word-count caps per block
+- `https://newsletter.victordibia.com` — community pattern for above-the-fold density limits
+- `https://claude.com/blog/improving-frontend-design-through-skills` — AI-slop avoid-list (composed)
+- `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` — Design-Thinking Framework reference
+
+Re-research trigger: Anthropic publishing a dedicated tutorial for one-pagers; community word-count caps drifting; new one-pager-specific community pattern emerging.

plugins/claude-design/skills/claude-design-facilitator/references/presets/pitch-decks.md

@@ -0,0 +1,198 @@
+# Preset: pitch-decks
+
+**Last updated:** 2026-05-17 | **Verified:** research/03-prompt-patterns-intent-presets.md
+**Evidence grade:** Community-only — Anthropic publishes no per-preset prompt patterns for this preset as of 2026-05-16.
+
+Evidence grade: Community-only — Anthropic publishes no per-preset prompt patterns for this preset as of 2026-05-16.
+
+Anthropic names `pitch-decks` in the launch enumeration at `https://anthropic.com/news/claude-design-anthropic-labs` but publishes no dedicated tutorial. **Critical caveat upfront:** community practitioner `https://moda.app/blog/claude-design-for-pitch-decks` documents an explicit recommendation against using Claude Design for external/investor pitch decks when PPTX is the required delivery format — see Section (d).
+
+---
+
+## (a) What this preset is
+
+Anthropic launch post one-sentence description: `pitch-decks` covers investor pitches, external partner proposals, and any high-stakes presentation format that needs to look polished. The preset distinguishes itself from the more general `slides` preset by audience — external rather than internal — and by typical destination — PPTX or PDF rather than HTML.
+
+The distinguishing question vs `slides`: **is the audience an external investor or external partner where the deck represents the company's positioning?** Yes → `pitch-decks`. Internal audience → `slides`.
+
+---
+
+## (b) Why Anthropic published no per-preset guidance
+
+Anthropic likely treats pitch-decks as a high-stakes specialisation of `slides` rather than a fundamentally distinct generation mode. The `slides` tutorial at `https://claude.com/resources/tutorials/using-claude-design-for-presentations-and-slide-decks` covers the prompt patterns; the `pitch-decks` preset inherits those patterns and adds the audience-stakes layer.
+
+Community practitioners have converged on patterns specific to pitch-deck production (Section c). The most important community contribution, however, is the PPTX-export caveat (Section d) — the failure mode is severe enough that the default recommendation diverges from `slides`.
+
+---
+
+## (c) Community patterns
+
+### Sagnik Bhattacharya's 10-slide template
+
+Community pattern from `https://sagnikbhattacharya.com/blog/claude-design` (cited in `research/03`): the convergent 10-slide pitch-deck template for B2B SaaS pitches:
+
+1. Title — company name, one-line positioning, tagline
+2. Problem — who has it, what it costs them, how acute
+3. Solution — what we built, one-sentence value prop
+4. Market — TAM / SAM / SOM (sized realistically)
+5. Product — 2-3 screenshots or visual demos
+6. Business model — how we charge, ACV ranges, GTM motion
+7. Traction — revenue, growth rate, named customers
+8. Team — founders + key hires, why this team for this problem
+9. Competition — competitive map (4-quadrant or named comparisons)
+10. Ask — funding round size, use of funds, timeline
+
+The template is community-converged, not Anthropic-published. It composes with Anthropic's `slides` tutorial patterns from `https://claude.com/resources/tutorials/using-claude-design-for-presentations-and-slide-decks`.
+
+### MindStudio per-slide micro-prompts
+
+Community pattern from MindStudio (cited in `research/03`): rather than briefing the full pitch deck in one prompt, micro-prompt each slide individually. The pattern produces tighter per-slide narrative because each slide gets dedicated attention.
+
+The micro-prompt pattern (per slide):
+
+```
+Generate slide N of the pitch deck. This slide does one job:
+[the slide's job — e.g., "convince the audience that the problem is
+acute by quantifying customer cost"].
+
+Visual elements: [specific to this slide — e.g., "one large number
+showing annual cost, two supporting smaller numbers, one explanatory
+sentence"].
+
+Constraints from DESIGN.md: [reference the project's DESIGN.md].
+
+Do not include filler — every element on this slide must support the
+one job.
+```
+
+Walk through slides 1-10 sequentially.
+
+### Outline-first scaffolding (composed from `slides.md`)
+
+The outline-first pattern from `slides.md` Section (d) applies: brief the deck as an outline first (turn 1), then expand to full slides (turn 2-N).
+
+---
+
+## (d) Critical caveats
+
+### PPTX export trap — explicit recommendation against external pitch decks
+
+Community-documented at `https://moda.app/blog/claude-design-for-pitch-decks` (cited in `research/03`) and `https://claudedesign.substack.com`: when an HTML-rendered pitch deck is exported to PPTX, richly-styled text can flatten to images. PowerPoint loses the editability — the text becomes a rasterised picture.
+
+For internal slide decks (audience tolerates some export friction), the operator can mitigate by keeping typography simple. For external pitch decks (audience expects polish, may want to add their own annotations or edit the deck), this failure mode is severe enough that the community recommendation is:
+
+> Do not use Claude Design for external/investor pitch decks where PPTX export is the required delivery format. Use HTML standalone or PDF if Claude Design is required; otherwise produce the deck in PowerPoint or Keynote directly.
+
+This plugin surfaces the recommendation but does not refuse to operate. The operator may have a reason to proceed (HTML acceptable, PDF acceptable, the PPTX text-as-text survival is verified to be acceptable for their specific styling). When proceeding, validate PPTX export early — generate slide 1 fully, export to PPTX, verify text-as-text survival, then commit to the deck.
+
+### Audience-stakes asymmetry
+
+A pitch deck for a $50M Series C carries different stakes than a pitch deck for a $500K seed extension. The operator's tolerance for export imperfection scales with the dollar amount on the line. Default conservatively — when in doubt about whether the export will survive, treat the deck as high-stakes.
+
+### Slop-fingerprints warning amplified
+
+Layer 3 negative constraints apply with extra weight on pitch decks. Investors see many decks; AI-slop fingerprints (purple gradients, generic three-column structure, Inter typography, centered-hero defaults, glassmorphism, neumorphism) signal that the deck is templated and the team did not invest care. The brief should over-specify the negative constraints.
+
+---
+
+## (e) One worked prompt — layers 1 + 3 composed, slide-by-slide micro-prompt pattern
+
+Goal: a 10-slide investor pitch deck for a B2B SaaS observability product, audience is Series A investors.
+
+```
+PRECONDITION: Before generating any slide, render slide 1 fully and
+export to PPTX. Verify text-as-text survival. If text flattens to
+images, switch destination to HTML standalone or PDF and notify me
+before continuing.
+
+Goal: A 10-slide Series A pitch deck for a B2B SaaS observability
+      product
+Layout (outline — per Sagnik Bhattacharya's 10-slide template at
+        https://sagnikbhattacharya.com/blog/claude-design):
+  1. Title
+  2. Problem
+  3. Solution
+  4. Market (TAM / SAM / SOM)
+  5. Product (2-3 visual demos)
+  6. Business model
+  7. Traction (revenue, growth, named customers)
+  8. Team
+  9. Competition
+ 10. Ask
+Content: Real numbers, real customer names, real founder names, real
+         competitive references. No lorem ipsum, no placeholder logos.
+Audience: Series A investors at top-tier funds, ages 35-55, see 50+
+          decks per quarter, allergic to template fingerprints
+
+Aesthetic family: editorial-confident — like Andreessen Horowitz pitch
+                  decks meets Linear's design language. Authoritative,
+                  no flourish, every visual element earns its place.
+Color palette (CSS hex):
+  --color-bg:       #FAFAF8
+  --color-surface:  #FFFFFF
+  --color-muted:    #6B6B6B
+  --color-fg:       #2A2A2A
+  --color-ink:      #0A0A0A
+  --color-accent:   #1A3552
+Typography: Söhne (preferred — concrete-named) or Inter Variable;
+            modular scale 1.333; weight palette 400 body / 600
+            emphasized / 700 slide titles
+Corner radius: 0 (full-bleed slides), 4px on any inline container
+Motion: none on static slides; ease-out 240ms on slide transitions
+Density: comfortable — one job per slide, generous spacing
+Surface: flat — full-bleed, no shadows
+
+Slide composition rules:
+  - Each slide does one job
+  - Slide titles are claims, not topics ("$2.4B addressable market"
+    not "Market")
+  - Body text is 2 lines max per slide
+  - One number, chart, or visual element per slide max
+  - Speaker notes carry depth; slides carry the takeaway
+
+Per-slide micro-prompt pattern (MindStudio, cited in research/03):
+  Generate slide N. Its one job: [name the job].
+  Visual elements: [specific to slide].
+  No filler — every element supports the one job.
+
+Negative constraints — do not produce any of:
+  - Inter, Roboto, Arial, Space Grotesk as primary typeface
+  - Purple gradients on white backgrounds
+  - Three-column feature grid as a default slide structure
+  - Centered-title-and-subtitle on every slide
+  - Glassmorphism, neumorphism, gradient hero backgrounds
+  - Pulse / breathing animations or fly-in transitions
+  - Generic "investor pitch deck template" defaults
+  - Stock-photo placeholder imagery
+
+If you find yourself defaulting to any AI-slop pattern (per
+https://claude.com/blog/improving-frontend-design-through-skills),
+stop and ask me to clarify before continuing.
+
+Slop-fingerprints warning is amplified — investors recognise template
+patterns. Over-specify the aesthetic to push the deck out of default
+neighbourhood.
+```
+
+Expected follow-up turns:
+
+1. Turn 1 (precondition): slide 1 + PPTX export validation. If text flattens, switch destination.
+2. Turn 2: 10-slide outline approval
+3. Turn 3-12: per-slide micro-prompt for each slide
+4. Turn 13: full-deck render, cross-slide consistency check
+5. Turn 14: Tweak panel for spacing and density adjustments
+6. Export and visual-audit at full deck level
+
+---
+
+## Sources
+
+- `https://anthropic.com/news/claude-design-anthropic-labs` — preset enumeration
+- `https://claude.com/resources/tutorials/using-claude-design-for-presentations-and-slide-decks` — Anthropic's slides tutorial (composed for pitch-decks)
+- `https://support.claude.com/en/articles/13521390-use-claude-for-powerpoint` — PowerPoint-mode conventions (relevant for PPTX export)
+- `https://moda.app/blog/claude-design-for-pitch-decks` — community-documented PPTX export caveat (load-bearing)
+- `https://claudedesign.substack.com` — community pattern reinforcing PPTX export caveat
+- `https://sagnikbhattacharya.com/blog/claude-design` — community 10-slide pitch-deck template
+- `https://claude.com/blog/improving-frontend-design-through-skills` — AI-slop avoid-list (amplified for pitch decks)
+
+Re-research trigger: Anthropic publishing a pitch-decks-specific tutorial; PPTX export behaviour changing (text-as-text survival improving or worsening); community 10-slide template drifting; new investor-deck pattern emerging.

plugins/claude-design/skills/claude-design-facilitator/references/presets/prototypes.md

@@ -0,0 +1,225 @@
+# Preset: prototypes
+
+**Last updated:** 2026-05-17 | **Verified:** research/03-prompt-patterns-intent-presets.md
+**Evidence grade:** Anthropic-documented + community-validated
+**Captured-on date:** 2026-05-16
+
+The `prototypes` intent preset generates interactive product flows for usability testing, design review, and stakeholder demos. Output is multi-screen HTML with working state transitions, clickable navigation, and per-state visual treatments. The preset is documented by Anthropic in a dedicated tutorial.
+
+---
+
+## (a) What this preset is
+
+Anthropic frames `prototypes` (launch post `https://anthropic.com/news/claude-design-anthropic-labs`) as the preset for product flows that need to behave like a real product, not just look like one. The distinguishing property vs `designs`: interaction state. Prototypes have hover states, active states, click-through transitions, multi-screen navigation, and per-state visual treatments.
+
+The dedicated tutorial is `https://claude.com/resources/tutorials/using-claude-design-for-prototypes-and-ux`. It is the load-bearing source for this preset.
+
+Output is HTML + React + inline CSS + JS (the JS makes the interactions work). Exportable to Code-handoff (engineering takes the working interaction logic forward) or HTML standalone (runs in a browser without Claude Design).
+
+---
+
+## (b) When to use it
+
+Pick `prototypes` when the goal is interactive validation. The decision matrix:
+
+| Operator goal | Preset |
+|---------------|--------|
+| Feature flow for usability testing (5-user study) | **prototypes** |
+| Internal tool demo for stakeholder review | **prototypes** |
+| A-B comparison of two design directions in working form | **prototypes** |
+| Onboarding flow walkthrough for new hire training | **prototypes** |
+| Static design exploration (no interaction needed) | designs |
+| Slide deck for a meeting | slides |
+
+If the operator describes the artifact in terms of "user clicks here, then sees this", they want `prototypes`. If they describe it in terms of "screen with these regions", they may want `designs`.
+
+---
+
+## (c) Anthropic-published prompt patterns
+
+The Anthropic tutorial `https://claude.com/resources/tutorials/using-claude-design-for-prototypes-and-ux` publishes nine canonical prompt patterns across four families:
+
+### Family 1 — Feature prototyping (4 verbatim canonical prompts)
+
+For new feature flows where the operator needs to test interaction logic. The patterns cover: a sign-in / sign-up multi-step flow; a checkout / payment flow with form validation states; a settings / preferences flow with toggles and selects; a search / filter flow with result-state transitions. Each prompt names entry point, success path, error states, and edge cases.
+
+Refer to the tutorial for the verbatim prompt text — Anthropic publishes the exact wording, and this plugin cites it by URL rather than copying it (per the brief's source-quality rule and the Apache-2.0/MIT compatibility note in `../04-handoff-and-scope.md`).
+
+### Family 2 — Design review and A-B comparison (2 verbatim canonical prompts)
+
+For prototyping when the goal is to compare two design directions side-by-side or in turn. The verbatim Anthropic comparison-prompt pattern:
+
+```
+Show me three different layouts for [feature]. For each:
+  - Visual direction (named, with concrete reference)
+  - Interaction model (where the user starts, where they end up)
+  - One-line rationale tying it to the audience and goal
+
+Once I pick one, generate the full interactive flow.
+```
+
+Use this for A-B-C exploration before committing to a direction. The pattern composes with layer 2b (propose-options-before-building) from `../01-prompt-fundamentals.md`.
+
+### Family 3 — User-flow scaffolding (1 verbatim canonical prompt)
+
+For mapping a multi-screen user journey. The pattern names the entry context, the screens in sequence, the decisions at each screen, and the success path vs the error paths. The output is a clickable multi-screen prototype with the navigation logic baked in.
+
+### Family 4 — Internal tools (2 verbatim canonical prompts)
+
+For internal-tooling prototypes — admin panels, content-moderation queues, customer-support consoles. The pattern emphasises dense interfaces, keyboard-driven navigation, and minimal aesthetic flourish. The patterns differ from external-product prototypes in tone and density.
+
+### Component-naming clarity, decision documentation, edge-case flagging
+
+The tutorial also publishes three transversal recommendations Anthropic asks operators to apply across all four families:
+
+- **Component-naming clarity** — name components in the brief so the generated artifact's component spec is engineering-handoff-ready (research/03 D2). Generic names like "Button1" produce generic component specs.
+- **Decision documentation** — ask Claude Design to document its design decisions inline (the PM-annotated notes feature) so the engineering handoff carries rationale, not just visuals.
+- **Edge-case flagging** — explicitly request that Claude Design flag interaction edge cases (empty state, loading state, error state, offline state, permission-denied state). The model defaults to happy-path-only without this directive.
+
+---
+
+## (d) Community uplift
+
+Three community-converged patterns extend Anthropic's published material for `prototypes`.
+
+### Request every state upfront
+
+Community pattern (`research/03`): explicitly request every interaction state in the first prompt rather than discovering missing states across iterations. The verbatim community phrasing:
+
+```
+For every interactive element in this prototype, generate:
+  - default state
+  - hover state
+  - active / pressed state
+  - focused state (keyboard navigation)
+  - disabled state
+  - loading state (if the element triggers async work)
+  - error state (if the element can fail)
+
+Render every state visibly somewhere in the prototype — either inline
+or in a dedicated state-catalogue page.
+```
+
+This catches the failure mode where the operator does not notice a missing state until a usability test surfaces it.
+
+### Real-data injection over lorem ipsum
+
+Same pattern as the `designs` preset, more important here: prototypes used in usability testing fail when the content is obviously fake. Test participants react to lorem ipsum and stop engaging with the flow. Use realistic content even when the prototype is throwaway.
+
+### Explicit motion timing and easing
+
+MindStudio community walkthrough (cited in `research/03`): name the easing curve and the duration explicitly for prototypes that include any motion. Default motion is the largest source of "feels like AI" in a prototype. The community-converged baselines for product prototypes:
+
+- Hover transitions: `transition: all 160ms ease-out`
+- Modal / drawer enter: `cubic-bezier(0.16, 1, 0.3, 1) 240ms`
+- Modal / drawer exit: `cubic-bezier(0.7, 0, 0.84, 0) 180ms`
+- Page transitions: `ease-out 280ms`
+
+---
+
+## (e) Critical caveats
+
+Three caveats specific to `prototypes`.
+
+### Interactive state count compounds context
+
+A prototype with 10 components × 7 states each = 70 distinct visual treatments in one artifact. Each treatment consumes context. Claude Design quality drops faster on prototypes than on `designs` for the same number of screens. Session-break heuristics (`../03-iteration-and-session.md`) apply with extra weight.
+
+### Test in target browsers before stakeholder review
+
+The standalone HTML export runs the prototype's JavaScript locally. Edge-case JavaScript (touch handlers, IntersectionObserver, ResizeObserver) does not always work the same across browsers. Test in Chrome + Safari + Firefox before sharing with stakeholders. If you target mobile usability testing, test on actual mobile devices, not just a browser DevTools mobile-emulation viewport.
+
+### Multi-screen exports — bundle in one export
+
+The token-cost trap in `../04-handoff-and-scope.md` Section 6 applies most strongly to multi-screen prototypes. Bundle all screens in one export turn; do not export screen-by-screen.
+
+---
+
+## (f) One end-to-end worked prompt — layers 1 + 2a + 3 composed
+
+Goal: a multi-step onboarding flow for a new SaaS analytics product, audience is small-business operators.
+
+```
+Goal: An interactive 5-step onboarding flow for new users of a SaaS
+      product. The flow: welcome → data-source connection → metric
+      selection → notification preferences → first-dashboard generation
+Layout: Single-column centered, fixed step indicator at top, primary
+        CTA at bottom of each step, secondary "back" link to top-left
+Content: Real product-facing copy (no lorem ipsum); step indicator
+         labels match the 5 steps verbatim; each step has a one-line
+         description below the step name; CTAs use action-verb naming
+         ("Connect your data", "Select your metrics", etc.)
+Audience: First-time users of a SaaS product, B2B small-business
+          operators, ages 30-55, comfortable with software but not
+          power-users
+
+Aesthetic family: warm-confident — like Linear's onboarding, like
+                  Notion's first-run, like Vercel's CLI prompts.
+                  Approachable but tight; never playful.
+Color palette (CSS hex):
+  --color-bg:       #FAFAF8
+  --color-surface:  #FFFFFF
+  --color-muted:    #6B6B6B
+  --color-fg:       #2A2A2A
+  --color-ink:      #0A0A0A
+  --color-accent:   #2D6356
+  --color-accent-hover: #1F4A41
+  --color-success:  #2D6356
+  --color-warning:  #C89B3F
+  --color-error:    #B23A48
+Typography: Söhne (preferred) or Inter Variable; modular scale 1.250;
+            weight palette 400 body / 500 emphasized / 600 headings
+Corner radius: 6px on cards, 4px on buttons and inputs
+Motion: transition: all 160ms ease-out on hover; cubic-bezier(0.16, 1,
+        0.3, 1) 240ms on step transitions
+Density: comfortable (44px touch targets, 16px card padding)
+Surface: subtle depth — 1px border + very subtle shadow on cards
+
+Interaction states (render every one for every interactive element):
+  default, hover, active, focused, disabled, loading, error
+
+Multi-screen requirements:
+  - Step 1: welcome — value prop in 2 sentences + Get Started CTA
+  - Step 2: data-source connection — list of 6 integrations with
+            connect buttons, hover states show "Connect" tooltip
+  - Step 3: metric selection — multi-select chip interface with 12
+            metric options, selection persists across step navigation
+  - Step 4: notification preferences — three toggle rows, with help-text
+            below each toggle
+  - Step 5: first-dashboard generation — loading state for 4-6 seconds,
+            then success state with "View Dashboard" CTA
+
+Edge cases to flag:
+  - Step 2 connection failure (network error visible)
+  - Step 3 zero metrics selected (CTA disabled, help-text appears)
+  - Step 5 generation timeout (recovery CTA appears)
+
+Negative constraints — do not produce any of:
+  - Inter, Roboto, Arial, or Space Grotesk as primary typeface
+  - Purple gradients on white backgrounds
+  - Centered-hero with single CTA (this is sequenced flow, not landing
+    page)
+  - Bouncy spring easing on hover
+  - Pulse animations on idle elements
+  - Generic "modern SaaS onboarding" template defaults
+```
+
+Expected follow-up turns:
+
+1. Turn 2: refine motion easing if step transitions feel sluggish or jumpy
+2. Turn 3: add layer 5 grading criteria (functionality 0.5, craft 0.3, design quality 0.2, originality 0)
+3. Turn 4+: Tweak panel for density and color-temperature adjustments
+4. Usability test surfaces missing states → iterate states via comments
+5. Export bundle for engineering handoff once stakeholders sign off
+
+---
+
+## Sources
+
+- `https://anthropic.com/news/claude-design-anthropic-labs` — preset enumeration
+- `https://claude.com/resources/tutorials/using-claude-design-for-prototypes-and-ux` — verbatim canonical prompts (4 families, 9 prompts) + component-naming clarity + decision documentation + edge-case flagging recommendations
+- `https://support.claude.com/en/articles/14604416-get-started-with-claude-design` — GLCA framework
+- `https://anthropic.com/engineering/harness-design-long-running-apps` — design grading criteria
+- `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` — Design-Thinking Framework, AI-slop avoid-list
+
+Re-research trigger: Anthropic updating the prototypes tutorial; new canonical prompt family added; component-naming-clarity / decision-documentation / edge-case-flagging recommendations materially revised.

plugins/claude-design/skills/claude-design-facilitator/references/presets/slides.md

@@ -0,0 +1,237 @@
+# Preset: slides
+
+**Last updated:** 2026-05-17 | **Verified:** research/03-prompt-patterns-intent-presets.md
+**Evidence grade:** Anthropic-documented + community-validated
+**Captured-on date:** 2026-05-16
+
+The `slides` intent preset generates presentation decks — internal stakeholder updates, executive roadmaps, customer briefings, partner proposals, all-hands meetings. Output is HTML deck with per-slide layouts, optionally exportable to PPTX (with caveats — see Section e).
+
+---
+
+## (a) What this preset is
+
+Anthropic launch post (`https://anthropic.com/news/claude-design-anthropic-labs`) names `slides` as a destination-shaped preset: the artifact assumes the slide-deck format, not the dashboard / one-pager / prototype format. Output renders in the Claude Design canvas as a slide-by-slide thumbnail strip plus the active slide in full view.
+
+Two Anthropic primary sources ground this preset:
+
+- The dedicated tutorial `https://claude.com/resources/tutorials/using-claude-design-for-presentations-and-slide-decks` publishes five verbatim canonical prompts (Section c) and the slide-deck composition framework.
+- The PowerPoint-mode article `https://support.claude.com/en/articles/13521390-use-claude-for-powerpoint` publishes the PPTX export conventions and the template-respecting guidance: Claude reads the slide master, layouts, fonts, and color scheme of an uploaded PPTX template and produces output that respects them.
+
+The two sources compose: the tutorial covers the prompt patterns, the PowerPoint-mode article covers the export discipline.
+
+---
+
+## (b) When to use it
+
+Pick `slides` when the destination is a presentation surface. The decision matrix:
+
+| Operator goal | Preset |
+|---------------|--------|
+| Internal team update / project review | **slides** |
+| Customer-prep briefing for a sales call | **slides** |
+| Executive roadmap or quarterly business review (Q1/Q2/Q3/Q4 results) | **slides** |
+| Partner proposal / co-development pitch | **slides** |
+| All-hands or company-wide announcement | **slides** |
+| External investor pitch deck | **pitch-decks** (separate preset — see preset file for the PPTX trap) |
+| Single-page memo / one-pager | one-pagers |
+
+The distinguishing question vs `pitch-decks`: **is the audience internal or external?** Internal → `slides`. External investor → `pitch-decks` (with explicit caveat about PPTX export, see `pitch-decks.md`).
+
+---
+
+## (c) Anthropic-published prompt patterns
+
+The Anthropic tutorial `https://claude.com/resources/tutorials/using-claude-design-for-presentations-and-slide-decks` publishes five verbatim canonical prompts:
+
+### Pattern 1 — Q1 results deck
+
+For quarterly business review decks (Q1 / Q2 / Q3 / Q4 results). Pattern names the metrics in priority order, the audience seniority level, the narrative arc (where we started, what changed, where we are, what's next), and the supporting visualisations (charts, tables, callout numbers).
+
+### Pattern 2 — Executive roadmap
+
+For multi-quarter roadmap decks. Pattern names the roadmap horizon (quarters or half-years), the workstreams (3-7 named tracks), the major milestones per workstream, the dependencies between workstreams, and the assumptions / risks per quarter.
+
+### Pattern 3 — Customer-prep briefing
+
+For sales-call preparation decks. Pattern names the customer (company + named contacts), the meeting goal, the customer's known priorities, the value-prop alignment, the proof points (case studies, metrics), and the asks / next steps.
+
+### Pattern 4 — Partner proposal
+
+For co-development or partnership proposals. Pattern names the proposed scope, the resourcing model, the timeline, the success metrics, the IP / licensing model, and the open questions.
+
+### Pattern 5 — All-hands announcement
+
+For company-wide updates. Pattern names the announcement (one sentence), the why-now context, the impact on employees, the timeline, and the resources / Q&A links.
+
+Refer to the tutorial URL for the verbatim prompt text. This plugin cites by URL rather than reproducing Anthropic's exact wording (per the brief's source-quality rule and the Apache-2.0/MIT compatibility note in `../04-handoff-and-scope.md`).
+
+### Template-respecting guidance (verbatim from PowerPoint-mode article)
+
+`https://support.claude.com/en/articles/13521390-use-claude-for-powerpoint` publishes the verbatim guidance about uploading an existing PPTX template:
+
+> Claude reads the slide master, layouts, fonts, and color scheme of an uploaded PowerPoint template and produces output that respects them.
+
+Practical implication: if the operator has an existing brand-compliant PPTX template, upload it as a Claude Design project asset before prompting. The generated deck will respect the template's typography, color palette, and layout conventions. Without an uploaded template, the model defaults to its convergent middle-ground deck aesthetic.
+
+---
+
+## (d) Community uplift
+
+Three community-converged patterns extend Anthropic's material for `slides`.
+
+### Outline-first narrative scaffolding
+
+Community pattern (`research/03`): brief the deck as an outline first (turn 1: produce the slide-by-slide outline as a markdown bullet list), then expand to full slides (turn 2: generate the deck from the approved outline). This forks the conversation but produces tighter narrative arcs than briefing the full deck in one turn.
+
+The outline-first pattern composes with Anthropic's GLCA framework (`../01-prompt-fundamentals.md` Layer 1) — Goal becomes the deck's takeaway, Layout becomes the outline, Content becomes the per-slide bullets, Audience becomes the seniority + context match.
+
+### Single-job-per-slide constraint
+
+Community pattern (research/03): each slide should communicate exactly one idea. Slides with two or more ideas leak comprehension. Brief the constraint explicitly:
+
+```
+Each slide does one job. If a slide is trying to communicate two ideas,
+split it into two slides. The takeaway from each slide should be
+nameable in one sentence.
+```
+
+### Audience translation matrix
+
+Community pattern (research/03): brief the audience translation explicitly when the deck spans seniority levels. For example, a roadmap deck shared with both engineering leads and executive sponsors needs to translate technical decisions into business outcomes for the exec audience without losing fidelity for the engineering audience. The pattern:
+
+```
+For each slide, write two versions of the takeaway:
+  - The technical-detail version (for the engineering audience)
+  - The business-outcome version (for the executive audience)
+
+Use the business-outcome version on the slide and the technical-detail
+version in the speaker notes.
+```
+
+---
+
+## (e) Critical caveats
+
+Three caveats specific to `slides`.
+
+### HTML → PPTX export is lossy for richly-styled text
+
+Community-documented at `https://moda.app/blog/claude-design-for-pitch-decks` (cited in research/03) and `https://claudedesign.substack.com`: when the operator exports an HTML-rendered slide deck to PPTX, richly-styled text (custom typography, mixed weights, inline color variations) can flatten to images. PowerPoint loses the editability — the text becomes a rasterised picture.
+
+The mitigation:
+
+- If the destination is final PPTX delivery, validate the rendered PPTX text-as-text count before assuming editability survived
+- If text-as-text is critical (legal review, copy-edit-after-the-fact), keep the typographic styling simple in the brief — single typeface, two weights, no inline color variation, no inline highlighting
+- For the `pitch-decks` preset specifically, this caveat is severe enough that the recommendation is "do not use Claude Design for external pitch decks where PPTX is required" — see `pitch-decks.md`
+
+### Don't trust the canvas as ground truth if destination is PPTX
+
+The Claude Design canvas renders the deck in HTML. The PPTX export converts to PowerPoint format. Some aesthetic decisions that look correct in the canvas do not survive the export:
+
+- Custom backgrounds with gradients can rasterize
+- Inline icons positioned via CSS can shift
+- Multi-column slide layouts can collapse
+- Speaker-notes-equivalent annotations may not round-trip
+
+Validate by opening the exported PPTX in PowerPoint before stakeholder delivery, especially for high-stakes decks.
+
+### Quota burn on long decks
+
+Multi-slide decks (10+ slides) compound context faster than single-page artifacts. The 4-screen inflection in `../03-iteration-and-session.md` applies — long decks reach the inflection within 2-3 chat turns. Plan to break the deck into outline → first 5 slides → next 5 slides if the deck is large, using the context-reset prompt between sessions.
+
+---
+
+## (f) One end-to-end worked prompt — layers 1 + 2a + 3 composed
+
+Goal: a 12-slide internal-team Q1 results deck, audience is engineering leadership + cross-functional partners.
+
+```
+Goal: A 12-slide Q1 2026 results deck covering platform-team delivery,
+      reliability metrics, headcount and hiring, top 3 themes for Q2,
+      and one slide on a major incident retrospective
+Layout (outline):
+  1. Title — "Platform team Q1 2026 results"
+  2. TL;DR — three bullet takeaways
+  3. Delivery — features shipped, % of roadmap completed
+  4. Reliability — uptime, MTTR, incident count
+  5. Latency — p95/p99 trend
+  6. Hiring — headcount delta, key hires, open roles
+  7. Top theme 1 for Q2 — name + one-sentence framing
+  8. Top theme 2 for Q2 — name + one-sentence framing
+  9. Top theme 3 for Q2 — name + one-sentence framing
+ 10. Incident retrospective — what happened, what we learned
+ 11. Asks — explicit asks of leadership and partners
+ 12. Q&A / Discussion prompt
+Content: Real numbers throughout — actual % completion, real MTTR
+         minutes, real headcount, real names for hires (or named
+         placeholders); each slide's takeaway nameable in one sentence
+Audience: VP of Engineering, peer Eng-leadership, partner-team PMs,
+          partner-team Eng-leads — mixed seniority, mixed technical
+          depth, ages 30-55
+
+Aesthetic family: editorial-confident — like The New York Times opinion
+                  section meets Linear's design language. Clean,
+                  authoritative, no flourish. Each slide reads like a
+                  well-edited paragraph.
+Color palette (CSS hex):
+  --color-bg:       #FAFAF8
+  --color-surface:  #FFFFFF
+  --color-muted:    #6B6B6B
+  --color-fg:       #2A2A2A
+  --color-ink:      #0A0A0A
+  --color-accent:   #3D5C8A
+  --color-success:  #2D6356
+  --color-warning:  #C89B3F
+  --color-error:    #B23A48
+Typography: Söhne or Inter Variable; modular scale 1.333 (perfect
+            fourth — slides scale up); weight palette 400 body / 600
+            emphasized / 700 slide titles
+Corner radius: 4px on any card-like containers; slides themselves
+               have no corner radius (full-bleed)
+Motion: none on static slides; ease-out 240ms on slide transitions
+Density: comfortable — generous spacing, one job per slide
+Surface: flat — full-bleed slides, no shadows, single subtle accent
+         line under slide title
+
+Slide composition rules:
+  - Each slide does one job
+  - Slide titles are claims, not topics ("We shipped 87% of roadmap"
+    not "Roadmap delivery")
+  - Body text is 2-3 lines max per slide
+  - One number, chart, or visual element per slide max
+  - Speaker notes carry the depth; slides carry the takeaway
+
+Negative constraints — do not produce any of:
+  - Inter, Roboto, Arial, Space Grotesk as primary typeface
+  - Purple gradients on white backgrounds
+  - Three-bullet-and-image generic slide template
+  - Pulse animations or fly-in transitions
+  - Generic "corporate deck" template defaults (centered title-and-
+    subtitle on every slide)
+  - Multi-column slides with more than two ideas per slide
+
+If the destination is PPTX, ensure text-heavy slides keep text as text
+(not rasterized). Keep typography simple to maximise text-as-text
+survival in export.
+```
+
+Expected follow-up turns:
+
+1. Turn 2: outline-first review — confirm the 12-slide structure, adjust ordering, swap titles if needed
+2. Turn 3: add audience translation per slide (speaker notes vs slide takeaway)
+3. Turn 4: render full deck against the approved outline
+4. Turn 5+: Tweak panel for typography scale and spacing; comments for slide-by-slide refinements
+5. Export validation: open PPTX in PowerPoint and audit text-as-text vs rasterized
+
+---
+
+## Sources
+
+- `https://anthropic.com/news/claude-design-anthropic-labs` — preset enumeration
+- `https://claude.com/resources/tutorials/using-claude-design-for-presentations-and-slide-decks` — verbatim canonical prompts (5 patterns), slide-deck composition framework
+- `https://support.claude.com/en/articles/13521390-use-claude-for-powerpoint` — PowerPoint-mode conventions, template-respecting guidance
+- `https://support.claude.com/en/articles/14604416-get-started-with-claude-design` — GLCA framework
+- `https://moda.app/blog/claude-design-for-pitch-decks` — community-documented PPTX export caveat (cited)
+- `https://anthropic.com/engineering/harness-design-long-running-apps` — design grading criteria
+
+Re-research trigger: Anthropic updating the slides tutorial; new canonical pattern added; PowerPoint-mode conventions revised; PPTX export behaviour changing materially.

plugins/claude-design/skills/claude-design-facilitator/references/presets/wireframes-mockups.md

@@ -0,0 +1,163 @@
+# Preset: wireframes-mockups
+
+**Last updated:** 2026-05-17 | **Verified:** research/03-prompt-patterns-intent-presets.md
+Evidence grade: Community-only — Anthropic publishes no per-preset prompt patterns for this preset as of 2026-05-16.
+
+Anthropic names `wireframes-mockups` in the launch enumeration at `https://anthropic.com/news/claude-design-anthropic-labs` but publishes no dedicated tutorial, support article, or canonical prompt set for it. The patterns below come from community practitioners; treat them as field-tested but not Anthropic-authoritative.
+
+---
+
+## (a) What this preset is
+
+Anthropic launch post one-sentence description: `wireframes-mockups` covers the spectrum from low-fidelity layout sketches (boxes, labels, structure-only) to high-fidelity mockups (visual design applied, but not interactive). The output is structural — the goal is to communicate layout, not aesthetic and not interaction.
+
+Distinguishing properties:
+
+- Static (not interactive) — wireframes and mockups do not have working state transitions; for interaction logic, use `prototypes`
+- Low-fi or high-fi — the preset spans both ends; the operator picks via prompt
+- Pre-visual-design — wireframes are often deliverables before the visual designer commits to a direction
+- Iteration-cheap — wireframes are intended to be iterated quickly, so the prompt patterns lean on N-variations-first generation
+
+---
+
+## (b) Why Anthropic published no per-preset guidance
+
+Wireframes occupy a niche between `designs` (visual exploration) and `prototypes` (interaction validation). Anthropic appears to treat the preset as a destination shape rather than a distinct generation mode. The Goal / Layout / Content / Audience framework (`../01-prompt-fundamentals.md` Layer 1) applies — Layout is the dominant concern, Content becomes structural labels, Audience determines fidelity level.
+
+Community practitioners have converged on the patterns below (Section c).
+
+---
+
+## (c) Community patterns
+
+### N-variations-first
+
+Community pattern from `https://designwithai.substack.com` (cited in `research/03`): wireframes are most useful when generated in N variations and compared. Brief the model to produce N distinct layout variations in the first turn, then pick one to refine.
+
+Convergent N values from community practice: 3 or 4 variations is the sweet spot. More than 4 dilutes the operator's attention; fewer than 3 does not surface meaningful alternatives.
+
+The brief pattern:
+
+```
+Generate 4 distinct wireframe variations for [feature/page]. For each:
+  - One sentence describing the structural direction
+  - The wireframe itself (boxes, labels, no visual design)
+
+After I pick one, refine that variation into a mockup with visual
+design applied.
+```
+
+This composes with Layer 2b (propose-options-before-building) from `../01-prompt-fundamentals.md`.
+
+### Wireframe vs High-Fidelity sub-preset selection
+
+Community pattern from `https://computingforgeeks.com` (cited in `research/03`): the preset spans low-fi to high-fi, but the model behaves differently across the spectrum. Brief the fidelity level explicitly:
+
+```
+Fidelity: low-fi
+  - boxes with labels, no typography weights other than 500
+  - one color (greyscale) — bg, surface, muted, fg
+  - no images, no icons — represent visual elements as labelled boxes
+  - 8pt grid visible if helpful
+
+OR
+
+Fidelity: high-fi
+  - actual typography, full color palette, real icons, real images
+  - production-ready visual treatment
+  - no interaction logic (this is wireframes preset, not prototypes)
+```
+
+Pick one explicitly. The default-mode failure is the model producing a mid-fidelity output that satisfies neither the low-fi structural goal nor the high-fi visual-validation goal.
+
+### The Aakashg / Nielsen "low-fi-is-deprecated" debate (flagged as unsettled)
+
+A community debate documented across Aakash Gupta's and Jakob Nielsen's posts in 2024-2025 (cited in `research/03`) argues that AI-generated high-fi mockups have made low-fi wireframes operationally obsolete — the marginal cost of generating a high-fi mockup is now low enough that there is no reason to start with low-fi. The counter-argument: low-fi wireframes still serve a communication function (forcing reviewers to focus on structure, not aesthetic) that high-fi mockups undermine.
+
+This plugin treats the debate as **unsettled**. The brief should pick the fidelity level deliberately, with the choice tied to the audience and the review purpose, not to a default assumption that one fidelity dominates. Flag the debate when the operator's choice seems unconsidered.
+
+---
+
+## (d) Critical caveats
+
+### Aesthetic drift if starting in high-fi
+
+When starting in high-fidelity mode, the model imports its convergent middle-ground aesthetic defaults more aggressively (because the visual decisions are within scope). Layer-3 negative constraints (`../01-prompt-fundamentals.md`) apply with extra weight on high-fi mockups.
+
+### Iteration economy — wireframes burn turns
+
+Each variation requested in the N-variations-first pattern costs a fraction of a turn (the model generates all N in one chat round). But subsequent refinement of the chosen variation often requires multiple turns (typography decisions, color palette, component-level styling). Budget accordingly — a wireframe-to-mockup flow can consume 4-6 turns for a single page.
+
+### Wireframe ≠ prototype
+
+If the operator describes user interactions ("the user clicks here, then sees this"), they want `prototypes`, not `wireframes-mockups`. Wireframes capture structure; prototypes capture behaviour. Misclassification leads to wasted turns regenerating an artifact in the wrong preset.
+
+---
+
+## (e) One worked prompt — layers 1 + 3 composed, N-variations-first pattern
+
+Goal: 4 wireframe variations for a customer-onboarding page, audience is product team for review.
+
+```
+Goal: 4 distinct wireframe variations for the first page of a customer
+      onboarding flow. The page introduces the product, captures
+      essential information, and routes the customer to one of three
+      paths (self-serve, sales-assisted, partner-handoff).
+Layout: Single page, viewport ~1440x900. Each variation lays out the
+        same content differently.
+Content: Real placeholder content — actual headlines, actual button
+         labels, actual form field labels. No lorem ipsum.
+Audience: Internal product team (PM, design lead, eng lead) reviewing
+          structure choices before committing to a direction
+
+Fidelity: low-fi (community pattern from
+          https://computingforgeeks.com — fidelity affects iteration
+          path)
+  - boxes with labels, no typography weights other than 500
+  - greyscale only (bg, surface, muted, fg)
+  - no images, no icons — labelled boxes
+  - 8pt grid visible
+
+N-variations-first (community pattern from
+https://designwithai.substack.com):
+
+Generate 4 distinct wireframe variations. For each variation:
+  - One-sentence description of the structural direction (e.g.,
+    "Top-down narrative — story first, paths second")
+  - The wireframe itself
+  - One-line rationale tying the structure to the audience and goal
+
+The 4 variations should be meaningfully distinct from each other —
+not minor tweaks of one base layout.
+
+After I pick one, generate a fifth output: a refined mockup of the
+chosen variation, transitioning fidelity from low-fi to medium-fi.
+
+Negative constraints (Anthropic AI-slop avoid-list):
+  - Inter, Roboto, Arial, Space Grotesk as primary typeface (the
+    fidelity-low constraint covers most of this, but flag explicitly)
+  - Purple gradients (low-fi means greyscale anyway)
+  - Three-column feature grid as the default structural pattern
+  - Centered-hero with single CTA as the default
+  - Cookie-cutter framing
+```
+
+Expected follow-up turns:
+
+1. Turn 1: 4 wireframe variations generated
+2. Turn 2: operator picks variation, refined low-fi mockup generated
+3. Turn 3: aesthetic family applied (full layer-2a brief), medium-fi mockup
+4. Turn 4: layer-4 dimensions applied (typography modular scale, color palette, component stylings)
+5. Turn 5+: Tweak panel for spacing and density adjustments
+
+---
+
+## Sources
+
+- `https://anthropic.com/news/claude-design-anthropic-labs` — preset enumeration, one-sentence description
+- `https://designwithai.substack.com` — community pattern: N-variations-first
+- `https://computingforgeeks.com` — community pattern: explicit Wireframe-vs-High-Fidelity fidelity selection
+- `https://claude.com/blog/improving-frontend-design-through-skills` — AI-slop avoid-list (composed for high-fi mode)
+- `https://github.com/anthropics/skills/skills/frontend-design/SKILL.md` — Design-Thinking Framework reference
+
+Re-research trigger: Anthropic publishing a dedicated wireframes-mockups tutorial; the Aakashg/Nielsen low-fi-is-deprecated debate reaching practitioner consensus; new sub-fidelity tier surfacing in community practice.

plugins/claude-design/tests/test-sc1-dogfood-log.sh

@@ -0,0 +1,203 @@
+#!/usr/bin/env bash
+# test-sc1-dogfood-log.sh — Verifies SC1 (operator-attested dogfood log) in REMEMBER.md
+#
+# Usage:
+#   bash tests/test-sc1-dogfood-log.sh           # missing block = WARN, exit 0
+#   bash tests/test-sc1-dogfood-log.sh --strict  # missing block = FAIL, exit 1
+#
+# Expects in REMEMBER.md (plugin root, gitignored):
+#   - A fenced section with heading `## Dogfood log — v0.1 slides run`
+#   - Five mechanically-checkable fields inside the section:
+#       artifact_type: <preset-name from .coverage.md>
+#       refine_rounds: <integer>
+#       final_prompt:
+#         ```
+#         <non-empty prompt content>
+#         ```
+#       shipped: yes  (or `shipped: equivalent`)
+#       comparison_to_unaided: <one sentence ending with .>
+#
+# REMEMBER.md is gitignored — this evidence is local-only. The script
+# validates format only; the outcome judgement is operator-attested.
+
+set -euo pipefail
+LC_ALL=en_US.UTF-8
+
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+NC='\033[0m'
+
+PLUGIN_ROOT="$(cd "$(dirname "$0")/.." && pwd)"
+PASS=0
+FAIL=0
+WARN=0
+
+pass() { printf "${GREEN}  ✓ %s${NC}\n" "$1"; PASS=$((PASS + 1)); }
+fail() { printf "${RED}  ✗ %s${NC}\n" "$1"; FAIL=$((FAIL + 1)); }
+warn() { printf "${YELLOW}  ⚠ %s${NC}\n" "$1"; WARN=$((WARN + 1)); }
+
+STRICT=false
+for arg in "$@"; do
+  case "$arg" in
+    --strict) STRICT=true ;;
+  esac
+done
+
+echo "=== test-sc1-dogfood-log ==="
+echo "Plugin root: $PLUGIN_ROOT"
+echo "Strict mode: $STRICT"
+echo ""
+
+REMEMBER_FILE="$PLUGIN_ROOT/REMEMBER.md"
+COVERAGE_FILE="$PLUGIN_ROOT/.coverage.md"
+
+# -------------------------------------------------------
+# Locate REMEMBER.md
+# -------------------------------------------------------
+if [ ! -f "$REMEMBER_FILE" ]; then
+  if $STRICT; then
+    fail "REMEMBER.md missing (strict mode — required)"
+    echo ""
+    echo "=== Summary ==="
+    printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+    exit 1
+  else
+    warn "REMEMBER.md missing (advisory until operator dogfood step)"
+    echo ""
+    echo "=== Summary ==="
+    printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+    exit 0
+  fi
+fi
+
+# -------------------------------------------------------
+# Extract fenced block between dogfood heading and next H2 (or EOF)
+# -------------------------------------------------------
+BLOCK="$(awk '
+  /^## Dogfood log — v0\.1 slides run$/ { capture = 1; next }
+  capture && /^## / { exit }
+  capture { print }
+' "$REMEMBER_FILE")"
+
+if [ -z "$BLOCK" ]; then
+  if $STRICT; then
+    fail "REMEMBER.md missing dogfood block '## Dogfood log — v0.1 slides run' (strict mode — required)"
+    echo ""
+    echo "=== Summary ==="
+    printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+    exit 1
+  else
+    warn "REMEMBER.md missing dogfood block (advisory until operator dogfood step)"
+    echo ""
+    echo "=== Summary ==="
+    printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+    exit 0
+  fi
+fi
+
+pass "found '## Dogfood log — v0.1 slides run' block"
+
+# -------------------------------------------------------
+# Field 1: artifact_type — must match a preset name from .coverage.md
+# -------------------------------------------------------
+ARTIFACT_TYPE="$(printf '%s\n' "$BLOCK" | awk -F': *' '/^artifact_type:/ { print $2; exit }' | tr -d '[:space:]')"
+
+if [ -z "$ARTIFACT_TYPE" ]; then
+  fail "artifact_type: field missing or empty"
+else
+  # extract preset names from .coverage.md table column 1
+  if [ -f "$COVERAGE_FILE" ]; then
+    PRESETS="$(awk -F'|' '
+      /^\| [a-z]/ { gsub(/^ +| +$/, "", $2); print $2 }
+    ' "$COVERAGE_FILE")"
+
+    FOUND=false
+    while IFS= read -r preset; do
+      [ -z "$preset" ] && continue
+      if [ "$preset" = "$ARTIFACT_TYPE" ]; then
+        FOUND=true
+        break
+      fi
+    done < <(printf '%s\n' "$PRESETS")
+
+    if $FOUND; then
+      pass "artifact_type='$ARTIFACT_TYPE' matches a preset in .coverage.md"
+    else
+      fail "artifact_type='$ARTIFACT_TYPE' does not match any preset in .coverage.md"
+    fi
+  else
+    fail ".coverage.md missing — cannot validate artifact_type"
+  fi
+fi
+
+# -------------------------------------------------------
+# Field 2: refine_rounds — integer
+# -------------------------------------------------------
+REFINE_ROUNDS_LINE="$(printf '%s\n' "$BLOCK" | grep -E '^refine_rounds:[[:space:]]*[0-9]+[[:space:]]*$' || true)"
+if [ -n "$REFINE_ROUNDS_LINE" ]; then
+  pass "refine_rounds: matches integer regex"
+else
+  fail "refine_rounds: missing or not an integer"
+fi
+
+# -------------------------------------------------------
+# Field 3: final_prompt: followed by non-empty fenced code block
+# -------------------------------------------------------
+HAS_FINAL_PROMPT="$(printf '%s\n' "$BLOCK" | grep -c '^final_prompt:' || true)"
+if [ "$HAS_FINAL_PROMPT" -ge 1 ]; then
+  # check that a fenced code block (```) appears after final_prompt:
+  FENCE_AFTER="$(awk '
+    /^final_prompt:/ { found = 1; next }
+    found && /^```/ { fence_open = !fence_open; if (fence_open) { in_fence = 1 } else { exit } }
+    found && in_fence && fence_open && /./ { content_lines++ }
+    END { print content_lines + 0 }
+  ' <<<"$BLOCK")"
+  if [ -z "$FENCE_AFTER" ]; then FENCE_AFTER=0; fi
+  if [ "$FENCE_AFTER" -ge 1 ]; then
+    pass "final_prompt: followed by non-empty fenced code block ($FENCE_AFTER content line(s))"
+  else
+    fail "final_prompt: not followed by a non-empty fenced code block"
+  fi
+else
+  fail "final_prompt: field missing"
+fi
+
+# -------------------------------------------------------
+# Field 4: shipped — yes or equivalent
+# -------------------------------------------------------
+SHIPPED_LINE="$(printf '%s\n' "$BLOCK" | grep -E '^shipped:[[:space:]]*(yes|equivalent)[[:space:]]*$' || true)"
+if [ -n "$SHIPPED_LINE" ]; then
+  pass "shipped: matches 'yes' or 'equivalent'"
+else
+  fail "shipped: missing or not 'yes'/'equivalent'"
+fi
+
+# -------------------------------------------------------
+# Field 5: comparison_to_unaided — non-empty sentence >=10 chars ending with .
+# -------------------------------------------------------
+COMP_LINE="$(printf '%s\n' "$BLOCK" | awk -F': *' '/^comparison_to_unaided:/ { for (i=2;i<=NF;i++) printf "%s%s", $i, (i<NF?": ":""); print ""; exit }')"
+COMP_TRIMMED="$(printf '%s' "$COMP_LINE" | sed -E 's/^[[:space:]]+//; s/[[:space:]]+$//')"
+COMP_LEN="${#COMP_TRIMMED}"
+
+if [ -z "$COMP_TRIMMED" ]; then
+  fail "comparison_to_unaided: field missing or empty"
+elif [ "$COMP_LEN" -lt 10 ]; then
+  fail "comparison_to_unaided: too short ($COMP_LEN chars; need >=10)"
+elif [ "${COMP_TRIMMED: -1}" != "." ]; then
+  fail "comparison_to_unaided: does not end with '.'"
+else
+  pass "comparison_to_unaided: non-empty, $COMP_LEN chars, ends with '.'"
+fi
+
+# -------------------------------------------------------
+# Summary
+# -------------------------------------------------------
+echo ""
+echo "=== Summary ==="
+printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+
+if [ "$FAIL" -gt 0 ]; then
+  exit 1
+fi
+exit 0

plugins/claude-design/tests/test-sc2-artifact-coverage.sh

@@ -0,0 +1,100 @@
+#!/usr/bin/env bash
+# test-sc2-artifact-coverage.sh — Verifies SC2 (per-preset coverage)
+#
+# Reads .coverage.md, extracts preset names from the table column 1,
+# for each preset runs:
+#   grep -rli "<preset>" plugins/claude-design/ --include='*.md' \
+#     --exclude-dir='.claude' --exclude-dir='tests'
+# and asserts ≥1 file hit.
+#
+# The preset list is NOT hardcoded — auto-adapts when .coverage.md changes.
+#
+# Usage: bash tests/test-sc2-artifact-coverage.sh
+# Exit codes: 0 = all presets covered; 1 = at least one preset uncovered
+
+set -euo pipefail
+LC_ALL=en_US.UTF-8
+
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+NC='\033[0m'
+
+PLUGIN_ROOT="$(cd "$(dirname "$0")/.." && pwd)"
+PASS=0
+FAIL=0
+WARN=0
+
+pass() { printf "${GREEN}  ✓ %s${NC}\n" "$1"; PASS=$((PASS + 1)); }
+fail() { printf "${RED}  ✗ %s${NC}\n" "$1"; FAIL=$((FAIL + 1)); }
+warn() { printf "${YELLOW}  ⚠ %s${NC}\n" "$1"; WARN=$((WARN + 1)); }
+
+COVERAGE_FILE="$PLUGIN_ROOT/.coverage.md"
+
+echo "=== test-sc2-artifact-coverage ==="
+echo "Plugin root: $PLUGIN_ROOT"
+echo ".coverage.md: $COVERAGE_FILE"
+echo ""
+
+if [ ! -f "$COVERAGE_FILE" ]; then
+  fail ".coverage.md missing — cannot verify SC2"
+  echo ""
+  echo "=== Summary ==="
+  printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+  exit 1
+fi
+
+# -------------------------------------------------------
+# Extract preset names from .coverage.md table column 1
+# -------------------------------------------------------
+# Table rows look like:
+#   | designs | skills/.../presets/designs.md | Evidence grade: ... | https://... |
+# Skip header (| Preset | ...) and separator (| --- | ...).
+PRESETS="$(awk -F'|' '
+  /^\| / && NR > 1 {
+    name = $2
+    gsub(/^ +| +$/, "", name)
+    if (name != "Preset" && name !~ /^-+$/ && name != "") {
+      print name
+    }
+  }
+' "$COVERAGE_FILE")"
+
+if [ -z "$PRESETS" ]; then
+  fail "no preset names extracted from .coverage.md"
+  echo ""
+  echo "=== Summary ==="
+  printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+  exit 1
+fi
+
+# -------------------------------------------------------
+# For each preset, grep for at least one file hit in plugin content
+# -------------------------------------------------------
+while IFS= read -r preset; do
+  [ -z "$preset" ] && continue
+
+  HITS="$(grep -rli "$preset" "$PLUGIN_ROOT" \
+    --include='*.md' \
+    --exclude-dir='.claude' \
+    --exclude-dir='tests' \
+    2>/dev/null || true)"
+
+  HIT_COUNT="$(printf '%s\n' "$HITS" | grep -c '.' || true)"
+  if [ -z "$HIT_COUNT" ]; then HIT_COUNT=0; fi
+
+  if [ "$HIT_COUNT" -ge 1 ]; then
+    pass "preset '$preset' covered by $HIT_COUNT file(s)"
+  else
+    fail "preset '$preset' has zero file hits in plugin content"
+  fi
+done < <(printf '%s\n' "$PRESETS")
+
+echo ""
+echo "=== Summary ==="
+printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+
+if [ "$FAIL" -gt 0 ]; then
+  exit 1
+fi
+exit 0

plugins/claude-design/tests/test-sc3-citations.sh

@@ -0,0 +1,123 @@
+#!/usr/bin/env bash
+# test-sc3-citations.sh — Verifies SC3 (Anthropic-domain citation discipline)
+#
+# Two checks:
+#   Negative — grep -rnE '\[CITE\]|\[verify\]|\baccording to\b' against
+#              shipped content. Zero hits expected.
+#   Positive — read .coverage.md "Authoritative-claims" bullet list
+#              (awk on '^- ' prefix), then for each file ensure ≥1
+#              Anthropic-domain URL citation is present.
+#
+# Excludes .claude/projects/** and tests/ from greps.
+#
+# Anthropic-domain URL regex (positive):
+#   https?://(docs\.anthropic\.com|anthropic\.com|github\.com/anthropics
+#            |claude\.com|support\.claude\.com|platform\.claude\.com)
+#
+# Usage: bash tests/test-sc3-citations.sh
+# Exit codes: 0 = pass; 1 = at least one FAIL
+
+set -euo pipefail
+LC_ALL=en_US.UTF-8
+
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+NC='\033[0m'
+
+PLUGIN_ROOT="$(cd "$(dirname "$0")/.." && pwd)"
+PASS=0
+FAIL=0
+WARN=0
+
+pass() { printf "${GREEN}  ✓ %s${NC}\n" "$1"; PASS=$((PASS + 1)); }
+fail() { printf "${RED}  ✗ %s${NC}\n" "$1"; FAIL=$((FAIL + 1)); }
+warn() { printf "${YELLOW}  ⚠ %s${NC}\n" "$1"; WARN=$((WARN + 1)); }
+
+COVERAGE_FILE="$PLUGIN_ROOT/.coverage.md"
+
+echo "=== test-sc3-citations ==="
+echo "Plugin root: $PLUGIN_ROOT"
+echo ""
+
+# -------------------------------------------------------
+# Negative grep: \[CITE\], \[verify\], \baccording to\b
+# -------------------------------------------------------
+echo "--- negative grep: forbidden placeholders ---"
+
+NEG_HITS="$(grep -rnE '\[CITE\]|\[verify\]|\baccording to\b' \
+  "$PLUGIN_ROOT" \
+  --include='*.md' \
+  --exclude-dir='.claude' \
+  --exclude-dir='tests' \
+  2>/dev/null || true)"
+
+if [ -z "$NEG_HITS" ]; then
+  pass "no forbidden placeholders ([CITE], [verify], 'according to') in shipped content"
+else
+  while IFS= read -r hit; do
+    fail "forbidden placeholder in shipped content: $hit"
+  done < <(printf '%s\n' "$NEG_HITS")
+fi
+echo ""
+
+# -------------------------------------------------------
+# Positive grep: Authoritative-claims files have Anthropic-domain URLs
+# -------------------------------------------------------
+echo "--- positive grep: Authoritative-claims citation coverage ---"
+
+if [ ! -f "$COVERAGE_FILE" ]; then
+  fail ".coverage.md missing — cannot read Authoritative-claims registry"
+  echo ""
+  echo "=== Summary ==="
+  printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+  exit 1
+fi
+
+# Extract bullet-list paths under the "Authoritative-claims" section
+AUTH_FILES="$(awk '
+  /^## Authoritative-claims files/ { capture = 1; next }
+  capture && /^## / { exit }
+  capture && /^- / {
+    sub(/^- /, "", $0)
+    print $0
+  }
+' "$COVERAGE_FILE")"
+
+if [ -z "$AUTH_FILES" ]; then
+  fail "no Authoritative-claims files extracted from .coverage.md"
+  echo ""
+  echo "=== Summary ==="
+  printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+  exit 1
+fi
+
+ANTHROPIC_REGEX='https?://(docs\.anthropic\.com|anthropic\.com|github\.com/anthropics|claude\.com|support\.claude\.com|platform\.claude\.com)'
+
+while IFS= read -r relpath; do
+  [ -z "$relpath" ] && continue
+  fpath="$PLUGIN_ROOT/$relpath"
+
+  if [ ! -f "$fpath" ]; then
+    fail "Authoritative-claims file missing: $relpath"
+    continue
+  fi
+
+  HIT_COUNT="$(grep -cE "$ANTHROPIC_REGEX" "$fpath" || true)"
+  if [ -z "$HIT_COUNT" ]; then HIT_COUNT=0; fi
+
+  if [ "$HIT_COUNT" -ge 1 ]; then
+    pass "$relpath: $HIT_COUNT Anthropic-domain URL citation(s)"
+  else
+    fail "$relpath: zero Anthropic-domain URL citations (anthropic.com expected)"
+  fi
+done < <(printf '%s\n' "$AUTH_FILES")
+
+echo ""
+echo "=== Summary ==="
+printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+
+if [ "$FAIL" -gt 0 ]; then
+  exit 1
+fi
+exit 0

plugins/claude-design/tests/test-skill-triggers.sh

@@ -0,0 +1,122 @@
+#!/usr/bin/env bash
+# test-skill-triggers.sh — Verifies skill description quality
+#
+# Honest limit: this only verifies strings are present in SKILL.md description.
+# It cannot prove Claude Code's orchestrator fires the skill on those prompts.
+# Runtime auto-fire validation is the operator's dogfood step (SC1).
+#
+# Checks:
+#   - SKILL.md frontmatter has 'description:' field
+#   - description block (from `description: |` to the closing `---`) is >=400 chars
+#   - if .triggers.txt exists, every phrase in it appears in SKILL.md description
+#
+# Usage: bash tests/test-skill-triggers.sh
+# Exit codes: 0 = pass; 1 = at least one FAIL
+
+set -euo pipefail
+LC_ALL=en_US.UTF-8
+
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+NC='\033[0m'
+
+PLUGIN_ROOT="$(cd "$(dirname "$0")/.." && pwd)"
+PASS=0
+FAIL=0
+WARN=0
+
+pass() { printf "${GREEN}  ✓ %s${NC}\n" "$1"; PASS=$((PASS + 1)); }
+fail() { printf "${RED}  ✗ %s${NC}\n" "$1"; FAIL=$((FAIL + 1)); }
+warn() { printf "${YELLOW}  ⚠ %s${NC}\n" "$1"; WARN=$((WARN + 1)); }
+
+echo "=== test-skill-triggers ==="
+echo "Plugin root: $PLUGIN_ROOT"
+echo ""
+
+# -------------------------------------------------------
+# Iterate over every SKILL.md
+# -------------------------------------------------------
+SKILL_COUNT=0
+for skill_file in "$PLUGIN_ROOT"/skills/*/SKILL.md; do
+  [ -f "$skill_file" ] || continue
+  SKILL_COUNT=$((SKILL_COUNT + 1))
+
+  skill_dir="$(dirname "$skill_file")"
+  skill_name="$(basename "$skill_dir")"
+
+  echo "--- $skill_name ---"
+
+  # ------------------------
+  # Frontmatter check
+  # ------------------------
+  first_line="$(head -n 1 "$skill_file")"
+  if [ "$first_line" != "---" ]; then
+    fail "$skill_name/SKILL.md: missing frontmatter delimiter on line 1"
+    echo ""
+    continue
+  fi
+
+  # ------------------------
+  # Description >=400 chars (Triggers on: enumeration counts)
+  # ------------------------
+  desc_block_chars="$(awk '/^description: \|/,/^---$/' "$skill_file" | wc -c | tr -d '[:space:]')"
+  if [ -z "$desc_block_chars" ]; then desc_block_chars=0; fi
+
+  if [ "$desc_block_chars" -ge 400 ]; then
+    pass "$skill_name: description block is $desc_block_chars chars (>=400)"
+  else
+    fail "$skill_name: description block is $desc_block_chars chars (<400 required)"
+  fi
+
+  # ------------------------
+  # Trigger-phrase coverage (.triggers.txt)
+  # ------------------------
+  triggers_file="$skill_dir/.triggers.txt"
+
+  if [ ! -f "$triggers_file" ]; then
+    warn "$skill_name: .triggers.txt missing (advisory — operator may want one)"
+    echo ""
+    continue
+  fi
+
+  trigger_count="$(grep -cE '.' "$triggers_file" || true)"
+  if [ -z "$trigger_count" ] || [ "$trigger_count" -lt 8 ]; then
+    fail "$skill_name/.triggers.txt: only $trigger_count phrase(s) (>=8 required)"
+  else
+    pass "$skill_name/.triggers.txt: $trigger_count phrase(s)"
+  fi
+
+  # check each phrase appears in SKILL.md description block
+  MISSING=0
+  while IFS= read -r phrase; do
+    [ -z "$phrase" ] && continue
+    if ! grep -qF "$phrase" "$skill_file"; then
+      fail "$skill_name: trigger phrase missing from SKILL.md description: '$phrase'"
+      MISSING=$((MISSING + 1))
+    fi
+  done < "$triggers_file"
+
+  if [ "$MISSING" -eq 0 ]; then
+    pass "$skill_name: all $trigger_count trigger phrase(s) appear in SKILL.md"
+  fi
+
+  echo ""
+done
+
+if [ "$SKILL_COUNT" -eq 0 ]; then
+  fail "no SKILL.md found under skills/*/"
+fi
+
+# -------------------------------------------------------
+# Summary
+# -------------------------------------------------------
+echo "=== Summary ==="
+printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+
+if [ "$FAIL" -gt 0 ]; then
+  exit 1
+fi
+exit 0
+
+# Triggers on: documented in each skill's .triggers.txt sibling file.

plugins/claude-design/tests/validate-plugin.sh

@@ -0,0 +1,265 @@
+#!/usr/bin/env bash
+# validate-plugin.sh — Foundation plugin structure validator for claude-design
+# Usage: bash tests/validate-plugin.sh
+# Exit codes: 0 = all checks pass; 1 = at least one FAIL
+#
+# Forked from plugins/ms-ai-architect/tests/validate-plugin.sh:
+#   keep:    helpers (pass/fail/warn), counters, PLUGIN_ROOT, JSON-validity check,
+#            README/CLAUDE.md existence checks
+#   strip:   agent frontmatter loop, commands frontmatter loop, KB-staleness checks,
+#            architect:* command-name assertions, references-count assertions
+#   add:     SKILL.md frontmatter + description-length, LICENSE content, GOVERNANCE
+#            existence, .coverage.md existence, forbidden-command-name regex (h),
+#            operator-private-context grep (i), Norwegian-leakage grep (j)
+
+set -euo pipefail
+LC_ALL=en_US.UTF-8
+
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+NC='\033[0m'
+
+PLUGIN_ROOT="$(cd "$(dirname "$0")/.." && pwd)"
+PASS=0
+FAIL=0
+WARN=0
+
+pass() { printf "${GREEN}  ✓ %s${NC}\n" "$1"; PASS=$((PASS + 1)); }
+fail() { printf "${RED}  ✗ %s${NC}\n" "$1"; FAIL=$((FAIL + 1)); }
+warn() { printf "${YELLOW}  ⚠ %s${NC}\n" "$1"; WARN=$((WARN + 1)); }
+
+echo "=== claude-design Plugin Validation ==="
+echo "Plugin root: $PLUGIN_ROOT"
+echo ""
+
+# -------------------------------------------------------
+# Check (a): plugin.json valid + required fields
+# -------------------------------------------------------
+echo "--- (a) plugin.json structure ---"
+
+PLUGIN_JSON="$PLUGIN_ROOT/.claude-plugin/plugin.json"
+
+if [ ! -f "$PLUGIN_JSON" ]; then
+  fail ".claude-plugin/plugin.json missing"
+else
+  if node -e "JSON.parse(require('fs').readFileSync('$PLUGIN_JSON'))" 2>/dev/null; then
+    pass ".claude-plugin/plugin.json is valid JSON"
+  else
+    fail ".claude-plugin/plugin.json is invalid JSON"
+  fi
+
+  for field in name version description; do
+    if node -e "const p = JSON.parse(require('fs').readFileSync('$PLUGIN_JSON')); if (typeof p['$field'] !== 'string' || p['$field'] === '') process.exit(1)" 2>/dev/null; then
+      pass "plugin.json has '$field'"
+    else
+      fail "plugin.json missing or empty '$field'"
+    fi
+  done
+fi
+echo ""
+
+# -------------------------------------------------------
+# Check (b): at least one SKILL.md under skills/*/
+# -------------------------------------------------------
+echo "--- (b) SKILL.md presence ---"
+
+SKILL_COUNT=0
+for skill_file in "$PLUGIN_ROOT"/skills/*/SKILL.md; do
+  [ -f "$skill_file" ] || continue
+  SKILL_COUNT=$((SKILL_COUNT + 1))
+done
+
+if [ "$SKILL_COUNT" -ge 1 ]; then
+  pass "found $SKILL_COUNT SKILL.md file(s) under skills/*/"
+else
+  fail "no SKILL.md found under skills/*/"
+fi
+echo ""
+
+# -------------------------------------------------------
+# Check (c): SKILL.md frontmatter has name+description, description >=400 chars
+# -------------------------------------------------------
+echo "--- (c) SKILL.md frontmatter quality ---"
+
+for skill_file in "$PLUGIN_ROOT"/skills/*/SKILL.md; do
+  [ -f "$skill_file" ] || continue
+  basename_skill="$(basename "$(dirname "$skill_file")")/SKILL.md"
+
+  first_line="$(head -n 1 "$skill_file")"
+  if [ "$first_line" != "---" ]; then
+    fail "$basename_skill: missing frontmatter delimiter on line 1"
+    continue
+  fi
+
+  frontmatter="$(awk 'NR==1{next} /^---$/{exit} {print}' "$skill_file")"
+
+  if echo "$frontmatter" | grep -qE '^name:'; then
+    pass "$basename_skill: has 'name:'"
+  else
+    fail "$basename_skill: missing 'name:'"
+  fi
+
+  if echo "$frontmatter" | grep -qE '^description:'; then
+    pass "$basename_skill: has 'description:'"
+  else
+    fail "$basename_skill: missing 'description:'"
+  fi
+
+  desc_len="$(awk '/^description: \|/,/^---$/' "$skill_file" | wc -c | tr -d '[:space:]')"
+  if [ -z "$desc_len" ]; then desc_len=0; fi
+  if [ "$desc_len" -ge 400 ]; then
+    pass "$basename_skill: description block is $desc_len chars (>=400)"
+  else
+    fail "$basename_skill: description block is $desc_len chars (<400)"
+  fi
+done
+echo ""
+
+# -------------------------------------------------------
+# Check (d): LICENSE exists, non-empty, contains "MIT License"
+# -------------------------------------------------------
+echo "--- (d) LICENSE ---"
+
+LICENSE_FILE="$PLUGIN_ROOT/LICENSE"
+
+if [ ! -f "$LICENSE_FILE" ]; then
+  fail "LICENSE missing"
+elif [ ! -s "$LICENSE_FILE" ]; then
+  fail "LICENSE is empty"
+elif ! grep -q "MIT License" "$LICENSE_FILE"; then
+  fail "LICENSE does not contain 'MIT License'"
+else
+  pass "LICENSE exists, non-empty, MIT License"
+fi
+echo ""
+
+# -------------------------------------------------------
+# Check (e): GOVERNANCE.md exists, non-empty
+# -------------------------------------------------------
+echo "--- (e) GOVERNANCE.md ---"
+
+GOVERNANCE_FILE="$PLUGIN_ROOT/GOVERNANCE.md"
+
+if [ ! -f "$GOVERNANCE_FILE" ]; then
+  fail "GOVERNANCE.md missing"
+elif [ ! -s "$GOVERNANCE_FILE" ]; then
+  fail "GOVERNANCE.md is empty"
+else
+  pass "GOVERNANCE.md exists, non-empty"
+fi
+echo ""
+
+# -------------------------------------------------------
+# Check (f): README.md + CLAUDE.md exist, non-empty
+# -------------------------------------------------------
+echo "--- (f) README.md and CLAUDE.md ---"
+
+for f in README.md CLAUDE.md; do
+  fpath="$PLUGIN_ROOT/$f"
+  if [ ! -f "$fpath" ]; then
+    fail "$f missing"
+  elif [ ! -s "$fpath" ]; then
+    fail "$f is empty"
+  else
+    pass "$f exists, non-empty"
+  fi
+done
+echo ""
+
+# -------------------------------------------------------
+# Check (g): .coverage.md exists at plugin root
+# -------------------------------------------------------
+echo "--- (g) .coverage.md ---"
+
+COVERAGE_FILE="$PLUGIN_ROOT/.coverage.md"
+
+if [ ! -f "$COVERAGE_FILE" ]; then
+  fail ".coverage.md missing"
+elif [ ! -s "$COVERAGE_FILE" ]; then
+  fail ".coverage.md is empty"
+else
+  pass ".coverage.md exists, non-empty"
+fi
+echo ""
+
+# -------------------------------------------------------
+# Check (h): forbidden command-name regex (scope fence vs
+#            Anthropic's knowledge-work-plugins/design)
+# -------------------------------------------------------
+echo "--- (h) forbidden command-name regex ---"
+
+FORBIDDEN_REGEX='^name:[[:space:]]*(claude-design:)?(critique|accessibility|ux-copy|research-synthesis|design-system|handoff)[[:space:]]*$'
+
+H_HIT=0
+
+for cmd_file in "$PLUGIN_ROOT"/commands/*.md "$PLUGIN_ROOT"/skills/*/SKILL.md; do
+  [ -f "$cmd_file" ] || continue
+  if grep -qE "$FORBIDDEN_REGEX" "$cmd_file"; then
+    fail "command-name collision with Anthropic's official knowledge-work-plugins/design plugin: $cmd_file"
+    H_HIT=$((H_HIT + 1))
+  fi
+done
+
+if [ "$H_HIT" -eq 0 ]; then
+  pass "no forbidden command-name collisions"
+fi
+echo ""
+
+# -------------------------------------------------------
+# Check (i): operator-private-context grep
+# -------------------------------------------------------
+echo "--- (i) operator-private-context grep ---"
+
+I_HITS="$(grep -rnE '(kjell|vegvesen|NEXT-SESSION-PROMPT|REMEMBER\.md content from)' \
+  "$PLUGIN_ROOT" \
+  --include='*.md' \
+  --exclude-dir='.claude' \
+  --exclude-dir='tests' \
+  --exclude='REMEMBER.md' \
+  --exclude='TODO.md' \
+  --exclude='NEXT-SESSION-PROMPT.local.md' \
+  2>/dev/null || true)"
+
+if [ -z "$I_HITS" ]; then
+  pass "no operator-private context leaks in shipped content"
+else
+  while IFS= read -r hit; do
+    fail "operator-private context leak in shipped content (brief NFR): $hit"
+  done < <(printf '%s\n' "$I_HITS")
+fi
+echo ""
+
+# -------------------------------------------------------
+# Check (j): Norwegian-leakage grep (WARN, not FAIL)
+# -------------------------------------------------------
+echo "--- (j) Norwegian-leakage grep ---"
+
+J_HITS="$(grep -rnE '[æøåÆØÅ]' \
+  "$PLUGIN_ROOT" \
+  --include='*.md' \
+  --exclude-dir='.claude' \
+  --exclude='REMEMBER.md' \
+  --exclude='TODO.md' \
+  --exclude='NEXT-SESSION-PROMPT.local.md' \
+  2>/dev/null || true)"
+
+if [ -z "$J_HITS" ]; then
+  pass "no Norwegian diacritics in shipped content"
+else
+  while IFS= read -r hit; do
+    warn "Norwegian diacritic in shipped content (review case-by-case): $hit"
+  done < <(printf '%s\n' "$J_HITS")
+fi
+echo ""
+
+# -------------------------------------------------------
+# Summary
+# -------------------------------------------------------
+echo "=== Summary ==="
+printf "Pass: %d  Fail: %d  Warn: %d\n" "$PASS" "$FAIL" "$WARN"
+
+if [ "$FAIL" -gt 0 ]; then
+  exit 1
+fi
+exit 0

plugins/claude-design/verify.sh

@@ -0,0 +1,152 @@
+#!/usr/bin/env bash
+# verify.sh — Top-level roll-up for claude-design plugin verification
+#
+# Runs the 5 test scripts in dependency order:
+#   1. tests/validate-plugin.sh           (foundation plugin structure)
+#   2. tests/test-skill-triggers.sh       (skill description + trigger phrases)
+#   3. tests/test-sc2-artifact-coverage.sh (SC2 — every preset has ≥1 file)
+#   4. tests/test-sc3-citations.sh        (SC3 — citation discipline)
+#   5. tests/test-sc1-dogfood-log.sh      (SC1 — operator dogfood log format)
+#
+# Flags:
+#   --strict   pass --strict to test-sc1-dogfood-log.sh (missing block = FAIL)
+#   --quick    skip tests/test-skill-triggers.sh (fast incremental runs)
+#
+# Exit codes: 0 = all sub-tests pass; non-zero = at least one sub-test failed
+#
+# Bash 3.2 compatible. Modelled on plugins/voyage/verify.sh helper style.
+
+set -u
+LC_ALL=en_US.UTF-8
+
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+BOLD='\033[1m'
+NC='\033[0m'
+
+PLUGIN_ROOT="$(cd "$(dirname "$0")" && pwd)"
+
+# Flag parsing
+STRICT=false
+QUICK=false
+for arg in "$@"; do
+  case "$arg" in
+    --strict) STRICT=true ;;
+    --quick)  QUICK=true ;;
+    -h|--help)
+      echo "Usage: $0 [--strict] [--quick]"
+      echo "  --strict   Pass --strict to test-sc1-dogfood-log.sh"
+      echo "  --quick    Skip tests/test-skill-triggers.sh"
+      exit 0
+      ;;
+    *)
+      echo "Unknown flag: $arg" >&2
+      echo "Usage: $0 [--strict] [--quick]" >&2
+      exit 2
+      ;;
+  esac
+done
+
+TOTAL_PASS=0
+TOTAL_FAIL=0
+TOTAL_WARN=0
+FAILED_SCRIPTS=""
+
+run_script() {
+  local script_name="$1"
+  shift
+  local script_path="$PLUGIN_ROOT/tests/$script_name"
+
+  if [ ! -f "$script_path" ]; then
+    printf "${RED}[MISSING]${NC} %s\n" "$script_name"
+    TOTAL_FAIL=$((TOTAL_FAIL + 1))
+    FAILED_SCRIPTS="$FAILED_SCRIPTS $script_name"
+    return 1
+  fi
+
+  printf "${BOLD}### %s${NC}\n" "$script_name"
+
+  local output exit_code
+  output="$(bash "$script_path" "$@" 2>&1)"
+  exit_code=$?
+
+  printf '%s\n' "$output"
+
+  # Parse the script's own Summary line: "Pass: N  Fail: N  Warn: N"
+  local summary
+  summary="$(printf '%s\n' "$output" | grep -E '^Pass: [0-9]+  Fail: [0-9]+  Warn: [0-9]+$' | tail -n 1)"
+
+  if [ -n "$summary" ]; then
+    local p f w
+    p="$(printf '%s' "$summary" | awk '{print $2}')"
+    f="$(printf '%s' "$summary" | awk '{print $4}')"
+    w="$(printf '%s' "$summary" | awk '{print $6}')"
+    TOTAL_PASS=$((TOTAL_PASS + p))
+    TOTAL_FAIL=$((TOTAL_FAIL + f))
+    TOTAL_WARN=$((TOTAL_WARN + w))
+  fi
+
+  if [ "$exit_code" -ne 0 ]; then
+    FAILED_SCRIPTS="$FAILED_SCRIPTS $script_name"
+  fi
+
+  printf "\n"
+  return "$exit_code"
+}
+
+echo "=== claude-design verify.sh ==="
+echo "Plugin root: $PLUGIN_ROOT"
+echo "Strict mode: $STRICT   Quick mode: $QUICK"
+echo ""
+
+# -------------------------------------------------------
+# 1. validate-plugin.sh
+# -------------------------------------------------------
+run_script "validate-plugin.sh" || true
+
+# -------------------------------------------------------
+# 2. test-skill-triggers.sh (skipped in --quick mode)
+# -------------------------------------------------------
+if $QUICK; then
+  printf "${YELLOW}### test-skill-triggers.sh${NC} (skipped — --quick)\n\n"
+else
+  run_script "test-skill-triggers.sh" || true
+fi
+
+# -------------------------------------------------------
+# 3. test-sc2-artifact-coverage.sh
+# -------------------------------------------------------
+run_script "test-sc2-artifact-coverage.sh" || true
+
+# -------------------------------------------------------
+# 4. test-sc3-citations.sh
+# -------------------------------------------------------
+run_script "test-sc3-citations.sh" || true
+
+# -------------------------------------------------------
+# 5. test-sc1-dogfood-log.sh (strict if --strict)
+# -------------------------------------------------------
+if $STRICT; then
+  run_script "test-sc1-dogfood-log.sh" --strict || true
+else
+  run_script "test-sc1-dogfood-log.sh" || true
+fi
+
+# -------------------------------------------------------
+# Aggregate summary
+# -------------------------------------------------------
+echo "================================================="
+echo "=== claude-design verify.sh — aggregate summary"
+echo "================================================="
+printf "${GREEN}Pass:${NC} %d   ${RED}Fail:${NC} %d   ${YELLOW}Warn:${NC} %d\n" \
+  "$TOTAL_PASS" "$TOTAL_FAIL" "$TOTAL_WARN"
+
+if [ -n "$FAILED_SCRIPTS" ]; then
+  printf "${RED}Failed scripts:${NC}%s\n" "$FAILED_SCRIPTS"
+fi
+
+if [ "$TOTAL_FAIL" -gt 0 ]; then
+  exit 1
+fi
+exit 0

plugins/config-audit/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "config-audit",
   "description": "Multi-agent workflow for analyzing, reporting, and optimizing Claude Code configuration across your entire machine",
-  "version": "5.0.0",
+  "version": "5.1.0",
   "author": {
     "name": "Kjell Tore Guttormsen"
   },

plugins/config-audit/CHANGELOG.md

@@ -5,6 +5,52 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [5.1.0] - 2026-05-01
+
+### Summary
+Plain-language UX humanizer release. Default output of all 18 commands now leads with prose; technical IDs surface at end-of-line as references rather than headlines. Non-expert users — the bulk of the OSS audience — now read findings like "Fix soon: The same automation is set up more than once" instead of "[high] CA-CNF-001: Hook duplicate event registration". Scanner internals are unchanged; humanization is a pure output-time transform applied at the rendering layer. The `--raw` flag preserves v5.0.0 verbatim output for tooling that scrapes stderr; `--json` is unchanged from v5.0.0 and remains byte-stable for programmatic consumption.
+
+Delivered across 6 waves (Wave 0 baseline → Wave 1 humanizer module → Wave 2 test re-anchoring → Wave 3 CLI wiring → Wave 4 contract tests → Wave 5 templates/agents → Wave 6 release).
+
+### Added
+- **`scanners/lib/humanizer.mjs`** — pure-function output translator: `humanizeFinding`, `humanizeFindings`, `humanizeEnvelope`, `computeRelevanceContext`. Never mutates inputs. Adds three additive fields per finding (`userImpactCategory`, `userActionLanguage`, `relevanceContext`) and replaces title/description/recommendation when a translation is available; falls through to originals otherwise.
+- **`scanners/lib/humanizer-data.mjs`** — TRANSLATIONS table for 13 scanner prefixes (CML, SET, HKV, RUL, MCP, IMP, CNF, COL, TOK, CPS, DIS, GAP, PLH). Three-step lookup per finding: exact title → regex pattern → `_default` → fall through to scanner original.
+- **`--raw` flag** threaded through every CLI: `posture.mjs`, `scan-orchestrator.mjs`, `token-hotspots-cli.mjs`, `manifest.mjs`, `whats-active.mjs`, `fix-cli.mjs`, `drift-cli.mjs`, `self-audit.mjs`. Bypasses humanizer; emits byte-stable v5.0.0 verbatim output.
+- **User-impact categories** (5 labels): Configuration mistake, Conflict, Wasted tokens, Missed opportunity, Dead config. Mapped from scanner prefix.
+- **Action-language phrases** (5 labels): Fix this now, Fix soon, Fix when convenient, Optional cleanup, FYI. Mapped from severity.
+- **Relevance context** (3 values): `test-fixture-no-impact`, `affects-this-machine-only`, `affects-everyone`. Computed from finding's file path — basenames matching `*.local.*` and paths containing `/tests/fixtures/` are recognized.
+- **Self-audit terminal humanization** — `formatSelfAudit()` routes through `humanizeEnvelope`. JSON path (`--json`) is unchanged; humanization applies only to the prose terminal render.
+- **Forbidden-words lint** (`tests/lint-forbidden-words.json` + runner) — 3-tier vocabulary blocklist enforced over default-mode output, ensuring humanized prose stays in plain language.
+- **Scenario read-test** (`tests/scenario-read-test.mjs` + 5 scenarios) — corpus-driven readability check covering broken hook, duplicate keys, stale @import, dead tool, oversized cascade.
+- **`tests/snapshots/v5.0.0/`** + **`tests/snapshots/v5.0.0-stderr/`** — frozen byte-equal references for SC-6 (--json) and SC-7 (--raw) backwards-compatibility tests across 8 CLIs.
+- **`tests/snapshots/default-output/`** — humanized-prose snapshots for SC-5 default-output stability.
+
+### Changed
+- **Default output of all 18 commands** now uses plain-language descriptions. Findings group by user-impact category; titles lead with prose; technical IDs (`CA-CML-001`, `CA-TOK-005`, …) surface at end-of-line as references.
+- **All 21 command and agent templates** updated to render humanized output by default and pass `--raw` through when the user requests v5.0.0 verbatim mode.
+- **CLI flag inventory** — every CLI now accepts `--raw` (new) in addition to `--json` (existing, unchanged). `--output-file <path>` still writes raw v5.0.0-shape JSON regardless of mode (humanizer-bypassed, posture-specific).
+
+### Migration
+- **No action required for existing automation** that consumes `--json` — the JSON envelope shape is byte-stable with v5.0.0 and humanizer fields are bypassed in `--json` and `--raw` paths.
+- **Tooling that scrapes stderr** from default mode (e.g., `posture.mjs`'s scorecard) needs review — default stderr now uses prose vocabulary. Pass `--raw` for byte-stable v5.0.0 verbatim stderr.
+- **No scanner-internal changes.** Finding IDs, severity ladders, scoring weights, and area scorecards are unchanged. Upgrades are presentation-layer only.
+
+### Test count
+- 635 → 792 tests across 52 test files (+157 humanizer-tester through Waves 0–5).
+- New top-level tests: `json-backcompat.test.mjs`, `raw-backcompat.test.mjs`, `scenario-read-test.test.mjs`, `snapshot-default-output.test.mjs`.
+- New lib tests: `humanizer.test.mjs`, `humanizer-data.test.mjs`, `scoring-humanizer.test.mjs`.
+- New scanner tests: `posture-humanizer.test.mjs`, `scan-orchestrator-humanizer.test.mjs`, `cli-humanizer.test.mjs`.
+
+### Out of scope (deferred to v5.1.1+)
+- **Posture `--output-file` humanization** — `posture.mjs` does not call `humanizeEnvelope`, so files written via `--output-file` are raw v5.0.0-shape JSON. Future revision: drop `--output-file` from command templates or add a `--humanized-json` flag.
+- **Knowledge cross-references** (Step 17 of plan) — not delivered per user decision (2a).
+- **Scoring scorecard JSON headline emission** — currently rendered prose-side only; command templates that want to skip stderr parsing would benefit.
+
+### Verification
+- 792/792 tests pass (`node --test 'tests/**/*.test.mjs'`)
+- `node scanners/self-audit.mjs --json --check-readme` returns `configGrade: A` (97), `pluginGrade: A` (100), `readmeCheck.passed: true`
+- README badge updated: `tests-635+` → `tests-792+`
+
 ## [5.0.0] - 2026-05-01
 
 ### Summary

plugins/config-audit/CLAUDE.md

@@ -50,77 +50,6 @@ Analyzes and optimizes Claude Code configuration across three pillars:
 | verifier-agent | Verify results | sonnet | purple | Read, Glob, Grep |
 | feature-gap-agent | Context-aware feature recommendations | opus | green | Read, Glob, Grep, Write |
 
-## Deterministic Scanners
-
-Node.js scanners (zero external dependencies), run via `node scanners/scan-orchestrator.mjs <path>`.
-Posture CLI: `node scanners/posture.mjs <path> [--json] [--global] [--full-machine] [--output-file path]`.
-Scanner CLI: `node scanners/scan-orchestrator.mjs <path> [--global] [--full-machine] [--no-suppress]`.
-
-| Scanner | Prefix | Detects |
-|---------|--------|---------|
-| `claude-md-linter.mjs` | CML | Structure, length, sections, @imports, duplicates, TODOs |
-| `settings-validator.mjs` | SET | Schema, unknown/deprecated keys, type mismatches, permissions |
-| `hook-validator.mjs` | HKV | Format, script existence, event validity, timeouts |
-| `rules-validator.mjs` | RUL | Glob matching, orphan rules, deprecated fields, unscoped rules |
-| `mcp-config-validator.mjs` | MCP | Server types, trust levels, env vars, unknown fields |
-| `import-resolver.mjs` | IMP | Broken @imports, circular refs, deep chains, tilde paths |
-| `conflict-detector.mjs` | CNF | Settings conflicts, permission contradictions, hook duplicates |
-| `feature-gap-scanner.mjs` | GAP | 25 feature checks across 4 tiers — shown as opportunities, not grades |
-| `token-hotspots.mjs` | TOK | Cache-breaking volatile content, redundant tool permissions, deep import chains, oversized cascade, bloated SKILL.md descriptions, MCP tool-schema budget (Opus 4.7 patterns) |
-| `cache-prefix-scanner.mjs` | CPS | Volatile content in lines 31–150 of CLAUDE.md cascade (beyond Pattern A's top-30 window) |
-| `disabled-in-schema-scanner.mjs` | DIS | Tools listed in BOTH `permissions.deny` AND `permissions.allow` — deny wins, allow entries are dead config |
-| `collision-scanner.mjs` | COL | Cross-plugin skill name collisions (low); user-vs-plugin overlaps (medium); `details.namespaces` payload |
-
-### Scanner Lib (`scanners/lib/`)
-
-| Module | Purpose |
-|--------|---------|
-| `severity.mjs` | Severity constants, risk scoring, verdict logic, `WEIGHTS` named export (v5 F3) |
-| `output.mjs` | Finding objects (CA-XXX-NNN format), scanner results, envelope, optional `details` payload (v5 N6) |
-| `file-discovery.mjs` | Config file discovery: single-path, multi-path (`discoverConfigFilesMulti`), full-machine (`discoverFullMachinePaths`) |
-| `yaml-parser.mjs` | Frontmatter parsing, JSON parsing, @import/section extraction |
-| `string-utils.mjs` | Line counting, truncation, similarity, key extraction |
-| `scoring.mjs` | Severity-weighted `scoreByArea` (v5 F3), health scorecard, dedup-by-area (v5 N3), `scoringVersion: 'v5'` |
-| `backup.mjs` | Backup creation, manifest parsing, checksum verification |
-| `diff-engine.mjs` | Drift diffing: diffEnvelopes(), formatDiffReport() |
-| `baseline.mjs` | Baseline save/load/list/delete for drift detection |
-| `report-generator.mjs` | Unified markdown reports: posture, drift, plugin health |
-| `suppression.mjs` | .config-audit-ignore parsing, finding suppression, audit trail |
-| `active-config-reader.mjs` | Read-only inventory: readActiveConfig(), detectGitRoot(), walkClaudeMdCascade(), readClaudeJsonProjectSlice() (longest-prefix match), enumeratePlugins(), enumerateSkills(), readActiveHooks(), readActiveMcpServers() (with cache → package.json tool-count fallback), estimateTokens() (v5: `'mcp'` kind = 500 + toolCount × 200) |
-| `tokenizer-api.mjs` | Anthropic `count_tokens` wrapper for `--accurate-tokens` (v5 N5); 5s AbortController timeout, exponential 429 backoff, key masking |
-
-### Action Engines (`scanners/`)
-
-| Module | Purpose |
-|--------|---------|
-| `fix-engine.mjs` | planFixes(), applyFixes(), verifyFixes() — 9 fix types |
-| `rollback-engine.mjs` | listBackups(), restoreBackup(), deleteBackup() |
-| `fix-cli.mjs` | CLI: `node fix-cli.mjs <path> [--apply] [--json] [--global]` |
-| `drift-cli.mjs` | CLI: `node drift-cli.mjs <path> [--save] [--baseline name] [--json]` |
-| `whats-active.mjs` | CLI: `node whats-active.mjs <path> [--json] [--verbose] [--suggest-disables]` — read-only active-config inventory |
-| `token-hotspots-cli.mjs` | CLI: `node token-hotspots-cli.mjs <path> [--json] [--global] [--output-file path] [--accurate-tokens] [--with-telemetry-recipe]` — Opus-4.7 token hotspots ranking with optional API calibration |
-| `manifest.mjs` | CLI: `node manifest.mjs <path> [--json]` — ranked system-prompt token-source table (v5 N2) |
-
-### Standalone Scanner
-
-| Module | Prefix | Purpose |
-|--------|--------|---------|
-| `plugin-health-scanner.mjs` | PLH | Plugin structure, frontmatter, cross-plugin conflicts (runs independently) |
-| `self-audit.mjs` | — | Runs all scanners + plugin health on this plugin itself |
-
-## Knowledge Base (`knowledge/`)
-
-| File | Content |
-|------|---------|
-| `claude-code-capabilities.md` | Feature register: 18 config surfaces, Anthropic guidance, relevance table |
-| `configuration-best-practices.md` | Per-layer best practices (v5: Opus 4.7 cache-stability guidance replaces Sonnet-era 200-line rule) |
-| `anti-patterns.md` | Common mistakes mapped to scanner IDs |
-| `hook-events-reference.md` | All 26 hook events with details |
-| `feature-evolution.md` | Feature timeline for staleness detection |
-| `gap-closure-templates.md` | Config-specific templates for closing gaps |
-| `opus-4.7-patterns.md` | Token-cost dynamics for Opus 4.7 era — patterns powering the TOK scanner |
-| `cache-telemetry-recipe.md` | Manual `jq` recipe for verifying prompt-cache hit rate from session transcripts (v5 M7) |
-
 ## Hooks
 
 | Event | Script | Purpose |
@@ -130,6 +59,21 @@ Scanner CLI: `node scanners/scan-orchestrator.mjs <path> [--global] [--full-mach
 | SessionStart | `session-start.mjs` | Checks for active (unfinished) sessions |
 | Stop | `stop-session-reminder.mjs` | Reminds about current session phase |
 
+## Reference docs (read on demand)
+
+- **Scanner inventory, lib modules, action engines, knowledge base:** `docs/scanner-internals.md`
+- **Plain-language output (v5.1.0), humanizer vocabularies, output modes:** `docs/humanizer.md`
+
+## Plain-Language Output (v5.1.0) — summary
+
+Default output of all 18 commands routes through `humanizeEnvelope` from `lib/humanizer.mjs`. Findings get three decorated fields:
+
+- `userImpactCategory` — Configuration mistake / Conflict / Wasted tokens / Dead config / Missed opportunity
+- `userActionLanguage` — Fix this now / Fix soon / Fix when convenient / Optional cleanup / FYI (derived from severity)
+- `relevanceContext` — `affects-everyone` (default) / `affects-this-machine-only` (`*.local.*` files) / `test-fixture-no-impact`
+
+`--raw` bypasses the humanizer for byte-stable v5.0.0 output. `--json` is also byte-stable. Full detail and Wave 5 lessons: `docs/humanizer.md`.
+
 ## Suppressions
 
 Create `.config-audit-ignore` at project root to suppress known findings:
@@ -165,7 +109,7 @@ Default: auto-detects scope from git context. Override with `/config-audit full|
 node --test 'tests/**/*.test.mjs'
 ```
 
-635 tests across 36 test files (12 lib + 23 scanner + 1 hook). Test fixtures in `tests/fixtures/`.
+792 tests across 52 test files (15 lib + 28 scanner + 1 hook + 1 agent + 3 commands + 4 top-level). Test fixtures in `tests/fixtures/`. Top-level humanizer tests: `json-backcompat.test.mjs`, `raw-backcompat.test.mjs`, `scenario-read-test.test.mjs`, `snapshot-default-output.test.mjs`.
 
 ## Gotchas
 

plugins/config-audit/GOVERNANCE.md

@@ -0,0 +1,131 @@
+# Governance
+
+How this marketplace is maintained, what you can expect from upstream, and how it's meant to be used.
+
+## TL;DR
+
+- Solo-maintained, AI-assisted development, MIT licensed.
+- **Fork-and-own is the default model.** Upstream is a starting point, not a vendor.
+- Issues welcome as signals. Pull requests are not accepted — see [Why no PRs](#pull-requests--no).
+- No SLA. Best-effort bug fixes and security advisories. Breaking changes happen and are noted in each plugin's CHANGELOG.
+
+---
+
+## Can I trust this?
+
+Be honest with yourself about what you're adopting:
+
+- **One maintainer.** If I get hit by a bus, the bus wins. The repos stay up under MIT, but no one owes you a fix.
+- **AI-generated code with human review.** Every plugin is built through dialog-driven development with Claude Code. I read, test, and judge the output before it ships, but I'm not auditing every line the way a security firm would. Treat it accordingly.
+- **No commercial interests.** I'm not selling a SaaS, not steering you toward a paid tier, not collecting telemetry. The plugins run locally in your Claude Code installation.
+- **MIT licensed.** Fork it, modify it, ship it under your own name.
+
+If you work somewhere that needs vendor accountability, support contracts, or signed assurances — **this isn't that.** Use it as a reference implementation, fork it into your own organization, and own the result.
+
+---
+
+## How this is meant to be used
+
+### Fork-and-own
+
+The intended workflow:
+
+1. **Fork** the marketplace (or a single plugin) into your own organization or namespace.
+2. **Tailor** it to your context — terminology, integrations, cycle lengths, regulatory framing, whatever doesn't fit out of the box.
+3. **Maintain it yourself.** Treat your fork as the canonical version for your team.
+4. **Watch upstream selectively.** Cherry-pick changes that help, ignore changes that don't. There's no obligation to stay in sync.
+
+This isn't a workaround for not accepting PRs. It's the actual recommended adoption pattern, especially for plugins like `okr` and `ms-ai-architect` where every Norwegian public sector organization will need its own tildelingsbrev mappings, terminology, and integrations. A central "one true plugin" would be wrong for everyone.
+
+### What to change first when you fork
+
+Each plugin differs, but the common edits are:
+
+- **Identity** — rename the plugin, replace authorship, update README.
+- **External integrations** — issue trackers, knowledge bases, dashboards, observability backends. The plugins ship as starting points, not pre-wired. Every organization must configure its own integrations.
+- **Norwegian-specific framing** — relevant for `okr` and `ms-ai-architect`. Other plugins are jurisdiction-neutral. Rewrite for your jurisdiction if you're outside Norway.
+- **Reference docs** — the knowledge base in each plugin reflects my reading. Replace with your organization's authoritative sources.
+- **Hooks and policies** — security thresholds, blocked commands, and audit gates are tuned to my taste. Tune them to yours.
+
+### Staying current with upstream
+
+If you want to pull in upstream changes later:
+
+- **Cherry-pick, don't merge.** Each plugin moves independently and breaking changes land without ceremony.
+- **Read the CHANGELOG first.** Every plugin has one.
+- **Keep your customizations in clearly-named files.** The harder upstream is to merge cleanly, the more painful staying current becomes. A `local/` directory or `*.local.md` convention helps.
+
+---
+
+## What upstream provides
+
+| | What I do | What I don't |
+|---|---|---|
+| **Bug fixes** | Best-effort when I notice or get a clear report | No SLA, no triage commitment |
+| **Security issues** | Investigate within reasonable time, document in CHANGELOG | No CVE process, no embargo coordination |
+| **New features** | When they fit my own usage | Not on request |
+| **Norwegian public sector context** | Kept current as long as the project lives | If I lose interest or change jobs, the framing freezes |
+| **Breaking changes** | Documented in CHANGELOG | They happen — version pin if you need stability |
+| **Compatibility** | Tracked against current Claude Code releases | No long-term support branches |
+
+If any of this is a dealbreaker — fork now, version-pin, and stop reading upstream.
+
+---
+
+## How to contribute
+
+### Issues — yes, please
+
+Issues are the most valuable thing you can send me:
+
+- **Bug reports** with reproduction steps. Even a screenshot helps.
+- **Use-case feedback.** "I tried to use this in my organization and X didn't fit" is genuinely useful, even if I can't fix it for you.
+- **Pointers to better sources.** If you know a DFØ veileder, an NSM guideline, or an academic paper that contradicts what's in a knowledge base, tell me.
+- **Security findings.** See each plugin's `SECURITY.md` for disclosure preference where one exists; otherwise email rather than open a public issue.
+
+### Pull requests — no
+
+This is deliberate, not laziness:
+
+- **Solo review is a bottleneck.** Honest PR review takes me longer than rewriting from scratch. The math doesn't work.
+- **Forks are where the value is.** The fork-and-own model means upstream consolidation isn't the point. Your organization's adaptations belong in your fork, not mine.
+- **AI-generated code complicates provenance.** Every line here is produced through dialog with Claude Code, with me as the judge. Mixing in PRs from contributors with different processes and licensing assumptions creates a mess I'd rather not untangle.
+
+If you've built something useful on top of a fork, **publish it under your own name and link back.** I'll happily list notable forks here once they exist.
+
+### Notable forks
+
+*(To be populated as forks emerge. If you've forked one of these plugins for production use, open an issue and I'll add a link.)*
+
+---
+
+## Relationship between plugins
+
+These plugins are **independent**. Install one without the others, fork one without the others. They share conventions (slash command naming, hook patterns, AI-generated disclosure) but no runtime dependencies.
+
+The marketplace is a **catalog**, not a suite. Don't fork the whole repo unless you actually want to maintain everything.
+
+---
+
+## Versioning and stability
+
+- **Semantic versioning per plugin.** Each plugin has its own `CHANGELOG.md` and version number.
+- **Breaking changes happen.** I bump the major version when they do, but I don't run an LTS branch.
+- **Pin your version.** If stability matters more than features, install a specific version and stay there until you choose to upgrade.
+
+---
+
+## Public sector adoption notes
+
+For Norwegian etater specifically:
+
+- **DPIA-relevant data flows are documented in the relevant plugin README where applicable.** Read them before installation.
+- **No data leaves your machine** beyond what Claude Code itself sends to Anthropic. The plugins themselves do not call external services unless you configure an integration.
+- **Drøftingsplikt and ledelsesansvar** are not replaced by these tools. The `okr` plugin coaches; it does not decide. The `ms-ai-architect` plugin advises; it does not approve.
+- **Choose your Claude deployment carefully.** claude.ai vs. API direct vs. Bedrock in EU region have different data residency profiles. The plugins don't choose for you.
+
+---
+
+## License
+
+MIT for all plugins in this marketplace. See each plugin's `LICENSE` file.

plugins/config-audit/README.md

@@ -2,17 +2,17 @@
 
 > Know if your configuration is correct. Find what could improve it. Fix it automatically.
 
-*Built for my own Claude Code workflow and shared openly for anyone who finds it useful. This is a solo project — bug reports and feature requests are welcome, but pull requests are not accepted.*
+> **Solo-maintained, fork-and-own.** This plugin is a starting point, not a vendor product. Issues are welcome as signals; pull requests are not accepted. See [GOVERNANCE.md](GOVERNANCE.md) for the full model and what upstream provides.
 
 *AI-generated: all code produced by Claude Code through dialog-driven development. [Full disclosure →](../../README.md#ai-generated-code-disclosure)*
 
-![Version](https://img.shields.io/badge/version-5.0.0-blue)
+![Version](https://img.shields.io/badge/version-5.1.0-blue)
 ![Platform](https://img.shields.io/badge/platform-Claude_Code_Plugin-purple)
 ![Scanners](https://img.shields.io/badge/scanners-12-cyan)
 ![Commands](https://img.shields.io/badge/commands-18-green)
 ![Agents](https://img.shields.io/badge/agents-6-orange)
 ![Hooks](https://img.shields.io/badge/hooks-4-red)
-![Tests](https://img.shields.io/badge/tests-635+-brightgreen)
+![Tests](https://img.shields.io/badge/tests-792+-brightgreen)
 ![License](https://img.shields.io/badge/license-MIT-lightgrey)
 
 A Claude Code plugin that checks configuration health, suggests context-aware improvements, and auto-fixes issues — `CLAUDE.md`, `settings.json`, hooks, rules, MCP servers, `@imports`, and plugins. 12 deterministic scanners across 10 quality areas, context-aware feature recommendations, auto-fix with backup/rollback, an Opus-4.7-aware Token Hotspots scanner with optional API-calibrated `--accurate-tokens` mode, plus cache-prefix stability, dead-tool, and cross-plugin collision detection. Zero external dependencies.
@@ -21,6 +21,7 @@ A Claude Code plugin that checks configuration health, suggests context-aware im
 
 ## Table of Contents
 
+- [What's New in v5.1.0](#whats-new-in-v510)
 - [What Is This?](#what-is-this)
 - [The Configuration Problem](#the-configuration-problem)
 - [Quick Start](#quick-start)
@@ -44,6 +45,59 @@ A Claude Code plugin that checks configuration health, suggests context-aware im
 
 ---
 
+## What's New in v5.1.0
+
+**Plain-language UX humanizer** — every command's default output now leads with prose. Findings are grouped by what they mean for the user (Configuration mistake, Conflict, Wasted tokens, Missed opportunity, Dead config) and led with an urgency phrase (Fix this now, Fix soon, Fix when convenient, Optional cleanup, FYI). Technical IDs (`CA-CML-001`, `CA-TOK-005`, …) still appear, but at end-of-line where they belong as references rather than headlines.
+
+### Before / after
+
+```
+v5.0.0 default
+  - [low] CA-CNF-001: Hook duplicate event registration
+
+v5.1.0 default
+  - [low] The same automation is set up more than once
+
+v5.1.0 with --json (machine-readable, byte-stable)
+  { "id": "CA-CNF-001", "title": "...", "userImpactCategory": "Conflict",
+    "userActionLanguage": "Optional cleanup", "relevanceContext": "affects-everyone" }
+```
+
+### Plain-language vocabulary
+
+The toolchain uses these terms when describing findings:
+
+| User-facing label | What it means |
+|-------------------|---------------|
+| Fix this now | Something is broken or risky and should be addressed immediately |
+| Fix soon | High-priority issue worth scheduling this week |
+| Fix when convenient | Real issue but not urgent |
+| Optional cleanup | Tidy-up that improves polish but isn't required |
+| FYI | Informational; no action expected |
+| Configuration mistake | A configuration file has an error or omission |
+| Conflict | Two configuration sources disagree |
+| Wasted tokens | Configuration is loading content that costs tokens without payback |
+| Missed opportunity | A Claude Code feature you aren't using that could help your project |
+| Dead config | Configuration that has no effect (e.g., a permission that's also denied) |
+
+### Backwards compatibility — the `--raw` flag
+
+Every CLI accepts `--raw` for byte-stable v5.0.0 verbatim output (technical IDs, raw severity, no prose translation). `--json` is unchanged from v5.0.0 — already byte-stable for programmatic consumption. Use `--raw` only if you've built tooling against v5.0.0 stderr scrapes; for new automation, prefer `--json`.
+
+```bash
+node scanners/posture.mjs .                # v5.1.0 plain-language default
+node scanners/posture.mjs . --raw          # v5.0.0 verbatim (byte-stable)
+node scanners/posture.mjs . --json         # unchanged JSON envelope
+```
+
+### What's not changed
+
+- All scanner internals (12 scanners + standalone PLH) emit the same finding IDs and structural data — humanization happens at output-formatting time only
+- `--json` envelope shape is byte-stable with v5.0.0 (humanizer fields are additive on findings only in default mode; the `--json` path bypasses humanization entirely)
+- 635 tests grew to 792 (+157 covering humanizer module, scenario read-tests, forbidden-words lint, JSON / `--raw` backwards-compat, default-output snapshots, and command-template / agent-prompt shape)
+
+---
+
 ## What Is This?
 
 Claude Code reads instructions from at least 7 different file types across multiple scopes: `CLAUDE.md`, `settings.json`, `.claude/rules/`, `hooks.json`, `.mcp.json`, `.claudeignore`, and `settings.local.json`. Each can exist at project level, user level, or both. Plugins add more. The system is powerful — but nobody tells you what you're using wrong, what you're missing, or what's silently conflicting.
@@ -544,6 +598,7 @@ This plugin is cautious by design — configuration files are important, and a b
 
 | Version | Date | Highlights |
 |---------|------|-----------|
+| **5.1.0** | 2026-05-01 | Plain-language UX humanizer. Default output of all 18 commands now leads with prose; findings grouped by user-impact category (Configuration mistake, Conflict, Wasted tokens, Missed opportunity, Dead config) and led by urgency phrase (Fix this now → FYI). New `--raw` flag preserves v5.0.0 verbatim output for tooling that scrapes stderr; `--json` is unchanged and byte-stable. New scanner-lib modules: `humanizer.mjs`, `humanizer-data.mjs` with TRANSLATIONS for 13 scanner prefixes. Self-audit terminal output also humanized. 792 tests (+157 humanizer-tester) |
 | **5.0.0** | 2026-05-01 | Reality-based token-optimization. 3 new scanners (CPS cache-prefix, DIS dead tools, COL plugin collisions) → 12 deterministic scanners. New `/config-audit manifest` and `--accurate-tokens` API calibration. Severity-weighted scoring (`scoringVersion: 'v5'`). MCP token estimates 15 → 500+. Plugin Hygiene as 10th quality area. Knowledge: cache-stability replaces 200-line rule, cache-telemetry recipe. **Breaking:** F2 token magnitude jump, F3 severity weighting, F5 Pattern D removed, N1 `CA-TOK-*` glob now matches CA-TOK-005. 635 tests |
 | **4.0.0** | 2026-04-19 | Opus 4.7 era: new TOK scanner (cache-breaking volatile content, redundant tool permissions, deep import chains, sonnet-era setups), `/config-audit tokens` command, Token Efficiency 8th quality area, scanner-agent + verifier-agent migrated haiku → sonnet. 543 tests |
 | **3.1.0** | 2026-04-14 | New `/config-audit whats-active` — read-only inventory of active plugins, skills, MCP, hooks, CLAUDE.md for a repo, with token estimates. 522 tests |

plugins/config-audit/agents/analyzer-agent.md

@@ -27,12 +27,23 @@ Analyze all discovered configuration files to:
 You will receive:
 1. Session ID with findings in `~/.claude/config-audit/sessions/{session-id}/findings/`
 2. Scope configuration from `~/.claude/config-audit/sessions/{session-id}/scope.yaml`
-3. Scanner JSON envelope (if available) from scan-orchestrator.mjs
+3. Scanner JSON envelope (if available) from scan-orchestrator.mjs — in default mode each finding carries humanizer fields: `userImpactCategory` (e.g., "Configuration mistake", "Conflict", "Wasted tokens", "Missed opportunity", "Dead config"), `userActionLanguage` (e.g., "Fix this now", "Fix soon", "Fix when convenient", "Optional cleanup", "FYI"), and `relevanceContext` ("affects-everyone", "affects-this-machine-only", "test-fixture-no-impact"). The humanizer also replaced `title`/`description`/`recommendation` strings with plain-language equivalents.
-4. Knowledge base at `{CLAUDE_PLUGIN_ROOT}/knowledge/` for best practices and anti-patterns
+4. Mode flag — when `$RAW_FLAG` is `--raw`, the envelope is v5.0.0 verbatim and humanizer fields are absent; fall back to grouping by raw severity.
+5. Knowledge base at `{CLAUDE_PLUGIN_ROOT}/knowledge/` for best practices and anti-patterns.
+
+## Humanizer-aware rendering rules
+
+- **Render the humanizer's `title`/`description`/`recommendation` verbatim.** Do not paraphrase. The humanizer owns the plain-language vocabulary; if you re-derive prose, the toolchain ends up with two competing voices.
+- **Group findings by `userImpactCategory`.** This replaces severity-bucket grouping in the report. The categories are pre-translated — do not invent your own bucket names.
+- **Lead each finding line with `userActionLanguage`.** This replaces raw severity prefiks ("critical", "high", "medium") in the report. Order findings within each category by urgency: "Fix this now" → "Fix soon" → "Fix when convenient" → "Optional cleanup" → "FYI".
+- **Surface `relevanceContext` when it isn't `affects-everyone`.** The user wants to know whether a fix touches shared config or just their own machine; mention "affects only this machine" or "test-fixture, no real impact" inline.
+- **Do not include "explain what X means" subroutines.** Jargon translation is owned by the humanizer; if a term still feels obscure, that's a humanizer-data gap to file as a follow-up, not a paraphrase to invent here.
+
+In `--raw` mode, fall back to v5.0.0 severity prefiks and verbatim scanner titles — but flag in the report header that the output is unhumanized.
 
 ## Task
 
-1. **Load all findings**: Read all `*.yaml` files from findings directory
+1. **Load all findings**: Use the Read tool on all `*.yaml` files from findings directory
 1.5. **Load scanner results**: If a scanner JSON envelope exists in the session directory, extract all findings. Cross-reference against `knowledge/anti-patterns.md` to add remediation context. Note any CA-{prefix}-NNN finding IDs in the report.
 2. **Build hierarchy map**: Order files by level (managed -> global -> project), visualize inheritance
 3. **Detect conflicts**: Compare settings across hierarchy levels, note which level wins
@@ -40,7 +51,7 @@ You will receive:
 5. **Identify optimizations**: Rules to globalize, missing configs, orphaned files
 6. **Security scan**: Aggregate secret warnings, check for insecure patterns
 7. **CLAUDE.md quality assessment**: Score each file against rubric, assign letter grades
-8. **Generate report**: Write comprehensive markdown report
+8. **Generate report**: Write comprehensive markdown report — group findings by `userImpactCategory`, lead with `userActionLanguage`
 
 ## Output
 

plugins/config-audit/agents/feature-gap-agent.md

@@ -19,10 +19,17 @@ You receive posture assessment data (JSON) containing:
 - `areas` — per-scanner grades (10 quality areas incl. Token Efficiency, Plugin Hygiene, + Feature Coverage)
 - `overallGrade` — health grade (quality areas only)
 - `opportunityCount` — number of unused features detected
-- `scannerEnvelope` — full scanner results including GAP findings
+- `scannerEnvelope` — full scanner results. In default mode each GAP finding carries humanizer fields: `userImpactCategory` ("Missed opportunity"), `userActionLanguage` ("Fix soon", "Fix when convenient", "Optional cleanup", "FYI"), and `relevanceContext`. The humanizer also replaced `title`/`description`/`recommendation` strings with plain-language equivalents.
 
 You also receive project context: language, file count, existing configuration.
 
+## Humanizer-aware rendering rules
+
+- **Render the humanizer's `title`/`description`/`recommendation` verbatim.** Do not paraphrase. The humanizer owns the plain-language vocabulary.
+- **Drive prioritization with `userActionLanguage`, not raw category tiers.** "Fix soon" → "Fix when convenient" → "Optional cleanup" → "FYI" replaces the t1/t2/t3/t4 tier ladder for output ordering.
+- **Skip findings with `relevanceContext === "test-fixture-no-impact"`** unless the user explicitly asked to include fixtures.
+- **Do not include "explain what X means" subroutines.** The category labels ("Missed opportunity") are pre-translated.
+
 ## Knowledge Files
 
 Read **at most 3** of these files from the plugin's `knowledge/` directory:
@@ -36,6 +43,8 @@ Write `feature-gap-report.md` to the session directory. Max 200 lines.
 
 ### Report Structure
 
+Group findings by `userActionLanguage` rather than by raw category tier. Render the humanizer's `title` and `recommendation` verbatim — the humanizer has already produced plain-language equivalents.
+
 ```markdown
 # Feature Opportunities
 
@@ -47,38 +56,34 @@ Write `feature-gap-report.md` to the session directory. Max 200 lines.
 
 ## High Impact
 
-These address correctness or security — consider them seriously.
+[Findings where userActionLanguage is "Fix soon" — these address correctness or security; consider them seriously.]
 
-→ **[feature name]**
+→ **[humanized title verbatim]**
-  Why: [evidence-backed reason, cite Anthropic docs or proven issues]
+  Why: [humanized description verbatim, plus "relevant because your project has X" context]
-  How: [2-3 concrete steps]
+  How: [humanized recommendation verbatim, broken into 2-3 concrete steps from gap-closure-templates.md]
-
-[Repeat for each T1 finding]
 
 ## Worth Considering
 
-These improve workflow efficiency for projects like yours.
+[Findings where userActionLanguage is "Fix when convenient" — these improve workflow efficiency for projects like yours.]
 
-→ **[feature name]**
+→ **[humanized title verbatim]**
-  Why: [reason, with "relevant because your project has X"]
+  Why: [humanized description verbatim, plus relevance context]
-  How: [2-3 concrete steps]
+  How: [humanized recommendation verbatim, broken into 2-3 concrete steps]
-
-[Repeat for each T2 finding]
 
 ## Explore When Ready
 
-Nice-to-have features. Skip these if your current setup works well.
+[Findings where userActionLanguage is "Optional cleanup" or "FYI" — nice-to-have, skip if current setup works well.]
 
-→ **[feature name]**
+→ **[humanized title verbatim]**
-  Why: [brief reason]
+  Why: [humanized description verbatim, brief]
-
-[Repeat for T3/T4 findings, keep brief]
 
 ## When You Might Skip These
 
-[Honest qualification: which recommendations are genuinely optional and why. A minimal setup can be the right choice.]
+[Honest qualification: which recommendations are genuinely optional and why. A minimal setup can be the right choice. Mention any findings whose `relevanceContext` is `affects-this-machine-only` so the user knows the change won't propagate to teammates.]
 ```
 
+In `--raw` mode (humanizer fields absent), fall back to grouping by raw category tier (t1/t2/t3/t4) and render scanner-emitted titles verbatim — flag in the report header that output is unhumanized.
+
 ## Guidelines
 
 - Frame everything as opportunities, never as failures or gaps

plugins/config-audit/agents/planner-agent.md

@@ -25,15 +25,26 @@ You will receive:
 1. Session ID
 2. Analysis report: `~/.claude/config-audit/sessions/{session-id}/analysis-report.md`
 3. Interview results: `~/.claude/config-audit/sessions/{session-id}/interview.md` (optional)
+4. Mode flag — `$RAW_FLAG`. When empty (default), the analysis report uses humanized vocabulary: each finding has been grouped by `userImpactCategory` and led with `userActionLanguage`. When `--raw`, the report is v5.0.0 verbatim severity prefiks.
+
+## Humanizer-aware planning rules
+
+- **Consume humanized fields from the analysis report.** The analyzer-agent has already grouped findings by `userImpactCategory` ("Configuration mistake", "Conflict", "Wasted tokens", "Missed opportunity", "Dead config") and led each line with `userActionLanguage` ("Fix this now", "Fix soon", "Fix when convenient", "Optional cleanup", "FYI"). Carry that vocabulary forward into the action plan — do not re-derive severity-to-prose mappings.
+- **Render finding titles and recommendations verbatim** as they appear in the analysis report. The humanizer owns the plain-language vocabulary; rephrasing introduces drift between report and plan.
+- **Order actions by `userActionLanguage` urgency**, not by raw severity. "Fix this now" + "Fix soon" precede "Fix when convenient" precede "Optional cleanup" precede "FYI".
+- **Surface `relevanceContext`** when an action only affects the user's machine or only touches test fixtures — these warrant different escalation paths.
+- **Do not perform translation duties in the action plan.** No "what this means in plain English" sections. The humanizer handles that upstream; if a finding's prose still reads like jargon, that's a data gap to flag, not a translation to invent.
+
+In `--raw` mode, the analysis report is v5.0.0 verbatim — fall back to severity-based prioritization and surface raw scanner titles. Flag in the plan header that the plan was generated from unhumanized analysis.
 
 ## Task
 
-1. **Load inputs**: Read analysis and interview (if exists)
+1. **Load inputs**: Use the Read tool on the analysis report and interview (if exists)
-2. **Generate actions**: Create action items for each finding
+2. **Generate actions**: Create action items for each finding, preserving humanized titles
 3. **Assess risk**: Evaluate risk level per action
-4. **Order by dependencies**: Ensure correct execution order
+4. **Order by dependencies AND `userActionLanguage`**: dependency-correct AND urgency-correct
 5. **Create rollback plans**: Define how to undo each action
-6. **Write action plan**: Output comprehensive plan
+6. **Write action plan**: Output comprehensive plan grouped by `userImpactCategory`
 
 ## Action Categories
 

plugins/config-audit/commands/analyze.md

@@ -14,11 +14,15 @@ Generate comprehensive analysis report from discovery findings.
 - Must have completed Phase 1 (discovery)
 - Findings must exist in `~/.claude/config-audit/sessions/{session-id}/findings/`
 
+## Arguments
+
+- `$ARGUMENTS` may contain `--raw` to forward to the analyzer agent's instructions; in `--raw` mode the agent renders v5.0.0 verbatim severity prefiks instead of humanized `userActionLanguage` urgency phrasing.
+
 ## Implementation
 
 ### Step 1: Verify session state
 
-Read `~/.claude/config-audit/sessions/{session-id}/state.yaml` and verify discovery phase completed. If not, tell the user: "Discovery hasn't been run yet. Start with `/config-audit discover` or just run `/config-audit` for a full audit."
+Read `~/.claude/config-audit/sessions/{session-id}/state.yaml` using the Read tool and verify discovery phase completed. If not, tell the user: "Discovery hasn't been run yet. Start with `/config-audit discover` or just run `/config-audit` for a full audit."
 
 ### Step 2: Tell the user what's happening
 
@@ -33,18 +37,29 @@ This includes hierarchy mapping, conflict detection, and prioritized recommendat
 
 Tell the user: **"Generating analysis (this takes about 30 seconds)..."**
 
+```bash
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+```
+
 ```
 Agent(subagent_type: "config-audit:analyzer-agent")
   model: sonnet
   prompt: |
     Analyze all findings in: ~/.claude/config-audit/sessions/{session-id}/findings/
+    Mode: $RAW_FLAG (empty = humanized; "--raw" = v5.0.0 verbatim severity prefiks)
     Generate comprehensive report covering:
-    1. Executive summary with key metrics
+    1. Executive summary with key metrics, grouped by userImpactCategory
     2. Hierarchy map visualization
     3. Conflict detection across config layers
     4. CLAUDE.md quality assessment
     5. Security issues (secrets, permissions)
-    6. Top 10 prioritized recommendations
+    6. Top 10 prioritized recommendations — lead each item with the
+       finding's userActionLanguage ("Fix this now," "Fix soon,"
+       "Fix when convenient," "Optional cleanup," "FYI") rather than
+       raw severity. The humanizer already replaced jargon-heavy
+       title/description/recommendation strings with plain-language
+       equivalents — render them verbatim, do not paraphrase.
     Output to: ~/.claude/config-audit/sessions/{session-id}/analysis-report.md
 ```
 

plugins/config-audit/commands/cleanup.md

@@ -13,13 +13,23 @@ Manage and clean up accumulated config-audit sessions in `~/.claude/config-audit
 
 ```
 /config-audit cleanup
+/config-audit cleanup --raw   # pass-through accepted; no-op (cleanup is file-management only, no findings prose)
 ```
 
 ## Implementation Steps
 
+0. **Parse flags**:
+
+   ```bash
+   RAW_FLAG=""
+   if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+   ```
+
+   `--raw` is accepted for CLI surface consistency but is a no-op here — cleanup manages session directories on disk, it does not produce findings prose.
+
 1. **List all sessions**:
    - Glob `~/.claude/config-audit/sessions/*/state.yaml`
-   - For each session, read state.yaml and extract:
+   - Use the Read tool on each session's state.yaml and extract:
      - Session ID
      - Created timestamp
      - Current phase
@@ -27,7 +37,7 @@ Manage and clean up accumulated config-audit sessions in `~/.claude/config-audit
 
 2. **Calculate disk usage**:
    - Use `du -sh ~/.claude/config-audit/sessions/{session-id}/` for each session
-   - Calculate total usage
+   - Calculate the total amount of disk space used
 
 3. **Display session table**:
    ```

plugins/config-audit/commands/config-audit.md

@@ -82,10 +82,12 @@ This is a silent infrastructure step — do NOT show output to the user.
 
 Tell the user: **"Running 12 configuration scanners..."**
 
-Run both scanners and posture in a single Bash command:
+Run both scanners and posture in a single Bash command. Default mode runs the humanizer, so each finding in `scan-results.json` carries `userImpactCategory`, `userActionLanguage`, and `relevanceContext` alongside the v5.0.0 fields. If the user passed `--raw`, thread it through to both CLIs to get v5.0.0 verbatim output.
 
 ```bash
-node ${CLAUDE_PLUGIN_ROOT}/scanners/scan-orchestrator.mjs <target-path> --output-file ~/.claude/config-audit/sessions/{session-id}/findings/scan-results.json [--full-machine] [--global] 2>/dev/null; node ${CLAUDE_PLUGIN_ROOT}/scanners/posture.mjs <target-path> --json --output-file ~/.claude/config-audit/sessions/{session-id}/posture.json [--full-machine] [--global] 2>/dev/null; echo $?
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+node ${CLAUDE_PLUGIN_ROOT}/scanners/scan-orchestrator.mjs <target-path> --output-file ~/.claude/config-audit/sessions/{session-id}/findings/scan-results.json [--full-machine] [--global] $RAW_FLAG 2>/dev/null; node ${CLAUDE_PLUGIN_ROOT}/scanners/posture.mjs <target-path> --output-file ~/.claude/config-audit/sessions/{session-id}/posture.json [--full-machine] [--global] $RAW_FLAG 2>/dev/null; echo $?
 ```
 
 Use `--full-machine` for `full` scope, `--global` for `home` scope. For `repo` and `current`, pass the resolved path directly.
@@ -134,19 +136,14 @@ Write to: `~/.claude/config-audit/sessions/{session-id}/state.yaml`
 
 ### Step 6: Display results
 
-Present results using this template. Replace all placeholders with actual values. **Adapt the summary sentence based on grade.**
+Present results using this template. The humanizer has already replaced jargon-heavy `title`/`description`/`recommendation` strings on every finding with plain-language equivalents — render them verbatim. Lead urgency phrasing with `userActionLanguage` ("Fix this now", "Fix soon", "Fix when convenient", "Optional cleanup", "FYI") and group "What you can do next" suggestions by that field. Do not re-derive an A/B/C/D/F-to-prose ladder here; the humanized stderr scorecard headline already supplies the grade context, and `userActionLanguage` supplies finding-level urgency.
 
 ```markdown
 ### Results
 
 **Health: {overallGrade}** | {qualityAreaCount} areas scanned
 
-{grade-based summary — pick ONE:}
+{Use the headline line from the humanized stderr scorecard — it carries grade-context prose already. Avoid hardcoding a separate per-grade prose ladder.}
-- Grade A: "Excellent — your configuration is correct and well-maintained."
-- Grade B: "Strong — your configuration is solid with minor improvements available."
-- Grade C: "Decent — your configuration works but has some issues worth addressing."
-- Grade D: "Needs work — several configuration issues could affect your Claude Code experience."
-- Grade F: "Significant issues found — addressing these will meaningfully improve your workflow."
 
 Scanned {files_scanned} files | {real_finding_count} findings ({severity_breakdown})
 {If test_fixture_count > 0: "({test_fixture_count} additional findings in test fixtures were excluded.)"}
@@ -164,26 +161,25 @@ Scanned {files_scanned} files | {real_finding_count} findings ({severity_breakdo
 | Imports | {grade} | {count} | {status} |
 | Conflicts | {grade} | {count} | {status} |
 
-{For the status column, use plain language like: "Well structured", "2 minor issues", "Missing trust levels", "No issues", etc.}
+{For the status column, use the humanized title from the most-severe finding in that area, or a one-phrase plain-language summary. Findings carry userImpactCategory which already groups by impact bucket — use that vocabulary, not raw scanner names.}
 
 {If opportunityCount > 0:}
 {opportunityCount} feature opportunities available — run `/config-audit feature-gap` for context-aware recommendations.
 
 ### What you can do next
 
-{Include only relevant options based on findings. Explain each one:}
+Group suggestions by `userActionLanguage` from the humanized findings:
 
-{If fixable_count > 0:}
+{If any finding has userActionLanguage "Fix this now" or "Fix soon":}
-- **`/config-audit fix`** — Automatically fix {fixable_count} issues. Creates a backup first so you can roll back with one command.
+- **`/config-audit fix`** — auto-fix what's possible (backup created first, one-command rollback). The remaining items go into a prioritized plan.
+- **`/config-audit plan`** — produce a prioritized action plan for the items that need manual attention.
 
-{If real findings > fixable_count:}
+{If most findings are "Fix when convenient" or "Optional cleanup":}
-- **`/config-audit plan`** — Get a prioritized action plan for the {remaining} issues that need manual attention.
+- **`/config-audit feature-gap`** — see which features could enhance your setup; pick what you want and implement on the spot.
+- **`/config-audit fix`** — auto-fix anything deterministic; the rest is genuinely optional.
 
-{If grade is C or better:}
+{If only "FYI" findings:}
-- **`/config-audit feature-gap`** — See which features could help your project, and implement the ones you want on the spot.
+- **`/config-audit feature-gap`** — explore opportunities; nothing is urgent.
-
-{If grade is D or F:}
-- **`/config-audit fix`** should be your first step — it handles the most impactful issues automatically.
 
 Session saved to: `~/.claude/config-audit/sessions/{session-id}/`
 ```

plugins/config-audit/commands/discover.md

@@ -67,10 +67,12 @@ If `--delta` flag:
 
 ### Step 5: Run discovery
 
-Run the scan orchestrator silently to discover and scan files:
+Run the scan orchestrator silently to discover and scan files. Default mode emits humanized JSON — each finding in `scan-results.json` carries `userImpactCategory`, `userActionLanguage`, and `relevanceContext` alongside the v5.0.0 fields. Pass `--raw` through if the user requested it (produces v5.0.0 verbatim envelope; humanizer fields absent).
 
 ```bash
-node ${CLAUDE_PLUGIN_ROOT}/scanners/scan-orchestrator.mjs <target-path> --output-file ~/.claude/config-audit/sessions/{session-id}/findings/scan-results.json [--full-machine] [--global] 2>/dev/null; echo $?
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+node ${CLAUDE_PLUGIN_ROOT}/scanners/scan-orchestrator.mjs <target-path> --output-file ~/.claude/config-audit/sessions/{session-id}/findings/scan-results.json [--full-machine] [--global] $RAW_FLAG 2>/dev/null; echo $?
 ```
 
 Check exit code: 0/1/2 → normal. 3 → "Discovery encountered an error. Try a narrower scope."
@@ -81,7 +83,7 @@ Write `scope.yaml` and `state.yaml` to session directory. Update state with `cur
 
 ### Step 7: Present summary
 
-Read the scan results file to count files and findings:
+Read the scan results file using the Read tool. When you surface initial findings, group them by `userImpactCategory` and lead each line with `userActionLanguage` rather than raw severity prefiks — the humanizer already mapped severity to plain-language phrasing ("Fix this now", "Fix soon", "Fix when convenient", "Optional cleanup", "FYI") so the rest of the toolchain sees consistent wording.
 
 **Full scan:**
 ```markdown
@@ -98,7 +100,7 @@ Read the scan results file to count files and findings:
 | Hooks | {n} |
 | Other | {n} |
 
-Initial scan found {finding_count} items to review.
+Initial scan found {finding_count} items to review (grouped by impact: {comma-separated counts per userImpactCategory}).
 
 **Next:** Run `/config-audit analyze` to generate your analysis report.
 ```

plugins/config-audit/commands/drift.md

@@ -16,6 +16,7 @@ Compare current configuration against a saved baseline to see what changed.
   - A target path (default: current working directory)
   - `--save`: Save current state as baseline
   - `--baseline <name>`: Compare against a specific named baseline (default: "default")
+  - `--raw`: Pass-through to the scanner; produces v5.0.0 verbatim diff output (bypasses the humanizer). Use when piping into v5.0.0-baseline diff tooling that depends on byte-stable output.
 
 ## Implementation
 
@@ -26,7 +27,9 @@ If `--save` is present:
 Tell the user: **"Saving current configuration as baseline..."**
 
 ```bash
-node ${CLAUDE_PLUGIN_ROOT}/scanners/drift-cli.mjs <path> --save --name <baseline-name> 2>/dev/null
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+node ${CLAUDE_PLUGIN_ROOT}/scanners/drift-cli.mjs <path> --save --name <baseline-name> $RAW_FLAG 2>/dev/null
 ```
 
 Read stdout for confirmation. Tell the user:
@@ -45,17 +48,21 @@ Without `--save`:
 Tell the user: **"Comparing current configuration against baseline..."**
 
 ```bash
-node ${CLAUDE_PLUGIN_ROOT}/scanners/drift-cli.mjs <path> --baseline <name> 2>/dev/null
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+node ${CLAUDE_PLUGIN_ROOT}/scanners/drift-cli.mjs <path> --baseline <name> $RAW_FLAG 2>/dev/null
 ```
 
-Read stdout. If baseline not found, tell the user:
+Read stdout. In default mode the diff sections are humanized — finding titles, descriptions, and recommendations have already been replaced with plain-language equivalents. New/resolved/changed finding lists carry `userImpactCategory`, `userActionLanguage`, and `relevanceContext` so you can group and prioritize without re-deriving severity prose. If `--raw` was passed, the v5.0.0 diff is verbatim — present it in a code block as-is.
+
+If baseline not found, tell the user:
 
 ```
 No baseline found. Save one first with:
   /config-audit drift --save
 ```
 
-Otherwise, parse and present the drift report:
+Otherwise, parse and present the drift report. Use the Read tool on the captured stdout (or pipe it into a tmpfile first if you prefer):
 
 ```markdown
 ### Configuration Drift
@@ -65,15 +72,15 @@ Otherwise, parse and present the drift report:
 
 {If new findings:}
 #### New Issues ({count})
-| ID | Severity | Description |
+| ID | Action | Description |
-|----|----------|-------------|
+|----|--------|-------------|
-| ... | ... | ... |
+| {id} | {userActionLanguage — "Fix this now", "Fix soon", etc.} | {humanized title} |
 
 {If resolved findings:}
 #### Resolved ({count})
 | ID | Description |
 |----|-------------|
-| ... | ... |
+| {id} | {humanized title} |
 
 {If area changes:}
 #### Area Changes
@@ -82,6 +89,8 @@ Otherwise, parse and present the drift report:
 | ... | ... | ... | ... |
 ```
 
+When iterating new/resolved findings, prefer `userActionLanguage` over raw `severity` for the "Action" column — the humanizer already mapped severity to plain-language phrasing, and surfacing it consistently keeps the toolchain coherent. Mention `relevanceContext` when it isn't `affects-everyone` (the user wants to know if a fix touches shared config or just their machine).
+
 ### List baselines
 
 If `$ARGUMENTS` contains `--list`:

plugins/config-audit/commands/feature-gap.md

@@ -20,9 +20,11 @@ Context-aware analysis of Claude Code features that could benefit your specific
 
 ## Implementation
 
-### Step 1: Determine target and greet
+### Step 1: Determine target and flags
 
-Parse `$ARGUMENTS` for a path (default: current working directory).
+Split `$ARGUMENTS` into a path and flags. Path is the first non-flag argument (default: current working directory). Recognized flags:
+
+- `--raw` — pass-through to the scanner; produces v5.0.0 verbatim envelope (bypasses the humanizer). When `--raw` is set, render with v5.0.0 finding-field shape only — humanizer fields are absent in raw output.
 
 Tell the user:
 
@@ -38,7 +40,9 @@ Generate session ID (`YYYYMMDD_HHmmss`) if no active session exists.
 
 ```bash
 mkdir -p ~/.claude/config-audit/sessions/{session-id}/findings 2>/dev/null
-node ${CLAUDE_PLUGIN_ROOT}/scanners/posture.mjs <target-path> --json --output-file ~/.claude/config-audit/sessions/{session-id}/posture.json 2>/dev/null; echo $?
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+node ${CLAUDE_PLUGIN_ROOT}/scanners/posture.mjs <target-path> --output-file ~/.claude/config-audit/sessions/{session-id}/posture.json $RAW_FLAG 2>/dev/null; echo $?
 ```
 
 If exit code is non-zero: "Assessment couldn't run. Check that the path exists and contains configuration files."
@@ -59,49 +63,51 @@ ls <target-path>/*.py <target-path>/requirements.txt <target-path>/pyproject.tom
 
 Read `${CLAUDE_PLUGIN_ROOT}/knowledge/gap-closure-templates.md` for implementation templates.
 
-Group GAP findings into three sections. Number them sequentially across sections:
+Group GAP findings by their humanized fields rather than re-deriving tier-to-prose mappings. In default mode (no `--raw`) each finding carries:
+
+- `userImpactCategory` (e.g., "Missed opportunity") — the impact bucket
+- `userActionLanguage` (e.g., "Fix soon", "Fix when convenient", "Optional cleanup", "FYI") — the urgency phrasing the rest of the toolchain uses
+- `relevanceContext` ("affects-everyone" / "affects-this-machine-only" / "test-fixture-no-impact") — the scope so the user knows whether the change touches shared config or just their own machine
+
+Group findings into three sections by `userActionLanguage`: "Fix this now" + "Fix soon" → **High Impact**, "Fix when convenient" → **Worth Considering**, "Optional cleanup" + "FYI" → **Explore When Ready**. Number sequentially across sections. Skip findings whose `relevanceContext === "test-fixture-no-impact"` unless the user explicitly asked to include fixtures.
+
+The humanizer has already replaced jargon-heavy strings with plain-language equivalents in `title`, `description`, and `recommendation` — render those verbatim. Do not paraphrase. Do not introduce inline tier-to-prose tables ("Tier 1 means…"); the categories are pre-translated.
+
+If `--raw` was passed, the v5.0.0 envelope is in effect — humanizer fields are absent. Fall back to grouping by `category` ("t1"/"t2"/"t3"/"t4") and render `title` + `recommendation` directly.
+
+Render shape (default mode):
 
 ```markdown
 ### High Impact
 
-These address correctness or safety — consider them seriously.
+{For each finding where userActionLanguage is "Fix this now" or "Fix soon":}
 
-**1.** Add permissions.deny for sensitive paths
+**{N}.** {title}
-  → Settings enforcement is stronger than CLAUDE.md instructions.
+  → {description}
-  → Effort: Low (5 min)
+  → {recommendation}
-
+  → Effort: {from gap-closure-templates.md}
-**2.** Configure at least one hook for safety automation
-  → Hooks guarantee the action happens. CLAUDE.md instructions are advisory.
-  → Effort: Medium (15 min)
 
 ### Worth Considering
 
-These improve workflow efficiency for projects like yours.
+{For each finding where userActionLanguage is "Fix when convenient":}
 
-**3.** Split CLAUDE.md into focused modules with @imports
+**{N}.** {title}
-  → Files over 200 lines degrade Claude's adherence to instructions.
+  → {description}
-  → Effort: Low (10 min)
+  → {recommendation}
-
-**4.** Add path-scoped rules for different file types
-  → Unscoped rules load every session regardless of relevance.
-  → Effort: Low (10 min)
 
 ### Explore When Ready
 
-Nice-to-have. Skip if your current setup works well.
+{For each finding where userActionLanguage is "Optional cleanup" or "FYI":}
 
-**5.** Custom keybindings (Shift+Enter for newline)
+**{N}.** {title}
-  → Effort: Low (2 min)
+  → {recommendation}
-
-**6.** Status line configuration
-  → Effort: Low (2 min)
 ```
 
 Each recommendation MUST have:
 - A number
-- A one-line description
+- The humanizer-provided `title`
-- A "Why" with evidence
+- The humanizer-provided `description` (where shown)
-- An effort estimate from the templates
+- An effort estimate looked up from the templates
 
 ### Step 5: Ask what to implement
 

plugins/config-audit/commands/fix.md

@@ -15,6 +15,7 @@ Auto-fix deterministic configuration issues. Scans, plans fixes, backs up origin
 - `$ARGUMENTS` may contain:
   - A target path (default: current working directory)
   - `--dry-run`: Show fix plan without applying
+  - `--raw`: Pass-through to scanners; produces v5.0.0 verbatim envelope (bypasses the humanizer) for byte-stable diff tooling
 
 ## Implementation
 
@@ -28,44 +29,50 @@ Tell the user:
 Scanning for auto-fixable issues...
 ```
 
-Run scanners silently:
+Parse flags and run scanners silently. Default mode emits humanized JSON — each finding carries `userImpactCategory`, `userActionLanguage`, and `relevanceContext` alongside the v5.0.0 fields:
 
 ```bash
-node ${CLAUDE_PLUGIN_ROOT}/scanners/scan-orchestrator.mjs <path> --output-file /tmp/config-audit-fix-scan-$$.json [--global] 2>/dev/null; echo $?
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+node ${CLAUDE_PLUGIN_ROOT}/scanners/scan-orchestrator.mjs <path> --output-file /tmp/config-audit-fix-scan-$$.json [--global] $RAW_FLAG 2>/dev/null; echo $?
 ```
 
 Exit code 3 → tell user: "Scanner error. Try `/config-audit posture` to check your configuration."
 
 ### Step 2: Plan fixes
 
-Run fix planner silently:
+Run fix planner silently. The fix-cli emits humanized prose to stderr in default mode and v5.0.0-shape JSON to stdout when `--json` is set; we use `--json` here for structured data and let the humanizer-aware rendering layer (this command's prose output below) supply the plain-language wording from the scan envelope above:
 
 ```bash
 node ${CLAUDE_PLUGIN_ROOT}/scanners/fix-cli.mjs <path> --json 2>/dev/null
 ```
 
-Read the JSON output. Categorize fixes into auto-fixable and manual.
+Read the JSON output using the Read tool. Cross-reference each fix-plan entry against the humanized scan envelope (`/tmp/config-audit-fix-scan-$$.json`) by finding ID to recover the humanized `title`/`description`/`recommendation` plus `userImpactCategory`/`userActionLanguage` for grouping.
 
 ### Step 3: Present fix plan
 
-Show what will be fixed and what needs manual attention:
+Show what will be fixed and what needs manual attention. Group by `userActionLanguage` so the urgency phrasing stays consistent with the rest of the toolchain:
 
 ```markdown
 ### Fix Plan
 
-**Auto-fixable ({N} issues):**
+**Auto-fixable ({N} issues), grouped by impact:**
+
+{For each userActionLanguage bucket in priority order — "Fix this now" → "Fix soon" → "Fix when convenient" → "Optional cleanup" → "FYI":}
+
+#### {userActionLanguage}
 
 | # | ID | Issue | File |
 |---|-----|-------|------|
-| 1 | CA-SET-003 | Add $schema to settings.json | .claude/settings.json |
+| 1 | {id} | {humanized title} | {file} |
-| 2 | ... | ... | ... |
 
-**Manual ({M} issues — require human judgment):**
+**Manual ({M} issues — require human judgment), grouped by impact:**
+
+{Same userActionLanguage grouping. Render humanized title and recommendation verbatim — the humanizer already produced plain-language strings, do not paraphrase.}
 
 | # | ID | Issue | Recommendation |
 |---|-----|-------|----------------|
-| 1 | CA-CML-003 | CLAUDE.md exceeds 200 lines | Split content into @imports or .claude/rules/ |
+| 1 | {id} | {humanized title} | {humanized recommendation} |
-| ... | ... | ... | ... |
 ```
 
 ### Step 4: Confirm with user

plugins/config-audit/commands/help.md

@@ -1,7 +1,7 @@
 ---
 name: config-audit:help
 description: Show all available config-audit commands
-allowed-tools: Read
+allowed-tools: Read, Bash
 model: sonnet
 ---
 
@@ -11,6 +11,19 @@ model: sonnet
 
 Just run `/config-audit` — it auto-detects your project scope and runs a full audit. No setup needed.
 
+The default output is written in plain language: each finding is grouped by impact ("Configuration mistake," "Conflict," "Wasted tokens," "Missed opportunity," "Dead config") and led with an urgency phrase ("Fix this now," "Fix soon," "Fix when convenient," "Optional cleanup," "FYI").
+
+If you prefer the v5.0.0 verbatim output (technical IDs, raw severity, no plain-language wording), pass `--raw` to any command — it's threaded through every CLI in the toolchain. Use the Read tool on the saved JSON to consume it programmatically.
+
+```bash
+# Examples — every command accepts --raw for byte-stable v5.0.0 output
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+# /config-audit posture --raw
+# /config-audit tokens --raw
+# /config-audit fix --raw
+```
+
 ## All Commands
 
 ### Core
@@ -22,15 +35,15 @@ Just run `/config-audit` — it auto-detects your project scope and runs a full
 | `/config-audit tokens` | Opus-4.7 token hotspots; optional `--accurate-tokens` API calibration |
 | `/config-audit manifest` | Ranked table of every system-prompt token source |
 | `/config-audit feature-gap` | Deep analysis of features you're not using |
-| `/config-audit fix` | Auto-fix deterministic issues with backup |
+| `/config-audit fix` | Auto-fix deterministic issues; a copy of every changed file is saved first so you can roll back with one command |
-| `/config-audit rollback` | Restore configuration from a backup |
+| `/config-audit rollback` | Restore configuration from a saved copy |
 
 ### Planning & Implementation
 
 | Command | Description |
 |---------|-------------|
 | `/config-audit plan` | Generate prioritized action plan from audit findings |
-| `/config-audit implement` | Execute action plan with automatic backup + verification |
+| `/config-audit implement` | Execute action plan; a copy of every changed file is saved first, and a verification pass runs after |
 | `/config-audit interview` | Set preferences to customize the action plan _(optional)_ |
 
 ### Monitoring
@@ -38,7 +51,7 @@ Just run `/config-audit` — it auto-detects your project scope and runs a full
 | Command | Description |
 |---------|-------------|
 | `/config-audit drift` | Compare current config against a saved baseline |
-| `/config-audit plugin-health` | Audit plugin structure and frontmatter quality |
+| `/config-audit plugin-health` | Audit plugin structure and the metadata block at the top of each command/agent file |
 | `/config-audit whats-active` | Show active plugins/skills/MCP/hooks/CLAUDE.md with token estimates |
 
 ### Utility
@@ -55,6 +68,25 @@ Just run `/config-audit` — it auto-detects your project scope and runs a full
 | `/config-audit discover` | Run only the discovery phase (find config files) |
 | `/config-audit analyze` | Run only the analysis phase (generate report) |
 
+## Plain-language vocabulary
+
+The toolchain uses these terms when describing findings:
+
+| User-facing label | What it means |
+|-------------------|---------------|
+| Fix this now | Something is broken or risky and should be addressed immediately |
+| Fix soon | High-priority issue worth scheduling this week |
+| Fix when convenient | Real issue but not urgent |
+| Optional cleanup | Tidy-up that improves polish but isn't required |
+| FYI | Informational; no action expected |
+| Configuration mistake | A configuration file has an error or omission |
+| Conflict | Two configuration sources disagree |
+| Wasted tokens | Configuration is loading content that costs tokens without payback |
+| Missed opportunity | A Claude Code feature you aren't using that could help your project |
+| Dead config | Configuration that has no effect (e.g., a permission that's also denied) |
+
+Use `--raw` if you'd rather see the v5.0.0 verbatim output (technical IDs and raw severity).
+
 ## Scope Override
 
 By default, `/config-audit` auto-detects scope from your current directory:

plugins/config-audit/commands/implement.md

@@ -14,13 +14,22 @@ Execute the action plan with full backup, verification, and rollback support.
 - Must have completed Phase 4 (plan)
 - Action plan at `~/.claude/config-audit/sessions/{session-id}/action-plan.md`
 
+## Arguments
+
+- `$ARGUMENTS` may contain `--raw` to forward to the implementer-agent's instructions; in `--raw` mode the agent renders v5.0.0 verbatim severity prefiks instead of humanized `userActionLanguage` urgency phrasing.
+
 ## Implementation
 
-### Step 1: Load and verify
+### Step 1: Parse flags, load and verify
+
+```bash
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+```
 
 Find the most recent session with a plan. If none: "No action plan found. Run `/config-audit plan` first."
 
-Read the action plan and count actions. Tell the user:
+Use the Read tool on the action plan and count actions. Tell the user:
 
 ```
 ## Implementing Action Plan
@@ -62,16 +71,20 @@ Agent(subagent_type: "config-audit:implementer-agent")
   prompt: |
     Execute action: {action-id}
     File: {file-path}, Type: {create|modify|delete}
+    Mode: $RAW_FLAG (empty = humanized progress prose; "--raw" = v5.0.0 verbatim)
     Details: {changes}
     Verify backup exists, make change, validate syntax.
-    Append result to: ~/.claude/config-audit/sessions/{session-id}/implementation-log.md
+    When logging progress, use the humanized title/userActionLanguage
+    fields from the action plan (the planner already rendered them) —
+    do not re-derive severity prose. Append result to:
+    ~/.claude/config-audit/sessions/{session-id}/implementation-log.md
 ```
 
-Show progress between groups:
+Show progress between groups using the humanized titles already present in the action plan:
 
 ```
-Action 1/N: {title} — done
+Action 1/N: {humanized title} — done
-Action 2/N: {title} — done
+Action 2/N: {humanized title} — done
 ...
 ```
 

plugins/config-audit/commands/interview.md

@@ -1,7 +1,7 @@
 ---
 name: config-audit:interview
 description: Phase 3 - Interactive interview to gather user preferences
-allowed-tools: Read, Write, Edit, AskUserQuestion
+allowed-tools: Read, Write, Edit, AskUserQuestion, Bash
 model: sonnet
 ---
 
@@ -17,10 +17,21 @@ AskUserQuestion requires synchronous terminal interaction and does not work when
 ## Prerequisites
 
 - Must have completed Phase 2 (analysis)
-- Read analysis from `~/.claude/config-audit/sessions/{session-id}/analysis-report.md`
+- Use the Read tool on the analysis at `~/.claude/config-audit/sessions/{session-id}/analysis-report.md`
+
+## Arguments
+
+- `$ARGUMENTS` may contain `--raw` — pass-through accepted for CLI surface consistency. Interview is interactive prose only (no scanner output, no findings prose), so `--raw` is a no-op here.
 
 ## Implementation Steps
 
+0. **Parse flags**:
+
+   ```bash
+   RAW_FLAG=""
+   if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+   ```
+
 1. **Load session state**: Verify analysis phase completed, read analysis report for context
 2. **Conduct interview inline**: Use AskUserQuestion tool directly (NOT via Task). Adapt questions based on analysis findings.
 3. **Save interview results**: Write to `~/.claude/config-audit/sessions/{session-id}/interview.md`
@@ -29,10 +40,10 @@ AskUserQuestion requires synchronous terminal interaction and does not work when
 
 ## Interview Questions
 
-Ask these using AskUserQuestion (skip questions that don't apply based on analysis):
+Ask these using AskUserQuestion (skip questions that don't apply based on analysis). Where the analysis report references finding IDs, use the humanized title from the report rather than re-deriving prose:
 
 1. **Config Style** — Centralized vs Distributed vs Hybrid organization
-2. **Unused Hooks** — Wire up, review individually, delete, or leave (only if found)
+2. **Unused automation that runs at specific events** — Wire up, review individually, delete, or leave (only if the analysis report flagged one)
 3. **Duplicate Permissions** — Remove from local, consolidate, or keep (only if found)
 4. **Modular Rules** — Use .claude/rules/ pattern? Yes/No
 5. **Path-Scoped Rules** — Which patterns (tests, src, config, docs) — only if Q4=Yes

plugins/config-audit/commands/manifest.md

@@ -24,6 +24,7 @@ Produce a ranked, single-table view of every token source loaded for a given rep
 First non-flag argument is the path (default `.`). Recognized flags:
 
 - `--json` — emit raw JSON instead of the rendered table.
+- `--raw` — pass-through to the scanner; accepted for CLI surface consistency with the other config-audit commands. The manifest CLI is data-table only (no findings prose), so `--raw` is a no-op here, but the flag is still threaded through so users get uniform behaviour across `--raw`.
 
 ### Step 2: Run the CLI silently
 
@@ -31,7 +32,9 @@ Tell the user: **"Building token-source manifest for `<path>`..."**
 
 ```bash
 TMPFILE="/tmp/ca-manifest-$$.json"
-node ${CLAUDE_PLUGIN_ROOT}/scanners/manifest.mjs <path> --output-file "$TMPFILE" 2>/dev/null; echo $?
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+node ${CLAUDE_PLUGIN_ROOT}/scanners/manifest.mjs <path> --output-file "$TMPFILE" $RAW_FLAG 2>/dev/null; echo $?
 ```
 
 **Exit code handling:**

plugins/config-audit/commands/plan.md

@@ -1,7 +1,7 @@
 ---
 name: config-audit:plan
 description: Phase 4 - Generate prioritized action plan with risk assessment
-allowed-tools: Read, Write, Glob, Grep, Agent
+allowed-tools: Read, Write, Glob, Grep, Agent, Bash
 model: opus
 ---
 
@@ -14,11 +14,15 @@ Generate a prioritized action plan based on analysis results.
 - Must have completed Phase 2 (analysis)
 - Phase 3 (interview) is optional — plan works with or without it
 
+## Arguments
+
+- `$ARGUMENTS` may contain `--raw` to forward to the planner-agent's instructions; in `--raw` mode the agent renders v5.0.0 verbatim severity prefiks instead of humanized `userActionLanguage` urgency phrasing.
+
 ## Implementation
 
 ### Step 1: Verify session state
 
-Find the most recent session with analysis completed. If none found: "No analysis results found. Run `/config-audit` first to scan your configuration."
+Find the most recent session with analysis completed using the Read tool on `~/.claude/config-audit/sessions/*/state.yaml`. If none found: "No analysis results found. Run `/config-audit` first to scan your configuration."
 
 ### Step 2: Tell the user what's happening
 
@@ -29,7 +33,12 @@ Building a prioritized plan based on your analysis results...
 Actions are ordered by impact, with risk assessment and dependency tracking.
 ```
 
-### Step 3: Spawn planner agent
+### Step 3: Parse flags and spawn planner agent
+
+```bash
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+```
 
 Tell the user: **"Generating your action plan (this takes about 30 seconds)..."**
 
@@ -40,8 +49,18 @@ Agent(subagent_type: "config-audit:planner-agent")
     Generate action plan based on:
     - Analysis: ~/.claude/config-audit/sessions/{session-id}/analysis-report.md
     - Interview: ~/.claude/config-audit/sessions/{session-id}/interview.md (if exists)
-    Create prioritized plan with:
+    Mode: $RAW_FLAG (empty = humanized; "--raw" = v5.0.0 verbatim severity prefiks)
-    - Risk assessment per action (low/medium/high)
+    Create a prioritized plan that consumes the humanized finding fields:
+    - Group actions by userImpactCategory (e.g., "Configuration mistake",
+      "Conflict", "Wasted tokens", "Missed opportunity", "Dead config")
+    - Lead each action with userActionLanguage ("Fix this now," "Fix soon,"
+      "Fix when convenient," "Optional cleanup," "FYI") rather than raw
+      severity. The humanizer already replaced jargon-heavy
+      title/description/recommendation strings with plain-language
+      equivalents — render them verbatim, do not paraphrase.
+    - Surface relevanceContext when it isn't "affects-everyone" so the
+      user knows whether a fix touches shared config or just their machine
+    - Include risk assessment per action (low/medium/high)
     - Rollback strategy
     - Dependency ordering
     - Effort estimates

plugins/config-audit/commands/plugin-health.md

@@ -14,6 +14,7 @@ Audit Claude Code plugin structure and quality — validates plugin.json, CLAUDE
 
 - `$ARGUMENTS` may contain a path to a specific plugin directory
 - If omitted: scans all plugins in the marketplace root
+- `--raw`: pass-through to the scanner; produces v5.0.0 verbatim envelope (bypasses the humanizer) for byte-stable diff tooling
 
 ## Implementation
 
@@ -31,13 +32,15 @@ Auditing {N} plugin(s) for structure, frontmatter quality, and cross-plugin conf
 
 ### Step 2: Run scanner
 
-Run silently for each plugin:
+Run silently for each plugin. Default mode emits a humanized JSON envelope where each PLH finding carries `userImpactCategory`, `userActionLanguage`, and `relevanceContext` alongside the v5.0.0 fields. `--raw` is passed through verbatim when present.
 
 ```bash
-node ${CLAUDE_PLUGIN_ROOT}/scanners/plugin-health-scanner.mjs <path> 2>/dev/null
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+node ${CLAUDE_PLUGIN_ROOT}/scanners/plugin-health-scanner.mjs <path> $RAW_FLAG 2>/dev/null
 ```
 
-Read stdout output (JSON). Parse findings.
+Read stdout output (JSON) using the Read tool. Parse findings.
 
 ### Step 3: Present results
 
@@ -59,10 +62,12 @@ Read stdout output (JSON). Parse findings.
 #### Findings by Plugin
 
 **{plugin-name}** ({finding_count} findings):
-1. [{id}] {title} — {recommendation}
+1. [{userActionLanguage}] {humanized title} ({id}) — {humanized recommendation}
 2. ...
 ```
 
+Group findings within each plugin by `userImpactCategory` (e.g., "Configuration mistake", "Conflict") and lead each line with `userActionLanguage` ("Fix this now", "Fix soon", "Optional cleanup"). The humanizer already produced the plain-language `title`/`recommendation` strings — render them verbatim, do not paraphrase.
+
 ### Step 4: Suggest next steps
 
 ```

plugins/config-audit/commands/posture.md

@@ -19,9 +19,13 @@ Quick, deterministic configuration health scorecard. No agents needed — runs a
 
 ## Implementation
 
-### Step 1: Determine target
+### Step 1: Determine target and flags
 
-Parse `$ARGUMENTS` for a path (default: current working directory). Resolve relative paths.
+Split `$ARGUMENTS` into a path and flags. Path is the first non-flag argument (default: current working directory). Resolve relative paths. Recognized flags:
+
+- `--raw` — pass-through to the scanner; produces v5.0.0 verbatim output (bypasses the humanizer). Power-user mode for byte-stable diffs and machine consumption.
+- `--drift` — append a "Configuration Drift" section (see Step 5).
+- `--plugin-health` — append a "Plugin Health" section (see Step 5).
 
 Tell the user:
 
@@ -33,32 +37,34 @@ Running quick assessment{if path != cwd: " on `{path}`"}...
 
 ### Step 2: Run posture scanner
 
-Run silently — all output goes to a file:
+Run silently — JSON goes to a file, the humanized scorecard prints to stderr (default mode). The humanized stderr scorecard already includes the grade headline and area-score lines in plain language, so render those directly rather than re-deriving prose tables.
 
 ```bash
-node ${CLAUDE_PLUGIN_ROOT}/scanners/posture.mjs <target-path> --json --output-file /tmp/config-audit-posture-$$.json 2>/dev/null; echo $?
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+node ${CLAUDE_PLUGIN_ROOT}/scanners/posture.mjs <target-path> --output-file /tmp/config-audit-posture-$$.json $RAW_FLAG 2>/tmp/config-audit-posture-stderr-$$.txt; echo $?
 ```
 
 If exit code is non-zero, tell the user: "Assessment couldn't complete. Check that the path exists and contains Claude Code configuration files."
 
+If `--raw` was passed, treat the captured stderr as v5.0.0-shape verbatim text and present it as-is in a code block; skip the humanized rendering steps below.
+
 ### Step 3: Read and interpret results
 
 Read the JSON output file using the Read tool. Extract:
 
 - `overallGrade`, `opportunityCount`
 - `areas[]` — each with `name`, `grade`, `score`, `findingCount`
+- `scannerEnvelope.scanners[].findings[]` — when surfacing individual findings, prefer the humanizer-provided fields: `userImpactCategory` (e.g., "Configuration mistake", "Wasted tokens"), `userActionLanguage` (e.g., "Fix this now", "Fix soon", "Optional cleanup"), and `relevanceContext` ("affects-everyone", "affects-this-machine-only", "test-fixture-no-impact"). These let you group and prioritize without hardcoded severity-to-prose mappings.
+
+Also Read the captured stderr file — its body is the humanized scorecard (grade headline, area-score block, opportunity hint). You can present it verbatim or interleave its lines with the JSON-driven table.
 
 ### Step 4: Present the scorecard
 
 ```markdown
 **Health: {overallGrade}** | {qualityAreaCount} areas scanned
 
-{grade-based context — pick ONE:}
+{Use the headline line from the humanized stderr scorecard — it carries grade-context prose already (e.g., " Health: A (97/100) — Healthy setup, only minor polish needed"). Do not re-derive an A/B/C/D prose table here; the humanizer owns that vocabulary.}
-- A: "Your configuration is correct and well-maintained."
-- B: "Solid configuration with minor improvements available."
-- C: "Working configuration with some issues worth addressing."
-- D: "Configuration needs attention in several areas."
-- F: "Significant issues found — addressing these will improve your experience."
 
 ### Area Scores
 
@@ -73,22 +79,13 @@ Read the JSON output file using the Read tool. Extract:
 ### What's next
 ```
 
-**Grade A or B:**
+Group "what's next" suggestions by `userActionLanguage` from the humanized findings:
-```
-Your configuration health is strong. Re-run after major changes to catch regressions.
-For feature recommendations: `/config-audit feature-gap`
-```
 
-**Grade C:**
+- Findings tagged "Fix this now" / "Fix soon" → suggest `/config-audit fix` first, then `/config-audit plan`.
-```
+- Findings tagged "Fix when convenient" / "Optional cleanup" → suggest `/config-audit feature-gap` and routine maintenance.
-Run `/config-audit fix` to auto-fix what's possible, then `/config-audit plan` for a prioritized improvement path.
+- No high-urgency findings → suggest `/config-audit feature-gap` for opportunities and re-running posture after major config changes.
-```
 
-**Grade D or F:**
+Avoid hardcoded grade-to-prose ladders here — the humanized scorecard headline already supplies grade context, and `userActionLanguage` supplies finding-level urgency.
-```
-Start with `/config-audit fix` — it handles the most impactful issues automatically with backup and rollback.
-Then run `/config-audit plan` for a step-by-step path to a better configuration.
-```
 
 ### Step 5: Optional sections
 

plugins/config-audit/commands/rollback.md

@@ -13,12 +13,19 @@ Restore configuration files from a previous backup. Without arguments, lists ava
 ## Arguments
 
 - `$ARGUMENTS` may contain a backup ID (format: `YYYYMMDD_HHMMSS`)
+- `--raw`: pass-through flag accepted for CLI surface consistency. Rollback is file restoration only (no scanner output, no findings prose), so `--raw` is a no-op here, but the flag is still parsed so users get uniform behaviour across the toolchain.
 
 ## Behavior
 
 ### List mode (no argument)
 
-List available backups from `~/.claude/config-audit/backups/`:
+Parse flags and list available backups from `~/.claude/config-audit/backups/`:
+
+```bash
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+ls -1 ~/.claude/config-audit/backups/
+```
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -33,11 +40,11 @@ List available backups from `~/.claude/config-audit/backups/`:
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
-Read each backup's `manifest.yaml` to extract file list and timestamps.
+Use the Read tool on each backup's `manifest.yaml` (the list of changes captured at backup time) to extract the file list and timestamps.
 
 ### Restore mode (with backup ID)
 
-1. Read manifest from `~/.claude/config-audit/backups/{backup-id}/manifest.yaml`
+1. Read the list of changes from `~/.claude/config-audit/backups/{backup-id}/manifest.yaml` using the Read tool
 2. Show files that will be restored — ask for confirmation:
    ```
    AskUserQuestion:
@@ -46,10 +53,10 @@ Read each backup's `manifest.yaml` to extract file list and timestamps.
        - "Yes, restore"
        - "Cancel"
    ```
-3. For each file in manifest:
+3. For each file in the list of changes:
-   a. Read backup file from `~/.claude/config-audit/backups/{backup-id}/files/{safeName}`
+   a. Read the backup file from `~/.claude/config-audit/backups/{backup-id}/files/{safeName}`
-   b. Write to original path
+   b. Write to the original path
-   c. Verify checksum matches manifest
+   c. Verify the checksum matches the recorded value in the list of changes
 4. Show result:
    ```
    Restored 3 files from backup 20260403_163045

plugins/config-audit/commands/status.md

@@ -1,7 +1,7 @@
 ---
 name: config-audit:status
 description: Show current session state and available actions
-allowed-tools: Read, Glob
+allowed-tools: Read, Glob, Bash
 model: sonnet
 ---
 
@@ -13,18 +13,40 @@ Display current session state and guide next actions.
 
 ```
 /config-audit status
+/config-audit status --raw   # show the raw v5.0.0 phase identifiers (current_phase: "discover", etc.) instead of humanized labels
 ```
 
+## Phase-label translation
+
+The `state.yaml` field `current_phase` is the machine contract — never rename it. The user-facing label is humanized. Map the field value to a plain-language label when rendering (default mode):
+
+| `current_phase` (machine field, unchanged) | User-facing label |
+|--------------------------------------------|-------------------|
+| `discover`  | Looking at your config files |
+| `analyze`   | Working out what to recommend |
+| `interview` | Asking what you'd like to focus on |
+| `plan`      | Putting together your action plan |
+| `implement` | Making the changes |
+| `verify`    | Double-checking everything worked |
+
+When `--raw` is in `$ARGUMENTS`, render the raw `current_phase` field value verbatim (no humanization).
+
 ## Implementation
 
-1. **Find active session**:
+1. **Parse flags**:
+   ```bash
+   RAW_FLAG=""
+   if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+   ```
+
+2. **Find active session**:
    ```
    Glob: ~/.claude/config-audit/sessions/*/state.yaml
    Sort by modification time
    Use most recent
    ```
 
-2. **Read session state**:
+3. **Read session state** with the Read tool:
    ```yaml
    session_id: "20250126_143022"
    current_phase: "analyze"
@@ -33,7 +55,7 @@ Display current session state and guide next actions.
    ...
    ```
 
-3. **Display status**:
+4. **Display status** (default mode — humanized phase labels):
    ```
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    Config-Audit Session Status
@@ -44,11 +66,11 @@ Display current session state and guide next actions.
 
    PHASE PROGRESS
    ──────────────
-   ✓ Phase 1: Discover   - 15 files found (current directory)
+   ✓ Phase 1: Looking at your config files     - 15 files found (current directory)
-   ✓ Phase 2: Analyze    - report generated
+   ✓ Phase 2: Working out what to recommend    - report generated
-   ○ Phase 3: Interview  - not started (optional)
+   ○ Phase 3: Asking what you'd like to focus on - not started (optional)
-   ○ Phase 4: Plan       - not started
+   ○ Phase 4: Putting together your action plan  - not started
-   ○ Phase 5: Implement  - not started
+   ○ Phase 5: Making the changes                 - not started
 
    NEXT ACTION
    ───────────
@@ -64,7 +86,9 @@ Display current session state and guide next actions.
    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    ```
 
-4. **If no session found**:
+   In `--raw` mode, replace the humanized phase labels with the verbatim machine field values (`Phase 1: discover`, `Phase 2: analyze`, etc.).
+
+5. **If no session found**:
    ```
    No active config-audit session found.
 

plugins/config-audit/commands/tokens.md

@@ -28,16 +28,21 @@ Complementary to `/config-audit whats-active`:
 Split `$ARGUMENTS` into a path and flags. Path is the first non-flag argument. Default to `.` (current working directory). Recognized flags:
 
 - `--global` — also include the user-level `~/.claude/` cascade
-- `--json` — emit raw JSON instead of rendered tables (power-user mode)
+- `--json` — emit raw JSON instead of rendered tables (power-user mode; bypasses the humanizer for byte-stable v5.0.0 output)
+- `--raw` — pass-through to the scanner; produces v5.0.0 verbatim JSON (bypasses the humanizer). Use when piping into v5.0.0-baseline diff tooling.
 - `--with-telemetry-recipe` — include `telemetry_recipe_path` in the JSON output, pointing to `knowledge/cache-telemetry-recipe.md`. Use this when you want to verify a structural fix actually improved cache hit rate (manual jq recipe, opt-in)
 
 ### Step 2: Run the CLI silently
 
 Tell the user: **"Analysing token hotspots for `<path>`..."**
 
+Default mode (no `--json`, no `--raw`) emits a humanized JSON envelope: each finding carries `userImpactCategory`, `userActionLanguage`, and `relevanceContext` in addition to the v5.0.0 fields. Pass `--raw` through verbatim if the user requested it.
+
 ```bash
 TMPFILE="/tmp/config-audit-tokens-$$.json"
-node ${CLAUDE_PLUGIN_ROOT}/scanners/token-hotspots-cli.mjs <path> --output-file "$TMPFILE" [--global] 2>/dev/null; echo $?
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+node ${CLAUDE_PLUGIN_ROOT}/scanners/token-hotspots-cli.mjs <path> --output-file "$TMPFILE" [--global] $RAW_FLAG 2>/dev/null; echo $?
 ```
 
 **Exit code handling:**
@@ -58,10 +63,10 @@ Use the Read tool on `$TMPFILE`. Extract:
 
 - `total_estimated_tokens` — top-line number
 - `hotspots[]` — top 10 ranked sources
-- `findings[]` — Opus 4.7 pattern findings (CA-TOK-001..003)
+- `findings[]` — Opus 4.7 pattern findings (CA-TOK-001..003); each finding in default mode carries humanizer fields (`userImpactCategory`, `userActionLanguage`, `relevanceContext`) alongside the v5.0.0 fields
 - `counts` — severity breakdown
 
-Render as markdown:
+Render as markdown. Group findings by `userImpactCategory` (e.g., "Wasted tokens" vs "Configuration mistake") rather than re-deriving severity prose; lead each line with `userActionLanguage` ("Fix this now", "Fix soon", "Optional cleanup", etc.) so the urgency phrasing stays consistent with the rest of the toolchain. The humanizer already replaced jargon-heavy `title`/`description`/`recommendation` strings with plain-language equivalents — render them verbatim.
 
 ```markdown
 **Token hotspots for `<path>`** — ~{total_estimated_tokens} estimated tokens loaded per turn
@@ -72,13 +77,14 @@ Render as markdown:
 |------|--------|--------|-----------------|
 | {rank} | `{source}` | ~{estimated_tokens} | {recommendations joined as `· ` bullets} |
 
-### Opus 4.7 pattern findings
+### Findings, grouped by impact
 
-{For each finding, render:}
+{Group findings[] by their userImpactCategory. Within each group, sort by userActionLanguage urgency (Fix this now → Fix soon → Fix when convenient → Optional cleanup → FYI), then render:}
 
-- **{id}** ({severity}) — {title}
+- **{userActionLanguage}** — {title}  ({id})
   - {description}
   - **Fix:** {recommendation}
+  - _{relevanceContext}_ when not "affects-everyone" (mention the scope so the user knows whether a fix touches shared config or just their machine)
 
 ### Severity summary
 

plugins/config-audit/commands/whats-active.md

@@ -24,6 +24,7 @@ Show a complete, read-only inventory of everything Claude Code loads for a given
 Split `$ARGUMENTS` into a path and flags. Path is the first non-flag argument. Default to `.` (current working directory). Recognized flags:
 
 - `--json` — emit raw JSON instead of rendered tables (power-user mode)
+- `--raw` — pass-through to the scanner; accepted for CLI surface consistency. `whats-active` is an inventory-only output (no findings prose), so `--raw` is a no-op here, but the flag is still threaded through for uniform behaviour across the toolchain.
 - `--verbose` — include per-file byte/line detail
 - `--suggest-disables` — append deterministic disable-candidates + LLM-judgment pass
 
@@ -33,7 +34,9 @@ Tell the user: **"Reading active configuration for `<path>`..."**
 
 ```bash
 TMPFILE="/tmp/ca-whats-active-$$.json"
-node ${CLAUDE_PLUGIN_ROOT}/scanners/whats-active.mjs <path> --output-file "$TMPFILE" [--verbose] [--suggest-disables] 2>/dev/null; echo $?
+RAW_FLAG=""
+if echo "$ARGUMENTS" | grep -q -- "--raw"; then RAW_FLAG="--raw"; fi
+node ${CLAUDE_PLUGIN_ROOT}/scanners/whats-active.mjs <path> --output-file "$TMPFILE" [--verbose] [--suggest-disables] $RAW_FLAG 2>/dev/null; echo $?
 ```
 
 **Exit code handling:**

plugins/config-audit/docs/humanizer.md

@@ -0,0 +1,52 @@
+# Config-Audit — Plain-language output (v5.1.0)
+
+Imported from `CLAUDE.md` via pointer.
+
+Default output of all 18 commands routes through `humanizeEnvelope` from `lib/humanizer.mjs`. Findings are decorated with three additive fields and may have title/description/recommendation replaced when a translation exists.
+
+## Output modes
+
+| Flag | Behavior |
+|------|----------|
+| (default, no flag) | Plain-language: humanizer applied, findings group by user-impact, titles lead with prose. Self-audit terminal render also humanized. |
+| `--raw` | Byte-stable v5.0.0 verbatim — humanizer bypassed, technical IDs and severity-only labels. For tooling that scrapes stderr from v5.0.0. |
+| `--json` | Unchanged from v5.0.0 — humanizer bypassed, byte-stable JSON envelope. Always preferred for programmatic consumption over `--raw`. |
+| `--output-file <path>` | Writes raw v5.0.0-shape JSON (humanizer bypassed). Posture-specific. |
+
+`--raw` is threaded through every CLI: `posture.mjs`, `scan-orchestrator.mjs`, `token-hotspots-cli.mjs`, `manifest.mjs`, `whats-active.mjs`, `fix-cli.mjs`, `drift-cli.mjs`, `self-audit.mjs`.
+
+## Vocabularies
+
+User-impact category (added to each finding as `userImpactCategory`, derived from scanner prefix):
+
+| Label | Scanners |
+|-------|----------|
+| Configuration mistake | CML, SET, HKV, RUL, MCP, IMP, PLH |
+| Conflict | CNF, COL |
+| Wasted tokens | TOK, CPS |
+| Dead config | DIS |
+| Missed opportunity | GAP |
+
+Action language (added to each finding as `userActionLanguage`, derived from severity):
+
+| Severity | Phrase |
+|----------|--------|
+| critical | Fix this now |
+| high | Fix soon |
+| medium | Fix when convenient |
+| low | Optional cleanup |
+| info | FYI |
+
+Relevance context (added to each finding as `relevanceContext`, computed from finding's file path):
+
+| Value | When |
+|-------|------|
+| `test-fixture-no-impact` | Path contains `/tests/fixtures/` or `/test/fixtures/` |
+| `affects-this-machine-only` | Basename matches `*.local.*` (e.g., `settings.local.json`) |
+| `affects-everyone` | Default — assumed shared/committed config |
+
+## Wave 5 lessons
+
+- Posture's stderr scorecard is rendered prose-side and is not part of the JSON envelope; `humanized.areas[].titleHumanized` referenced by command templates lives only in the prose render.
+- Posture's `--output-file` writes raw v5.0.0-shape JSON because `posture.mjs` does not call `humanizeEnvelope`. If session-files should later be humanized, posture needs its own humanize pass — out of v5.1.0 scope.
+- The default-output snapshot at `tests/snapshots/default-output/posture.json` is frozen — change requires `UPDATE_SNAPSHOT=1` plus intent confirmation.

plugins/config-audit/docs/scanner-internals.md

@@ -0,0 +1,76 @@
+# Config-Audit — Scanner internals
+
+Detailed scanner inventory, lib modules, action engines, knowledge base. Imported from `CLAUDE.md` via pointer.
+
+## Deterministic Scanners
+
+Node.js scanners (zero external dependencies), run via `node scanners/scan-orchestrator.mjs <path>`.
+Posture CLI: `node scanners/posture.mjs <path> [--json] [--global] [--full-machine] [--output-file path]`.
+Scanner CLI: `node scanners/scan-orchestrator.mjs <path> [--global] [--full-machine] [--no-suppress]`.
+
+| Scanner | Prefix | Detects |
+|---------|--------|---------|
+| `claude-md-linter.mjs` | CML | Structure, length, sections, @imports, duplicates, TODOs |
+| `settings-validator.mjs` | SET | Schema, unknown/deprecated keys, type mismatches, permissions |
+| `hook-validator.mjs` | HKV | Format, script existence, event validity, timeouts |
+| `rules-validator.mjs` | RUL | Glob matching, orphan rules, deprecated fields, unscoped rules |
+| `mcp-config-validator.mjs` | MCP | Server types, trust levels, env vars, unknown fields |
+| `import-resolver.mjs` | IMP | Broken @imports, circular refs, deep chains, tilde paths |
+| `conflict-detector.mjs` | CNF | Settings conflicts, permission contradictions, hook duplicates |
+| `feature-gap-scanner.mjs` | GAP | 25 feature checks across 4 tiers — shown as opportunities, not grades |
+| `token-hotspots.mjs` | TOK | Cache-breaking volatile content, redundant tool permissions, deep import chains, oversized cascade, bloated SKILL.md descriptions, MCP tool-schema budget (Opus 4.7 patterns) |
+| `cache-prefix-scanner.mjs` | CPS | Volatile content in lines 31–150 of CLAUDE.md cascade (beyond Pattern A's top-30 window) |
+| `disabled-in-schema-scanner.mjs` | DIS | Tools listed in BOTH `permissions.deny` AND `permissions.allow` — deny wins, allow entries are dead config |
+| `collision-scanner.mjs` | COL | Cross-plugin skill name collisions (low); user-vs-plugin overlaps (medium); `details.namespaces` payload |
+
+## Scanner Lib (`scanners/lib/`)
+
+| Module | Purpose |
+|--------|---------|
+| `severity.mjs` | Severity constants, risk scoring, verdict logic, `WEIGHTS` named export (v5 F3) |
+| `output.mjs` | Finding objects (CA-XXX-NNN format), scanner results, envelope, optional `details` payload (v5 N6) |
+| `file-discovery.mjs` | Config file discovery: single-path, multi-path (`discoverConfigFilesMulti`), full-machine (`discoverFullMachinePaths`) |
+| `yaml-parser.mjs` | Frontmatter parsing, JSON parsing, @import/section extraction |
+| `string-utils.mjs` | Line counting, truncation, similarity, key extraction |
+| `scoring.mjs` | Severity-weighted `scoreByArea` (v5 F3), health scorecard, dedup-by-area (v5 N3), `scoringVersion: 'v5'` |
+| `backup.mjs` | Backup creation, manifest parsing, checksum verification |
+| `diff-engine.mjs` | Drift diffing: diffEnvelopes(), formatDiffReport() |
+| `baseline.mjs` | Baseline save/load/list/delete for drift detection |
+| `report-generator.mjs` | Unified markdown reports: posture, drift, plugin health |
+| `suppression.mjs` | .config-audit-ignore parsing, finding suppression, audit trail |
+| `active-config-reader.mjs` | Read-only inventory: readActiveConfig(), detectGitRoot(), walkClaudeMdCascade(), readClaudeJsonProjectSlice() (longest-prefix match), enumeratePlugins(), enumerateSkills(), readActiveHooks(), readActiveMcpServers() (with cache → package.json tool-count fallback), estimateTokens() (v5: `'mcp'` kind = 500 + toolCount × 200) |
+| `tokenizer-api.mjs` | Anthropic `count_tokens` wrapper for `--accurate-tokens` (v5 N5); 5s AbortController timeout, exponential 429 backoff, key masking |
+| `humanizer.mjs` | Plain-language output translator (v5.1.0): `humanizeFinding`, `humanizeFindings`, `humanizeEnvelope`, `computeRelevanceContext`. Pure functions; never mutate inputs. Adds `userImpactCategory`, `userActionLanguage`, `relevanceContext` fields and replaces title/description/recommendation when a translation exists. Bypassed by `--raw` and `--json` paths. |
+| `humanizer-data.mjs` | TRANSLATIONS table for 13 scanner prefixes (CML/SET/HKV/RUL/MCP/IMP/CNF/COL/TOK/CPS/DIS/GAP/PLH). Three-step lookup: exact title → regex pattern → `_default` → fall through to original |
+
+## Action Engines (`scanners/`)
+
+| Module | Purpose |
+|--------|---------|
+| `fix-engine.mjs` | planFixes(), applyFixes(), verifyFixes() — 9 fix types |
+| `rollback-engine.mjs` | listBackups(), restoreBackup(), deleteBackup() |
+| `fix-cli.mjs` | CLI: `node fix-cli.mjs <path> [--apply] [--json] [--global]` |
+| `drift-cli.mjs` | CLI: `node drift-cli.mjs <path> [--save] [--baseline name] [--json]` |
+| `whats-active.mjs` | CLI: `node whats-active.mjs <path> [--json] [--verbose] [--suggest-disables]` — read-only active-config inventory |
+| `token-hotspots-cli.mjs` | CLI: `node token-hotspots-cli.mjs <path> [--json] [--global] [--output-file path] [--accurate-tokens] [--with-telemetry-recipe]` — Opus-4.7 token hotspots ranking with optional API calibration |
+| `manifest.mjs` | CLI: `node manifest.mjs <path> [--json]` — ranked system-prompt token-source table (v5 N2) |
+
+## Standalone Scanner
+
+| Module | Prefix | Purpose |
+|--------|--------|---------|
+| `plugin-health-scanner.mjs` | PLH | Plugin structure, frontmatter, cross-plugin conflicts (runs independently) |
+| `self-audit.mjs` | — | Runs all scanners + plugin health on this plugin itself |
+
+## Knowledge Base (`knowledge/`)
+
+| File | Content |
+|------|---------|
+| `claude-code-capabilities.md` | Feature register: 18 config surfaces, Anthropic guidance, relevance table |
+| `configuration-best-practices.md` | Per-layer best practices (v5: Opus 4.7 cache-stability guidance replaces Sonnet-era 200-line rule) |
+| `anti-patterns.md` | Common mistakes mapped to scanner IDs |
+| `hook-events-reference.md` | All 26 hook events with details |
+| `feature-evolution.md` | Feature timeline for staleness detection |
+| `gap-closure-templates.md` | Config-specific templates for closing gaps |
+| `opus-4.7-patterns.md` | Token-cost dynamics for Opus 4.7 era — patterns powering the TOK scanner |
+| `cache-telemetry-recipe.md` | Manual `jq` recipe for verifying prompt-cache hit rate from session transcripts (v5 M7) |

plugins/config-audit/docs/v5-implementation-log.md

@@ -180,6 +180,44 @@ Written at the end of each session. State for the next session lives in
 
 ---
 
-## Session 5 — release (TBD)
+## Session 5 — release (2026-05-01)
 
-*Steps 28-30, including SC-6b release gate.*
+**Outcome:** All 3 steps shipped. v5.0.0 tagged and pushed (`config-audit/v5.0.0` on Forgejo). 635 tests still green. SC-6b release-gate **PASS** at −0.85% delta.
+
+### Per-step result
+
+| # | Step | Result | Commit |
+|---|------|--------|--------|
+| 28 | README + CLAUDE.md straggler-sweep | ✓ green; `--check-readme` PASSES (counts: scanners 12, commands 18, tests 635, knowledge 8, agents 6, hooks 4); self-audit also updated to (a) exclude `plugin-health-scanner.mjs` from `countScannerShape` so the orchestrated-scanner count matches the README badge taxonomy, and (b) `countTestCases` runs `node --test` to count test cases (635) instead of test files (36) — required for badge accuracy | `5bf500e` `docs(config-audit): straggler sweep for v5.0.0 — sync all badge counts` |
+| 29 | Version bump 4.0.0 → 5.0.0 + consolidated CHANGELOG | ✓ `plugin.json` bumped, README version badge bumped, Version History row added, marketplace root README updated (Config-Audit row v4.0.0 → v5.0.0 + counts), `## [5.0.0]` consolidated entry written from alpha.1/alpha.2/beta.1/rc.1 | `dcf8087` `chore(config-audit): bump version to 5.0.0` |
+| 30 | Final self-audit + SC-6b gate + tag | ✓ verdict PASS (config A 97/100, plugin A 100/100, readmeCheck PASS); SC-6b gate PASS at 0.85% delta; tag `config-audit/v5.0.0` created and pushed | `6cfca82` `fix(config-audit): expose hotspot.path for --accurate-tokens calibration + SC-6b PASS` (incl. tag) |
+
+### SC-6b release-gate outcome
+
+- **PASS — verified at release time with live `ANTHROPIC_API_KEY`.**
+- Fixture: `tests/fixtures/marketplace-large/`. Top-3 hotspots = 1 file-backed (`CLAUDE.md`) + 2 MCP virtuals.
+- MCP entries skipped per design (no readable content; their tokens are formula-based at 500 + toolCount × 200, not file content).
+- `CLAUDE.md` actual: **589 tokens** (Anthropic `count_tokens`, default `claude-opus-4-7`).
+- `CLAUDE.md` estimated: **594 tokens** (4-bytes/token heuristic via `estimateTokens`).
+- Delta: **−5 tokens / −0.85%** — well within ±5% gate.
+- API cost: ≈ 1 call × ~600 tokens = trivial (< $0.01).
+- No tuning of `estimateTokens` heuristic required.
+
+### Notable observations / deviations
+
+- **Step 30 surfaced a latent N5 bug.** The rc.1 implementation of `--accurate-tokens` looked up `hotspot.path` but the scanner only emitted `source` — every iteration hit the `if (!hotspot?.path) continue` guard and `actual_tokens` stayed at 0. Detected when running the gate. Minimal fix: file-backed hotspots now expose `path: h.absPath` in the JSON output; MCP-server hotspots intentionally leave `path` unset. Tests updated coverage already in place; no test changes required (the bug was a missing field, not a logic error). After the fix, the calibration produced the expected 589 actual_tokens for CLAUDE.md.
+- **Self-audit `--check-readme` now counts test cases by spawning `node --test`.** Slow (~16s on the full plugin) but produces the canonical test count (635) that matches the README badge. `countTestFiles` retained as fallback when the subprocess fails (timeout, parse failure).
+- **`plugin-health-scanner.mjs` excluded from `countScannerShape`.** It exports `scan` but is documented under "Standalone Scanner" in README/CLAUDE.md and runs separately from `scan-orchestrator.mjs`. Aligning self-audit's counter with the human/badge taxonomy.
+- **API key retrieved from macOS keychain** via `security find-generic-password -a ktg -s anthropic-api-key -w` per global CLAUDE.md convention. Key was masked to `sk-ant-a...` in all error paths (verified: tokenizer-api.mjs maskKey).
+- **`sampled_hotspots: 3`** in the calibration JSON is slightly misleading — the slice length is 3 but only 1 had a readable path (other 2 are MCP virtuals). Substantive result is correct: 1 file-backed sample, 0.85% delta. A follow-up could change this to `samples_calibrated: actualCount` for clarity (v5.0.1 candidate).
+- **`pre-commit-docs-gate` hook** did not trigger on Session 5 commits — all were `docs:`, `chore:`, or `fix:` types (gate only blocks `feat:`).
+- **Marketplace root README updated** in Step 29 (Config-Audit row v4.0.0 → v5.0.0, counts refreshed: 8→12 scanners, 17→18 commands, 543→635 tests, 4→6 patterns, +manifest, +--accurate-tokens, +CPS/DIS/COL).
+
+### Result
+
+- 3 steps + 1 in-step bug fix shipped. Pushed to Forgejo `main` (autorisert).
+- Tag: `config-audit/v5.0.0` (pushed; `git ls-remote --tags origin | grep -c "refs/tags/config-audit/v5.0.0$"` → 1).
+- Test count: 635 (unchanged — Session 5 was docs/release-sync, not new functionality apart from the path-field bug fix).
+- v5.0.0 release run is **complete**.
+
+**No blockers carried forward.** Backlog items deferred to v5.0.1: plugin-vs-built-in collision (research uncertainty), `CA-TOK-*` glob suppression runtime warning, `samples_calibrated` field rename in calibration output, hook-path-bug in legacy `~/.config-audit/`.

plugins/config-audit/docs/v5.1.0-test-audit.md

@@ -0,0 +1,121 @@
+# v5.1.0 Title-String Assertion Audit
+
+Generated by Wave 0 / Step 0 pre-flight on 2026-05-01.
+
+This document is the authoritative change list for **Step 4** (replace title-string assertions with ID-based or shape-based assertions). Step 5 cannot wire the humanizer until every "WILL BREAK" entry below is converted.
+
+## Classification key
+
+- **(a) shape-only** — checks existence, type, or test-fixture input; not affected by humanization.
+- **(b) literal-string WILL BREAK** — exact equality or substring match against scanner-produced title prose. Humanization rewrites these strings; the assertion must be re-anchored to `finding.id`, `finding.scanner`, or `finding.evidence`.
+- **(c) ID-based** — already anchored on `finding.id` or scanner prefix. No change needed.
+
+## Audit summary
+
+| Test file | Matches | Will break (b) | Safe (a/c) |
+|-----------|---------|----------------|------------|
+| `tests/lib/output.test.mjs` | 1 | 0 | 1 |
+| `tests/scanners/feature-gap-scanner.test.mjs` | 6 | 6 | 0 |
+| `tests/scanners/hook-validator.test.mjs` | 12 | 9 | 3 |
+| `tests/lib/diff-engine.test.mjs` | 2 | 0 | 2 |
+| `tests/scanners/fix-engine.test.mjs` | 1 | 0 | 1 |
+| `tests/scanners/plugin-health-scanner.test.mjs` | 9 | 8 | 1 |
+| `tests/scanners/settings-validator.test.mjs` | 11 | 11 | 0 |
+| **Total** | **42** | **34** | **8** |
+
+## Per-file findings
+
+### `tests/lib/output.test.mjs`
+
+| Line | Code | Class | Action |
+|------|------|-------|--------|
+| 46 | `assert.strictEqual(f.title, 'Test')` | (a) shape-only | None — `'Test'` is the test's own input to `finding()` constructor, not a scanner-produced title. |
+
+### `tests/scanners/feature-gap-scanner.test.mjs`
+
+| Line | Code | Class | Action |
+|------|------|-------|--------|
+| 45 | `f.title === 'No CLAUDE.md file'` | (b) WILL BREAK | Replace with `f.id === '<GAP-ID-for-no-CLAUDE.md>'`. Anchor on ID. |
+| 49 | `f.title === 'No MCP servers configured'` | (b) WILL BREAK | Replace with ID anchor. |
+| 53 | `f.title === 'No hooks configured'` | (b) WILL BREAK | Replace with ID anchor. |
+| 96 | `f.title === 'No hooks configured'` | (b) WILL BREAK | Replace with ID anchor. |
+| 100 | `f.title === 'No MCP servers configured'` | (b) WILL BREAK | Replace with ID anchor. |
+| 150 | `f.title === 'No CLAUDE.md file'` | (b) WILL BREAK | Replace with ID anchor. |
+
+> **Implementation note for Step 4:** look up the actual GAP finding IDs via `grep -n "title:" scanners/feature-gap-scanner.mjs` and substitute. For shape only: `assert.ok(f.id.startsWith('CA-GAP-'))` is acceptable when the test only cares that a GAP finding fired.
+
+### `tests/scanners/hook-validator.test.mjs`
+
+| Line | Code | Class | Action |
+|------|------|-------|--------|
+| 30 | `serious.map(f => f.title).join(', ')` | (a) shape-only | None — title used only for error-message formatting in failed assert; not the assertion itself. |
+| 49 | `f.title === 'Unknown hook event'` | (b) WILL BREAK | Replace with ID anchor. |
+| 54 | `f.title.includes('Matcher must be a string')` | (b) WILL BREAK | Replace with ID anchor or `.evidence.includes(...)`. |
+| 59 | `f.title === 'Invalid hook handler type'` | (b) WILL BREAK | Replace with ID anchor. |
+| 64 | `f.title.includes('timeout')` | (b) WILL BREAK | Replace with ID anchor. |
+| 69 | `f.title === 'Unknown hook event'` | (b) WILL BREAK | Replace with ID anchor. |
+| 80 | `/verbose hook output/i.test(x.title \|\| '')` | (b) WILL BREAK | Replace with ID anchor. |
+| 81 | `result.findings.map(x => x.title).join(' \| ')` | (a) shape-only | Used only in error-message formatting. None. |
+| 91 | `/verbose hook output/i.test(x.title \|\| '')` | (b) WILL BREAK | Replace with ID anchor. |
+| 92 | `f?.title` | (a) shape-only | Used only in error-message formatting. None. |
+
+### `tests/lib/diff-engine.test.mjs`
+
+| Line | Code | Class | Action |
+|------|------|-------|--------|
+| 66 | `diff.newFindings[0].title === 'New issue'` | (a) shape-only | None — `'New issue'` is the test's synthetic finding input, not scanner-produced. |
+| 78 | `diff.resolvedFindings[0].title === 'Old issue'` | (a) shape-only | None — synthetic test input. |
+
+### `tests/scanners/fix-engine.test.mjs`
+
+| Line | Code | Class | Action |
+|------|------|-------|--------|
+| 62 | `assert.ok(m.title, 'Manual finding should have title')` | (a) shape-only | None — pure existence check. |
+
+### `tests/scanners/plugin-health-scanner.test.mjs`
+
+| Line | Code | Class | Action |
+|------|------|-------|--------|
+| 52 | `f.title.includes('Missing required field')` | (b) WILL BREAK | Replace with ID anchor or `f.evidence.includes(...)`. |
+| 59 | `f.title.includes('missing') && f.title.includes('section')` | (b) WILL BREAK | Replace with ID anchor on the missing-section finding. |
+| 68 | `f.title.includes('Missing required field')` | (b) WILL BREAK | Replace with ID anchor. |
+| 75 | `f.title === 'Missing CLAUDE.md'` | (b) WILL BREAK | Replace with ID anchor. |
+| 82 | `f.title === 'Command missing frontmatter'` | (b) WILL BREAK | Replace with ID anchor. |
+| 90 | `f.title.startsWith('Agent missing frontmatter field:')` | (b) WILL BREAK | Replace with ID anchor + `f.evidence.includes(...)` for the field name (humanizer preserves evidence). |
+| 93 | `missingAgent.map(f => f.title).join(', ')` | (a) shape-only | Used only in error-message formatting. None. |
+| 102 | `result.findings[0].title === 'No plugins found'` | (b) WILL BREAK | Replace with ID anchor. |
+| 125 | `assert.ok(f.title)` | (a) shape-only | None — pure existence check. |
+
+### `tests/scanners/settings-validator.test.mjs`
+
+| Line | Code | Class | Action |
+|------|------|-------|--------|
+| 49 | `f.title === 'Unknown settings key'` | (b) WILL BREAK | Replace with ID anchor (likely `CA-SET-001` or similar — verify). |
+| 54 | `f.title === 'Deprecated settings key'` | (b) WILL BREAK | Replace with ID anchor. |
+| 59 | `f.title === 'Type mismatch in settings'` | (b) WILL BREAK | Replace with ID anchor. |
+| 64 | `f.title === 'Invalid effortLevel value'` | (b) WILL BREAK | Replace with ID anchor. |
+| 69 | `f.title.includes('array instead of object')` | (b) WILL BREAK | Replace with ID anchor. |
+| 74 | `f.title.includes('array instead of object')` | (b) WILL BREAK | Replace with ID anchor. |
+| 86 | `f.title === 'Unknown settings key' && /additionalDirectories/.test(f.evidence)` | (b) WILL BREAK | Keep evidence regex; replace title check with ID anchor. |
+| 96 | `/additionalDirectories/i.test(x.title \|\| '')` | (b) WILL BREAK | Replace with ID anchor + evidence regex (additionalDirectories likely appears in evidence already). |
+| 98 | `f?.title` | (a) shape-only — but inside breaking assertion | Will become moot after line 96 is fixed. |
+| 106 | `/additionalDirectories/i.test(x.title \|\| '')` | (b) WILL BREAK | Replace with ID anchor + evidence regex. |
+| 107 | `result.findings.map(x => x.title).join(' \| ')` | (a) shape-only | Error-message formatting only. None. |
+
+## Step 4 implementation guidance
+
+1. For each (b) WILL BREAK row, look up the actual finding ID from the corresponding scanner source:
+   - `grep -n "id: 'CA-GAP-" scanners/feature-gap-scanner.mjs`
+   - `grep -n "id: 'CA-HKV-" scanners/hook-validator.mjs`
+   - `grep -n "id: 'CA-PLH-" scanners/plugin-health-scanner.mjs`
+   - `grep -n "id: 'CA-SET-" scanners/settings-validator.mjs`
+2. Replace the title check with `f.id === '<exact-id>'`. If the test cares about a sub-variant (e.g., a specific deprecated key), pair the ID anchor with an `f.evidence.includes(...)` substring check — humanizer preserves `evidence` exactly.
+3. For broad categorical checks ("any GAP finding fired"), use `f.id.startsWith('CA-GAP-')`.
+4. For tests that capture `f.title` only inside `assert` failure-message templates (class (a)): leave them. Humanization changes the displayed string but the assertion still anchors on `f.id`.
+5. Re-run `node --test 'tests/**/*.test.mjs'` after changes; expect zero regressions before proceeding to Step 5.
+
+## Total scope for Step 4
+
+- **6 test files** require code changes (`output.test.mjs` and `diff-engine.test.mjs` are clean).
+- **34 distinct assertions** to convert.
+- Estimated effort: 1–2 hours including ID lookup and verification.

plugins/config-audit/scanners/drift-cli.mjs

@@ -14,6 +14,7 @@ import { resolve } from 'node:path';
 import { runAllScanners } from './scan-orchestrator.mjs';
 import { diffEnvelopes, formatDiffReport } from './lib/diff-engine.mjs';
 import { saveBaseline, loadBaseline, listBaselines } from './lib/baseline.mjs';
+import { humanizeFindings } from './lib/humanizer.mjs';
 
 async function main() {
   const args = process.argv.slice(2);
@@ -22,6 +23,7 @@ async function main() {
   let save = false;
   let list = false;
   let jsonMode = false;
+  let rawMode = false;
   let includeGlobal = false;
 
   for (let i = 0; i < args.length; i++) {
@@ -35,6 +37,8 @@ async function main() {
       list = true;
     } else if (args[i] === '--json') {
       jsonMode = true;
+    } else if (args[i] === '--raw') {
+      rawMode = true;
     } else if (args[i] === '--global') {
       includeGlobal = true;
     } else if (!args[i].startsWith('-')) {
@@ -45,7 +49,7 @@ async function main() {
   // --- List mode ---
   if (list) {
     const result = await listBaselines();
-    if (jsonMode) {
+    if (jsonMode || rawMode) {
       process.stdout.write(JSON.stringify(result, null, 2) + '\n');
     } else {
       if (result.baselines.length === 0) {
@@ -66,15 +70,15 @@ async function main() {
 
   // --- Save mode ---
   if (save) {
-    if (!jsonMode) {
+    if (!jsonMode && !rawMode) {
       process.stderr.write(`Config-Audit Drift CLI v2.1.0\n`);
       process.stderr.write(`Saving baseline "${baselineName}" for ${resolve(targetPath)}\n\n`);
     }
 
-    const envelope = await runAllScanners(targetPath, { includeGlobal });
+    const envelope = await runAllScanners(targetPath, { includeGlobal, humanizedProgress: !jsonMode && !rawMode });
     const result = await saveBaseline(envelope, baselineName);
 
-    if (jsonMode) {
+    if (jsonMode || rawMode) {
       process.stdout.write(JSON.stringify({ saved: true, name: result.name, path: result.path }, null, 2) + '\n');
     } else {
       process.stderr.write(`\nBaseline "${result.name}" saved to ${result.path}\n`);
@@ -84,7 +88,7 @@ async function main() {
   }
 
   // --- Drift mode (default) ---
-  if (!jsonMode) {
+  if (!jsonMode && !rawMode) {
     process.stderr.write(`Config-Audit Drift CLI v2.1.0\n`);
     process.stderr.write(`Target: ${resolve(targetPath)}\n`);
     process.stderr.write(`Baseline: ${baselineName}\n\n`);
@@ -93,7 +97,7 @@ async function main() {
   // Load baseline
   const baseline = await loadBaseline(baselineName);
   if (!baseline) {
-    if (jsonMode) {
+    if (jsonMode || rawMode) {
       process.stdout.write(JSON.stringify({ error: `Baseline "${baselineName}" not found. Save one with --save.` }, null, 2) + '\n');
     } else {
       process.stderr.write(`Baseline "${baselineName}" not found.\n`);
@@ -103,15 +107,27 @@ async function main() {
   }
 
   // Run current scan
-  const current = await runAllScanners(targetPath, { includeGlobal });
+  const current = await runAllScanners(targetPath, {
+    includeGlobal,
+    humanizedProgress: !jsonMode && !rawMode,
+  });
 
   // Diff
   const diff = diffEnvelopes(baseline, current);
 
-  if (jsonMode) {
+  if (jsonMode || rawMode) {
+    // --json and --raw both write the raw v5.0.0-shape diff (byte-identical).
     process.stdout.write(JSON.stringify(diff, null, 2) + '\n');
   } else {
-    const report = formatDiffReport(diff);
+    // Default mode: humanize finding-bearing diff fields before report rendering.
+    const humanizedDiff = {
+      ...diff,
+      newFindings: humanizeFindings(diff.newFindings || []),
+      resolvedFindings: humanizeFindings(diff.resolvedFindings || []),
+      unchangedFindings: humanizeFindings(diff.unchangedFindings || []),
+      movedFindings: humanizeFindings(diff.movedFindings || []),
+    };
+    const report = formatDiffReport(humanizedDiff);
     process.stderr.write('\n' + report + '\n');
   }
 

plugins/config-audit/scanners/fix-cli.mjs

@@ -12,12 +12,14 @@ import { resolve } from 'node:path';
 import { runAllScanners } from './scan-orchestrator.mjs';
 import { planFixes, applyFixes, verifyFixes } from './fix-engine.mjs';
 import { createBackup } from './lib/backup.mjs';
+import { humanizeFinding } from './lib/humanizer.mjs';
 
 async function main() {
   const args = process.argv.slice(2);
   let targetPath = '.';
   let apply = false;
   let jsonMode = false;
+  let rawMode = false;
   let includeGlobal = false;
 
   for (let i = 0; i < args.length; i++) {
@@ -25,6 +27,8 @@ async function main() {
       apply = true;
     } else if (args[i] === '--json') {
       jsonMode = true;
+    } else if (args[i] === '--raw') {
+      rawMode = true;
     } else if (args[i] === '--global') {
       includeGlobal = true;
     } else if (!args[i].startsWith('-')) {
@@ -32,9 +36,12 @@ async function main() {
     }
   }
 
+  // Whether to suppress prose stderr (true for both --json and --raw machine paths).
+  const machineMode = jsonMode || rawMode;
+
   const resolvedPath = resolve(targetPath);
 
-  if (!jsonMode) {
+  if (!machineMode) {
     process.stderr.write(`Config-Audit Fix CLI v2.1.0\n`);
     process.stderr.write(`Target: ${resolvedPath}\n`);
     process.stderr.write(`Mode: ${apply ? 'APPLY' : 'DRY-RUN'}\n\n`);
@@ -42,12 +49,15 @@ async function main() {
   }
 
   // 1. Run all scanners
-  const envelope = await runAllScanners(targetPath, { includeGlobal });
+  const envelope = await runAllScanners(targetPath, {
+    includeGlobal,
+    humanizedProgress: !machineMode,
+  });
 
   // 2. Plan fixes
   const { fixes, skipped, manual } = planFixes(envelope);
 
-  if (!jsonMode) {
+  if (!machineMode) {
     process.stderr.write(`\n`);
     process.stderr.write(`━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n`);
     process.stderr.write(` Config-Audit Fix Plan\n`);
@@ -63,9 +73,20 @@ async function main() {
     }
 
     if (manual.length > 0) {
+      // Default mode humanizes the manual-finding titles for the prose render.
+      // The JSON `manual` array (later in this function) keeps v5.0.0 verbatim.
       process.stderr.write(`\n Manual (${manual.length}):\n`);
       for (let i = 0; i < manual.length; i++) {
-        process.stderr.write(`  ${fixes.length + i + 1}. [${manual[i].findingId}] ${manual[i].title}\n`);
+        const m = manual[i];
+        const title = humanizeFinding({
+          id: m.findingId,
+          scanner: typeof m.findingId === 'string' ? m.findingId.split('-')[1] || '' : '',
+          severity: m.severity || 'info',
+          title: m.title,
+          description: m.description || '',
+          recommendation: m.recommendation || '',
+        }).title;
+        process.stderr.write(`  ${fixes.length + i + 1}. [${m.findingId}] ${title}\n`);
       }
     }
 
@@ -84,7 +105,7 @@ async function main() {
   let backupId = null;
 
   if (fixes.length === 0) {
-    if (jsonMode) {
+    if (machineMode) {
       const output = { planned: [], applied: [], failed: [], verified: [], regressions: [], manual, backupId: null };
       process.stdout.write(JSON.stringify(output, null, 2) + '\n');
     }
@@ -97,7 +118,7 @@ async function main() {
     const backup = createBackup(filesToBackup);
     backupId = backup.backupId;
 
-    if (!jsonMode) {
+    if (!machineMode) {
       process.stderr.write(`\n Backup created: ${backup.backupPath}\n`);
       process.stderr.write(` Applying ${fixes.length} fixes...\n\n`);
     }
@@ -106,7 +127,7 @@ async function main() {
     applied = result.applied;
     failed = result.failed;
 
-    if (!jsonMode) {
+    if (!machineMode) {
       process.stderr.write(` Results: ${applied.length} applied, ${failed.length} failed\n`);
       if (failed.length > 0) {
         for (const f of failed) {
@@ -117,7 +138,7 @@ async function main() {
 
     // 4. Verify
     if (applied.length > 0) {
-      if (!jsonMode) {
+      if (!machineMode) {
         process.stderr.write(`\n Verifying...\n`);
       }
 
@@ -125,7 +146,7 @@ async function main() {
       verified = verification.verified;
       regressions = verification.regressions;
 
-      if (!jsonMode) {
+      if (!machineMode) {
         process.stderr.write(` Verified: ${verified.length}/${applied.length}\n`);
         if (regressions.length > 0) {
           process.stderr.write(` Regressions: ${regressions.join(', ')}\n`);
@@ -138,13 +159,13 @@ async function main() {
     const result = await applyFixes(fixes, { dryRun: true });
     applied = result.applied;
 
-    if (!jsonMode) {
+    if (!machineMode) {
       process.stderr.write(`\n Dry-run complete. Pass --apply to execute.\n`);
     }
   }
 
-  // JSON output
+  // JSON output (both --json and --raw write byte-equal v5.0.0-shape stdout)
-  if (jsonMode) {
+  if (machineMode) {
     const output = {
       planned: fixes.map(f => ({
         findingId: f.findingId,

plugins/config-audit/scanners/lib/humanizer-data.mjs

@@ -0,0 +1,743 @@
+/**
+ * Plain-language translation table for config-audit v5.1.0.
+ *
+ * Structure: TRANSLATIONS[scannerPrefix] = {
+ *   static:   { '<exact title>': { title, description, recommendation }, ... },
+ *   patterns: [ { regex: RegExp, translation: {...} }, ... ],   // for template-literal titles
+ *   _default: { title, description, recommendation }            // fallback
+ * }
+ *
+ * Rules (from research/03 SR-1..SR-17):
+ *   - active voice, second person, present tense
+ *   - sentences ≤ 25 words
+ *   - tier1 absolute prohibitions and tier3 domain jargon may NOT appear in prose
+ *   - tier1/tier3 terms ARE permitted inside `backtick spans` (code/filename references)
+ *   - lead with the actual problem, not a label
+ *   - recommendation states a concrete action
+ *
+ * The humanizer module looks up: static[title] → patterns matching title → _default → original strings.
+ * Original `id`, `severity`, `evidence`, `file`, `line`, `category`, `autoFixable` are always preserved by the humanizer caller.
+ */
+
+/** @type {Record<string, { static: Record<string, {title:string,description:string,recommendation:string}>, patterns: Array<{regex: RegExp, translation: {title:string,description:string,recommendation:string}}>, _default: {title:string,description:string,recommendation:string} }>} */
+export const TRANSLATIONS = {
+  // ─────────────────────────────────────────────────────────────
+  // CML — CLAUDE.md Linter
+  // Category: Configuration mistake
+  // ─────────────────────────────────────────────────────────────
+  CML: {
+    static: {
+      'No CLAUDE.md found': {
+        title: 'Your project has no instructions file for Claude',
+        description: 'Without `CLAUDE.md` at your project root, Claude has to work out your conventions from scratch every conversation. Project-specific guidance is the single highest-impact thing you can add.',
+        recommendation: 'Create a file called `CLAUDE.md` in your project root. Start with a one-paragraph project overview, common commands, and any quirks Claude should know about.',
+      },
+      'CLAUDE.md is nearly empty': {
+        title: 'Your `CLAUDE.md` is mostly empty',
+        description: 'An empty instructions file gives Claude no project-specific context, so behavior falls back to defaults.',
+        recommendation: 'Add at least the project purpose, common commands you run, and any conventions Claude should follow.',
+      },
+      'CLAUDE.md exceeds 500 lines': {
+        title: 'Your `CLAUDE.md` is very long',
+        description: 'Long instruction files load on every turn and crowd out room for the actual conversation. Over 500 lines is a strong signal to split things up.',
+        recommendation: 'Move section-specific guidance into separate files and pull them in with `@import`. Keep the main file under 500 lines.',
+      },
+      'CLAUDE.md exceeds recommended 200 lines': {
+        title: 'Your `CLAUDE.md` is getting long',
+        description: 'Files over 200 lines start to take noticeable space on every turn.',
+        recommendation: 'Consider splitting longer sections into separate files linked with `@import`.',
+      },
+      'CLAUDE.md has no markdown headings': {
+        title: 'Your instructions file has no section headings',
+        description: 'Without headings, Claude can\'t easily navigate or reference specific parts of your guidance.',
+        recommendation: 'Add markdown headings (e.g. `# Project Overview`) to organize the file into sections.',
+      },
+      'Missing recommended sections': {
+        title: 'Your instructions file is missing common sections',
+        description: 'Sections like Project Overview, Commands, and Conventions help Claude apply your guidance consistently across tasks.',
+        recommendation: 'Add the missing sections noted in the details.',
+      },
+      '@import with deep relative path': {
+        title: 'A linked file lives several folders away',
+        description: 'Deep relative paths (`../../`) make the link fragile if files move.',
+        recommendation: 'Move the linked file closer, or use an absolute reference.',
+      },
+      'Repeated content detected': {
+        title: 'The same text appears more than once',
+        description: 'Repeated text wastes space on every turn.',
+        recommendation: 'Remove the duplicate, or pull the shared text into one place and link it.',
+      },
+      'Uses HTML comments': {
+        title: 'Your file has HTML comments',
+        description: 'HTML comments still count as text sent to Claude on every turn — they don\'t actually hide anything.',
+        recommendation: 'Delete the comment text if you don\'t want it sent, or convert it to a regular note.',
+      },
+      'Contains TODO/FIXME markers': {
+        title: 'Your file has TODO or FIXME notes',
+        description: 'These notes are sent to Claude on every turn even when they\'re internal reminders.',
+        recommendation: 'Resolve the TODO, or move it out of the file into your issue tracker.',
+      },
+    },
+    patterns: [],
+    _default: {
+      title: 'Your project instructions file has an issue',
+      description: 'A check on your instructions file flagged something worth a look.',
+      recommendation: 'Open the file shown and review the section indicated.',
+    },
+  },
+
+  // ─────────────────────────────────────────────────────────────
+  // SET — Settings Validator
+  // ─────────────────────────────────────────────────────────────
+  SET: {
+    static: {
+      'Unknown settings key': {
+        title: 'A settings key isn\'t recognized',
+        description: 'A key in your settings file isn\'t one Claude Code understands. It will be ignored.',
+        recommendation: 'Check the key name for typos, or remove the key if it\'s no longer in use.',
+      },
+      'Deprecated settings key': {
+        title: 'A settings key is no longer supported',
+        description: 'This key was removed or renamed in a newer version of Claude Code.',
+        recommendation: 'Replace it with the current equivalent shown in the details, or remove it.',
+      },
+      'Type mismatch in settings': {
+        title: 'A settings value has the wrong type',
+        description: 'The value (string, number, boolean, list, etc.) doesn\'t match what this setting expects, so the setting is ignored.',
+        recommendation: 'Open your settings file and change the value to the type shown in the details.',
+      },
+      'Invalid effortLevel value': {
+        title: 'The `effortLevel` value isn\'t one Claude Code accepts',
+        description: 'This setting only accepts a fixed list of values; the current one is outside that list.',
+        recommendation: 'Set `effortLevel` to one of the accepted values shown in the details.',
+      },
+      'Hooks configured as array instead of object': {
+        title: 'Your `hooks` block uses the old list format',
+        description: 'Newer versions of Claude Code expect `hooks` as an object keyed by event name, not as a list.',
+        recommendation: 'Convert the list into an object with one key per event (the details show the structure).',
+      },
+      'Many additionalDirectories entries': {
+        title: 'You have many extra directories in `additionalDirectories`',
+        description: 'Each extra directory adds context Claude has to consider on every turn, which slows responses.',
+        recommendation: 'Trim the list to only directories Claude actually needs to see.',
+      },
+      'No allow rules configured': {
+        title: 'You have no permission rules letting Claude use specific tools',
+        description: 'Without `allow` rules, Claude must ask before every tool use, which interrupts your workflow.',
+        recommendation: 'Add `allow` rules in `permissions` for the tools you trust Claude to use without asking.',
+      },
+      'No deny rules configured': {
+        title: 'You have no permission rules blocking risky tools',
+        description: 'Without `deny` rules, Claude can be asked to run anything you accept in a prompt.',
+        recommendation: 'Add `deny` rules for tools or commands that should never run (for example destructive shell commands).',
+      },
+      'Missing $schema reference': {
+        title: 'Your settings file is missing the format link',
+        description: 'Adding the format link lets your editor offer auto-complete and catch typos as you type.',
+        recommendation: 'Add `"$schema": "..."` at the top of the settings file (see the details for the right URL).',
+      },
+      'Invalid JSON in settings file': {
+        title: 'Your settings file isn\'t readable as JSON',
+        description: 'Claude Code can\'t parse the file, so all your settings are skipped.',
+        recommendation: 'Open the file and fix the JSON syntax shown in the details (often a missing comma or quote).',
+      },
+    },
+    patterns: [],
+    _default: {
+      title: 'Your settings file has an issue',
+      description: 'A check on your settings file flagged something worth a look.',
+      recommendation: 'Open the file shown and review the line indicated.',
+    },
+  },
+
+  // ─────────────────────────────────────────────────────────────
+  // HKV — Hook Validator
+  // ─────────────────────────────────────────────────────────────
+  HKV: {
+    static: {
+      'Hooks must be an object with event keys': {
+        title: 'Your hooks block has the wrong shape',
+        description: 'Claude Code expects `hooks` to be an object whose keys are event names (like `PreToolUse`).',
+        recommendation: 'Wrap your existing entries inside an object keyed by the event name (see the details for the structure).',
+      },
+      'Unknown hook event': {
+        title: 'An automation is tied to an event Claude Code doesn\'t recognize',
+        description: 'The event name isn\'t one Claude Code emits, so the automation will never fire.',
+        recommendation: 'Check the event name for typos. The details list the events Claude Code currently emits.',
+      },
+      'Matcher must be a string, not an object': {
+        title: 'A matcher uses the wrong format',
+        description: 'The matcher is written as an object, but Claude Code expects a plain string (or regex).',
+        recommendation: 'Replace the object with a string. The details show what the line should look like.',
+      },
+      'Hook handlers must be an array': {
+        title: 'A handler list uses the wrong format',
+        description: 'Claude Code expects `hooks` (inside an event) to be a list of handler objects.',
+        recommendation: 'Wrap the handler in `[ ... ]` if there\'s only one, or list each handler inside the array.',
+      },
+      'Missing hooks array in handler group': {
+        title: 'A handler group has no actual handlers',
+        description: 'The group declares an event but has no `hooks` list inside it, so nothing runs.',
+        recommendation: 'Add at least one handler to the group, or remove the empty group.',
+      },
+      'Invalid hook handler type': {
+        title: 'A handler uses an unrecognized type',
+        description: 'Each handler must say what kind it is (typically `command`). The current type isn\'t one Claude Code accepts.',
+        recommendation: 'Set `type` to a supported value. The details show the accepted list.',
+      },
+      'Hook timeout must be a number': {
+        title: 'A timeout isn\'t a number',
+        description: 'The `timeout` value must be an integer (milliseconds), not a string or other type.',
+        recommendation: 'Change the value to a plain number (for example `5000`).',
+      },
+      'Hook timeout outside recommended range': {
+        title: 'A timeout is unusually short or long',
+        description: 'Very short timeouts can cause flakiness; very long ones make Claude wait if a script hangs.',
+        recommendation: 'Pick a value between 500 ms and 30 seconds for typical scripts.',
+      },
+      'Hook script not found': {
+        title: 'A handler points to a script that doesn\'t exist',
+        description: 'The path in the handler doesn\'t match any file on disk, so the handler will never run.',
+        recommendation: 'Fix the path, or create the script at the location shown in the details.',
+      },
+      'Verbose hook output (loud script)': {
+        title: 'A handler script prints a lot of text',
+        description: 'Loud scripts crowd Claude\'s view of what just happened and can confuse later tool calls.',
+        recommendation: 'Quiet the script — print only what Claude needs to see, and send the rest to a log file.',
+      },
+      'Invalid JSON in hooks.json': {
+        title: 'Your hooks file isn\'t readable as JSON',
+        description: 'Claude Code can\'t parse the file, so none of your automations run.',
+        recommendation: 'Open the file and fix the JSON syntax shown in the details.',
+      },
+    },
+    patterns: [],
+    _default: {
+      title: 'An automation has an issue',
+      description: 'A check on your automations flagged something worth a look.',
+      recommendation: 'Open the automations file shown and review the section indicated.',
+    },
+  },
+
+  // ─────────────────────────────────────────────────────────────
+  // RUL — Rules Validator
+  // ─────────────────────────────────────────────────────────────
+  RUL: {
+    static: {
+      'Rule path pattern matches no files': {
+        title: 'A rule\'s file pattern matches nothing in your project',
+        description: 'The rule will never apply, because the pattern doesn\'t match any actual file.',
+        recommendation: 'Fix the pattern (typo, path change, or generalize it), or delete the rule if it\'s no longer needed.',
+      },
+      'Rule has no frontmatter (always active)': {
+        title: 'A rule has no scoping settings, so it loads everywhere',
+        description: 'Without scoping, the rule loads on every conversation regardless of which files you\'re working with.',
+        recommendation: 'Add a scoping block at the top of the file to limit when the rule loads (see the details).',
+      },
+      'Rule uses deprecated "globs" field': {
+        title: 'A rule uses an old field name',
+        description: 'The field was renamed; the old name still works for now but may stop working in a future release.',
+        recommendation: 'Rename the field to the current equivalent shown in the details.',
+      },
+      'Rule file is not .md': {
+        title: 'A rule file uses an unexpected extension',
+        description: 'Claude Code only reads `.md` files in the rules folder.',
+        recommendation: 'Rename the file to end in `.md`, or move it out of the rules folder.',
+      },
+      'Rule file is nearly empty': {
+        title: 'A rule file has almost no content',
+        description: 'An empty rule file does nothing for Claude.',
+        recommendation: 'Either add the rule\'s content, or delete the empty file.',
+      },
+      'Large unscoped rule file': {
+        title: 'A large rule file loads on every conversation',
+        description: 'Big files without scoping load on every turn and use space whether or not the rule is relevant.',
+        recommendation: 'Add scoping at the top of the file so it only loads for the files it applies to.',
+      },
+    },
+    patterns: [],
+    _default: {
+      title: 'A rule configuration has an issue',
+      description: 'A check on your rules flagged something worth a look.',
+      recommendation: 'Open the rule file shown and review the section indicated.',
+    },
+  },
+
+  // ─────────────────────────────────────────────────────────────
+  // MCP — MCP Config Validator
+  // ─────────────────────────────────────────────────────────────
+  MCP: {
+    static: {
+      'Unknown MCP server type': {
+        title: 'A connected service uses an unrecognized type',
+        description: 'The `type` field doesn\'t match one Claude Code knows how to start (typically `stdio`, `sse`, or `http`).',
+        recommendation: 'Change the `type` to one of the supported values shown in the details.',
+      },
+      'Invalid trust level': {
+        title: 'A connected service has an unrecognized trust setting',
+        description: 'Trust controls whether Claude can use the service\'s tools without asking.',
+        recommendation: 'Set the trust value to one of the accepted ones (see details).',
+      },
+      'Missing trust level': {
+        title: 'A connected service has no trust setting',
+        description: 'Without an explicit trust value, Claude has to ask before each tool use, which slows your work.',
+        recommendation: 'Add a trust value to the entry. The details show the accepted values.',
+      },
+      'Unknown MCP server field': {
+        title: 'A connected service has an unrecognized setting',
+        description: 'The setting isn\'t one Claude Code reads, so it will be ignored.',
+        recommendation: 'Check the spelling, or remove the setting if it\'s no longer used.',
+      },
+      'SSE server type — consider HTTP': {
+        title: 'A connected service uses an older transport type',
+        description: '`sse` works but the newer `http` transport is faster and more reliable for most setups.',
+        recommendation: 'If your service supports it, change the type to `http`.',
+      },
+      'Unreferenced env var in args': {
+        title: 'A configuration mentions an environment value that isn\'t set',
+        description: 'The connected service expects to find a value (like an API key) in your environment, but nothing is providing it.',
+        recommendation: 'Set the environment value before starting Claude Code, or update the entry to point to the right name.',
+      },
+      'Invalid JSON in MCP config': {
+        title: 'A connected-services file isn\'t readable as JSON',
+        description: 'Claude Code can\'t parse the file, so none of the connected services in it will load.',
+        recommendation: 'Open the file and fix the JSON syntax shown in the details.',
+      },
+    },
+    patterns: [],
+    _default: {
+      title: 'A connected-services configuration has an issue',
+      description: 'A check on your external-service setup flagged something worth a look.',
+      recommendation: 'Open the file shown and review the entry indicated.',
+    },
+  },
+
+  // ─────────────────────────────────────────────────────────────
+  // IMP — Import Resolver
+  // ─────────────────────────────────────────────────────────────
+  IMP: {
+    static: {
+      'Broken @import link': {
+        title: 'A file link points nowhere',
+        description: 'The link in `@import` references a file that doesn\'t exist, so the linked content never loads.',
+        recommendation: 'Fix the path, or remove the broken link.',
+      },
+      'Circular @import reference': {
+        title: 'Two files link back to each other in a loop',
+        description: 'A circular link makes Claude Code stop loading partway, which can drop important context.',
+        recommendation: 'Break the loop by removing one of the links, or by extracting the shared content into a third file.',
+      },
+      'Deep @import chain': {
+        title: 'A chain of file links goes more than three levels deep',
+        description: 'Long chains slow down loading and make it hard to see what content actually reaches Claude.',
+        recommendation: 'Flatten the chain by inlining intermediate files, or by linking directly to the deepest one.',
+      },
+      'Tilde path in @import': {
+        title: 'A file link uses a home-folder shortcut',
+        description: 'The `~/` shortcut works on your machine but breaks when teammates clone the repository.',
+        recommendation: 'Replace the tilde path with a relative path inside the project.',
+      },
+    },
+    patterns: [],
+    _default: {
+      title: 'A file link has an issue',
+      description: 'A check on your file links flagged something worth a look.',
+      recommendation: 'Open the file shown and review the link indicated.',
+    },
+  },
+
+  // ─────────────────────────────────────────────────────────────
+  // CNF — Conflict Detector
+  // ─────────────────────────────────────────────────────────────
+  CNF: {
+    static: {
+      'Permission allow/deny conflict': {
+        title: 'A tool is both let-in and shut-out by your permissions',
+        description: 'A `deny` entry takes priority over an `allow`, so the `allow` does nothing — but it also looks like the tool is approved.',
+        recommendation: 'Remove either the `allow` or the `deny` entry to make your intent clear.',
+      },
+      'Duplicate hook definition': {
+        title: 'The same automation is set up more than once',
+        description: 'Duplicate handlers run twice on the same event, which can produce double-output or unintended side effects.',
+        recommendation: 'Keep one copy and remove the others.',
+      },
+    },
+    patterns: [
+      {
+        regex: /^Settings key conflict:/,
+        translation: {
+          title: 'A settings key is set in more than one place with different values',
+          description: 'When the same key appears at different scopes (user, project, local) with different values, the more specific one wins — but the conflict often hides a forgotten override.',
+          recommendation: 'Check the locations shown in the details and decide which value should remain.',
+        },
+      },
+    ],
+    _default: {
+      title: 'Your configuration has a conflict',
+      description: 'Two parts of your setup tell Claude different things about the same setting.',
+      recommendation: 'Review the locations shown in the details and pick one source of truth.',
+    },
+  },
+
+  // ─────────────────────────────────────────────────────────────
+  // GAP — Feature Gap Scanner (opportunities, not problems)
+  // ─────────────────────────────────────────────────────────────
+  GAP: {
+    static: {
+      'No CLAUDE.md file': {
+        title: 'You haven\'t added project instructions for Claude yet',
+        description: 'A `CLAUDE.md` at your project root is the highest-impact thing you can add. It tells Claude how you work in this codebase.',
+        recommendation: 'Create `CLAUDE.md` with a one-paragraph overview, common commands, and any conventions Claude should know.',
+      },
+      'No permissions configured': {
+        title: 'You haven\'t set up tool permissions yet',
+        description: 'Permission rules let Claude use trusted tools without asking, and block risky ones outright.',
+        recommendation: 'Add `permissions.allow` for trusted tools and `permissions.deny` for ones to block.',
+      },
+      'No hooks configured': {
+        title: 'You haven\'t set up any automations yet',
+        description: 'Automations can run before or after Claude\'s actions — for example, formatting on save, or warning before risky commands.',
+        recommendation: 'Add a `hooks` block with at least one event to start.',
+      },
+      'No custom skills or commands': {
+        title: 'You haven\'t added any custom shortcuts yet',
+        description: 'Custom skills give you `/your-shortcut` invocations for tasks you do often.',
+        recommendation: 'Create a skill in `.claude/skills/` for a workflow you find yourself repeating.',
+      },
+      'No MCP servers configured': {
+        title: 'You haven\'t connected Claude to any external tools yet',
+        description: 'Connected services let Claude reach databases, search engines, browsers, ticket systems, and more.',
+        recommendation: 'Add a connection in `.mcp.json` for a service you want Claude to use.',
+      },
+      'Settings only at one scope': {
+        title: 'You only have settings at one level',
+        description: 'Settings can live at user, project, or local-only scope. Using more than one lets you keep personal preferences separate from team-shared ones.',
+        recommendation: 'Consider moving team-wide settings to project scope and keeping personal ones at user or local scope.',
+      },
+      'CLAUDE.md not modular': {
+        title: 'Your instructions file is one big block',
+        description: 'Splitting long instructions into smaller linked files makes them easier to maintain and easier on the loading time.',
+        recommendation: 'Break out long sections into separate files and link them with `@import`.',
+      },
+      'No path-scoped rules': {
+        title: 'Your rules all load on every conversation',
+        description: 'Path-scoped rules only load when you\'re working with files that match — keeps each conversation focused.',
+        recommendation: 'Add scoping to your rules so they only load for the files they apply to.',
+      },
+      'Auto-memory explicitly disabled': {
+        title: 'You\'ve turned auto-memory off',
+        description: 'Auto-memory lets Claude remember facts about you and your projects across conversations.',
+        recommendation: 'If this was unintentional, re-enable it in your user settings.',
+      },
+      'Low hook diversity': {
+        title: 'Your automations all listen to similar events',
+        description: 'Listening to a wider range of events (before-tool, after-tool, session-start, etc.) lets you catch more workflow opportunities.',
+        recommendation: 'Look at the events your current automations skip and consider adding one or two.',
+      },
+      'No custom subagents': {
+        title: 'You haven\'t set up any specialized helper agents yet',
+        description: 'Subagents handle parallel work in separate contexts (research, code review, testing) without crowding your main conversation.',
+        recommendation: 'Create a subagent in `.claude/agents/` for a task you delegate often.',
+      },
+      'No model configuration': {
+        title: 'You haven\'t pinned a model preference',
+        description: 'Setting a default model lets you choose between speed and depth of reasoning for your work.',
+        recommendation: 'Add a `model` setting in your settings file.',
+      },
+      'No status line configured': {
+        title: 'You haven\'t set up a status line yet',
+        description: 'A status line shows live context (token usage, current branch, time) at the bottom of your terminal.',
+        recommendation: 'Add a `statusLine` setting if you want this information at a glance.',
+      },
+      'No custom keybindings': {
+        title: 'You haven\'t set up any custom keybindings',
+        description: 'Custom keybindings let you trigger your most-used skills with a keystroke.',
+        recommendation: 'Add bindings in your settings for skills you run often.',
+      },
+      'Using default output style': {
+        title: 'You\'re using the default output style',
+        description: 'Output styles let you change how Claude formats responses (concise, verbose, bullet-heavy, etc.).',
+        recommendation: 'Try a different `outputStyle` setting if you have a strong preference.',
+      },
+      'No worktree workflow': {
+        title: 'You haven\'t set up parallel worktree support',
+        description: 'Worktrees let Claude work on a branch in an isolated copy of the repo without disturbing your main checkout.',
+        recommendation: 'Enable worktrees if you regularly work on multiple branches at once.',
+      },
+      'No advanced skill frontmatter': {
+        title: 'Your skills don\'t use the richer settings block',
+        description: 'Adding richer settings at the top of a skill lets you control when it loads, what tools it uses, and more.',
+        recommendation: 'Add fields like `model`, `tools`, or `description` to your skill files where useful.',
+      },
+      'No subagent isolation': {
+        title: 'Your subagents share Claude\'s main work folder',
+        description: 'Isolated subagents run in their own copy of the repo so they can\'t accidentally disturb your main work.',
+        recommendation: 'Add `isolation: worktree` to subagents that do destructive or experimental work.',
+      },
+      'No dynamic skill context': {
+        title: 'Your skills don\'t include live context',
+        description: 'Dynamic context lets a skill see fresh information (file contents, command output) at the moment it runs, not at the time it was written.',
+        recommendation: 'Use the dynamic-context block in skills that need up-to-date information.',
+      },
+      'No autoMode classifier': {
+        title: 'You haven\'t set up auto-mode classification',
+        description: 'Auto-mode classification helps Claude decide when to act on its own vs. ask you, based on the kind of task.',
+        recommendation: 'Add an auto-mode classifier in your settings if you want this nuance.',
+      },
+      'No project .mcp.json in git': {
+        title: 'Your team has no shared list of connected services',
+        description: 'Without a project-level connected-services file, every teammate has to set up their own connections.',
+        recommendation: 'Add `.mcp.json` at the project root so teammates get the same external tools.',
+      },
+      'No custom plugin': {
+        title: 'You haven\'t built a custom plugin yet',
+        description: 'Plugins let you bundle skills, automations, and connected services that you want available across many projects.',
+        recommendation: 'If you have workflows you repeat across projects, consider packaging them as a plugin.',
+      },
+      'Agent teams not enabled': {
+        title: 'You haven\'t enabled agent teams',
+        description: 'Agent teams let multiple subagents collaborate on a complex task, each with its own role.',
+        recommendation: 'Enable agent teams in settings if you tackle large multi-step work.',
+      },
+      'No managed settings': {
+        title: 'Your project has no settings managed by your organization',
+        description: 'Managed settings let your organization apply rules everyone has to follow.',
+        recommendation: 'If you work in a team setting, consider whether managed settings would help.',
+      },
+      'No LSP plugins': {
+        title: 'You haven\'t connected Claude to your editor\'s language servers',
+        description: 'Language-server connections let Claude see types, error messages, and definitions the same way your editor does.',
+        recommendation: 'Set up LSP integration if you work in a typed language.',
+      },
+    },
+    patterns: [],
+    _default: {
+      title: 'You have a feature opportunity worth a look',
+      description: 'There\'s a feature you haven\'t set up yet that might help your workflow.',
+      recommendation: 'See the details for what to add and where.',
+    },
+  },
+
+  // ─────────────────────────────────────────────────────────────
+  // TOK — Token Hotspots
+  // Category: Wasted tokens
+  // ─────────────────────────────────────────────────────────────
+  TOK: {
+    static: {
+      'CLAUDE.md cascade exceeds 10k tokens per turn': {
+        title: 'Your instruction files take a lot of space on every turn',
+        description: 'When the combined size of your instruction files goes above 10,000 tokens, every turn carries that weight. Responses get slower and you have less room for the conversation itself.',
+        recommendation: 'Trim or split the largest files. The details show which file contributes most.',
+      },
+      'Cache-breaking volatile content at top of CLAUDE.md': {
+        title: 'Your file starts with content that changes between turns',
+        description: 'Claude reuses earlier turns when the start of your instructions stays the same. Putting changing content (timestamps, session notes, todo lists) at the top breaks that reuse and slows every response.',
+        recommendation: 'Move the changing content to the bottom of the file, or out of the file entirely.',
+      },
+      'Deep @import chain defeats prompt-cache reuse': {
+        title: 'A long chain of file links breaks Claude\'s memory of your setup',
+        description: 'When linked files keep changing position, Claude can\'t reuse earlier work and has to re-read the whole chain.',
+        recommendation: 'Flatten the chain, or pin the most-changing parts at the end.',
+      },
+      'Redundant permission declarations': {
+        title: 'You have permission rules that duplicate each other',
+        description: 'Duplicate rules waste space and make it harder to see what\'s actually allowed.',
+        recommendation: 'Consolidate the duplicates into a single rule.',
+      },
+      'Bloated skill description (loads on every turn)': {
+        title: 'A skill description is unusually long',
+        description: 'Skill descriptions load on every turn whether you use the skill or not. Long descriptions add up.',
+        recommendation: 'Trim the description to one short sentence and move details into the skill body.',
+      },
+    },
+    patterns: [
+      {
+        regex: /^High .+ tool-schema budget on server/,
+        translation: {
+          title: 'A connected service exposes many tools, all loading on every turn',
+          description: 'Each tool a connected service exposes adds its description to every turn. Services with many tools eat space fast.',
+          recommendation: 'Limit which tools the service exposes (often via a `tools` allow-list), or disconnect services you rarely use.',
+        },
+      },
+    ],
+    _default: {
+      title: 'Something is using more space than needed',
+      description: 'A check on space-usage flagged something worth a look.',
+      recommendation: 'See the details for which file or setting to trim.',
+    },
+  },
+
+  // ─────────────────────────────────────────────────────────────
+  // CPS — Cache-Prefix Stability
+  // Category: Wasted tokens
+  // ─────────────────────────────────────────────────────────────
+  CPS: {
+    static: {
+      'Volatile content inside cached prefix breaks reuse': {
+        title: 'Content that changes between turns sits in the part Claude tries to reuse',
+        description: 'Claude saves space by reusing the start of your instructions across turns. Changing content in that area forces a fresh read every time, which slows responses.',
+        recommendation: 'Move the changing content (timestamps, session notes) below the first 150 lines, or out of the file.',
+      },
+    },
+    patterns: [],
+    _default: {
+      title: 'Content in your instructions is breaking Claude\'s memory of your setup',
+      description: 'A check on the reusable portion of your instructions flagged something worth a look.',
+      recommendation: 'See the details for which content to move.',
+    },
+  },
+
+  // ─────────────────────────────────────────────────────────────
+  // DIS — Disabled-In-Schema
+  // Category: Dead config
+  // ─────────────────────────────────────────────────────────────
+  DIS: {
+    static: {
+      'Tool listed in both permissions.deny and permissions.allow': {
+        title: 'A tool is in both the let-in list and the shut-out list',
+        description: 'When a tool is in both lists, the shut-out always wins, so the let-in entry does nothing. It looks like the tool is approved, but it isn\'t.',
+        recommendation: 'Decide whether the tool should be allowed or denied, and remove it from the other list.',
+      },
+    },
+    patterns: [],
+    _default: {
+      title: 'Part of your config doesn\'t actually do anything',
+      description: 'A check on dead-config flagged something worth a look.',
+      recommendation: 'See the details for which entry is overridden.',
+    },
+  },
+
+  // ─────────────────────────────────────────────────────────────
+  // COL — Collision Scanner
+  // Category: Conflict
+  // ─────────────────────────────────────────────────────────────
+  COL: {
+    static: {},
+    patterns: [
+      {
+        regex: /^Skill name ".+" used by multiple plugins/,
+        translation: {
+          title: 'Two plugins both define a skill with the same name',
+          description: 'When two plugins offer the same skill name, only one wins, and which one is hard to predict.',
+          recommendation: 'Rename the skill in one of the plugins, or disable the one you don\'t use.',
+        },
+      },
+      {
+        regex: /^Skill name ".+" collides between user-level and plugin sources/,
+        translation: {
+          title: 'Your personal skill clashes with one from a plugin',
+          description: 'Your user-level skill and a plugin\'s skill share the same name, so only one of them runs when you call it.',
+          recommendation: 'Rename your personal version, or disable the plugin\'s version.',
+        },
+      },
+    ],
+    _default: {
+      title: 'A skill name is used in more than one place',
+      description: 'A check on overlapping skill names flagged something worth a look.',
+      recommendation: 'See the details for the overlapping name.',
+    },
+  },
+
+  // ─────────────────────────────────────────────────────────────
+  // PLH — Plugin Health
+  // Category: Configuration mistake
+  // ─────────────────────────────────────────────────────────────
+  PLH: {
+    static: {
+      'Missing CLAUDE.md': {
+        title: 'A plugin has no instructions file',
+        description: 'Plugins should ship with `CLAUDE.md` so users understand what the plugin does and how to use it.',
+        recommendation: 'Add `CLAUDE.md` to the plugin folder with a brief overview.',
+      },
+      'Missing plugin.json': {
+        title: 'A plugin folder has no manifest',
+        description: 'A `plugin.json` is required for Claude Code to recognize and load the plugin.',
+        recommendation: 'Add `plugin.json` to the plugin folder. The details show the required fields.',
+      },
+      'Invalid plugin.json': {
+        title: 'A plugin\'s manifest has a problem',
+        description: 'The manifest exists but Claude Code can\'t parse it, so the plugin won\'t load.',
+        recommendation: 'Open `plugin.json` and fix the JSON syntax.',
+      },
+      'Command missing frontmatter': {
+        title: 'A command file has no settings block at the top',
+        description: 'The settings block at the top of a command file tells Claude how to handle it.',
+        recommendation: 'Add a settings block (delimited by `---`) at the top of the file.',
+      },
+      'Agent missing frontmatter': {
+        title: 'An agent file has no settings block at the top',
+        description: 'The settings block tells Claude what tools and model the agent should use.',
+        recommendation: 'Add a settings block (delimited by `---`) at the top of the file.',
+      },
+      'Cross-plugin command name conflict': {
+        title: 'Two plugins both define a command with the same name',
+        description: 'When two plugins use the same command name, only one wins.',
+        recommendation: 'Rename the command in one of the plugins, or disable the one you don\'t need.',
+      },
+      'No plugins found': {
+        title: 'No plugins are installed in this location',
+        description: 'The location was checked but contains no plugins (or no plugins Claude Code recognizes).',
+        recommendation: 'Check that the path is correct, or install a plugin if that was intended.',
+      },
+      'Invalid hooks.json structure': {
+        title: 'A plugin\'s automations file has the wrong shape',
+        description: 'The automations file isn\'t structured the way Claude Code expects, so its automations won\'t load.',
+        recommendation: 'Open `hooks.json` and fix the structure as shown in the details.',
+      },
+      'Invalid hooks.json': {
+        title: 'A plugin\'s automations file isn\'t valid JSON',
+        description: 'Claude Code can\'t parse the file, so its automations won\'t load.',
+        recommendation: 'Open `hooks.json` and fix the JSON syntax.',
+      },
+      'hooks.json uses array instead of object': {
+        title: 'A plugin\'s automations file uses the old list format',
+        description: 'Newer Claude Code expects automations as an object keyed by event name.',
+        recommendation: 'Convert the list to an object as shown in the details.',
+      },
+      'Unknown file in .claude-plugin/': {
+        title: 'A file in the plugin folder isn\'t one Claude Code expects',
+        description: 'Unknown files are ignored, but they often signal a typo or leftover content.',
+        recommendation: 'Move or delete the file if it isn\'t needed.',
+      },
+    },
+    patterns: [
+      {
+        regex: /^Missing required field in plugin\.json/,
+        translation: {
+          title: 'A plugin\'s manifest is missing a required field',
+          description: 'The manifest exists but is missing a field Claude Code needs.',
+          recommendation: 'Add the missing field shown in the details.',
+        },
+      },
+      {
+        regex: /^CLAUDE\.md missing .+ section$/,
+        translation: {
+          title: 'A plugin\'s instructions file is missing a recommended section',
+          description: 'The plugin\'s instructions file exists but is missing a section users tend to look for.',
+          recommendation: 'Add the section shown in the details.',
+        },
+      },
+      {
+        regex: /^Command missing frontmatter field:/,
+        translation: {
+          title: 'A command file is missing a setting at the top',
+          description: 'A required setting in the command\'s top-of-file block is missing.',
+          recommendation: 'Add the missing setting shown in the details.',
+        },
+      },
+      {
+        regex: /^Agent missing frontmatter field:/,
+        translation: {
+          title: 'An agent file is missing a setting at the top',
+          description: 'A required setting in the agent\'s top-of-file block is missing.',
+          recommendation: 'Add the missing setting shown in the details.',
+        },
+      },
+    ],
+    _default: {
+      title: 'A plugin has a configuration issue',
+      description: 'A check on the plugin\'s structure flagged something worth a look.',
+      recommendation: 'See the details for what needs to change.',
+    },
+  },
+};

plugins/config-audit/scanners/lib/humanizer.mjs

@@ -0,0 +1,196 @@
+/**
+ * Plain-language humanizer for config-audit findings.
+ *
+ * Pure functions. Never mutate inputs. Translates technical scanner output
+ * into user-friendly language at output-formatting time. Adds three new
+ * fields to each finding:
+ *   - userImpactCategory: human-readable label per scanner (research/02)
+ *   - userActionLanguage: one-line urgency phrase per severity
+ *   - relevanceContext: deterministic file-pattern heuristic
+ *
+ * Original id, scanner, severity, file, line, evidence, category, autoFixable
+ * are preserved exactly. Title, description, recommendation are replaced when
+ * a translation is found; otherwise the originals are kept.
+ *
+ * Lookup order (per scanner prefix):
+ *   1. exact title in TRANSLATIONS[prefix].static
+ *   2. first regex match in TRANSLATIONS[prefix].patterns
+ *   3. TRANSLATIONS[prefix]._default
+ *   4. fallthrough: original strings (when scanner prefix has no entry)
+ *
+ * Zero external dependencies.
+ */
+
+import { TRANSLATIONS } from './humanizer-data.mjs';
+
+/**
+ * Map scanner prefix to user-facing impact-category label (research/02 line 124).
+ */
+const SCANNER_TO_CATEGORY = {
+  CML: 'Configuration mistake',
+  SET: 'Configuration mistake',
+  HKV: 'Configuration mistake',
+  RUL: 'Configuration mistake',
+  MCP: 'Configuration mistake',
+  IMP: 'Configuration mistake',
+  CNF: 'Conflict',
+  COL: 'Conflict',
+  TOK: 'Wasted tokens',
+  CPS: 'Wasted tokens',
+  DIS: 'Dead config',
+  GAP: 'Missed opportunity',
+  PLH: 'Configuration mistake',
+};
+
+/**
+ * Map severity to one-line action-language phrase (research/02 line 134).
+ */
+const SEVERITY_TO_ACTION = {
+  critical: 'Fix this now',
+  high: 'Fix soon',
+  medium: 'Fix when convenient',
+  low: 'Optional cleanup',
+  info: 'FYI',
+};
+
+/**
+ * Compute relevance context from a finding's file path. Deterministic, in-process,
+ * no subprocess. Conservative — defaults to 'affects-everyone' when ambiguous.
+ *
+ * @param {string|null|undefined} filePath
+ * @returns {'test-fixture-no-impact' | 'affects-this-machine-only' | 'affects-everyone'}
+ */
+export function computeRelevanceContext(filePath) {
+  if (typeof filePath !== 'string' || filePath.length === 0) {
+    return 'affects-everyone';
+  }
+  if (filePath.includes('/tests/fixtures/') || filePath.includes('/test/fixtures/')) {
+    return 'test-fixture-no-impact';
+  }
+  // Match basename pattern *.local.* (e.g., settings.local.json, claude.local.md)
+  const basename = filePath.split('/').pop() || '';
+  if (/\.local\./.test(basename)) {
+    return 'affects-this-machine-only';
+  }
+  return 'affects-everyone';
+}
+
+/**
+ * Look up translation for a finding by scanner prefix and title.
+ * Returns the translation object or null when no match (caller falls through to original).
+ *
+ * @param {string} scanner
+ * @param {string} title
+ * @returns {{title:string, description:string, recommendation:string} | null}
+ */
+function lookupTranslation(scanner, title) {
+  const entry = TRANSLATIONS[scanner];
+  if (!entry) return null;
+
+  // 1. Exact static match
+  if (typeof title === 'string' && entry.static && Object.prototype.hasOwnProperty.call(entry.static, title)) {
+    return entry.static[title];
+  }
+
+  // 2. Pattern match
+  if (Array.isArray(entry.patterns) && typeof title === 'string') {
+    for (const p of entry.patterns) {
+      if (p.regex instanceof RegExp && p.regex.test(title)) {
+        return p.translation;
+      }
+    }
+  }
+
+  // 3. Default
+  if (entry._default) {
+    return entry._default;
+  }
+
+  return null;
+}
+
+/**
+ * Humanize a single finding. Pure — never mutates input. Returns a new object.
+ *
+ * @param {object} finding - finding object from scanner output
+ * @returns {object} new finding with translated title/description/recommendation +
+ *                   userImpactCategory, userActionLanguage, relevanceContext fields
+ */
+export function humanizeFinding(finding) {
+  if (!finding || typeof finding !== 'object') {
+    return finding;
+  }
+
+  const translation = lookupTranslation(finding.scanner, finding.title);
+  const category = SCANNER_TO_CATEGORY[finding.scanner] || 'Other';
+  const action = SEVERITY_TO_ACTION[finding.severity] || 'FYI';
+  const relevance = computeRelevanceContext(finding.file);
+
+  const out = {
+    // Preserve identifying / structural fields exactly
+    id: finding.id,
+    scanner: finding.scanner,
+    severity: finding.severity,
+    // Replace prose if a translation exists; otherwise keep originals
+    title: translation ? translation.title : finding.title,
+    description: translation ? translation.description : finding.description,
+    file: finding.file ?? null,
+    line: finding.line ?? null,
+    evidence: finding.evidence ?? null,
+    category: finding.category ?? null,
+    recommendation: translation ? translation.recommendation : finding.recommendation,
+    autoFixable: finding.autoFixable ?? false,
+    // New humanized fields
+    userImpactCategory: category,
+    userActionLanguage: action,
+    relevanceContext: relevance,
+  };
+
+  // Preserve optional details payload if present (v5 N6)
+  if (finding.details && typeof finding.details === 'object') {
+    out.details = finding.details;
+  }
+
+  return out;
+}
+
+/**
+ * Humanize an array of findings. Pure — returns a new array of new objects.
+ *
+ * @param {object[]} findings
+ * @returns {object[]}
+ */
+export function humanizeFindings(findings) {
+  if (!Array.isArray(findings)) return findings;
+  return findings.map(humanizeFinding);
+}
+
+/**
+ * Humanize a top-level envelope produced by `runAllScanners`. Walks
+ * `env.scanners[].findings`. Pure — returns a new envelope with new
+ * scanner objects and new finding objects. The envelope-level shape
+ * (scanners array, target_path, total_duration_ms, aggregate, etc.)
+ * is preserved.
+ *
+ * @param {object} env
+ * @returns {object}
+ */
+export function humanizeEnvelope(env) {
+  if (!env || typeof env !== 'object' || !Array.isArray(env.scanners)) {
+    return env;
+  }
+
+  const newScanners = env.scanners.map((s) => {
+    if (!s || typeof s !== 'object') return s;
+    if (!Array.isArray(s.findings)) return s;
+    return {
+      ...s,
+      findings: humanizeFindings(s.findings),
+    };
+  });
+
+  return {
+    ...env,
+    scanners: newScanners,
+  };
+}

plugins/config-audit/scanners/lib/scoring.mjs

@@ -4,6 +4,19 @@
  */
 
 import { gradeFromPassRate, WEIGHTS } from './severity.mjs';
+import { humanizeFinding } from './humanizer.mjs';
+
+/**
+ * One-line plain-language context per overall grade. Used when a scorecard
+ * is rendered with `options.humanized: true`.
+ */
+const GRADE_CONTEXT = {
+  A: 'Healthy setup, only minor polish needed',
+  B: 'Good shape — a few items to address',
+  C: 'Some attention needed',
+  D: 'Several issues — prioritize the urgent ones',
+  F: 'Important issues need attention',
+};
 
 // --- Tier weights for utilization calculation ---
 const TIER_WEIGHTS = { t1: 3, t2: 2, t3: 1, t4: 1 };
@@ -235,14 +248,21 @@ export function scoreByArea(scannerResults) {
 /**
  * Derive top 3 actions from GAP findings (T1 first, then T2).
  * @param {object[]} gapFindings
+ * @param {object} [options]
+ * @param {boolean} [options.humanized=false] - When true, return humanized
+ *   recommendations (looked up via humanizer translations).
  * @returns {string[]}
  */
-export function topActions(gapFindings) {
+export function topActions(gapFindings, options = {}) {
   const tierOrder = ['t1', 't2', 't3', 't4'];
   const sorted = [...gapFindings].sort(
     (a, b) => tierOrder.indexOf(a.category) - tierOrder.indexOf(b.category),
   );
-  return sorted.slice(0, 3).map(f => f.recommendation);
+  const top3 = sorted.slice(0, 3);
+  if (options.humanized) {
+    return top3.map(f => humanizeFinding(f).recommendation);
+  }
+  return top3.map(f => f.recommendation);
 }
 
 /**
@@ -307,32 +327,58 @@ export function generateScorecard(areaScores, utilization, maturity, segment, ac
  * Shows only the quality areas (currently 8) — no utilization, maturity, or segment.
  * @param {{ areas: Array<{ name: string, grade: string, score: number }>, overallGrade: string }} areaScores
  * @param {number} opportunityCount - Number of GAP findings (shown as opportunity count)
+ * @param {object} [options]
+ * @param {boolean} [options.humanized=false] - When true, render with plain-language
+ *   grade context and friendlier opportunity phrasing. When false (default),
+ *   render the v5.0.0 verbatim scorecard (backwards-compatible).
  * @returns {string}
  */
-export function generateHealthScorecard(areaScores, opportunityCount) {
+export function generateHealthScorecard(areaScores, opportunityCount, options = {}) {
   const qualityAreas = areaScores.areas.filter(a => a.name !== 'Feature Coverage');
   const avgScore = qualityAreas.length > 0
     ? Math.round(qualityAreas.reduce((s, a) => s + a.score, 0) / qualityAreas.length)
     : 0;
 
+  const humanized = options.humanized === true;
+
   const lines = [];
   lines.push('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━');
-  lines.push(' Config-Audit Health Score');
+  lines.push(humanized ? ' Configuration health' : ' Config-Audit Health Score');
   lines.push('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━');
   lines.push('');
+
+  if (humanized) {
+    const context = GRADE_CONTEXT[areaScores.overallGrade] || '';
+    const headline = context
+      ? ` Health: ${areaScores.overallGrade} (${avgScore}/100) — ${context}`
+      : ` Health: ${areaScores.overallGrade} (${avgScore}/100)`;
+    lines.push(headline);
+    lines.push(` ${qualityAreas.length} areas reviewed`);
+  } else {
     lines.push(` Health: ${areaScores.overallGrade} (${avgScore}/100)    ${qualityAreas.length} areas scanned`);
+  }
+
   lines.push('');
-  lines.push(' Area Scores');
+  lines.push(humanized ? ' Area scores' : ' Area Scores');
   lines.push(' ───────────');
 
-  // Format areas in 2-column layout (quality areas only)
+  // Format areas in 2-column layout (quality areas only).
+  // In humanized mode, area names are wrapped in backticks so SC-3 can treat
+  // them as code references (technical identifiers like CLAUDE.md, MCP, Hooks
+  // are tier3 jargon outside backtick spans). Padding compensates for the
+  // two extra characters so column alignment matches the v5.0.0 layout.
+  const padBase = humanized ? 22 : 20;
+  const padCol = humanized ? 37 : 35;
+  const labelOf = (a) => (humanized ? `\`${a.name}\`` : a.name);
   for (let i = 0; i < qualityAreas.length; i += 2) {
     const left = qualityAreas[i];
     const right = qualityAreas[i + 1];
-    const leftStr = ` ${left.name} ${'.'.repeat(Math.max(1, 20 - left.name.length))} ${left.grade} (${left.score})`;
+    const leftLabel = labelOf(left);
+    const leftStr = ` ${leftLabel} ${'.'.repeat(Math.max(1, padBase - leftLabel.length))} ${left.grade} (${left.score})`;
     if (right) {
-      const rightStr = `${right.name} ${'.'.repeat(Math.max(1, 20 - right.name.length))} ${right.grade} (${right.score})`;
+      const rightLabel = labelOf(right);
-      lines.push(`${leftStr.padEnd(35)}${rightStr}`);
+      const rightStr = `${rightLabel} ${'.'.repeat(Math.max(1, padBase - rightLabel.length))} ${right.grade} (${right.score})`;
+      lines.push(`${leftStr.padEnd(padCol)}${rightStr}`);
     } else {
       lines.push(leftStr);
     }
@@ -340,8 +386,13 @@ export function generateHealthScorecard(areaScores, opportunityCount) {
 
   if (opportunityCount > 0) {
     lines.push('');
+    if (humanized) {
+      const noun = opportunityCount === 1 ? 'way' : 'ways';
+      lines.push(` ${opportunityCount} ${noun} you could get more out of Claude Code — see /config-audit feature-gap`);
+    } else {
       lines.push(` ${opportunityCount} ${opportunityCount === 1 ? 'opportunity' : 'opportunities'} available — run /config-audit feature-gap for recommendations`);
     }
+  }
 
   lines.push('');
   lines.push('━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━');

plugins/config-audit/scanners/manifest.mjs

@@ -103,9 +103,13 @@ async function main() {
   let targetPath = '.';
   let outputFile = null;
   let jsonMode = false;
+  // --raw is accepted for CLI surface consistency but is a no-op here:
+  // manifest produces a token-source inventory, not findings.
+  let rawMode = false;
 
   for (let i = 0; i < args.length; i++) {
     if (args[i] === '--json') jsonMode = true;
+    else if (args[i] === '--raw') rawMode = true;
     else if (args[i] === '--output-file' && args[i + 1]) outputFile = args[++i];
     else if (!args[i].startsWith('-')) targetPath = args[i];
   }
@@ -143,7 +147,7 @@ async function main() {
     await writeFile(outputFile, json, 'utf-8');
   }
 
-  if (jsonMode || !outputFile) {
+  if (jsonMode || rawMode || !outputFile) {
     process.stdout.write(json + '\n');
   }
 }

plugins/config-audit/scanners/plugin-health-scanner.mjs

@@ -13,6 +13,7 @@ import { join, basename, resolve } from 'node:path';
 import { finding, scannerResult, resetCounter } from './lib/output.mjs';
 import { SEVERITY } from './lib/severity.mjs';
 import { parseFrontmatter } from './lib/yaml-parser.mjs';
+import { humanizeFindings } from './lib/humanizer.mjs';
 
 const SCANNER = 'PLH';
 
@@ -420,27 +421,33 @@ async function main() {
   const args = process.argv.slice(2);
   let targetPath = '.';
   let jsonMode = false;
+  let rawMode = false;
 
   for (let i = 0; i < args.length; i++) {
     if (args[i] === '--json') {
       jsonMode = true;
+    } else if (args[i] === '--raw') {
+      rawMode = true;
     } else if (!args[i].startsWith('-')) {
       targetPath = args[i];
     }
   }
 
-  process.stderr.write(`Plugin Health Scanner v2.1.0\n`);
+  const humanizedProgress = !jsonMode && !rawMode;
+  process.stderr.write(humanizedProgress ? `Plugin Health v2.1.0\n` : `Plugin Health Scanner v2.1.0\n`);
   process.stderr.write(`Target: ${resolve(targetPath)}\n\n`);
 
   const result = await scan(targetPath);
 
-  if (jsonMode) {
+  if (jsonMode || rawMode) {
+    // --json and --raw both write the v5.0.0-shape result (byte-identical).
     process.stdout.write(JSON.stringify(result, null, 2) + '\n');
   } else {
-    // Brief summary
+    // Default mode humanizes finding titles before writing the brief summary.
-    const count = result.findings.length;
+    const findings = humanizeFindings(result.findings);
+    const count = findings.length;
     process.stderr.write(`Findings: ${count}\n`);
-    for (const f of result.findings) {
+    for (const f of findings) {
       process.stderr.write(`  [${f.severity}] ${f.title}\n`);
     }
   }

plugins/config-audit/scanners/posture.mjs

@@ -60,6 +60,7 @@ async function main() {
   let targetPath = '.';
   let outputFile = null;
   let jsonMode = false;
+  let rawMode = false;
   let includeGlobal = false;
   let fullMachine = false;
 
@@ -68,6 +69,8 @@ async function main() {
       outputFile = args[++i];
     } else if (args[i] === '--json') {
       jsonMode = true;
+    } else if (args[i] === '--raw') {
+      rawMode = true;
     } else if (args[i] === '--global') {
       includeGlobal = true;
     } else if (args[i] === '--full-machine') {
@@ -80,16 +83,28 @@ async function main() {
   }
 
   const filterFixtures = !args.includes('--include-fixtures');
-  const result = await runPosture(targetPath, { includeGlobal, fullMachine, filterFixtures });
+  const humanizedProgress = !jsonMode && !rawMode;
+  const result = await runPosture(targetPath, {
+    includeGlobal,
+    fullMachine,
+    filterFixtures,
+    humanizedProgress,
+  });
 
-  if (jsonMode) {
+  // stdout JSON path: --json and --raw both write the v5.0.0-shape result
+  // (byte-identical). Default mode writes nothing to stdout.
+  if (jsonMode || rawMode) {
     const json = JSON.stringify(result, null, 2);
     process.stdout.write(json + '\n');
-  } else {
+  }
-    // Terminal scorecard (v3 health format)
+
+  // stderr scorecard path: --json suppresses; --raw renders v5.0.0 verbatim
+  // (humanized=false); default renders humanized scorecard.
+  if (!jsonMode) {
     const scorecard = generateHealthScorecard(
       { areas: result.areas, overallGrade: result.overallGrade },
       result.opportunityCount,
+      { humanized: !rawMode },
     );
     process.stderr.write('\n' + scorecard + '\n');
   }

plugins/config-audit/scanners/scan-orchestrator.mjs

@@ -13,6 +13,7 @@ import { resetCounter } from './lib/output.mjs';
 import { envelope } from './lib/output.mjs';
 import { discoverConfigFiles, discoverConfigFilesMulti, discoverFullMachinePaths } from './lib/file-discovery.mjs';
 import { loadSuppressions, applySuppressions, formatSuppressionSummary } from './lib/suppression.mjs';
+import { humanizeEnvelope } from './lib/humanizer.mjs';
 
 // Scanner registry — import order determines execution order
 import { scan as scanClaudeMd } from './claude-md-linter.mjs';
@@ -100,7 +101,10 @@ export async function runAllScanners(targetPath, opts = {}) {
       const result = await scanner.fn(resolvedPath, discovery);
       results.push(result);
       const count = result.findings.length;
-      process.stderr.write(`  [${scanner.name}] ${scanner.label}: ${count} finding(s) (${Date.now() - scanStart}ms)\n`);
+      const label = opts.humanizedProgress
+        ? `\`[${scanner.name}] ${scanner.label}\``
+        : `[${scanner.name}] ${scanner.label}`;
+      process.stderr.write(`  ${label}: ${count} finding(s) (${Date.now() - scanStart}ms)\n`);
     } catch (err) {
       results.push({
         scanner: scanner.name,
@@ -111,7 +115,10 @@ export async function runAllScanners(targetPath, opts = {}) {
         counts: { critical: 0, high: 0, medium: 0, low: 0, info: 0 },
         error: err.message,
       });
-      process.stderr.write(`  [${scanner.name}] ${scanner.label}: ERROR — ${err.message}\n`);
+      const label = opts.humanizedProgress
+        ? `\`[${scanner.name}] ${scanner.label}\``
+        : `[${scanner.name}] ${scanner.label}`;
+      process.stderr.write(`  ${label}: ERROR — ${err.message}\n`);
     }
   }
 
@@ -201,6 +208,10 @@ async function main() {
       // handled below
     } else if (args[i] === '--include-fixtures') {
       // handled below
+    } else if (args[i] === '--json') {
+      // handled below — explicit machine-readable mode (bypass humanizer)
+    } else if (args[i] === '--raw') {
+      // handled below — v5.0.0 verbatim mode (bypass humanizer)
     } else if (!args[i].startsWith('-')) {
       targetPath = args[i];
     }
@@ -210,15 +221,26 @@ async function main() {
   const fullMachine = args.includes('--full-machine');
   const suppress = !args.includes('--no-suppress');
   const filterFixtures = !args.includes('--include-fixtures');
+  const jsonMode = args.includes('--json');
+  const rawMode = args.includes('--raw');
 
-  process.stderr.write(`Config-Audit Scanner v2.2.0\n`);
+  const humanizedProgress = !jsonMode && !rawMode;
+  process.stderr.write(humanizedProgress ? `Config-Audit v2.2.0\n` : `Config-Audit Scanner v2.2.0\n`);
   process.stderr.write(`Target: ${resolve(targetPath)}\n`);
   process.stderr.write(`Scope: ${fullMachine ? 'full-machine' : includeGlobal ? 'global' : 'project'}\n`);
   process.stderr.write(`Fixtures: ${filterFixtures ? 'excluded' : 'included'}\n\n`);
 
-  const result = await runAllScanners(targetPath, { includeGlobal, fullMachine, suppress, filterFixtures });
+  const result = await runAllScanners(targetPath, {
+    includeGlobal,
+    fullMachine,
+    suppress,
+    filterFixtures,
+    humanizedProgress,
+  });
 
-  const json = JSON.stringify(result, null, 2);
+  // Default mode runs the humanizer; --json and --raw bypass for v5.0.0 byte-equal output.
+  const output = (jsonMode || rawMode) ? result : humanizeEnvelope(result);
+  const json = JSON.stringify(output, null, 2);
 
   if (outputFile) {
     await writeFile(outputFile, json, 'utf-8');
@@ -229,7 +251,9 @@ async function main() {
 
   if (saveBaseline) {
     const bPath = baselinePath || resolve(targetPath, '.config-audit-baseline.json');
-    await writeFile(bPath, json, 'utf-8');
+    // Always save baselines as raw v5.0.0-shape envelope so future humanizer
+    // changes don't trigger false-positive drift findings.
+    await writeFile(bPath, JSON.stringify(result, null, 2), 'utf-8');
     process.stderr.write(`Baseline saved to ${bPath}\n`);
   }
 

plugins/config-audit/scanners/self-audit.mjs

@@ -19,6 +19,7 @@ import { scoreByArea } from './lib/scoring.mjs';
 import { gradeFromPassRate } from './lib/severity.mjs';
 import { loadSuppressions, applySuppressions } from './lib/suppression.mjs';
 import { parseJson } from './lib/yaml-parser.mjs';
+import { humanizeEnvelope, humanizeFindings } from './lib/humanizer.mjs';
 
 const execFileAsync = promisify(execFile);
 
@@ -268,6 +269,14 @@ export async function runSelfAudit(opts = {}) {
  * @returns {string}
  */
 export function formatSelfAudit(result) {
+  // Humanize findings for terminal-output path only. JSON path (--json) is
+  // unaffected \u2014 it serializes the original `result` object directly.
+  const humanizedConfigEnv = humanizeEnvelope(result.configEnvelope);
+  const humanizedAllFindings = [
+    ...humanizedConfigEnv.scanners.flatMap(s => s.findings),
+    ...humanizeFindings(result.pluginHealthResult.findings),
+  ];
+
   const lines = [];
   lines.push('\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501\u2501');
   lines.push(' Config-Audit Self-Audit');
@@ -278,7 +287,7 @@ export function formatSelfAudit(result) {
   lines.push('');
 
   // Issues summary
-  const nonInfo = result.allFindings.filter(f => f.severity !== 'info');
+  const nonInfo = humanizedAllFindings.filter(f => f.severity !== 'info');
   if (nonInfo.length > 0) {
     lines.push(` Issues (${nonInfo.length}):`);
     for (const f of nonInfo.slice(0, 10)) {

plugins/config-audit/scanners/token-hotspots-cli.mjs

@@ -19,6 +19,7 @@ import { discoverConfigFiles } from './lib/file-discovery.mjs';
 import { resetCounter } from './lib/output.mjs';
 import { scan } from './token-hotspots.mjs';
 import * as tokenizerApi from './lib/tokenizer-api.mjs';
+import { humanizeFindings } from './lib/humanizer.mjs';
 
 const __dirname = dirname(fileURLToPath(import.meta.url));
 const TELEMETRY_RECIPE_PATH = resolve(__dirname, '..', 'knowledge', 'cache-telemetry-recipe.md');
@@ -51,12 +52,14 @@ async function main() {
   let targetPath = '.';
   let outputFile = null;
   let jsonMode = false;
+  let rawMode = false;
   let includeGlobal = false;
   let withTelemetryRecipe = false;
   let accurateTokens = false;
 
   for (let i = 0; i < args.length; i++) {
     if (args[i] === '--json') jsonMode = true;
+    else if (args[i] === '--raw') rawMode = true;
     else if (args[i] === '--global') includeGlobal = true;
     else if (args[i] === '--with-telemetry-recipe') withTelemetryRecipe = true;
     else if (args[i] === '--accurate-tokens') accurateTokens = true;
@@ -111,13 +114,19 @@ async function main() {
     }
   }
 
+  // Default mode humanizes payload.findings (NOT result.findings).
+  // --json and --raw bypass for v5.0.0 byte-equal output.
+  if (!jsonMode && !rawMode) {
+    payload.findings = humanizeFindings(payload.findings);
+  }
+
   const json = JSON.stringify(payload, null, 2);
 
   if (outputFile) {
     await writeFile(outputFile, json, 'utf-8');
   }
 
-  if (jsonMode || !outputFile) {
+  if (jsonMode || rawMode || !outputFile) {
     process.stdout.write(json + '\n');
   }
 }

plugins/config-audit/scanners/whats-active.mjs

@@ -21,11 +21,15 @@ async function main() {
   let targetPath = '.';
   let outputFile = null;
   let jsonMode = false;
+  // --raw is accepted for CLI surface consistency but is a no-op here:
+  // whats-active produces an inventory snapshot, not findings.
+  let rawMode = false;
   let verbose = false;
   let suggestDisables = false;
 
   for (let i = 0; i < args.length; i++) {
     if (args[i] === '--json') jsonMode = true;
+    else if (args[i] === '--raw') rawMode = true;
     else if (args[i] === '--verbose') verbose = true;
     else if (args[i] === '--suggest-disables') suggestDisables = true;
     else if (args[i] === '--output-file' && args[i + 1]) outputFile = args[++i];
@@ -51,7 +55,7 @@ async function main() {
     await writeFile(outputFile, json, 'utf-8');
   }
 
-  if (jsonMode || !outputFile) {
+  if (jsonMode || rawMode || !outputFile) {
     process.stdout.write(json + '\n');
   }
 }