@rubytech/create-maxy-code 0.1.106 → 0.1.108

package/dist/index.js

@@ -59,7 +59,7 @@ function claudePluginEnv() {
  *  evidence. When a third brand is added under `brands/`, append its hostname
  *  here AND in the matching constant in `uninstall.ts` (intentional duplication
  *  per `uninstall.ts:` "Shell helpers (duplicated from index.ts ...)" policy). */
-const KNOWN_BRAND_HOSTNAMES = ["maxy", "realagent", "maxy-2", "maxy-3", "maxy-4"];
+const KNOWN_BRAND_HOSTNAMES = ["maxy", "maxy-code", "realagent", "realagent-code", "maxy-2", "maxy-3", "maxy-4"];
 // The device's actual hostname — may differ from BRAND.hostname if the user customized it.
 // Updated by installSystemDeps() after hostname setup; used for user-facing URLs.
 let DEVICE_HOSTNAME = BRAND.hostname;

package/dist/uninstall.js

@@ -103,7 +103,7 @@ export function isMaxyInstalled() {
  *  `.service` file — stale units, gnome-keyring disable markers, and unrelated
  *  user services are not peer evidence. When a third brand is
  *  added under `brands/`, append its hostname here. */
-const KNOWN_BRAND_HOSTNAMES = ["maxy", "realagent", "maxy-2", "maxy-3", "maxy-4"];
+const KNOWN_BRAND_HOSTNAMES = ["maxy", "maxy-code", "realagent", "realagent-code", "maxy-2", "maxy-3", "maxy-4"];
 /** Detect whether another brand is installed on this device.
  *  device-wide steps (apt package purge, Ollama binary removal, apt
  *  repo cleanup, ~/.claude / ~/.ollama wipes) must skip when a peer brand is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy-code",
-  "version": "0.1.106",
+  "version": "0.1.108",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy-code": "./dist/index.js"

package/payload/platform/config/brand.json

@@ -16,6 +16,7 @@
   "claudeSessionManagerPort": 19400,
   "commercialMode": false,
   "vertical": null,
+  "shipsPremiumBundles": ["venture-studio"],
 
   "defaultColors": {
     "primary": "#7C8C72",

package/payload/platform/plugins/.claude-plugin/marketplace.json

@@ -39,11 +39,6 @@
       "source": "./email",
       "version": "0.1.0"
     },
-    {
-      "name": "founder-pack",
-      "source": "./founder-pack",
-      "version": "0.1.0"
-    },
     {
       "name": "linkedin-extension",
       "source": "./linkedin-extension",
@@ -85,13 +80,13 @@
       "version": "0.1.0"
     },
     {
-      "name": "teaching",
-      "source": "./teaching",
+      "name": "telegram",
+      "source": "./telegram",
       "version": "0.1.0"
     },
     {
-      "name": "telegram",
-      "source": "./telegram",
+      "name": "venture-studio",
+      "source": "./venture-studio",
       "version": "0.1.0"
     },
     {
@@ -113,11 +108,6 @@
       "name": "workflows",
       "source": "./workflows",
       "version": "0.1.0"
-    },
-    {
-      "name": "writer-craft",
-      "source": "./writer-craft",
-      "version": "0.1.0"
     }
   ]
 }

package/payload/platform/plugins/business-assistant/PLUGIN.md

@@ -43,7 +43,10 @@ When the owner asks about sessions, tasks, or what's in progress — use `sessio
 
 ## Industry Overlays
 
-Load industry-specific references from `overlays/` based on the business type in memory. If no industry is set, ask during the first conversation.
+When the first conversation starts, branch on whether this is a new or existing business:
+
+- **New business** ("I want to start a business", "I have an idea for a venture", "let's found a company") → invoke the `venture-studio` agent via the Skill tool. Venture-studio owns the founding-a-business workflow (data-room scaffold, Project + Tasks, brand pack, PMF validation, business plan, prospectus, term sheet, deck). Hand off and do not continue the industry-overlay flow.
+- **Existing business** → load industry-specific references from `overlays/` based on the business type in memory. If no industry is set, ask now.
 
 ## References
 

package/payload/platform/plugins/docs/references/plugins-guide.md

@@ -68,13 +68,20 @@ Install verbatim:
 
 ### Premium Plugins
 
-Brand decides which premium plugins ship. Maxy installs ship only `platform/plugins/*`. Real Agent installs ship every plugin under `platform/plugins/*` plus every bundle under `premium-plugins/*`. There is no per-account purchase record; brand identity is the gate.
+Brand decides which premium plugins ship. The brand's `shipsPremiumBundles` field in `brand.json` is the gate; three shapes are supported:
+
+- **omitted / false** — ship nothing from `premium-plugins/` (the legacy Maxy default).
+- **`true`** — ship every bundle under `premium-plugins/*` (Real Agent / `realagent-code`).
+- **`["bundle-a", "bundle-b"]`** — ship only the named bundle directories (Maxy Code's `["venture-studio"]`). Names with no matching directory on disk are silently dropped; non-allowlisted bundles are stripped from any account that was previously stamped with them.
+
+There is no per-account purchase record; the brand decides the shipping set.
 
 | Plugin | Type | What it does | Public agent |
 |--------|------|-------------|-------------|
 | `teaching` | Skills | Interactive tutoring, lesson planning, and study pack generation from your knowledge base | Yes — all 3 skills serve students and parents |
 | `real-agent` | Bundle (13 sub-plugins) | UK estate agency skills — sales, listings, vendor management, buyer management, lead generation, coaching, business operations, teaching, Loop CRM (five value pillars: auto-respond, viewing lifecycle, pipeline mining, listings prospecting, maintenance & preferences), PropertyData market analytics (valuation, sold prices, £/sqft baselines, £/sqft growth, demand-rent, area risk, planning precedent, UPRN matching, property-type distribution), gov.uk EPC floor-area lookup, property brochures, social-share image cards, A4 market reports, and single-address preval packs (full UK address → 4-page A4 PDF covering valuation, area, and demand). 3 specialist roles (negotiator, valuer, compliance) | 4 sub-plugins (estate-sales, buyers, estate-coaching, estate-teaching) |
 | `writer-craft` | Skills + Agent | Manuscript review and writing craft — story architecture, reader engagement, prose craft, editorial practice, and multi-level review | No — writing craft serves the author |
+| `venture-studio` | Skills + Agent | Founding-a-business workflow — office-hours discovery, brand pack, zero-to-prototype validation, and the full investor data room (business plan, prospectus, term sheet, deck blueprint, A4 print pipeline). Pre-seeds a `Project` with one `Task` per artefact so nothing gets forgotten. | No — founder-facing only |
 
 **How it works:** Every boot {{productName}} delivers the brand's premium plugins from staging into `platform/plugins/` and stamps `enabledPlugins` against what is actually on disk. No conversation needed — the brand's full set is active from the first turn after install. Updates and reinstalls re-deliver from staging.
 

package/payload/platform/plugins/venture-studio/.claude-plugin/plugin.json

@@ -0,0 +1,8 @@
+{
+  "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.",
+  "version": "0.1.0",
+  "author": {
+    "name": "Rubytech LLC"
+  }
+}

package/payload/platform/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/platform/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/platform/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)