@rubytech/create-maxy-code 0.1.106 → 0.1.108

package/payload/premium-plugins/venture-studio/PLUGIN.md

@@ -0,0 +1,79 @@
+---
+name: venture-studio
+description: "Founding-a-business agent. Drives an operator from raw idea to fundraise-ready deliverables: validated wedge, branded identity, prototyped product, structured data room, business plan, prospectus + term sheet, deck. Every artefact slots into a tracked Project + Task graph so nothing gets forgotten."
+requires:
+  - projects
+  - work
+metadata: {"platform":{"always":false,"embed":["admin"],"pluginKey":"venture-studio","optional":true,"recommended":true}}
+---
+
+# Venture Studio
+
+You are the founding-a-business agent. The operator has a business they want to start; your job is to take them from idea to a fundraise-ready pack — without losing track of any artefact along the way.
+
+## Operating principle: data-room first
+
+Every business this agent founds produces the same set of artefacts: a discovery design doc, a brand pack, a validated wedge with a landing page and PRD, a structured data room, a business plan, a prospectus, a term sheet, a deck. The operator does not have to remember any of this. The agent's job is to ensure every artefact has a tracked Task before any artefact is produced.
+
+Outcome (binding):
+
+- **Every artefact has a tracked Task** in a `Project` named for this business, before that artefact's skill is invoked.
+- **Section order is preserved.** Artefacts are produced in the data-room's section order (`01-narrative` → `02-corporate-legal` → ... → `10-supporting`), with the `html/<artefact>/` rendered outputs landing as the section's content matures.
+- **Nothing is forgotten.** The Project's Task list IS the operator's view of what is done, what is in flight, what is outstanding.
+
+Constraint (binding): **No downstream venture-studio skill (`brand-pack`, `zero-to-prototype`, `investor-data-room` Stages 3+, etc.) is invoked before the data-room scaffold + Project + per-artefact Tasks exist on disk and in the graph.** If the operator asks you to skip straight to a deliverable ("just write me a business plan"), restate the scaffold-first principle and offer to scaffold the data room first, then jump straight to that artefact's task. The principle is the outcome contract; the scaffold proves it.
+
+## First-conversation routing
+
+When the operator first invokes this agent, confirm the intent ("Are we founding a new business, or working on an existing one?") and run the scaffolding sequence:
+
+1. **Scaffold the data room.** Invoke the `investor-data-room` skill Stage 2 — it creates the ten-section graph under the operator's project root (`<project-site>/.docs/data-room/`). The tree is named upfront so every artefact has a slot to land in.
+2. **Create the `Project` node.** Use the `projects` plugin's `project-create` tool with tier `full` (data-room work is multi-phase). Project name is the business's working name; description references the data-room root path. The `project-create` call accepts a work-items list — pre-seed it with the artefact tasks below in one transaction.
+3. **Enumerate Tasks per artefact**, one per data-room section / output document, in section order. Suggested task list (the `project-create` tool accepts these as `workItems`):
+   - **Stage 1 — Office-hours design doc** → produces `01-narrative/office-hours-design.md` (skill: `office-hours`)
+   - **Brand pack** → produces brand identity files into `06-product-ip/brand/` (skill: `brand-pack`)
+   - **Stage 2 — Wedge validation + landing page + PRD** → produces `01-narrative/{PMF, LANDING, PRD}.md` (skill: `zero-to-prototype`)
+   - **Stage 3 — Business plan** → produces `01-narrative/business-plan.md` (skill: `investor-data-room` Stage 3)
+   - **Stage 3b — Term sheet** → produces `html/prospectus/term_sheet.html` (skill: `investor-data-room` Stage 3b)
+   - **Stage 4 — Deck blueprint** → produces `01-narrative/deck-blueprint.md` (skill: `investor-data-room` Stage 4)
+   - **Stage 4b — Prospectus** → produces `html/prospectus/index.html` (skill: `investor-data-room` Stage 4b)
+   - **Stage 5 — Rendered PDFs** → produces `html/{business-plan,prospectus,deck}/*.pdf` (skill: `investor-data-room` Stage 5)
+
+After these three steps land, the operator sees the project + task list before any skill produces output. Subsequent turns execute the tasks one at a time, calling the relevant venture-studio skill to produce that section's artefact.
+
+## Skill routing
+
+The following intent phrases route to specific skills. These calls are gated by the scaffold-first principle: refuse to fire any of them until the data-room scaffold + Project + Tasks exist.
+
+| Operator says | Skill |
+|---|---|
+| "I want to think this through" / "office hours" / "is this worth building" | `office-hours` |
+| "let's brand this" / "tokens for the brand" / "logo and palette" | `brand-pack` |
+| "validate this idea" / "let's find PMF" / "draft the landing page" / "write the PRD" | `zero-to-prototype` |
+| "build me a data room" / "scaffold the data room" | `investor-data-room` (Stage 2) |
+| "draft the business plan" | `investor-data-room` (Stage 3) |
+| "draft the term sheet" | `investor-data-room` (Stage 3b) |
+| "draft the deck blueprint" / "build the deck" | `investor-data-room` (Stage 4) |
+| "draft the prospectus" / "investment prospectus" | `investor-data-room` (Stage 4b) |
+| "render the PDFs" / "print-ready deliverables" | `investor-data-room` (Stage 5) |
+
+When the operator's intent matches a row but the scaffold does not yet exist, run the first-conversation routing sequence above before the skill fires.
+
+## Project & Task hygiene during execution
+
+- Before starting any artefact's task, mark its Task `in_progress` via the `work` plugin (or the `projects` plugin's helpers). When the artefact is on disk and verified, mark it `completed`.
+- If a section reveals a new artefact the operator wants (e.g. a competitor-claims-rebuttal in `08-market/`), `work-create` a new Task under the same Project, then proceed.
+- The Project's health signal (green/amber/red) is computed from Task state. Use `project-get` at the start of each turn to surface what's outstanding.
+
+## Tone
+
+Founder-facing. Direct, evidence-based, no flattery. You are the chief of staff for a one-person founding team — your job is to keep every artefact tracked and every deadline visible, while the operator focuses on the parts only they can do (customer conversations, founder signal, vision).
+
+## References
+
+The four skills shipped under this plugin carry their own SKILL.md detail:
+
+- `skills/office-hours/SKILL.md` — YC office-hours forcing questions in startup + builder modes; outputs the design-doc substrate every later artefact derives from.
+- `skills/brand-pack/SKILL.md` — brand identity (palette, typography, tone, logo) tokenised for the data-room artefacts to consume.
+- `skills/zero-to-prototype/SKILL.md` — 31 frameworks for customer discovery, validation, positioning, PMF measurement, landing page, PRD.
+- `skills/investor-data-room/SKILL.md` — full seed-raise pack: data room scaffold, business plan, term sheet, deck blueprint, prospectus, A4 print pipeline.

package/payload/premium-plugins/venture-studio/skills/brand-pack/SKILL.md

@@ -0,0 +1,256 @@
+---
+name: brand-pack
+description: Generate a complete, best-practice brand identity package from scratch. Use this skill whenever a user wants to create brand guidelines, a brand pack, brand identity, style guide, brand kit, tone of voice document, or any combination of branding assets for a new or existing business. Also trigger when a user mentions needing a logo guide, color palette, typography system, or messaging framework — even if they don't use the word "brand". This skill produces a comprehensive, professional-grade output structured around industry best practices.
+---
+
+# Brand Pack Generator
+
+Generates a complete brand identity package following industry best practice structure (based on Superside, Pentagram, and leading agency standards).
+
+## What This Skill Produces
+
+A full brand pack as a set of output files:
+
+1. `brand-guidelines.md` — Master brand guidelines document
+2. `brand-summary.md` — One-page brand summary (shareable with contractors/designers)
+3. `color-palette.md` — Full color system with hex, RGB, CMYK values
+4. `typography-system.md` — Font stack, hierarchy, and usage rules
+5. `tone-of-voice.md` — Voice, tone, messaging framework, and copy examples
+6. `logo-guidelines.md` — Logo usage rules, clear space, variations, misuse guide
+
+---
+
+## Step 1: Intake
+
+Before generating anything, gather the following. Ask all questions in a single message — do not drip-feed them one at a time.
+
+**Required inputs:**
+- Company/brand name
+- One-sentence description of what they do
+- Target audience (who are their customers?)
+- Industry/sector
+- 3-5 words that describe the brand personality (e.g. bold, trustworthy, playful)
+- Primary competitors (2-3 names if known)
+- Existing colors or logo? (yes/no — if yes, ask them to describe or share)
+- Preferred font style? (modern/clean, classic/serif, bold/impactful, or no preference)
+- Any colors to avoid?
+
+**Optional but useful:**
+- Website URL (fetch it if provided — extract existing colors, fonts, tone)
+- Inspiration brands (brands they admire aesthetically)
+
+If the user provides a URL, use the fetch tool to read it and extract: dominant colors (check CSS or visual description), font choices, tone of copy, and any existing brand signals. Pre-fill your recommendations based on this research.
+
+---
+
+## Step 2: Generate Color Palette
+
+Create a palette of 5-7 colors with rationale for each choice:
+
+**Structure:**
+- 1 Primary brand color (dominant, used most)
+- 1-2 Secondary colors (complement primary, used for accents/CTAs)
+- 1 Dark neutral (for body text, usually near-black)
+- 1 Light neutral (for backgrounds)
+- 1 Alert/accent color (optional, for highlights or warnings)
+
+**For each color provide:**
+- Name (e.g. "Midnight Navy")
+- Hex code
+- RGB values
+- CMYK values (for print)
+- Usage guidance (when/where to use it)
+- Accessibility note (contrast ratio against white/black — flag if WCAG AA fails)
+
+**Color psychology guidance by industry** (read `references/color-psychology.md` for full detail):
+- Fintech/finance: blues, deep greens, charcoal — trustworthy, stable
+- Health/wellness: greens, soft blues, warm whites — calm, clean
+- Tech/SaaS: bold blues, purples, sharp accents — innovative, confident
+- Creative/agency: varied, can be bolder — distinctive, expressive
+- Consumer/retail: depends on positioning — warm for approachable, cool for premium
+
+---
+
+## Step 3: Typography System
+
+Select a font stack with clear hierarchy:
+
+**Levels:**
+- Display/H1: Large headline font (personality, impact)
+- H2/H3: Section heading font (can be same family, different weight)
+- Body: Readable body font (readability is paramount)
+- UI/Caption: Small text, labels, captions
+- Accent: Optional — a contrasting typeface for pull quotes or callouts
+
+Read `references/typography-reference.md` for proven pairings, size scales, and font personality guidance before making recommendations.
+
+**Rules to follow:**
+- Recommend Google Fonts or Adobe Fonts (free/accessible)
+- Limit to 2 typeface families maximum
+- Provide pixel/pt sizes for each level (desktop and mobile)
+- Include line-height and letter-spacing recommendations
+- Note: serif for authority/tradition, sans-serif for modern/clean, mono for tech
+
+**Output format per font:**
+- Font name + weight
+- Use case
+- Size scale (H1 → caption)
+- Pairing rationale
+
+---
+
+## Step 4: Logo Guidelines
+
+Since this is a text-based brand pack (no actual logo file), produce a **Logo Usage Guide** that specifies:
+
+- Primary logo description and intended construction
+- Logo variants: horizontal, stacked, icon-only, wordmark-only
+- Clear space rule: minimum padding = height of the logo's capital letter on each side
+- Minimum size: 24px digital / 0.75 inch print
+- Approved color versions: full color, reversed (white on dark), single color black, single color white
+- Background rules: which backgrounds are approved
+- Misuse examples (describe, don't show): don't stretch, don't recolor outside palette, don't add drop shadows, don't place on busy backgrounds without clear space
+
+---
+
+## Step 5: Tone of Voice
+
+Structure this as a practical, usable guide — not abstract principles.
+
+**Sections:**
+
+### Brand Personality
+3-5 core personality traits, each with:
+- The trait
+- What it means in practice
+- What it is NOT (to prevent misinterpretation)
+
+### Voice (stable) vs Tone (variable)
+- Voice = how you always sound (consistent)
+- Tone = how you adapt for context (varies)
+
+### Tone by scenario
+Provide guidance for at least 4 scenarios:
+- Website homepage / hero copy
+- Social media
+- Customer support / error messages
+- Sales / outreach emails
+- (Add industry-specific ones as relevant)
+
+### Writing rules
+- Sentence length preference (short/punchy vs longer/considered)
+- Active vs passive voice
+- Use of jargon (avoid/embrace/explain)
+- Contractions? (formal vs informal)
+- Emoji? (never/occasionally/freely)
+- Oxford comma? (yes/no)
+
+### Copy examples
+For each tone scenario, provide 2 examples:
+- One that embodies the brand voice correctly
+- One that violates it (marked clearly as wrong)
+
+---
+
+## Step 6: Brand Guidelines Master Document
+
+Compile everything into `brand-guidelines.md` with this structure:
+
+```
+# [Brand Name] Brand Guidelines
+
+## 1. Brand Foundation
+- Mission
+- Vision  
+- Values (3-5)
+- Brand promise (one sentence)
+- Positioning statement
+
+## 2. Logo & Visual Identity
+- [Link/reference to logo-guidelines.md]
+- Summary of key rules
+
+## 3. Color Palette
+- [Link/reference to color-palette.md]
+- Primary usage rules
+
+## 4. Typography
+- [Link/reference to typography-system.md]
+- Key hierarchy summary
+
+## 5. Tone of Voice
+- [Link/reference to tone-of-voice.md]
+- Core voice traits (3 bullet points)
+
+## 6. Photography & Imagery Style
+- Subject matter guidance
+- Treatment/filters (clean/editorial/warm/cool)
+- Things to avoid
+
+## 7. Graphic Elements
+- Any patterns, textures, or shapes that extend the brand
+- Icon style (outlined/filled/rounded/sharp)
+- Illustration style if applicable
+
+## 8. Brand in Use
+- Website application notes
+- Social media application notes
+- Document/presentation notes
+- Business card guidance
+
+## 9. What Not To Do
+- 5-8 specific, concrete misuse examples
+```
+
+---
+
+## Step 7: Brand Summary (One-Pager)
+
+Create `brand-summary.md` — a concise reference card for designers, contractors, and team members:
+
+```
+# [Brand Name] — Brand Quick Reference
+
+**What we do:** [one sentence]
+**Who we serve:** [audience]
+**Our personality:** [3 words]
+
+## Colors
+| Name | Hex | Use |
+|------|-----|-----|
+| ... | ... | ... |
+
+## Fonts
+- Headlines: [Font, weight, size]
+- Body: [Font, weight, size]
+
+## Voice
+[3 bullet points]
+
+## Key rules
+- Always: ...
+- Never: ...
+```
+
+---
+
+## Output Instructions
+
+- Create all files in `/mnt/user-data/outputs/brand-pack/[brand-name]/`
+- Use clean markdown formatting throughout
+- Be specific — avoid vague guidance like "use professionally". Give concrete rules.
+- Where you make creative choices, briefly note the rationale
+- After creating all files, present them to the user with a brief summary of the key creative decisions made
+
+---
+
+## Quality Checklist
+
+Before finishing, verify:
+- [ ] Color palette has hex + RGB + CMYK for every color
+- [ ] Accessibility: at least primary text color passes WCAG AA on white background
+- [ ] Typography has sizes for all heading levels
+- [ ] Tone of voice has at least 4 scenario examples
+- [ ] Logo guidelines includes misuse section
+- [ ] Brand summary fits on one page
+- [ ] All files are consistent with each other (same colors, same voice)

package/payload/premium-plugins/venture-studio/skills/brand-pack/references/color-psychology.md

@@ -0,0 +1,118 @@
+# Color Psychology Reference
+
+## By Sector
+
+### Financial Services / Fintech
+- **Blues** (navy, royal, midnight): Trust, stability, authority, professionalism
+- **Deep greens**: Growth, money, prosperity
+- **Charcoal/dark greys**: Sophistication, premium, serious
+- **Gold/amber accents**: Premium, success, achievement
+- Avoid: Hot pinks, neons, overly playful palettes — undermine trust signals
+
+### Healthcare / Wellness
+- **Soft blues**: Calm, clean, clinical trust
+- **Greens** (sage, mint, forest): Health, nature, balance
+- **Warm whites / off-whites**: Clean, open, breathing room
+- **Warm neutrals**: Approachable, human, caring
+- Avoid: Heavy blacks, aggressive reds — create anxiety
+
+### Technology / SaaS
+- **Electric blues, purples**: Innovation, intelligence, forward-thinking
+- **Sharp accents** (electric green, cyan): Energy, speed, action
+- **Dark backgrounds** (dark navy, near-black): Premium, focused, modern
+- Gradient use common and acceptable
+- Avoid: Overly corporate greys alone — feel dated
+
+### Creative / Agency / Design
+- More latitude — can be bold, unexpected
+- Contrast-heavy palettes work well
+- Consider monochromatic with one bold accent
+- Can use black-heavy palettes for premium creative positioning
+
+### Consumer / Retail
+- **Warm tones** (terracotta, warm orange, coral): Approachable, energetic, fun
+- **Cool tones** (slate, cool grey, navy): Premium, considered, calm
+- **Bright primaries**: Accessible, friendly, value-focused
+- Match palette to price positioning: warm/bright = accessible, cool/muted = premium
+
+### Food & Beverage
+- **Reds and oranges**: Appetite stimulation, warmth, energy
+- **Greens**: Fresh, natural, healthy
+- **Browns/earth tones**: Artisanal, craft, natural
+- Avoid: Blues for food (natural appetite suppressant) unless deliberately clinical/tech-adjacent
+
+### Education
+- **Blues**: Knowledge, trust, calm
+- **Greens**: Growth, learning, development
+- **Bright accents**: Energy, curiosity, engagement
+- Depends heavily on age of audience — younger = brighter, older = more subdued
+
+---
+
+## Emotional Associations Quick Reference
+
+| Color | Primary associations | Secondary associations |
+|-------|---------------------|----------------------|
+| Red | Energy, urgency, passion | Danger, aggression |
+| Orange | Warmth, enthusiasm, creativity | Cheap (if overused) |
+| Yellow | Optimism, clarity, warmth | Caution, anxiety (bright) |
+| Green | Growth, health, nature | Money, envy |
+| Blue | Trust, calm, authority | Cold, corporate |
+| Purple | Premium, creativity, wisdom | Artificial, excessive |
+| Pink | Warmth, care, approachable | Gendered (use carefully) |
+| Black | Premium, power, elegance | Heavy, exclusionary |
+| White | Clean, simple, open | Empty, clinical |
+| Grey | Neutral, sophisticated | Boring, uncommitted |
+| Brown | Earthy, natural, reliable | Dull (if dominant) |
+| Gold | Premium, success, quality | Garish (if overused) |
+
+---
+
+## Accessibility Standards
+
+### WCAG AA Requirements (minimum for compliance)
+- Normal text (< 18pt): contrast ratio ≥ 4.5:1
+- Large text (≥ 18pt or 14pt bold): contrast ratio ≥ 3:1
+- UI components and graphics: contrast ratio ≥ 3:1
+
+### WCAG AAA (enhanced — aim for where possible)
+- Normal text: contrast ratio ≥ 7:1
+- Large text: contrast ratio ≥ 4.5:1
+
+### Quick contrast checks
+- Black (#000000) on white (#FFFFFF): 21:1 ✓
+- Dark navy (#1a2744) on white: ~14:1 ✓
+- Medium grey (#767676) on white: 4.54:1 ✓ (barely passes AA)
+- Light grey (#aaaaaa) on white: 2.32:1 ✗ (fails)
+- White on mid-blue (#0066cc): ~5.7:1 ✓
+
+**Always flag** if a proposed text/background combination fails WCAG AA.
+
+---
+
+## Color Combination Principles
+
+### Complementary (opposite on color wheel)
+- High contrast, vibrant, energetic
+- Use sparingly — can feel aggressive at full saturation
+- Works well: one dominant, one accent
+
+### Analogous (adjacent on color wheel)
+- Harmonious, cohesive, calm
+- Easy to live with, less dramatic
+- Good for brands wanting approachable, consistent feel
+
+### Triadic (three equally spaced)
+- Balanced but vibrant
+- Requires careful proportion (60/30/10 rule)
+- One dominant, one secondary, one accent
+
+### Monochromatic (single hue, varied lightness/saturation)
+- Sophisticated, focused, coherent
+- Easy to extend across materials
+- Add one contrasting accent to avoid monotony
+
+### 60/30/10 Rule
+- 60% primary/neutral colour (backgrounds, large areas)
+- 30% secondary colour (sections, supporting elements)
+- 10% accent colour (CTAs, highlights, key interactions)

package/payload/{platform/plugins/founder-pack → premium-plugins/venture-studio}/skills/investor-data-room/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: investor-data-room
-description: Use when a UK-domiciled founder needs to produce a full seed-raise pack from idea to deliverables: graph-structured data room, 15-section business plan, 12-slide deck blueprint, print-ready HTML+PDF for both. Trigger phrases include "build me a data room", "draft a business plan", "deck from the business plan", "print-ready PDF for the prospectus", "from office hours to investor pack", "set up the fundraise repo". The skill never speculates on financial figures or cap-table values: every number traces to a Companies House filing, a financial model worksheet, or a source citation. Public-facing artefacts contain zero internal workings (no "reconciliation pending", no "open Q" markers, no comparison-to-baseline commentary). Design tokens are harmonised across business plan, deck, and prospectus per `realagent-site/.docs/design-tokens.md`.
+description: Use when a UK-domiciled founder needs to produce a full seed-raise pack from idea to deliverables: graph-structured data room, 15-section business plan, persuasive prospectus + formal term sheet (with FCA self-certification appendices), 12-slide deck blueprint, print-ready HTML+PDF for each. Trigger phrases include "build me a data room", "draft a business plan", "deck from the business plan", "draft an investment prospectus", "generate a term sheet", "from office hours to investor pack", "set up the fundraise repo". The skill never speculates on financial figures or cap-table values: every number traces to a Companies House filing, a financial model worksheet, or a source citation. Public-facing artefacts contain zero internal workings (no "reconciliation pending", no "open Q" markers, no comparison-to-baseline commentary). Design tokens are harmonised across business plan, prospectus, term sheet, and deck via the operator's project design-tokens spec.
 allowed-tools:
   - Bash
   - Read
@@ -78,7 +78,7 @@ Skip stages that are already complete; do not regenerate stale artefacts blindly
 
 ## Stage 1 — Office-hours ideation
 
-Drive a conversational discovery session using the `/office-hours` skill (or equivalent YC-style forcing questions: demand reality, status quo, desperate specificity, narrowest wedge, observation, future-fit). Output a single `office-hours-design.md` capturing:
+Drive a conversational discovery session using the sibling `office-hours` skill. Output a single `office-hours-design.md` capturing:
 
 - Problem statement
 - Demand evidence (with numbers and dates)
@@ -158,7 +158,7 @@ Generate `html/prospectus/term_sheet.html` as an **A4 portrait, 10-page formal t
 
 **Doctrine for the term sheet:**
 
-- **Entity name is the IN01-filed name**, not a marketing entity. Issuer must read as the actual filed company (e.g. "Real Agent Network Limited" not "Real Agent Systems Ltd").
+- **Entity name is the IN01-filed name**, not a marketing entity. Issuer must read as the actual filed company (e.g. the name on the IN01 statement of capital, not the trading or marketing brand).
 - **Cap table matches the IN01 + Round 1 dilution model exactly.** Pre-investment shares + new investor Round Shares = post-investment total. No fractional shares; no rounding to the % column that breaks share totals.
 - **Founder list reads exactly as the cap table.** No phantom founders. Strategic shareholders (e.g. an investing LLP) ride in the cap table by entity name, not via their individuals.
 - **Sole director on IN01 is the director-designate.** A term sheet that names two directors when IN01 names one is a defect.
@@ -185,10 +185,110 @@ Generate `01-narrative/deck-blueprint.md` as a **12-slide brief** the deck desig
 11. Milestones (M0 to M-final timeline)
 12. Other Information (compliance + platform dependency + contact)
 
-Production notes attached: format (16:9 landscape, PDF + source deck), design tokens reference (`realagent-site/.docs/design-tokens.md` or project equivalent), chart-source consistency with the financial model, speaker-note attribution.
+Production notes attached: format (16:9 landscape, PDF + source deck), design tokens reference (the operator's project design-tokens spec, path supplied at Stage 5 invocation), chart-source consistency with the financial model, speaker-note attribution.
 
 References: `references/deck-blueprint-template.md`.
 
+## Stage 4b — Prospectus synthesis
+
+Generate `html/prospectus/index.html` as an **A4 portrait, 7-page persuasive prospectus** alongside the formal term sheet from Stage 3b. The prospectus is the narrative companion to the term sheet: cover + executive summary + architecture + go-to-market + platform asset + operating plan + use of funds / founders / team.
+
+The templates live under `templates/prospectus/`:
+
+```
+templates/prospectus/
+  index.html          # 7-page prospectus with {{ placeholders }}
+  term_sheet.html     # 8-page term sheet with {{ placeholders }} (shared with Stage 3b)
+  render-pdf.mjs      # image-only PDF renderer (shared with Stage 5)
+```
+
+**Intake — ask these before substituting any placeholder.** Group by section; wait for answers before drafting.
+
+*Company identity:*
+
+1. Legal name of the company (use "to be incorporated" if pre-IN01).
+2. Trading / brand name (topbar + body copy + signatures).
+3. Tagline / one-paragraph deck — what does the company do, who is it for, why is it different. ≤ 80 words.
+4. Brand icon — 22×22 px PNG/SVG mark. Save as `<brand>-icon.png` alongside the HTML.
+5. Cover hero image — landscape photograph, ≥ 2800 px on the long edge. Save as `hero.png` alongside the HTML.
+6. Document month / year (topbar meta, e.g. "May 2026").
+7. Document IDs — short refs for footers: prospectus (e.g. "ACME / FIN-001 / V1.0") and term sheet (e.g. "ACME / TS-001 / V1.0").
+
+*The round:*
+
+8. Round size, gross, £.
+9. Post-money valuation cap, £.
+10. Issue price per share, £. Confirm split between nominal value (typically £0.01) and share premium.
+11. Number of new Round Shares (= round size ÷ issue price).
+12. Founder shares retained at close — total and percentage (typically 80%).
+13. Total shares post-closing.
+14. Minimum cheque per investor, £.
+15. Minimum aggregate raise, £, below which the round does not proceed.
+16. Round close date and funds expected date (DD Month YYYY).
+17. Use-of-proceeds split — typically four buckets (product, GTM, infrastructure, working capital + legal) totalling 100%.
+
+*Founders and team:*
+
+18. Founders — for each: full name, role, share count, percentage. Mark full-time vs advisors.
+19. Director-designates at closing (at least one executive director).
+20. NED nomination right — confirm threshold (e.g. any investor ≥ 10% may nominate one NED, subject to founder approval not unreasonably withheld).
+21. Observer threshold (typically ≥ 5%).
+22. First product hires planned in Y1 — trigger conditions for each.
+
+*The thesis (narrative):*
+
+23. The market — size, growth rate, target customer cohort. Cite sources (ONS, industry reports, named studies).
+24. The opportunity / problem — what is currently broken or unmet.
+25. Value proposition — pricing, what the customer gets, why it beats alternatives.
+26. Architecture and differentiation — the structural moat. What does the company do that nobody else does? "AI" is not a moat; the moat is in *how* AI is applied.
+27. Wedge → beachhead → blitzscale — staged GTM. Wedge = narrow entry product. Beachhead = one decisively winnable segment funded by Round 1. Blitzscale = market expansion funded by Round 2.
+28. Distribution funnel — specific channels producing customers in months 1–6. Concrete: integrations, channels, named partners.
+29. Pilots / paying customers at close — name them, who runs them, what they're paying.
+
+*Financial model:*
+
+30. Opening cash post-close — founder subscription + this round proceeds, less any capex at M0.
+31. Capex at M0 — one-off hardware / set-up costs.
+32. Monthly burn by phase — M1–M2 (founders only), M3–M9 (with first hire), M10–M12 (with second hire). Per-line breakdown.
+33. MRR ramp — month-by-month MRR for M1–M12. Distinguish customer segments.
+34. Customer count and device count by month if hardware is part of the offering.
+35. Cash trajectory — month-by-month closing cash balance derived from (33) − burn. Identify cash low point and break-even month.
+36. Round 2 plan — size range, timing (which month), gating milestones, what it funds.
+
+*Operational / legal:*
+
+37. Founder IP assignment — who is assigning IP to the company at closing? Outright? Any licence-back?
+38. Conditions to closing — incorporation, IP assignment, DD, shareholders' agreement, cleared funds.
+39. Governing law — confirm "English law, Exclusive jurisdiction of England & Wales courts" or substitute.
+40. Long-form documentation timeline — within how many days of mutual signature will the subscription & shareholders' agreement and articles be circulated?
+
+If the operator cannot answer (28), (33–35), or (36), flag explicitly that the prospectus will be incomplete and ask for sensible base-case assumptions. The financial chart on the cover and the operating-plan section both depend on these numbers.
+
+**How to apply answers.**
+
+1. Copy `templates/prospectus/{index.html, term_sheet.html, render-pdf.mjs}` into `html/prospectus/`.
+2. Save the operator-supplied hero image as `hero.png` and brand icon as `<brand>-icon.png`.
+3. Replace **global atomic placeholders** in both HTML files (the templates already carry these): `{{ BRAND_NAME }}`, `{{ COMPANY_LEGAL_NAME }}`, `{{ BRAND_ICON }}`, `{{ HERO_IMAGE }}`, `{{ TERM_SHEET_HTML }}`, `{{ TERM_SHEET_PDF }}`, `{{ PROSPECTUS_PDF }}`, `{{ TERM_SHEET_DOC_ID }}`, `{{ PROSPECTUS_DOC_ID }}`, `{{ DOC_MONTH_YEAR }}`, `{{ ROUND_SIZE }}`, `{{ POST_MONEY_CAP }}`, `{{ ISSUE_PRICE }}`, `{{ NOMINAL_VALUE }}`, `{{ SHARE_PREMIUM }}`, `{{ ROUND_SHARES }}`, `{{ FOUNDER_SHARES }}`, `{{ TOTAL_SHARES_POST }}`, `{{ MIN_CHEQUE }}`, `{{ MIN_AGGREGATE }}`, `{{ ROUND_CLOSE_DATE }}`, `{{ FUNDS_EXPECTED_DATE }}`, `{{ NEW_INVESTOR_PCT }}`, `{{ FOUNDERS_PCT }}`.
+4. Replace **narrative blocks** in `index.html` paragraph-by-paragraph using the answers from sections (23)–(29) and (32)–(36). The placeholder narrative blocks are structural references, not content to keep.
+5. Replace **cap table rows** in `term_sheet.html` (`<tr>` inside `<div class="captable">`) with the operator's actual founder names, roles, share counts, percentages.
+6. Replace **signature block** in `term_sheet.html` with the director-designates.
+7. Replace **financial chart data** in `index.html`. The cover chart is hand-coded SVG — find the `<polyline points="...">` for the cash line, the `<rect>` MRR bars, and the burn step-lines, and recompute coordinates from the new financial model (each MRR bar's `y` = `290 - (mrr_k / 60) * 120`, height = `120 - y_offset`). If recomputation is non-trivial, ask the operator for the 12 monthly cash and MRR values directly.
+8. Update `<title>` and `<meta>` tags to reflect the new company.
+
+**Doctrine for the prospectus.**
+
+- **UK seed round only.** The templates encode UK FCA self-certification under FSMA 2000 (FPO) articles 48 (HNWI) and 50A (Self-certified Sophisticated Investor). Do not adapt for US, EU, or non-UK regimes without explicit operator instruction — the legal exemption text is jurisdiction-specific.
+- **SEIS/EIS is post-funding, not a closing contingency.** The templates state that SEIS/EIS advance assurance will be pursued *after* the round closes and is not a condition of subscription. Do not promote SEIS/EIS as assured before distribution — it is misleading and breaks the FCA exemption.
+- **Image-only PDF via Stage 5's `render-pdf.mjs`.** Same pipeline; the prospectus shares one renderer with the business plan and deck.
+- **A4 fit is enforced.** Every `<section class="page">` must have `scrollHeight ≤ 1123 px + 2 px slack`. The remedy on overflow is to split the section into two `<section class="page">` blocks — never to shrink fonts or pad less.
+- **Render to the same folder as the HTML.** The renderer reads relative asset paths (icon, hero image).
+
+**Verify before shipping.**
+
+1. Read every PNG in `.tmp-*/`. `pdfinfo` reporting "7 pages, A4" is not verification. Confirm: content fills the page, no whitespace gaps > 25 mm at the bottom, the cover hero looks right, the chart values match the model, founder names are spelled correctly, the cap table totals to 100%.
+2. Hero image resolution floor: 2800 px on the long edge. Below that the cover prints soft.
+3. The two FCA self-cert pages render cleanly — HNWI (FPO art. 48) and Sophisticated (FPO art. 50A). These are legally prescribed text; do not edit their wording without lawyer sign-off.
+
 ## Stage 5 — HTML + PDF render pipeline
 
 For each artefact that ships as a print-ready PDF (business plan, prospectus, deck), produce three files under `html/<artefact>/`:
@@ -199,7 +299,7 @@ render-pdf.mjs    # Playwright + img2pdf + qpdf pipeline (image-only PDF, linear
 <artefact>.pdf    # rendered output (regenerate after every HTML edit)
 ```
 
-**Hard constraints** (from the `property-brochure:a4-print-documents` skill):
+**Hard constraints (A4 portrait, image-only PDF):**
 
 - A4 portrait: `@page { size: A4 portrait; margin: 18mm 16mm 20mm; }`
 - One `<section class="page">` per A4 page; renderer aborts if `scrollHeight` exceeds 1123px + 2px slack.
@@ -250,9 +350,10 @@ References: `references/html-pdf-pipeline.md` for the canonical `render-pdf.mjs`
 - `references/html-pdf-pipeline.md` — render-pdf.mjs canonical source + CSS scaffold
 - `references/compliance-research-checklist.md` — UK + EU regulatory regimes to verify
 - `references/internal-workings-scrub.md` — the public-vs-internal doctrine, patterns to scrub, recurrence list
-- `references/design-tokens-application.md` — how to consume `realagent-site/.docs/design-tokens.md` from an artefact's `:root` block
+- `references/design-tokens-application.md` — how to consume the operator's project design-tokens spec from an artefact's `:root` block
 - `references/termsheet-template.md` — A4-portrait term-sheet structure, cap-table reconciliation, common defects
+- `templates/prospectus/` — A4-portrait prospectus + term-sheet HTML templates and the shared `render-pdf.mjs` (consumed by Stages 3b, 4b, 5)
 
-## Reference project
+## Reference example
 
-The first execution of this skill produced `realagent-site/.docs/data-room/` for Real Agent Network Limited (Companies House 17237239). Read that directory as the canonical example; the skill's job is to reproduce its structure and doctrine for any subsequent UK seed raise.
+When this skill has previously rendered a data room for the current operator, that directory is the canonical example — read it before drafting. When no prior data room exists for the operator, the fallback reference is `references/data-room-structure.md` (section-by-section purpose statements) plus the per-stage references listed above.

package/payload/premium-plugins/{founder-pack → venture-studio}/skills/investor-data-room/references/html-pdf-pipeline.md

@@ -1,6 +1,6 @@
 # HTML + PDF render pipeline
 
-Image-only A4 portrait PDF, rendered from a single HTML file via Playwright + img2pdf + qpdf. Mirrors the constraints in the `property-brochure:a4-print-documents` skill.
+Image-only A4 portrait PDF, rendered from a single HTML file via Playwright + img2pdf + qpdf. Constraints inlined in the parent `SKILL.md` Stage 5.
 
 ## File layout per artefact
 

package/payload/{platform/plugins/founder-pack → premium-plugins/venture-studio}/skills/investor-data-room/references/termsheet-template.md

@@ -45,7 +45,7 @@ Issue price = pre-money / pre-investment shares = £1,400,000 / 500,000 = **£2.
 
 ## Doctrine
 
-- **Issuer name is the IN01-filed legal entity.** Stale term sheets that reference a marketing entity (e.g. "Real Agent Systems Ltd" instead of the filed "Real Agent Network Limited") are defects. The Companies House number on every page header should match.
+- **Issuer name is the IN01-filed legal entity.** Stale term sheets that reference a marketing or trading entity instead of the filed company are defects. The Companies House number on every page header should match the IN01.
 - **Founder list reads exactly as the cap table.** Six holders on the cap table = six in the founder list. No phantom founders. Strategic shareholders (e.g. an investing LLP) ride in by entity name, not by their constituent individuals.
 - **Sole director on IN01 is the director-designate on the term sheet's signature page.** A term sheet that names two directors when IN01 named one needs reconciling before issue.
 - **SEIS/EIS posture is post-funding obligation, never closing contingency.** Never assured prior to distribution; no representation as to qualifying status. Forms no part of consideration.