brand-gen-setup

Brand Gen Setup

Pi / Sage full-pipeline prompt

For Sage brand work in Pi, use the paste-ready prompt at docs/prompts/pi-sage-brand-gen-full-pipeline.md. It routes Pi through the typed brand_* tools, the brand-orchestrator subagent, exact-text gates, v2/DSPy review, GEPA-ready disagreement fields, and typed mutation loops. Keep this link instead of copying the full prompt into skill bodies.

This skill covers installation, validation, and host wiring.

After setup is complete, load:

• skills/brand-gen/SKILL.md — main workflow
• skills/brand-gen-reference/SKILL.md — models, surfaces, file layout
• skills/brand-gen-logo/SKILL.md — logo workflows
• skills/brand-content-ideation/SKILL.md — messaging/copy ideation

New saved brands and testing sessions also get a generated Pi runtime prompt at <brand-dir>/prompts/pi-full-pipeline.md. Use that brand-scoped prompt for non-Sage brands instead of the Sage-specific prompt under docs/prompts/.

Prerequisites

• Python 3.11+
• a Replicate API token
• Node.js if using Pi, OpenClaw, or agent-browser

Step 1 — clone and install

git clone <your-fork-or-repo-url>
cd brand-gen
python3 -m venv .venv
source .venv/bin/activate
python3 -m pip install -e .
bgen --help

If bgen is not found, activate the venv first.

Step 2 — configure environment

cp .env.example .env

Set REPLICATE_API_TOKEN in .env.

Important notes:

• repo-local .env is the preferred config source
• a legacy host-specific fallback may still be read for compatibility
• set BRAND_GEN_DIR if you want durable state outside the repo checkout

Local config

Create .brand-gen-local.json at the repo root. The agent should do this automatically:

1. Detect repo_root from the current working directory (pwd).
2. Ask the user: "Do you have an Obsidian vault or brand docs folder you want to connect? If so, what's the path and which brand should use it?" If yes, prefer a brand-specific map (brand_vault_paths / brand_knowledge_base_paths). Use global vault_paths only for a single-brand checkout.
3. Write the file:

{
  "repo_root": "<detected path>",
  "vault_paths": [],
  "brand_vault_paths": {
    "<brand-key>": ["<user-provided Obsidian vault path if any>"]
  },
  "brand_knowledge_base_paths": {
    "<brand-key>": ["<user-provided docs path if any>"]
  }
}