@rubytech/create-maxy-code 0.1.107 → 0.1.109

package/payload/platform/plugins/work/mcp/dist/cli/project-create-cli.js

@@ -0,0 +1,78 @@
+// CLI bridge for shell scripts that need to scaffold a Project + Tasks
+// atomically (e.g. premium-plugins/venture-studio/bin/scaffold.sh). The
+// scaffold script is the deterministic enforcement layer for the
+// venture-studio scaffold-first principle (see Task 286 +
+// feedback_doctrine_paragraph_is_not_a_gate); to remain deterministic it
+// must invoke a single binary, not narrate intent for the LLM. This CLI
+// is that binary.
+//
+// Contract:
+//   node project-create-cli.js '<json-payload>'
+//   payload: { accountId, name, description, tier, workItems[], createdBy }
+//   exit 0 + stdout JSON { projectId, existing: boolean } on success
+//   exit non-zero + literal stderr message on any failure
+//
+// Idempotency guard lives here, NOT in projectCreate(). projectCreate()
+// always mints a fresh UUID — modifying it to MERGE on (accountId, name)
+// would change semantics for every existing caller. The CLI runs a
+// pre-check MATCH on (accountId, name); if a Project exists, it returns
+// the existing projectId with existing=true and skips the write. This
+// makes the scaffold script safely re-runnable after a partial failure
+// (e.g. graph write succeeds but mkdir fails — second run finds the
+// Project and only retries mkdir).
+import { projectCreate } from "../tools/project-create.js";
+import { getDriver } from "../lib/neo4j.js";
+async function findExistingProject(accountId, name) {
+    const driver = getDriver();
+    const session = driver.session();
+    try {
+        const result = await session.run(`MATCH (p:Project {accountId: $accountId, name: $name})
+       RETURN p.taskId AS projectId LIMIT 1`, { accountId, name });
+        if (result.records.length === 0)
+            return null;
+        return result.records[0].get("projectId");
+    }
+    finally {
+        await session.close();
+    }
+}
+async function main() {
+    const raw = process.argv[2];
+    if (!raw) {
+        process.stderr.write("project-create-cli: missing JSON payload argument\n");
+        process.exit(2);
+    }
+    let payload;
+    try {
+        payload = JSON.parse(raw);
+    }
+    catch (err) {
+        process.stderr.write(`project-create-cli: malformed JSON payload: ${err.message}\n`);
+        process.exit(2);
+    }
+    if (!payload.accountId || !payload.name) {
+        process.stderr.write("project-create-cli: payload missing required field (accountId, name)\n");
+        process.exit(2);
+    }
+    const createdBy = payload.createdBy ?? {
+        tool: "project-create-cli",
+        source: "scaffold-script",
+    };
+    const existing = await findExistingProject(payload.accountId, payload.name);
+    if (existing) {
+        process.stdout.write(JSON.stringify({ projectId: existing, existing: true }) + "\n");
+        return;
+    }
+    const result = await projectCreate({
+        ...payload,
+        createdBy,
+    });
+    process.stdout.write(JSON.stringify({ projectId: result.projectId, existing: false, childTaskIds: result.childTaskIds }) + "\n");
+}
+main()
+    .then(() => process.exit(0))
+    .catch((err) => {
+    process.stderr.write(`project-create-cli: ${err.message}\n`);
+    process.exit(1);
+});
+//# sourceMappingURL=project-create-cli.js.map

package/payload/platform/plugins/work/mcp/dist/cli/project-create-cli.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"project-create-cli.js","sourceRoot":"","sources":["../../src/cli/project-create-cli.ts"],"names":[],"mappings":"AAAA,uEAAuE;AACvE,wEAAwE;AACxE,iEAAiE;AACjE,0DAA0D;AAC1D,yEAAyE;AACzE,wEAAwE;AACxE,kBAAkB;AAClB,EAAE;AACF,YAAY;AACZ,gDAAgD;AAChD,4EAA4E;AAC5E,qEAAqE;AACrE,0DAA0D;AAC1D,EAAE;AACF,wEAAwE;AACxE,yEAAyE;AACzE,mEAAmE;AACnE,wEAAwE;AACxE,sEAAsE;AACtE,uEAAuE;AACvE,oEAAoE;AACpE,mCAAmC;AAEnC,OAAO,EAAE,aAAa,EAA4B,MAAM,4BAA4B,CAAC;AACrF,OAAO,EAAE,SAAS,EAAE,MAAM,iBAAiB,CAAC;AAM5C,KAAK,UAAU,mBAAmB,CAChC,SAAiB,EACjB,IAAY;IAEZ,MAAM,MAAM,GAAG,SAAS,EAAE,CAAC;IAC3B,MAAM,OAAO,GAAG,MAAM,CAAC,OAAO,EAAE,CAAC;IACjC,IAAI,CAAC;QACH,MAAM,MAAM,GAAG,MAAM,OAAO,CAAC,GAAG,CAC9B;4CACsC,EACtC,EAAE,SAAS,EAAE,IAAI,EAAE,CACpB,CAAC;QACF,IAAI,MAAM,CAAC,OAAO,CAAC,MAAM,KAAK,CAAC;YAAE,OAAO,IAAI,CAAC;QAC7C,OAAO,MAAM,CAAC,OAAO,CAAC,CAAC,CAAC,CAAC,GAAG,CAAC,WAAW,CAAW,CAAC;IACtD,CAAC;YAAS,CAAC;QACT,MAAM,OAAO,CAAC,KAAK,EAAE,CAAC;IACxB,CAAC;AACH,CAAC;AAED,KAAK,UAAU,IAAI;IACjB,MAAM,GAAG,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAC5B,IAAI,CAAC,GAAG,EAAE,CAAC;QACT,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,qDAAqD,CAAC,CAAC;QAC5E,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;IAED,IAAI,OAAmB,CAAC;IACxB,IAAI,CAAC;QACH,OAAO,GAAG,IAAI,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC;IAC5B,CAAC;IAAC,OAAO,GAAG,EAAE,CAAC;QACb,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,+CAAgD,GAAa,CAAC,OAAO,IAAI,CAAC,CAAC;QAChG,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;IAED,IAAI,CAAC,OAAO,CAAC,SAAS,IAAI,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC;QACxC,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,wEAAwE,CAAC,CAAC;QAC/F,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IAClB,CAAC;IAED,MAAM,SAAS,GAAG,OAAO,CAAC,SAAS,IAAI;QACrC,IAAI,EAAE,oBAAoB;QAC1B,MAAM,EAAE,iBAAiB;KAC1B,CAAC;IAEF,MAAM,QAAQ,GAAG,MAAM,mBAAmB,CAAC,OAAO,CAAC,SAAS,EAAE,OAAO,CAAC,IAAI,CAAC,CAAC;IAC5E,IAAI,QAAQ,EAAE,CAAC;QACb,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,SAAS,CAAC,EAAE,SAAS,EAAE,QAAQ,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC,GAAG,IAAI,CAAC,CAAC;QACrF,OAAO;IACT,CAAC;IAED,MAAM,MAAM,GAAG,MAAM,aAAa,CAAC;QACjC,GAAG,OAAO;QACV,SAAS;KACa,CAAC,CAAC;IAE1B,OAAO,CAAC,MAAM,CAAC,KAAK,CAClB,IAAI,CAAC,SAAS,CAAC,EAAE,SAAS,EAAE,MAAM,CAAC,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE,YAAY,EAAE,MAAM,CAAC,YAAY,EAAE,CAAC,GAAG,IAAI,CAC3G,CAAC;AACJ,CAAC;AAED,IAAI,EAAE;KACH,IAAI,CAAC,GAAG,EAAE,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;KAC3B,KAAK,CAAC,CAAC,GAAU,EAAE,EAAE;IACpB,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,uBAAuB,GAAG,CAAC,OAAO,IAAI,CAAC,CAAC;IAC7D,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AAClB,CAAC,CAAC,CAAC"}

package/payload/platform/scripts/vnc.sh

@@ -323,9 +323,10 @@ start_chrome() {
 }
 
 # ---------------------------------------------------------------------------
-# retired the admin-UI terminal surface entirely: the header
-# TerminalOverlay + UpdateModal embedded terminal stack is gone. Only
-# the Chromium surface remains for BrowserOverlay.
+# Retired in Task 287: the admin-UI terminal and browser-overlay surfaces
+# are gone. This script still launches Chromium for legacy installs where
+# the brand VNC is used for ad-hoc operator browsing; on maxy-code the
+# admin chat PTY is the only interactive surface.
 # ---------------------------------------------------------------------------
 
 start_chrome_native() {

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

@@ -5,13 +5,13 @@
   },
   "plugins": [
     {
-      "name": "founder-pack",
-      "source": "./founder-pack",
+      "name": "teaching",
+      "source": "./teaching",
       "version": "0.1.0"
     },
     {
-      "name": "teaching",
-      "source": "./teaching",
+      "name": "venture-studio",
+      "source": "./venture-studio",
       "version": "0.1.0"
     },
     {

package/payload/premium-plugins/real-agent/plugins/brochures/skills/property-brochure/references/build.md

@@ -13,11 +13,10 @@
 8. Verify every page fits A4: measure `scrollHeight` for all `.page` elements
 9. Verify no 404s in the browser console
 10. Repeat 6–9 until user approves the final copy
-11. **Preview manifest gate** — render `<property_dir>/output/.review/` thumbnails (per-page PNGs at 1× DPR) plus `<property_dir>/output/.review/manifest.json` capturing the active register, computed `--paper-25 / --serif / --gold-700 / --ink` token values, risk probes for `.mi-row .v` / `.folio em` / `.opener-title`, and which always-emit blocks were emitted (`DARK_SURFACE_PROTECTION`, `LIGHT_SURFACE_DATA_PROTECTION`, `STRUCTURAL_CLAMP_LOOSEN`). Halt and wait until the operator writes `<property_dir>/output/.review/approved`. The interactive form of the same gate is the browser-review loop in steps 6–10; this file-based halt is the structural form that scripted or autonomous runs cannot bypass — the build refuses to advance until `approved` exists.
-12. **Only after `approved` exists**: render snapshots (two passes — 300 dpi to `output/`, 192 dpi to `output/.snapshots-web/`) per **Print snapshot capture** below
-13. Build both PDFs (img2pdf + qpdf) per **PDF deliverable** below
-14. Build the web bundle (96 dpi JPGs + bundled web PDF + zip) per **Web bundle** below
-15. User downloads the web PDF via brochure.html's Download button or receives the print master separately for press/print runs
+11. **Only after user approval**: render snapshots (two passes — 300 dpi to `output/`, 192 dpi to `output/.snapshots-web/`) per **Print snapshot capture** below
+12. Build both PDFs (img2pdf + qpdf) per **PDF deliverable** below
+13. Build the web bundle (96 dpi JPGs + bundled web PDF + zip) per **Web bundle** below
+14. User downloads the web PDF via brochure.html's Download button or receives the print master separately for press/print runs
 
 Do not capture snapshots during the editing cycle — they are expensive and invalidated by every change.
 

package/payload/premium-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/premium-plugins/venture-studio/PLUGIN.md

@@ -0,0 +1,110 @@
+---
+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.
+
+### Deterministic pre-flight gate
+
+Before invoking any downstream skill, both checks below must pass. Both are deterministic — exit-code on `ls`, structured output on `project-list`. Neither check depends on LLM judgement.
+
+1. **Directory check:** `[ -d "${PROJECT_ROOT}/.docs/data-room/01-narrative" ]` returns exit 0.
+2. **Graph check:** the `project-list` tool returns a Project whose `name` matches the business's working name.
+
+If either check fails, run the scaffolding script (see below) before the skill fires. If the script fails, surface the literal stderr error to the operator — do not narrate around it (memory: [[feedback_no_stdout_parsing_for_control_flow]]).
+
+### Scaffolding script
+
+`bin/scaffold.sh` is the deterministic enforcement layer. It creates the Project + eight artefact Tasks (via the work plugin's `project-create-cli` bridge) and materialises the ten-section directory tree. Graph write first, directories second; idempotent re-run if any partial state lands.
+
+```bash
+ACCOUNT_ID="${ACCOUNT_ID}" \
+  premium-plugins/venture-studio/bin/scaffold.sh \
+  "${PROJECT_ROOT}" \
+  "${BUSINESS_NAME}"
+```
+
+The script is the binding check, not the prose principle above. The prose explains why; the script is what makes it true.
+
+## 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 script — it does steps 1–3 below in a single atomic invocation:
+
+```bash
+ACCOUNT_ID="${ACCOUNT_ID}" \
+  premium-plugins/venture-studio/bin/scaffold.sh \
+  "${PROJECT_ROOT}" \
+  "${BUSINESS_NAME}"
+```
+
+The script's three effects:
+
+1. **Scaffolds the data room.** Materialises the ten-section directory tree under `<project-root>/.docs/data-room/`. Every artefact has a slot to land in before any artefact is produced.
+2. **Creates the `Project` node.** Tier `full` (data-room work is multi-phase). Project name is the business's working name; description references the data-room root path.
+3. **Enumerates the eight artefact Tasks** in section order — one transaction, atomic with the Project. The work-item list the script pre-seeds:
+   - **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/bin/scaffold.sh

@@ -0,0 +1,104 @@
+#!/usr/bin/env bash
+# Venture-studio data-room scaffold — deterministic enforcement of the
+# scaffold-first principle (Task 286 + feedback_doctrine_paragraph_is_not_a_gate).
+#
+# Creates exactly one Project (with eight pre-seeded artefact Tasks) in
+# the graph, then materialises the ten-section data-room directory tree
+# on disk. The venture-studio agent's downstream skills are gated on
+# both signals existing — see venture-studio/PLUGIN.md.
+#
+# Order of operations: graph write first, directories second. The CLI's
+# duplicate-name guard makes the script safely re-runnable after any
+# partial failure: a second run finds the existing Project, returns its
+# id, and retries the mkdir step.
+#
+# Usage:
+#   ACCOUNT_ID=<uuid> scaffold.sh <project-root> <business-name>
+#
+# Exit codes:
+#   0   scaffold complete (or already existed)
+#   2   bad arguments / missing ACCOUNT_ID
+#   1   graph write failed, directory mkdir failed, or CLI binary missing
+
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+# Deployed layout per packages/create-maxy-code/scripts/bundle.js:
+#   <install>/premium-plugins/venture-studio/bin/scaffold.sh
+#   <install>/platform/plugins/work/mcp/dist/cli/project-create-cli.js
+CLI_BIN="${SCRIPT_DIR}/../../../platform/plugins/work/mcp/dist/cli/project-create-cli.js"
+
+if [[ $# -ne 2 ]]; then
+  echo "scaffold.sh: usage: ACCOUNT_ID=<uuid> $0 <project-root> <business-name>" >&2
+  exit 2
+fi
+
+PROJECT_ROOT="$1"
+BUSINESS_NAME="$2"
+
+if [[ -z "${ACCOUNT_ID:-}" ]]; then
+  echo "scaffold.sh: ACCOUNT_ID env var required" >&2
+  exit 2
+fi
+
+if [[ ! -d "$PROJECT_ROOT" ]]; then
+  echo "scaffold.sh: project root does not exist: $PROJECT_ROOT" >&2
+  exit 2
+fi
+
+if [[ ! -f "$CLI_BIN" ]]; then
+  echo "scaffold.sh: project-create CLI not built or missing at: $CLI_BIN" >&2
+  exit 1
+fi
+
+DATA_ROOM="${PROJECT_ROOT}/.docs/data-room"
+
+# Eight pre-seeded artefact tasks — order and names match
+# premium-plugins/venture-studio/PLUGIN.md § First-conversation routing.
+# Section order is preserved so the agent can walk them sequentially.
+PAYLOAD=$(cat <<JSON
+{
+  "accountId": "${ACCOUNT_ID}",
+  "name": "${BUSINESS_NAME}",
+  "description": "Venture-studio data room for ${BUSINESS_NAME}. Root: ${DATA_ROOM}",
+  "tier": "full",
+  "workItems": [
+    {"name": "Stage 1 — Office-hours design doc", "description": "Produces 01-narrative/office-hours-design.md via the office-hours skill."},
+    {"name": "Brand pack", "description": "Produces brand identity (palette, typography, logo) into 06-product-ip/brand/ via the brand-pack skill."},
+    {"name": "Stage 2 — Wedge validation + landing page + PRD", "description": "Produces 01-narrative/{PMF,LANDING,PRD}.md via the zero-to-prototype skill."},
+    {"name": "Stage 3 — Business plan", "description": "Produces 01-narrative/business-plan.md via investor-data-room Stage 3."},
+    {"name": "Stage 3b — Term sheet", "description": "Produces html/prospectus/term_sheet.html via investor-data-room Stage 3b."},
+    {"name": "Stage 4 — Deck blueprint", "description": "Produces 01-narrative/deck-blueprint.md via investor-data-room Stage 4."},
+    {"name": "Stage 4b — Prospectus", "description": "Produces html/prospectus/index.html via investor-data-room Stage 4b."},
+    {"name": "Stage 5 — Rendered PDFs", "description": "Produces html/{business-plan,prospectus,deck}/*.pdf via investor-data-room Stage 5."}
+  ]
+}
+JSON
+)
+
+# Graph write first. CLI returns {projectId, existing:bool} on stdout;
+# on any failure it exits non-zero with a literal stderr message that
+# propagates here verbatim — no prose-parsing for control flow
+# (memory: feedback_no_stdout_parsing_for_control_flow).
+RESULT=$(node "$CLI_BIN" "$PAYLOAD")
+echo "scaffold.sh: project-create CLI returned: $RESULT"
+
+# Directories second. The agent's pre-flight gate keys on the existence
+# of 01-narrative/ (it AND-checks with project-list); creating it last
+# means partial state (graph-only) is naturally invisible to the gate
+# until mkdir succeeds.
+for section in \
+  01-narrative \
+  02-corporate-legal \
+  03-cap-table \
+  04-financials \
+  05-team \
+  06-product-ip \
+  07-customers \
+  08-market \
+  09-traction-metrics \
+  10-supporting; do
+  mkdir -p "${DATA_ROOM}/${section}"
+done
+
+echo "scaffold.sh: data-room scaffolded at ${DATA_ROOM}"

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)