$npx -y skills add MoizIbnYousaf/marketing-cli --skill paper-marketingOn-brand visual marketing content using Paper MCP and parallel agent teams. Reads the project's brand/ directory to build a design system, then spawns designer agents in parallel — each creating a unique artboard with a different on-brand layout interpretation. Intelligently adap
| 1 | # /paper-marketing — On-Brand Visual Content in Paper MCP |
| 2 | |
| 3 | Spawn parallel designer agents in Paper, each creating a unique on-brand interpretation of marketing content. Same brand system, different creative executions. Agent count and approach intelligently adapt to the user's actual goal. |
| 4 | |
| 5 | ## Quick Reference |
| 6 | |
| 7 | | Phase | What Happens | Key Tool | |
| 8 | |-------|-------------|----------| |
| 9 | | 1. Load Brand | Read brand/ files, discover Paper file, confirm with user | `mcp__paper__get_basic_info()` | |
| 10 | | 2. Goal Discovery | Interrogate user: content type, variation count, priority | `AskUserQuestion` | |
| 11 | | 3. Create Tasks | Build rich task descriptions with full brand system + content | `TeamCreate` + `TaskCreate` | |
| 12 | | 4. Spawn Agents | Launch N designer agents in parallel | `Agent` (background, Sonnet) | |
| 13 | | 5. Review | Screenshot artboards, compare, user selects winner | `mcp__paper__get_screenshot()` | |
| 14 | | 6. Export | Extract JSX, write handoff YAML, instruct user to export PNG | `mcp__paper__get_jsx()` | |
| 15 | | 7. Log | Update brand/assets.md, append workflow log | File writes | |
| 16 | |
| 17 | For Paper MCP HTML rules, see [references/paper-mcp-rules.md](references/paper-mcp-rules.md). |
| 18 | For brand system extraction template, see [references/brand-system-template.md](references/brand-system-template.md). |
| 19 | For platform-specific conventions, see [references/platform-conventions.md](references/platform-conventions.md). |
| 20 | For agent quality rubric, see [references/agent-quality-rubric.md](references/agent-quality-rubric.md). |
| 21 | |
| 22 | ## Workflow |
| 23 | |
| 24 | ### Phase 1: Load Brand System + Discover Paper File |
| 25 | |
| 26 | **Step 1a: Load brand context.** Run `mktg status --json` to confirm brand files exist. Then read in parallel: |
| 27 | - `brand/voice-profile.md` — tone, vocabulary, do's/don'ts, signature phrases |
| 28 | - `brand/creative-kit.md` — colors (hex + roles), fonts (families + weights + sizes), spacing rhythm |
| 29 | - `brand/positioning.md` — angles, headlines, proof points |
| 30 | - `brand/assets.md` — what already exists (avoid duplication) |
| 31 | |
| 32 | **Step 1b: Extract the design system.** From brand files, build: |
| 33 | - **Palette**: every color token with hex and role (bg, accent, text, muted, divider) |
| 34 | - **Typography**: font families, weights, sizes for each role (display, section, body, label, stat) |
| 35 | - **Layout tokens**: slide dimensions, padding, content area, footer structure |
| 36 | - **Voice rules**: signature phrases, copy rules, words to use/avoid |
| 37 | - **Positioning angles**: available angles and their headline directions |
| 38 | |
| 39 | If `creative-kit.md` is missing, use AskUserQuestion to gather basics (bg color light/dark, accent color, font preference), then write the result to `brand/creative-kit.md` so it persists. |
| 40 | |
| 41 | **Step 1c: Discover the Paper workspace.** Call `mcp__paper__get_basic_info()` and record: |
| 42 | - **File name** — this is the workspace all agents will use |
| 43 | - **Existing artboards** — names and IDs, so agents know what's already there |
| 44 | - **Loaded fonts** — so agents can use them without guessing |
| 45 | |
| 46 | **Step 1d: Confirm with AskUserQuestion:** |
| 47 | ``` |
| 48 | "I see Paper file '{fileName}' is open with artboards: {list}. I'll create new artboards here for the marketing designs. Right file?" |
| 49 | |
| 50 | Options: |
| 51 | 1. "Yes, use this file" — proceed |
| 52 | 2. "Different file" — user specifies which file to open |
| 53 | ``` |
| 54 | |
| 55 | Do NOT proceed until the user confirms. |
| 56 | |
| 57 | ### Phase 2: Intelligent Goal Discovery |
| 58 | |
| 59 | This is the most important phase. Use **AskUserQuestion** to understand what the user |