docs(web-bundles): rewrite copy to actually sell what each bundle does

The JSON drives the bmadcode.com/web-bundles/ page; previous copy
was generic and undersold the actual capabilities. Rewrote each
tagline + description to lead with concrete, differentiating facts
pulled directly from each bundle's SKILL.md:

- Brainstorming Coach: 60 techniques across 10 categories with
  specific names (SCAMPER, Drunk History Retelling, Nature's
  Solutions, Shadow Work Mining, Superposition Collapse); calls
  out the 4 routes (browse, recommend, random, progressive) and
  the ~100-idea quantity-unlocks-quality target.
- Product Brief Coach: names the three intent modes (Create /
  Update / Validate) and the two working paths (Fast / Coaching);
  surfaces the [ASSUMPTION] tag system and the Addendum.
- PRFAQ Coach: details the 4 stages (Ignition / Press Release /
  Customer FAQ / Internal FAQ + Verdict), the 9 press release
  sections, the weasel-word list ("best-in-class", "seamless"),
  and that it adapts for commercial, internal, OSS, community.
- PRD Coach: spells out the two entry points (Vision+Features
  vs Journey-led), named-protagonist journeys, glossary
  discipline, stable ID system (FR-1..N, SM-C1..N), and the
  7-dimension validation rubric.
- UX Coach: leads with the two-spine contract (DESIGN.md +
  EXPERIENCE.md), Don Norman framing, named-protagonist
  journeys, surface closure as the test, and Stitch integration.
- Market & Industry Research: leads with Deep Research as the
  engine, names Porter and Christensen as anchors, lists the 6
  deliverable sections, and frames the deliverable as synthesis
  not a research dump.

web-bundles/bundles.json

@@ -6,8 +6,8 @@
     {
       "slug": "brainstorming-coach",
       "name": "Brainstorming Coach",
-      "tagline": "60 ideation techniques across 10 categories — structured, wild, biomimetic, theatrical, and more",
-      "description": "Sixty proven brainstorming techniques spanning structured frameworks (SCAMPER, Five Whys, First Principles), wild plays (Drunk History Retelling, Zombie Apocalypse Planning), biomimetic prompts (Nature's Solutions), theatrical methods (Six Thinking Hats, Role Playing), introspective work (Shadow Work Mining, Values Archaeology), and quantum-flavored framings (Superposition Collapse, Observer Effect). The coach picks the right one for your problem and walks you through it.",
+      "tagline": "60 ideation techniques across 10 categories — from SCAMPER to Zombie Apocalypse Planning",
+      "description": "Sixty proven brainstorming techniques spanning structured frameworks (SCAMPER, Five Whys, First Principles), wild plays (Drunk History Retelling, Zombie Apocalypse Planning), biomimetic prompts (Nature's Solutions), introspective work (Shadow Work Mining, Values Archaeology), and quantum-flavored framings (Superposition Collapse). Pick a route — browse the library, get a recommendation, take a random surprise, or run a progressive divergence-to-action flow. The coach asks; you generate every idea. Targets ~100 ideas before organizing (the breakthroughs live past idea 20), then promotes the session into themes, a 2×2 prioritization, and a breakthrough collage in Canvas.",
       "defaultPersona": {
         "name": "Carson",
         "title": "Elite Brainstorming Specialist",
@@ -28,8 +28,8 @@
     {
       "slug": "product-brief-coach",
       "name": "Product Brief Coach",
-      "tagline": "Shape, evolve, or pressure-test a product brief through guided discovery",
-      "description": "Shape a raw idea, evolve an existing brief, or pressure-test a draft before it goes downstream. Brief length is whatever the product earns — focused for early-stage, longer for complex products. The coach mirrors before pushing, names the assumption hiding under your confident sentence, and refuses to write the brief for you.",
+      "tagline": "Three modes (Create / Update / Validate), two paths (Fast / Coaching), one brief you're proud of",
+      "description": "Create a brief drawn out through real conversation. Update an existing brief against a change signal. Or Validate — honest critique against the brief's own purpose. Two working modes: Fast path batches the gaps into one or two consolidated questions and tags assumptions for you to fix in review (best for pitching tomorrow); Coaching path walks section by section, mirrors before pushing, names the assumption hiding under your confident sentence (best for the brief you want to be proud of). The coach refuses to invent moats, traction, or differentiation you didn't give it. Depth that doesn't fit the brief lands in an Addendum so nothing valuable gets lost. Length is whatever the product earns.",
       "defaultPersona": {
         "name": "Mary",
         "title": "Strategic Business Analyst",
@@ -50,8 +50,8 @@
     {
       "slug": "prfaq-coach",
       "name": "PRFAQ Coach",
-      "tagline": "Working Backwards challenge to forge product concepts",
-      "description": "Write the press release first. Stress-test a product concept against the customer who will actually buy it, before any building begins. Customer-first by force of method.",
+      "tagline": "Amazon's Working Backwards as a forcing function — write the press release before you build",
+      "description": "Four stages of customer-first pressure: Ignition (specific customer, concrete problem, real stakes), Press Release (9 sections, each forcing a different clarity — headline, problem paragraph, solution paragraph, leader quote, customer quote, getting started), Customer FAQ (validate the value proposition from outside in), and Internal FAQ + Verdict (feasibility, trade-offs, what survived). Hardcore mode: weasel words like 'best-in-class', 'seamless', and 'revolutionary' get challenged on sight; if you lead with technology, the coach redirects to the customer's actual problem. Generates a hero image for the press release. Works for commercial products, internal tools, open source, and community initiatives — the structure stays, the language adapts.",
       "defaultPersona": {
         "name": "Mary",
         "title": "Strategic Business Analyst",
@@ -72,8 +72,8 @@
     {
       "slug": "prd-coach",
       "name": "PRD Coach",
-      "tagline": "Product Requirements with built-in validation",
-      "description": "Coach a PRD that engineering can actually build from. Capabilities go in the PRD, mechanism in the Addendum. Validation pass surfaces the gap between what you said and what you meant.",
+      "tagline": "PRD coaching with built-in validation — capabilities in the PRD, mechanism in the Addendum",
+      "description": "Three modes (Create / Update / Validate), two entry points (Vision + Features for enterprise and dev products, Journey-led for consumer and UX-heavy products). Captures named-protagonist user journeys ('Mary, mom of three, kids finally asleep') instead of abstract personas. Enforces glossary discipline: every domain noun defined once, used verbatim across FRs, UJs, and SMs. Maintains stable IDs (FR-1..N globally, success metrics paired with counter-metrics SM-C1..N). The 7-dimension validation rubric grades decision-readiness, substance over theater, strategic coherence, done-ness clarity, scope honesty, downstream usability, and shape fit, with each finding cited to a specific PRD location. Length scales with stakes — hobby PRDs hit two pages; launch PRDs run as long as the FRs require.",
       "defaultPersona": {
         "name": "John",
         "title": "Product Manager",
@@ -94,8 +94,8 @@
     {
       "slug": "ux-coach",
       "name": "UX Coach",
-      "tagline": "UX patterns, flows, and design specifications",
-      "description": "Build spines engineering can take and ship. Pressure-test hierarchy, behavior, and visual logic. Hand-off-ready specs with optional Stitch integration for editable mockups.",
+      "tagline": "Two spines engineering can build from — DESIGN.md + EXPERIENCE.md as the contract",
+      "description": "Don Norman's human-centered design as the operating method. The coach elicits your vision and never imposes its own — no colors, fonts, or layouts you didn't put on the table. Captures named-protagonist journeys ('Mary on her couch after the kids are asleep') as the unit of design thinking. Produces two spines: DESIGN.md for visual identity (tokens in YAML frontmatter), EXPERIENCE.md for information architecture, behavior, states, and accessibility. Spines win on conflict with any mock, wireframe, or Stitch output. Surface closure is the test: every stated need has a surface, every surface has a journey. Pairs with Google Stitch — the handoff produces a Stitch prompt you copy straight from Canvas to generate editable mockups.",
       "defaultPersona": {
         "name": "Sally",
         "title": "UX Designer",
@@ -116,8 +116,8 @@
     {
       "slug": "market-and-industry-research",
       "name": "Market & Industry Research",
-      "tagline": "Competitive landscape, JTBD, segments — Deep Research integrated",
-      "description": "Market research that drives a positioning decision, not a deliverable. Segments, competitive alternatives, regulatory and technical lenses. Uses Deep Research for the heavy lift.",
+      "tagline": "Deep Research wrapped in a sharp brief — research as input to a decision, not a deliverable",
+      "description": "Built around platform Deep Research mode. The coach handles the conversation: scopes what you actually need, drafts a sharp Deep Research brief you copy directly into Gemini or ChatGPT, then ingests the report and shapes the deliverable around your decision or learning goal. Methodology anchors when they help: Michael Porter for competitive structure, Clayton Christensen for Jobs-to-be-Done. Six sections to mix and match — market dynamics, customer insights, competitive landscape, regulatory & compliance, technical & technology trends, strategic synthesis. Validates every numeric, regulatory, or competitive claim against a source and a date. Generic findings ('the market is growing') get pushed back to specifics ('which segment, what rate, citing whom'). The deliverable is the synthesis against your decision, not the research dump.",
       "defaultPersona": {
         "name": "Mary",
         "title": "Strategic Business Analyst",