diff --git a/creative-strategy-foundations/package.json b/creative-strategy-foundations/package.json
index 907a2c53..12380651 100644
--- a/creative-strategy-foundations/package.json
+++ b/creative-strategy-foundations/package.json
@@ -2,7 +2,7 @@
   "schemaVersion": 1,
   "id": "creative-strategy-foundations",
   "name": "Creative Strategy Foundations",
-  "version": "1",
+  "version": "2",
   "description": "Baseline Runneth creative strategy skills installed outside the protected Runneth volume.",
   "installPolicy": "auto",
   "updatePolicy": "auto",
diff --git a/creative-strategy-foundations/skills/analyzing/SKILL.md b/creative-strategy-foundations/skills/analyzing/SKILL.md
index 597fa2ec..f68c68d5 100644
--- a/creative-strategy-foundations/skills/analyzing/SKILL.md
+++ b/creative-strategy-foundations/skills/analyzing/SKILL.md
@@ -37,7 +37,7 @@ Use this skill to turn data, research, and creative review into decisions, not j
 - `/runneth/references/creative-strategy-engine.md` when the ask needs structural mapping across pain, desire, persona, angle, audience, or stage
 - `/runneth/references/creative-benchmarks.md` for benchmark interpretation and next-test logic
 - `/runneth/references/researching--review-mining.md` for customer-language extraction and review synthesis
-- `/runneth/references/design-system.md` only when the chosen deliverable is HTML or when you need a Web Awesome visual component or layout pattern
+- `/runneth/references/html-generation--design-system.md` only when the chosen deliverable is HTML or when you need a reusable visual component or layout pattern
 
 ### Match the depth to the ask
 
@@ -101,7 +101,7 @@ Open by reflecting what source material you actually used in natural language. F
 
 If the response is data-grounded, add a short "What mattered" block before the main analysis or deliverable. Keep it to 2 to 4 bullets. Separate validated data from inference when both appear.
 
-Every response that references specific ads must show them visually. For inline responses, use the active surface's visual presentation for the creatives in the same turn. For HTML artifacts, embed the creatives directly using the creative card pattern from `/runneth/references/components/creative-card.md`. For Markdown artifacts, keep the document readable first and place `motionUrl` links or compact supporting references directly beside the insight they support.
+Every response that references specific ads must show them visually. For inline responses, use the active surface's visual presentation for the creatives in the same turn. For HTML artifacts, embed the creatives directly using the Creative Cards pattern from `/runneth/references/html-generation--design-system.md`. For Markdown artifacts, keep the document readable first and place `motionUrl` links or compact supporting references directly beside the insight they support.
 
 Visual evidence rules:
 
diff --git a/creative-strategy-foundations/skills/briefing/SKILL.md b/creative-strategy-foundations/skills/briefing/SKILL.md
index 48612c54..074ab4e0 100644
--- a/creative-strategy-foundations/skills/briefing/SKILL.md
+++ b/creative-strategy-foundations/skills/briefing/SKILL.md
@@ -32,7 +32,7 @@ Use this skill to turn an approved or newly formed concept into a production-rea
 
 - `/runneth/references/hook-generation--standards.md` for hook quality and pressure checks
 - `/runneth/references/creative-strategy-engine.md` only when the brief needs audience, stage, or context adaptation or clearer strategic mapping
-- `/runneth/references/design-system.md` only when the output is HTML or the user needs a Web Awesome layout or reusable visual component pattern
+- `/runneth/references/html-generation--design-system.md` only when the output is HTML or the user needs a visual example layout or reusable visual component pattern
 
 ### Build missing concept elements inline
 
@@ -107,7 +107,7 @@ For execution-ready file outputs:
 - use HTML only when the user explicitly asks for HTML, or when the deliverable should be a page the user opens in the browser or be visually rich enough that Markdown is the wrong fit
 - use PDF only when the user explicitly asks for it, or when fixed-layout output is clearly the point
 
-Briefing owns the workflow; when the deliverable should be a browser-openable page, hand off rendering and serving to `app-builder`; when the user explicitly asked for standalone HTML source or a downloadable HTML file, hand off to `html-generation`. Do not skip the briefing workflow and jump straight to bare rendering.
+When HTML is the chosen format, briefing owns the workflow and then hands off to `html-generation` as the rendering layer. Do not skip straight to bare `html-generation`.
 
 Do not duplicate artifact content inline. Write a brief preamble, then reference the artifact.
 
diff --git a/package-index.json b/package-index.json
index 1d7b6440..78ea4bcc 100644
--- a/package-index.json
+++ b/package-index.json
@@ -6,7 +6,7 @@
       "id": "creative-strategy-foundations",
       "name": "Creative Strategy Foundations",
       "description": "Baseline Runneth creative strategy skills installed outside the protected Runneth volume.",
-      "version": "1",
+      "version": "2",
       "packageManagerVersion": 1,
       "categories": [
         "baseline"