@cliangdev/conductor 0.43.0 → 0.45.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/assets/claude/agents/conductor-coder.md +1 -1
- package/assets/claude/agents/conductor-marketing-art-director.md +4 -0
- package/assets/claude/commands/conductor/implement.md +3 -2
- package/assets/claude/commands/conductor/prd.md +162 -32
- package/assets/claude/skills/conductor-marketing-create/SKILL.md +7 -5
- package/assets/claude/skills/conductor-marketing-create/references/brand-kit-setup.md +28 -0
- package/assets/claude/skills/conductor-marketing-create/references/direct.md +5 -2
- package/assets/claude/skills/conductor-marketing-create/references/slideshow-formats.md +52 -5
- package/assets/claude/skills/conductor-marketing-create/references/team-run.md +18 -10
- package/assets/cli-manifest.json +13 -5
- package/dist/commands/lint.d.ts +3 -1
- package/dist/commands/lint.d.ts.map +1 -1
- package/dist/commands/lint.js +174 -7
- package/dist/commands/lint.js.map +1 -1
- package/dist/daemon/watcher.d.ts.map +1 -1
- package/dist/daemon/watcher.js +2 -1
- package/dist/daemon/watcher.js.map +1 -1
- package/dist/lib/content-type.d.ts +7 -0
- package/dist/lib/content-type.d.ts.map +1 -0
- package/dist/lib/content-type.js +9 -0
- package/dist/lib/content-type.js.map +1 -0
- package/dist/lib/slideshow/compose.d.ts +8 -0
- package/dist/lib/slideshow/compose.d.ts.map +1 -1
- package/dist/lib/slideshow/compose.js +10 -3
- package/dist/lib/slideshow/compose.js.map +1 -1
- package/dist/lib/slideshow/css.d.ts +7 -2
- package/dist/lib/slideshow/css.d.ts.map +1 -1
- package/dist/lib/slideshow/css.js +25 -11
- package/dist/lib/slideshow/css.js.map +1 -1
- package/dist/lib/slideshow/html.d.ts +2 -1
- package/dist/lib/slideshow/html.d.ts.map +1 -1
- package/dist/lib/slideshow/html.js +33 -8
- package/dist/lib/slideshow/html.js.map +1 -1
- package/dist/lib/slideshow/index.d.ts +1 -0
- package/dist/lib/slideshow/index.d.ts.map +1 -1
- package/dist/lib/slideshow/index.js +1 -0
- package/dist/lib/slideshow/index.js.map +1 -1
- package/dist/lib/slideshow/spec.d.ts +3 -0
- package/dist/lib/slideshow/spec.d.ts.map +1 -1
- package/dist/lib/slideshow/spec.js +3 -0
- package/dist/lib/slideshow/spec.js.map +1 -1
- package/dist/lib/slideshow/style.d.ts +108 -0
- package/dist/lib/slideshow/style.d.ts.map +1 -0
- package/dist/lib/slideshow/style.js +200 -0
- package/dist/lib/slideshow/style.js.map +1 -0
- package/dist/lib/slug.d.ts +13 -0
- package/dist/lib/slug.d.ts.map +1 -0
- package/dist/lib/slug.js +26 -0
- package/dist/lib/slug.js.map +1 -0
- package/dist/mcp/index.d.ts +615 -1
- package/dist/mcp/index.d.ts.map +1 -1
- package/dist/mcp/index.js +62 -9
- package/dist/mcp/index.js.map +1 -1
- package/dist/mcp/tools/comments.d.ts +7 -0
- package/dist/mcp/tools/comments.d.ts.map +1 -1
- package/dist/mcp/tools/comments.js.map +1 -1
- package/dist/mcp/tools/creative-drafts.d.ts +0 -1
- package/dist/mcp/tools/creative-drafts.d.ts.map +1 -1
- package/dist/mcp/tools/creative-drafts.js +1 -4
- package/dist/mcp/tools/creative-drafts.js.map +1 -1
- package/dist/mcp/tools/creative-images.d.ts.map +1 -1
- package/dist/mcp/tools/creative-images.js +2 -1
- package/dist/mcp/tools/creative-images.js.map +1 -1
- package/dist/mcp/tools/creatives.d.ts +25 -0
- package/dist/mcp/tools/creatives.d.ts.map +1 -1
- package/dist/mcp/tools/creatives.js +79 -1
- package/dist/mcp/tools/creatives.js.map +1 -1
- package/dist/mcp/tools/documents.d.ts.map +1 -1
- package/dist/mcp/tools/documents.js +7 -5
- package/dist/mcp/tools/documents.js.map +1 -1
- package/dist/mcp/tools/slideshow.d.ts +12 -1
- package/dist/mcp/tools/slideshow.d.ts.map +1 -1
- package/dist/mcp/tools/slideshow.js +59 -3
- package/dist/mcp/tools/slideshow.js.map +1 -1
- package/package.json +2 -1
|
@@ -18,7 +18,7 @@ You will be given:
|
|
|
18
18
|
- **Task description** — what to build
|
|
19
19
|
- **Acceptance criteria** — tagged `[auto]` (must have automated test) or `[manual]` (document verification steps)
|
|
20
20
|
- **Epic context** — background and goals
|
|
21
|
-
- **PRD path** — for deeper context if needed
|
|
21
|
+
- **PRD path (.html or .md)** — for deeper context if needed. In an HTML PRD, a feature is an `<article data-feature>` and each acceptance criterion an `<li data-ac="AC-...">`
|
|
22
22
|
|
|
23
23
|
Read all of it before writing any code.
|
|
24
24
|
|
|
@@ -56,6 +56,10 @@ and nothing else; the orchestrator passes it to `compose_slideshow`. Rules:
|
|
|
56
56
|
text sits between y 16 and 75. No logo, badge or offer on any slide. No invented numbers.
|
|
57
57
|
- In `direction.md`, the Publish assets section still lists the cover frame (card 1), alt text for
|
|
58
58
|
every slide in order, and the sound. Alt text describes each slide for someone who cannot see it.
|
|
59
|
+
- If the run chose a slideshow look, the object may also carry a top-level `style` (the fields in
|
|
60
|
+
`references/slideshow-formats.md`, "Style") and the orchestrator is given `brandKitId`; write colours
|
|
61
|
+
and sizes only from that choice, never invent a look. The orchestrator passes `brandKitId`/`style` to
|
|
62
|
+
`compose_slideshow` and the resolved style as `slideStyle` on the preview. Absent: native.
|
|
59
63
|
- Do not use `creative-spec.json` for it, and do not write layout, theme or headline fields.
|
|
60
64
|
|
|
61
65
|
## creative-spec.json (RENDER only; STILL and MOTION)
|
|
@@ -58,7 +58,8 @@ Load the PRD if not already in context.
|
|
|
58
58
|
|
|
59
59
|
2. **If the PRD is not in context**:
|
|
60
60
|
- Call `get_work_item` with the resolved `issueId` — note the returned `absolutePath` (the issue directory on disk); use it for any subsequent `Read` / `Write` / `Edit` calls in this skill (the `Read`, `Write`, and `Edit` tools require absolute paths)
|
|
61
|
-
- Read the local
|
|
61
|
+
- Read the local PRD at `{absolutePath}prd.html` if it exists, otherwise `{absolutePath}prd.md`. Remember which one exists as `prdPath` (the full absolute path) and pass it to coders
|
|
62
|
+
- Acceptance-criteria IDs: for `prd.html`, take them from the `data-ac` attributes (`<li data-ac="AC-P0-1.1">`; each sits inside the `<article data-feature>` it belongs to); for `prd.md`, use the checkbox regex ``^- \[[ x]\] `AC-P[01]-\d+\.\d+` ``
|
|
62
63
|
|
|
63
64
|
---
|
|
64
65
|
|
|
@@ -295,7 +296,7 @@ For each batch, spawn `conductor-coder` subagents in parallel using the Agent to
|
|
|
295
296
|
## Context
|
|
296
297
|
- Epic: {epic.id} - {epic.title}
|
|
297
298
|
- Issue: {issue_id} - {issue_title}
|
|
298
|
-
- Full PRD:
|
|
299
|
+
- Full PRD: {prdPath} (prd.html or prd.md, whichever exists; read if more context needed)
|
|
299
300
|
|
|
300
301
|
## Workflow
|
|
301
302
|
1. Write tests for each [auto] criterion FIRST
|
|
@@ -1,7 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: conductor:prd
|
|
3
|
-
description: Create PRDs for Conductor projects through discovery, research, and guided writing
|
|
4
|
-
|
|
3
|
+
description: Create PRDs for Conductor projects through discovery, research, and guided writing. Writes an HTML PRD by default (markdown on request), or imports an existing HTML page / claude.ai artifact as a PRD.
|
|
4
|
+
argument-hint: "[import <claude.ai artifact URL or .html path>]"
|
|
5
|
+
allowed-tools: mcp__conductor__*, AskUserQuestion, Task, Read, Write, Glob, Grep, WebSearch, Bash, Artifact
|
|
5
6
|
---
|
|
6
7
|
|
|
7
8
|
# /conductor:prd
|
|
@@ -11,6 +12,8 @@ You are a PRD creation assistant for the Conductor workflow.
|
|
|
11
12
|
## Trigger
|
|
12
13
|
This skill runs when the user invokes `/conductor:prd`.
|
|
13
14
|
|
|
15
|
+
If the argument starts with `import` (`/conductor:prd import <claude.ai artifact URL or .html path>`), skip Phases 1-3 and follow **Import Route** at the end of this file. Otherwise continue with the phases below.
|
|
16
|
+
|
|
14
17
|
## Prerequisites Check
|
|
15
18
|
Read `~/.conductor/config.json`. If missing or lacking `localPath`, `projectId`, or `apiKey`, respond:
|
|
16
19
|
> Run `conductor login` and `conductor init` first to set up Conductor in this project.
|
|
@@ -98,22 +101,129 @@ Use AskUserQuestion:
|
|
|
98
101
|
|
|
99
102
|
### 3b. Write Full PRD
|
|
100
103
|
|
|
101
|
-
Write the PRD
|
|
104
|
+
**Format.** Write the PRD as **HTML** (`prd.html`) unless the user asked for markdown, in which case use the markdown fallback (`prd.md`). Both formats carry the same schema-v2 content: seven required sections in a fixed order, stable feature and acceptance-criterion IDs, and a contract block on every P0 feature. Target 1-2 pages — concise enough to review in under 5 minutes.
|
|
102
105
|
|
|
103
|
-
**
|
|
104
|
-
-
|
|
105
|
-
-
|
|
106
|
-
- If `Glossary` or `Reference Patterns` truly has nothing to add, write `_None._` rather than omitting the section
|
|
106
|
+
**Content guidelines (both formats):**
|
|
107
|
+
- The seven required sections appear in this exact order: Problem, Glossary, Goals, Non-Goals, Users, Reference Patterns, Features. Optional sections (Out of Scope, Open Questions, Supporting Documents) come after.
|
|
108
|
+
- If Glossary or Reference Patterns truly has nothing to add, say so explicitly ("None") rather than omitting the section or leaving it empty
|
|
107
109
|
- Features get stable IDs that restart within each priority: `P0-1`, `P0-2`, ... and `P1-1`, `P1-2`, ...
|
|
108
|
-
- Every P0 feature
|
|
109
|
-
-
|
|
110
|
-
-
|
|
111
|
-
-
|
|
112
|
-
-
|
|
113
|
-
|
|
114
|
-
|
|
110
|
+
- Every P0 feature carries What, Not, Inputs, Outputs, Invariants and Acceptance Criteria. For a P0 feature with no exclusions, write "None" under Not. P1 features may omit Not, Inputs, Outputs and Invariants
|
|
111
|
+
- Every acceptance criterion gets a stable ID matching `^AC-P[01]-\d+\.\d+$` (e.g. `AC-P0-1.1`), unique within the PRD, with the feature's ID inside it (`AC-P0-3.2` belongs to `P0-3`)
|
|
112
|
+
- Acceptance criteria are verifiable: Given/When/Then or measurable thresholds, not "works correctly"
|
|
113
|
+
- Keep technical implementation details out of the PRD (they go in `architecture.md`) and edge cases out (they go in implementation specs)
|
|
114
|
+
- Leave Supporting Documents empty until documents exist
|
|
115
|
+
|
|
116
|
+
**HTML contract (`prd.html`):**
|
|
117
|
+
- `<head>` has `<title>` and three metas: `conductor:doc-type` = `prd`, `conductor:schema-version` = `2`, `conductor:issue-id` = the Work Item ID
|
|
118
|
+
- Each section is `<section id="{name}" data-prd-section="{name}">` with an `<h2>`; names, in order: `problem`, `glossary`, `goals`, `non-goals`, `users`, `reference-patterns`, `features`, then optional `out-of-scope`, `open-questions`, `supporting-documents`
|
|
119
|
+
- An empty Glossary or Reference Patterns contains exactly `<p><em>None.</em></p>`
|
|
120
|
+
- Each feature is `<article id="P0-1" data-feature="P0-1">` with an `<h3>`, then a `<dl>` whose `<dt>`s are What, Not, Inputs, Outputs, Invariants, then `<ul data-acs>` of `<li data-ac="AC-P0-1.1">…</li>`
|
|
121
|
+
- Self-contained: inline `<style>` and `<script>`, Google Fonts, and pinned CDN scripts only from cdnjs.cloudflare.com, cdn.jsdelivr.net, unpkg.com, cdn.tailwindcss.com or code.jquery.com. No `fetch`/XHR/WebSocket (the viewer's CSP blocks them), no `window.claude`, no `window.open` (popups are blocked). Links are plain `<a href>`: `#hash` scrolls inside the page and `http(s)` links open in a new tab through the Conductor app. The page needs no script; add one only when it earns its place
|
|
122
|
+
- Escape `<`, `>` and `&` in text. Keep ids stable: reviewers' comments reference the nearest section id. Comment quotes are rendered text (tags dropped, whitespace collapsed), so write section text that reads naturally
|
|
123
|
+
|
|
124
|
+
### HTML PRD Template
|
|
125
|
+
|
|
126
|
+
Keep this structure and token block; adapt the visual style to the product's design language from Phase 2a when the PRD is UI-heavy.
|
|
127
|
+
|
|
128
|
+
```html
|
|
129
|
+
<!doctype html>
|
|
130
|
+
<html lang="en">
|
|
131
|
+
<head>
|
|
132
|
+
<meta charset="utf-8">
|
|
133
|
+
<meta name="viewport" content="width=device-width, initial-scale=1">
|
|
134
|
+
<meta name="conductor:doc-type" content="prd">
|
|
135
|
+
<meta name="conductor:schema-version" content="2">
|
|
136
|
+
<meta name="conductor:issue-id" content="{issueId}">
|
|
137
|
+
<title>{title}</title>
|
|
138
|
+
<style>
|
|
139
|
+
:root{--bg:#fff;--fg:#1a1d21;--muted:#5b6470;--line:#e3e6ea;--card:#f6f7f9;--accent:#2f5bea}
|
|
140
|
+
@media (prefers-color-scheme:dark){:root{--bg:#14161a;--fg:#e8eaed;--muted:#9aa3ae;--line:#2a2e35;--card:#1c1f25;--accent:#7b9bff}}
|
|
141
|
+
*{box-sizing:border-box}
|
|
142
|
+
body{margin:0;background:var(--bg);color:var(--fg);font:16px/1.6 system-ui,-apple-system,"Segoe UI",sans-serif}
|
|
143
|
+
nav{position:sticky;top:0;z-index:1;display:flex;gap:16px;overflow-x:auto;white-space:nowrap;padding:10px 16px;background:var(--bg);border-bottom:1px solid var(--line);font-size:14px}
|
|
144
|
+
nav a{color:var(--muted);text-decoration:none}nav a:hover{color:var(--accent)}
|
|
145
|
+
main{max-width:760px;margin:0 auto;padding:0 16px 64px}
|
|
146
|
+
h1{font-size:2rem;line-height:1.2;margin:32px 0 4px}
|
|
147
|
+
h2{font-size:1.25rem;margin:0 0 12px}
|
|
148
|
+
h3{font-size:1.05rem;margin:0 0 8px}
|
|
149
|
+
.sub{color:var(--muted);margin:0 0 8px}
|
|
150
|
+
section{padding:24px 0;border-top:1px solid var(--line);scroll-margin-top:56px}
|
|
151
|
+
article{background:var(--card);border:1px solid var(--line);border-radius:10px;padding:16px;margin:12px 0}
|
|
152
|
+
dl{display:grid;grid-template-columns:max-content 1fr;gap:6px 16px;margin:0 0 12px}
|
|
153
|
+
dt{color:var(--muted);font-weight:600}dd{margin:0}
|
|
154
|
+
ul[data-acs]{margin:0;padding-left:20px}
|
|
155
|
+
@media (max-width:560px){dl{grid-template-columns:1fr}dd{margin-bottom:6px}}
|
|
156
|
+
</style>
|
|
157
|
+
</head>
|
|
158
|
+
<body>
|
|
159
|
+
<nav>
|
|
160
|
+
<a href="#problem">Problem</a><a href="#glossary">Glossary</a><a href="#goals">Goals</a><a href="#non-goals">Non-Goals</a><a href="#users">Users</a><a href="#reference-patterns">Reference Patterns</a><a href="#features">Features</a>
|
|
161
|
+
</nav>
|
|
162
|
+
<main>
|
|
163
|
+
<h1>{title}</h1>
|
|
164
|
+
<p class="sub">PRD · {issueId}</p>
|
|
165
|
+
|
|
166
|
+
<section id="problem" data-prd-section="problem"><h2>Problem</h2>
|
|
167
|
+
<p>{2-3 sentences: what hurts, for whom, and how we know}</p></section>
|
|
168
|
+
|
|
169
|
+
<section id="glossary" data-prd-section="glossary"><h2>Glossary</h2>
|
|
170
|
+
<dl><dt>{Term}</dt><dd>{project-specific definition}</dd></dl>
|
|
171
|
+
<!-- nothing to define: replace the <dl> with <p><em>None.</em></p> --></section>
|
|
172
|
+
|
|
173
|
+
<section id="goals" data-prd-section="goals"><h2>Goals</h2>
|
|
174
|
+
<ul><li>{Measurable outcome}</li></ul></section>
|
|
175
|
+
|
|
176
|
+
<section id="non-goals" data-prd-section="non-goals"><h2>Non-Goals</h2>
|
|
177
|
+
<ul><li>{Explicit exclusion}</li></ul></section>
|
|
178
|
+
|
|
179
|
+
<section id="users" data-prd-section="users"><h2>Users</h2>
|
|
180
|
+
<p>{Target users and their primary needs, 2-4 sentences}</p></section>
|
|
181
|
+
|
|
182
|
+
<section id="reference-patterns" data-prd-section="reference-patterns"><h2>Reference Patterns</h2>
|
|
183
|
+
<ul><li><strong>{Aspect}</strong>: {existing file or convention to mirror}</li></ul>
|
|
184
|
+
<!-- none apply: replace the <ul> with <p><em>None.</em></p> --></section>
|
|
185
|
+
|
|
186
|
+
<section id="features" data-prd-section="features"><h2>Features</h2>
|
|
187
|
+
<h3 class="sub">P0: Must Have</h3>
|
|
188
|
+
<article id="P0-1" data-feature="P0-1"><h3>P0-1: {Feature Name}</h3>
|
|
189
|
+
<dl>
|
|
190
|
+
<dt>What</dt><dd>{precise scope in 1 sentence}</dd>
|
|
191
|
+
<dt>Not</dt><dd>{explicit exclusions, or <em>None.</em>}</dd>
|
|
192
|
+
<dt>Inputs</dt><dd>{what triggers this / what data flows in}</dd>
|
|
193
|
+
<dt>Outputs</dt><dd>{artifact, response or state change}</dd>
|
|
194
|
+
<dt>Invariants</dt><dd>{properties that must always hold}</dd>
|
|
195
|
+
</dl>
|
|
196
|
+
<ul data-acs>
|
|
197
|
+
<li data-ac="AC-P0-1.1">{Given/When/Then or measurable threshold}</li>
|
|
198
|
+
<li data-ac="AC-P0-1.2">{testable criterion}</li>
|
|
199
|
+
</ul></article>
|
|
200
|
+
|
|
201
|
+
<h3 class="sub">P1: Should Have</h3>
|
|
202
|
+
<article id="P1-1" data-feature="P1-1"><h3>P1-1: {Feature Name}</h3>
|
|
203
|
+
<dl><dt>What</dt><dd>{precise scope in 1 sentence}</dd></dl>
|
|
204
|
+
<ul data-acs><li data-ac="AC-P1-1.1">{testable criterion}</li></ul></article>
|
|
205
|
+
</section>
|
|
206
|
+
|
|
207
|
+
<section id="out-of-scope" data-prd-section="out-of-scope"><h2>Out of Scope</h2>
|
|
208
|
+
<ul><li>{Item explicitly deferred}</li></ul></section>
|
|
209
|
+
|
|
210
|
+
<section id="open-questions" data-prd-section="open-questions"><h2>Open Questions</h2>
|
|
211
|
+
<ul><li>{unresolved item}</li></ul></section>
|
|
212
|
+
|
|
213
|
+
<section id="supporting-documents" data-prd-section="supporting-documents"><h2>Supporting Documents</h2>
|
|
214
|
+
<p>Links are added here as supporting documents are created.</p></section>
|
|
215
|
+
</main>
|
|
216
|
+
</body>
|
|
217
|
+
</html>
|
|
218
|
+
```
|
|
115
219
|
|
|
116
|
-
###
|
|
220
|
+
### Markdown fallback (`prd.md`, only when the user asks for markdown)
|
|
221
|
+
|
|
222
|
+
Same content rules. Markdown specifics:
|
|
223
|
+
- Frontmatter MUST include `schemaVersion: 2`
|
|
224
|
+
- If `Glossary` or `Reference Patterns` has nothing to add, write `_None._`
|
|
225
|
+
- Every P0 feature includes all six bold-prefix lines: `**What**`, `**Not**`, `**Inputs**`, `**Outputs**`, `**Invariants**`, `**Acceptance Criteria**` (`**Not**: _None._` when nothing is excluded)
|
|
226
|
+
- Each AC line is `- [ ] \`AC-P0-1.1\` …`
|
|
117
227
|
|
|
118
228
|
```markdown
|
|
119
229
|
---
|
|
@@ -130,7 +240,6 @@ schemaVersion: 2
|
|
|
130
240
|
|
|
131
241
|
## Glossary
|
|
132
242
|
- **{Term}**: {project-specific definition, distinguishing it from generic usage}
|
|
133
|
-
- **{Term}**: {definition}
|
|
134
243
|
|
|
135
244
|
(If truly nothing to define, write `_None._`)
|
|
136
245
|
|
|
@@ -140,14 +249,12 @@ schemaVersion: 2
|
|
|
140
249
|
|
|
141
250
|
## Non-Goals
|
|
142
251
|
- {Explicit exclusion 1}
|
|
143
|
-
- {Explicit exclusion 2}
|
|
144
252
|
|
|
145
253
|
## Users
|
|
146
254
|
{Target users and their primary needs — 2-4 sentences}
|
|
147
255
|
|
|
148
256
|
## Reference Patterns
|
|
149
257
|
- **{Aspect}**: {existing file or convention to mirror, e.g. "follow `src/commands/doctor.ts` — same Commander registration, `--json` output mode, exit codes"}
|
|
150
|
-
- **{Aspect}**: {pattern}
|
|
151
258
|
|
|
152
259
|
(If truly no reference patterns apply, write `_None._`)
|
|
153
260
|
|
|
@@ -165,15 +272,6 @@ schemaVersion: 2
|
|
|
165
272
|
- [ ] `AC-P0-1.1` {Given/When/Then or measurable threshold}
|
|
166
273
|
- [ ] `AC-P0-1.2` {testable criterion}
|
|
167
274
|
|
|
168
|
-
#### P0-2: {Feature Name}
|
|
169
|
-
- **What**: {precise scope in 1 sentence}
|
|
170
|
-
- **Not**: _None._
|
|
171
|
-
- **Inputs**: {inputs}
|
|
172
|
-
- **Outputs**: {outputs}
|
|
173
|
-
- **Invariants**: {invariants}
|
|
174
|
-
- **Acceptance Criteria**:
|
|
175
|
-
- [ ] `AC-P0-2.1` {testable criterion}
|
|
176
|
-
|
|
177
275
|
### P1: Should Have
|
|
178
276
|
|
|
179
277
|
#### P1-1: {Feature Name}
|
|
@@ -193,8 +291,19 @@ schemaVersion: 2
|
|
|
193
291
|
|
|
194
292
|
### 3c. Self-Check
|
|
195
293
|
|
|
196
|
-
Before showing the PRD to the user in Step 3d, run through
|
|
294
|
+
Before showing the PRD to the user in Step 3d, run through the checklist for the format you wrote and fix any item that fails. Do not skip — this is the gate that keeps schema v2 PRDs deterministic for downstream agents. `conductor lint {issueId}` runs the same checks after saving.
|
|
197
295
|
|
|
296
|
+
**If HTML (`prd.html`):**
|
|
297
|
+
- [ ] `<head>` has `<title>` and the metas `conductor:doc-type` = `prd`, `conductor:schema-version` = `2`, `conductor:issue-id`
|
|
298
|
+
- [ ] Seven `<section id data-prd-section>` elements in order: `problem`, `glossary`, `goals`, `non-goals`, `users`, `reference-patterns`, `features` — each with an `<h2>`
|
|
299
|
+
- [ ] `glossary` and `reference-patterns` hold real entries or exactly `<p><em>None.</em></p>`
|
|
300
|
+
- [ ] Every feature is `<article id="P0-n" data-feature="P0-n">` (numbering restarts per priority) with an `<h3>`
|
|
301
|
+
- [ ] Every P0 feature's `<dl>` has `<dt>`s What, Not, Inputs, Outputs, Invariants, and a `<ul data-acs>` follows (P1 features may omit all but What)
|
|
302
|
+
- [ ] Every criterion is `<li data-ac="AC-P0-1.1">` with an id matching `^AC-P[01]-\d+\.\d+$`
|
|
303
|
+
- [ ] Every AC id is unique, and its feature part matches the enclosing article (`AC-P0-3.2` only inside `P0-3`)
|
|
304
|
+
- [ ] No `fetch`/XHR/`window.claude`/`window.open`; scripts, if any, are inline or pinned from cdnjs.cloudflare.com, cdn.jsdelivr.net, unpkg.com, cdn.tailwindcss.com or code.jquery.com
|
|
305
|
+
|
|
306
|
+
**If markdown (`prd.md`):**
|
|
198
307
|
- [ ] Frontmatter contains `schemaVersion: 2`
|
|
199
308
|
- [ ] All seven H2 sections are present in this exact order: `Problem`, `Glossary`, `Goals`, `Non-Goals`, `Users`, `Reference Patterns`, `Features`
|
|
200
309
|
- [ ] `Glossary` and `Reference Patterns` are non-empty (either real entries, or the literal text `_None._`)
|
|
@@ -225,10 +334,10 @@ Call MCP tools in this exact sequence:
|
|
|
225
334
|
2. **Create the Work Item**: `create_work_item({workflow, type: "PRD", title, description})`
|
|
226
335
|
- Receive: `{issueId, displayId, localPath}`
|
|
227
336
|
|
|
228
|
-
3. **Scaffold document**: `scaffold_document({issueId, filename: "prd.
|
|
229
|
-
- Receive: `{localPath: ".conductor/issues/{issueId}/prd.
|
|
337
|
+
3. **Scaffold document**: `scaffold_document({issueId, filename: "prd.html"})` (or `"prd.md"` when writing markdown). The filename extension sets the content type.
|
|
338
|
+
- Receive: `{localPath: ".conductor/issues/{issueId}/prd.html", absolutePath: "/abs/path/to/.conductor/issues/{issueId}/prd.html"}`
|
|
230
339
|
|
|
231
|
-
4. **Write content**: Use the Write tool with the `absolutePath` from step 3 (Write requires absolute paths) to write the full PRD with
|
|
340
|
+
4. **Write content**: Use the Write tool with the `absolutePath` from step 3 (Write requires absolute paths) to write the full PRD, with the `issueId` from step 2 in the `conductor:issue-id` meta tag (HTML) or the YAML frontmatter (markdown).
|
|
232
341
|
|
|
233
342
|
5. **Move to IN_REVIEW** (definition-driven): call `get_available_transitions({issueId})` to confirm `IN_REVIEW` is an available next status from the Workflow's initial status, then `transition_work_item({issueId, toStatus: "IN_REVIEW"})`, signalling the PRD is ready for team review.
|
|
234
343
|
|
|
@@ -246,7 +355,9 @@ Options:
|
|
|
246
355
|
For each accepted supporting document:
|
|
247
356
|
1. `scaffold_document({issueId, filename: "{doc-filename}"})`
|
|
248
357
|
2. Write the template content (see templates below) using the Write tool with the returned `absolutePath`
|
|
249
|
-
3. **Update the PRD's Supporting Documents section**: Read the saved
|
|
358
|
+
3. **Update the PRD's Supporting Documents section**: Read the saved PRD file (use the `absolutePath` returned from step 3 of the main save sequence), replace the placeholder line with a relative link entry, and write it back.
|
|
359
|
+
- HTML PRD: add `<li><a href="./architecture.md">Architecture</a> (architecture.md)</li>` inside a `<ul>` in the `supporting-documents` section. Conductor's HTML viewer does not yet turn `./` links into document tabs, so keep the filename visible as text next to the link.
|
|
360
|
+
- Markdown PRD: `- [Architecture](./architecture.md)` (the markdown viewer opens it as a tab).
|
|
250
361
|
|
|
251
362
|
**UI/UX quality bar for wireframes and HTML mocks:**
|
|
252
363
|
Before writing any UI artifact, recall the design language catalogued in Phase 2a. All wireframes and mocks must:
|
|
@@ -418,3 +529,22 @@ Write a valid standalone HTML file with inline CSS — no external dependencies.
|
|
|
418
529
|
- Use the same component vocabulary: if the product uses card containers with subtle shadows, use that here; if it uses bordered panels, do that instead
|
|
419
530
|
- Show at least two states: the default/happy-path view AND one of empty/loading/error
|
|
420
531
|
- Add a small `<!-- note: ... -->` comment for any placeholder or approximation that differs from the real product
|
|
532
|
+
|
|
533
|
+
## Import Route
|
|
534
|
+
|
|
535
|
+
`/conductor:prd import <claude.ai artifact URL or .html path>` brings an existing HTML page into Conductor as a PRD. It uses your Claude Code access to the artifact, because Conductor's backend cannot fetch private claude.ai pages.
|
|
536
|
+
|
|
537
|
+
1. **Read the page.**
|
|
538
|
+
- A `.html` / `.htm` path: Read the file.
|
|
539
|
+
- A claude.ai artifact URL (`claude.ai/artifact/{id}` or `claude.ai/code/artifact/{id}`): call the Artifact tool with `action: "read"` and the URL.
|
|
540
|
+
- If the result is only a summary because the artifact belongs to someone else, **stop**. Say the full page is only readable for artifacts the user owns, and ask them to download the `.html` file and re-run `/conductor:prd import <path>`.
|
|
541
|
+
- If the result lists declared runtime capabilities (live data, shared state, Claude calls), warn the user: Conductor renders pages in a sandbox that blocks `fetch`/XHR and popups and has no `window.claude`, so those parts will not work there.
|
|
542
|
+
- For the user's own artifact the result names a saved file that holds the full page: Read that file.
|
|
543
|
+
2. **Detect whether it already meets the HTML PRD contract**: the `conductor:doc-type` = `prd` meta tag plus `data-prd-section` and `data-ac` markers (Grep the content).
|
|
544
|
+
- **Meets it**: keep the page verbatim. Skip to step 3 and only set `conductor:issue-id` (adding the meta tag if absent) once the Work Item exists. Run the HTML self-check from 3c and report any failures to the user rather than rewriting their page.
|
|
545
|
+
- **Does not meet it**: use AskUserQuestion with these options:
|
|
546
|
+
- "Convert to Conductor PRD (keeps content and styling, adds the structure)" (Recommended) — restructure the page into the seven sections, feature articles and `data-ac` criteria; keep the author's wording, CSS and layout. Do not invent content: put real source material in each section, write "None" where the page has nothing, and draft any missing P0 fields (Not, Inputs, Outputs, Invariants, acceptance criteria) from the page's own content, flagging them for review. Run the 3c self-check, then 3d.
|
|
547
|
+
- "Attach as-is as a supporting document"
|
|
548
|
+
- "Cancel" — stop.
|
|
549
|
+
- **Attach as-is**: ask (AskUserQuestion) which Work Item to attach to — an existing one (`list_work_items`) or a new one (resolve the Workflow and create it as in Phase 4 steps 1-2). Then `scaffold_document({issueId, filename})` with a descriptive `.html` filename that is not `prd.html`, Write the page verbatim to the returned `absolutePath`, and confirm. No status transition.
|
|
550
|
+
3. **Save a PRD** (meets the contract, or converted) with the Phase 4 sequence: resolve the Workflow, `create_work_item` (title from `<title>` or the `<h1>`, description from the Problem section), `scaffold_document({issueId, filename: "prd.html"})`, Write, then the IN_REVIEW transition and confirmation. Offer supporting documents as in Phase 4.
|
|
@@ -20,10 +20,12 @@ do not post it.
|
|
|
20
20
|
non-empty `otherKits`, ask once with `AskUserQuestion` which kit to use: the default first, labelled
|
|
21
21
|
as the default, then up to 3 others (up to 4 options; "Other" covers the rest by name). Pass the
|
|
22
22
|
chosen kit's id as `brandKitId` on every `preview_creative_draft` and `create_creative` call for
|
|
23
|
-
the run, and take the Knowledge page and copy rules from that same kit. If the chosen kit's
|
|
23
|
+
the run (the default kit needs none), and take the Knowledge page and copy rules from that same kit. If the chosen kit's
|
|
24
24
|
`configured` is `false` the brand has never been set up: follow `references/brand-kit-setup.md`
|
|
25
25
|
and offer setup before making anything. Copy and visuals come from the Brand Kit and its Knowledge
|
|
26
|
-
page, not from invention.
|
|
26
|
+
page, not from invention. For slideshows the *style source* (native, or a kit's `slideshowStyle`)
|
|
27
|
+
is a separate choice: that kit's id goes only to `compose_slideshow`, never onto the Creative
|
|
28
|
+
unless it is also the brand kit (`references/slideshow-formats.md`, "Style").
|
|
27
29
|
- **Draft first, save after approval.** `preview_creative_draft` renders on this machine and writes
|
|
28
30
|
nothing to Conductor. Only after the person has seen the draft and approved it does
|
|
29
31
|
`commit_creative_draft` upload the media, save the Creative and run the full render. Never commit
|
|
@@ -35,7 +37,7 @@ do not post it.
|
|
|
35
37
|
|
|
36
38
|
| The person has | Mode | Read |
|
|
37
39
|
|---|---|---|
|
|
38
|
-
| A headline, photo, clip or finished images, an existing Creative to vary,
|
|
40
|
+
| A headline, photo, clip or finished images, an existing Creative to vary, wants the brand set up, or wants a kit style made from slides they like ("Make a kit style from slides") | **Direct** | `references/direct.md` |
|
|
39
41
|
| A goal or topic ("a post about X for Y") and wants the idea chosen for them | **Team** (honours `--quick`: two ideators, no finalist renders) | `references/team-run.md` |
|
|
40
42
|
|
|
41
43
|
Infer the mode from the request. A concrete headline, photo, clip or existing Creative (including a
|
|
@@ -49,14 +51,14 @@ preview, check and commit steps (S6 reads `references/direct.md`).
|
|
|
49
51
|
|
|
50
52
|
- `references/direct.md`: the Direct flow (read the brand, angle, headline, photo, preview, critique, commit), sequences, video, finished images, short videos, music, cleanup.
|
|
51
53
|
- `references/team-run.md`: the Team flow (run folder, stages S0 to S6, FILM ideas, final message, failure handling).
|
|
52
|
-
- `references/brand-kit-setup.md`: check the Brand Kit and set it up from a website, a brand doc or direct answers.
|
|
54
|
+
- `references/brand-kit-setup.md`: check the Brand Kit and set it up from a website, a brand doc or direct answers; "Make a kit style from slides" (Direct mode) turns slides the person likes into a slideshow style on a new or existing kit.
|
|
53
55
|
- `references/hooks.md`: writing and scoring headline candidates.
|
|
54
56
|
- `references/voice.md`: making every line read like a person posted it, with the self-check every
|
|
55
57
|
hook, card and caption passes (both modes).
|
|
56
58
|
- `references/layout-guide.md`: choosing a layout, resolution and safe zones.
|
|
57
59
|
- `references/design-critique.md`: the six-criterion score applied to every draft before it is shown.
|
|
58
60
|
- `references/realism-check.md`: the check every generated or library photo passes.
|
|
59
|
-
- `references/slideshow-formats.md`: native slideshow spec, archetypes and text rules for organic posts.
|
|
61
|
+
- `references/slideshow-formats.md`: native slideshow spec, style (native default, kit style, one-off style), archetypes and text rules for organic posts.
|
|
60
62
|
- `references/rubric.md`: the judging rubric the creative director uses (Team).
|
|
61
63
|
- `references/capabilities.md`: what Conductor can render, and what needs filming (Team).
|
|
62
64
|
- `references/platform-specs.md`: per-platform formats, lengths and limits (Team).
|
|
@@ -43,3 +43,31 @@ making anything:
|
|
|
43
43
|
a trial offer or similar in the caption instead. Verify with `get_brand_kit` —
|
|
44
44
|
`configured` should now read `true`.
|
|
45
45
|
- **Skip for now**: proceed; the skill below will render against the default kit as given.
|
|
46
|
+
|
|
47
|
+
A kit can also carry a slideshow style (the look of organic slideshows); it is optional, and native is
|
|
48
|
+
the default. `update_brand_kit` sets it (`slideshowStyle`, fields in `references/slideshow-formats.md`).
|
|
49
|
+
|
|
50
|
+
## Make a kit style from slides
|
|
51
|
+
|
|
52
|
+
Triggers: "I like these slides", "I like this look", "make a kit (style) from it". Never change the
|
|
53
|
+
default kit, and never delete anything.
|
|
54
|
+
|
|
55
|
+
1. **Identify the slides and read their style.**
|
|
56
|
+
- A Creative (display id such as `12a`): `get_creative` and read `slideStyle`. A CAROUSEL with a
|
|
57
|
+
null `slideStyle` was made before styles were recorded: treat it as the native defaults and say so.
|
|
58
|
+
- A local slideshow folder (`.conductor/slideshows/*/spec.json`): read the spec's top-level `resolvedStyle`
|
|
59
|
+
(the full look that was composed; the spec's own `style` is only the partial input). A folder
|
|
60
|
+
with neither `resolvedStyle` nor `style` was made before styles were recorded: treat it as the
|
|
61
|
+
native defaults and say so (the same as a Creative with a null `slideStyle`).
|
|
62
|
+
- Images designed elsewhere: look at them, sample the colours (text box, text, outline, accent),
|
|
63
|
+
and ask the person for the font name (and a Google Fonts link if it is one). Compose one sample
|
|
64
|
+
slide with `compose_slideshow` and that inline `style`, show it, and continue only once they
|
|
65
|
+
say it matches.
|
|
66
|
+
2. **Ask once** (`AskUserQuestion`): a new kit, or add it to an existing kit.
|
|
67
|
+
- **New kit:** ask for a name. Offer `copyFrom` the current kit so copy rules, voice, tokens and
|
|
68
|
+
font carry over; call `create_brand_kit({name, slideshowStyle, copyFrom?})`. Logos are not
|
|
69
|
+
copied: offer `upload_brand_image` for the new kit's slots.
|
|
70
|
+
- **Existing kit:** `get_brand_kit({kitId})` first. If it already has a `slideshowStyle`, say it
|
|
71
|
+
will be replaced and show the old one, then `update_brand_kit({kitId, slideshowStyle})`.
|
|
72
|
+
3. **Verify** with `get_brand_kit({kitId})`: `slideshowStyle` matches what was sent. Report the kit
|
|
73
|
+
name and how to use it (pick it at the kit question, or pass `brandKitId` to `compose_slideshow`).
|
|
@@ -36,6 +36,9 @@ only what the choice needs: one or two follow-up questions, not a form.
|
|
|
36
36
|
slides with `compose_slideshow`, then post them as a CAROUSEL Creative. Read
|
|
37
37
|
`references/slideshow-formats.md` first; it covers the spec, archetypes, text rules and the flow.
|
|
38
38
|
No logo, badge or offer goes on the slides, and the brand layouts below do not apply.
|
|
39
|
+
Style is native unless the person asks for a kit's look or a kit has a slideshow style; the
|
|
40
|
+
"Style" section there says how to offer it once and pass it through. The brand kit (the
|
|
41
|
+
Creative's `brandKitId`) and the style source (`compose_slideshow`'s `brandKitId`) are separate.
|
|
39
42
|
- **An ad** (a paid placement, or art that must carry the brand lockup and CTA): use the brand
|
|
40
43
|
layouts (STILL) as described below.
|
|
41
44
|
- **A video**, a **clip** or **finished images**: see their sections below.
|
|
@@ -339,10 +342,10 @@ thing).
|
|
|
339
342
|
result, so retry only the ones with an `error`. Find an already uploaded set with
|
|
340
343
|
`list_creative_media({labelPrefix: "01-import"})` rather than uploading again. `label`, `source`
|
|
341
344
|
and `licence` can't exceed 200 characters.
|
|
342
|
-
2. Local files: `preview_creative_draft({kind: "CAROUSEL", caption, slidePaths: {"4x5": [path, ...]}})`
|
|
345
|
+
2. Local files: `preview_creative_draft({kind: "CAROUSEL", brandKitId, caption, slidePaths: {"4x5": [path, ...]}})`
|
|
343
346
|
returns a contact sheet per placement (slides in order), readiness and any violations; look at it
|
|
344
347
|
with the person, then `commit_creative_draft` (it uploads in order and requests the render).
|
|
345
|
-
Media already in the library: `create_creative({kind: "CAROUSEL", slides: {"4x5": [mediaId, ...]}, slideAltText, caption})`
|
|
348
|
+
Media already in the library: `create_creative({kind: "CAROUSEL", brandKitId, slides: {"4x5": [mediaId, ...]}, slideAltText, caption})`
|
|
346
349
|
and then `render_creative` (instant, server-side).
|
|
347
350
|
3. Placements. `slides` is a list per placement key (`4x5`, `9x16`, `1x1`); `default` is the
|
|
348
351
|
fallback for a placement with no list of its own. Each image must match its placement's aspect
|
|
@@ -4,8 +4,8 @@ For organic posts: a native-looking photo slideshow (TikTok photo post, Instagra
|
|
|
4
4
|
promotes an app or product by being worth watching first. Build it with `compose_slideshow`, then
|
|
5
5
|
post it as a CAROUSEL Creative. Ads use the brand layouts (STILL) instead; this is not the ad path.
|
|
6
6
|
|
|
7
|
-
Branding is light: no logo, badge or offer on the slides
|
|
8
|
-
opener.
|
|
7
|
+
Branding is light: no logo, badge or offer on the slides, and the product appears as the payoff, not
|
|
8
|
+
the opener. The look of the text (font, colours, sizes) is separate and optional: see Style.
|
|
9
9
|
|
|
10
10
|
## Post anatomy
|
|
11
11
|
|
|
@@ -103,6 +103,49 @@ photo full-bleed at 9:16 uses 675x1200 source pixels, a 1.6x upscale. Check ever
|
|
|
103
103
|
the largest size in that aspect (`aspect: "9:16"`), use a different photo, or use a slide type that
|
|
104
104
|
shows the photo framed at or below native size (such as `grid` or `stack`).
|
|
105
105
|
|
|
106
|
+
## Style
|
|
107
|
+
|
|
108
|
+
The native look (TikTok Sans, white and black text boxes, a pink callout accent) is the default and
|
|
109
|
+
needs no setup. A slideshow can instead take the look of a Brand Kit's `slideshowStyle`, or a one-off
|
|
110
|
+
inline `style`, or both (the kit's style first, the inline fields on top).
|
|
111
|
+
|
|
112
|
+
Two separate choices, never conflated:
|
|
113
|
+
|
|
114
|
+
- **The brand kit** (SKILL.md "Brand kit first": the kit question, or the default) is the Creative's
|
|
115
|
+
`brandKitId`. Pass it on every `preview_creative_draft` / `create_creative` call whenever it is not
|
|
116
|
+
the default kit. Choosing "native look" never changes it.
|
|
117
|
+
- **The style source** is either native or a kit whose `slideshowStyle` is used. That kit's id goes
|
|
118
|
+
only to `compose_slideshow`'s `brandKitId`. A kit used only for its look never becomes the
|
|
119
|
+
Creative's brand kit unless it is also the brand kit.
|
|
120
|
+
|
|
121
|
+
- **When to offer the choice.** Ask once, never twice in a run, when the person asks for a kit's look
|
|
122
|
+
or when a kit with a slideshow style exists (`get_brand_kit`'s `slideshowStyle` is set, or an
|
|
123
|
+
`otherKits[]` entry has `hasSlideshowStyle: true`). Options: "Native look" first, then each styled
|
|
124
|
+
kit (up to 4 options in all). No styled kit and no request: do not ask, use native.
|
|
125
|
+
- **Team mode.** One question before S0 covers whatever choice exists, and there is never more than
|
|
126
|
+
one (a single `AskUserQuestion` call; it may carry the kit part and the look part together):
|
|
127
|
+
several kits and none named: which kit and, if any kit has a slideshow style, native vs that look;
|
|
128
|
+
a single kit that has a `slideshowStyle`: native vs the kit's look; nothing to choose: no question.
|
|
129
|
+
Store the answers in `run.json` (`brandKitId`, and `slideshowStyle: {"styleKitId": "<id>" | null,
|
|
130
|
+
"style": {...} | null}`, where a null `styleKitId` is native) and reuse them on resume.
|
|
131
|
+
- **Compose.** Pass `brandKitId` (the style source kit only; a kit with no slideshow style is refused
|
|
132
|
+
with a clear error: fall back to native or set one with `update_brand_kit`) and/or `style` (`fontFamily` as a name or a comma list such as `Inter, sans-serif`, `fontUrl` for an https
|
|
133
|
+
Google Fonts stylesheet, `boxBg`, `boxInk`, `darkBg`, `darkInk`, `strokeInk` (outlined text and sub text, white by default), `outline`, `accent` as `#RRGGBB`,
|
|
134
|
+
`defaultText` of `box|dark|stroke`, `textSize` 24-120, `subSize` 16-96). In `style` (and in a
|
|
135
|
+
spec's own `style`) a field you leave out inherits from the layer below; a field set to `null`
|
|
136
|
+
resets that field to the native value (`fontFamily: null` is the bundled TikTok Sans with no
|
|
137
|
+
`fontUrl`). Notes, week, receipt,
|
|
138
|
+
placard and messages slides keep their system-UI fonts by design. A custom font that fails to load,
|
|
139
|
+
or a `fontFamily` that is not installed when there is no `fontUrl`, is a blocking `font` check naming the family.
|
|
140
|
+
- **Record it.** The result's `style` and the output `spec.json`'s `resolvedStyle` are the full object,
|
|
141
|
+
native defaults included (the spec's own `style` is kept as you wrote it). Layers: native, then
|
|
142
|
+
the kit (`brandKitId`), then the spec's `style`, then the inline `style`; re-composing an output
|
|
143
|
+
`spec.json` ignores `resolvedStyle`. Pass it as `slideStyle` on `preview_creative_draft` / `create_creative`
|
|
144
|
+
so every composed slideshow has a style that can later become a kit style
|
|
145
|
+
(`references/brand-kit-setup.md`, "Make a kit style from slides"). A saved Creative keeps its `slideStyle`
|
|
146
|
+
unless `update_creative` (or a draft over `baseCreativeId`) changes the slides without sending a
|
|
147
|
+
`slideStyle`, which clears it; send the new `style` with the new slides, or `slideStyle: null` to clear it.
|
|
148
|
+
|
|
106
149
|
## Honesty and brand
|
|
107
150
|
|
|
108
151
|
- No logo, badge or offer on the slides. The offer, if any, goes in the caption.
|
|
@@ -125,10 +168,14 @@ Captions on TikTok and Instagram cannot hold clickable links, so do not rely on
|
|
|
125
168
|
|
|
126
169
|
## Flow
|
|
127
170
|
|
|
128
|
-
1. Write the spec (`slideshow-spec.json`); call `compose_slideshow({specPath})
|
|
171
|
+
1. Write the spec (`slideshow-spec.json`); call `compose_slideshow({specPath})`, adding the *style
|
|
172
|
+
source* kit as `brandKitId` (only when the look comes from a kit) and/or `style` per Style above.
|
|
173
|
+
Omit `brandKitId` for the native look.
|
|
129
174
|
2. If `passed` is false, fix every `error` check and compose again. Warnings are advisory.
|
|
130
|
-
3. `preview_creative_draft({kind: "CAROUSEL", slidePaths, caption, slideAltText})`
|
|
131
|
-
returned `slidePaths` (`9x16` for TikTok, `4x5` for Instagram).
|
|
175
|
+
3. `preview_creative_draft({kind: "CAROUSEL", brandKitId: <the Creative's brand kit>, slidePaths, slideStyle, caption, slideAltText})`
|
|
176
|
+
using the returned `slidePaths` and `style` (as `slideStyle`) (`9x16` for TikTok, `4x5` for Instagram).
|
|
177
|
+
The `brandKitId` here is the *brand kit*, not the style source: pass it whenever it is not the
|
|
178
|
+
default kit, and leave it out for the default, whatever the look. Look at the contact sheet and show
|
|
132
179
|
it.
|
|
133
180
|
With music (`audio: {source: "track", trackId}`, a library track from
|
|
134
181
|
`list_creative_media({kind: "AUDIO"})`; a new file is uploaded there first with its source and
|
|
@@ -23,13 +23,17 @@ Each exists because of a known failure mode (sources are in `references/rubric.m
|
|
|
23
23
|
own leader.
|
|
24
24
|
- **One gate.** The person is asked only at the final draft preview. Do not stop to ask which idea.
|
|
25
25
|
Two exceptions: S5b's disclosure question, asked only when disclosure cannot be inferred; and the
|
|
26
|
-
|
|
27
|
-
|
|
26
|
+
pre-S0 question, at most one before S0, covering whatever choice exists: several kits and none
|
|
27
|
+
named, which kit (SKILL.md "Brand kit first") and, if any kit has a slideshow style, native vs that
|
|
28
|
+
look; a single kit that has a slideshow style, native vs the kit's look; nothing to choose, no
|
|
29
|
+
question (`references/slideshow-formats.md`, "Style"). A resumed run reuses the `brandKitId` and
|
|
30
|
+
`slideshowStyle` stored in `run.json`; the brand kit and the style source are separate answers.
|
|
28
31
|
- **A run never creates a Post.** It ends at a committed Creative (or a shoot script).
|
|
29
32
|
- **Organic posts default to a slideshow.** A `RENDER` idea for an organic post (not an ad) is a
|
|
30
33
|
native-looking slideshow built by `compose_slideshow` and posted as a CAROUSEL; see
|
|
31
34
|
`references/slideshow-formats.md`. STILL and MOTION stay for ideas that really are one still, an
|
|
32
|
-
ad, or a motion piece. A slideshow never carries a logo, badge or offer
|
|
35
|
+
ad, or a motion piece. A slideshow never carries a logo, badge or offer; its text look is native
|
|
36
|
+
unless the run's choice names a kit style or an inline `style`.
|
|
33
37
|
- **Rejected copy stays rejected.** A CTA or offer line on a card or in a caption is opt-in per
|
|
34
38
|
request, never a default. That means a sales line: the kit's `ctaClaim`, a trial, price, plan or
|
|
35
39
|
discount. Naming the app so it can be searched is not one. Approved lines in the knowledge pages are allowed, not required. When the
|
|
@@ -75,6 +79,7 @@ shoot/ shoot-script.md (FILM winner only)
|
|
|
75
79
|
"S6": "pending"},
|
|
76
80
|
"idMap": {"I1": {"angle": "story/emotion", "file": "ideas/angle-1.md", "n": 3}},
|
|
77
81
|
"brandKitId": null,
|
|
82
|
+
"slideshowStyle": {"styleKitId": null, "style": null},
|
|
78
83
|
"finalists": [], "winner": null, "tag": null, "runnerUps": [],
|
|
79
84
|
"tags": {"hookType": null, "angle": null, "format": null},
|
|
80
85
|
"drafts": {"finalist-I3": "<absolute dir>", "final": "<absolute dir>"},
|
|
@@ -88,8 +93,8 @@ linked to IDs; it is never shown to the director.
|
|
|
88
93
|
**Resume check (first thing).** Glob `.conductor/content-runs/*/run.json`. If one has a stage that is
|
|
89
94
|
not `done` or `skipped` and no `creativeId` or `shootDoc`, ask with `AskUserQuestion` whether to
|
|
90
95
|
**Resume** that run (name it and its last finished stage) or **Start a new run**. On resume, skip
|
|
91
|
-
done stages and continue from the first pending one, using the `brandKitId`
|
|
92
|
-
`run.json`; never ask the
|
|
96
|
+
done stages and continue from the first pending one, using the `brandKitId` and
|
|
97
|
+
`slideshowStyle` already in `run.json`; never ask the pre-S0 question again for a run that has them stored.
|
|
93
98
|
|
|
94
99
|
## Delegation prompt template
|
|
95
100
|
|
|
@@ -117,8 +122,9 @@ has failed the stage: retry once with a one-line reminder, then tell the person.
|
|
|
117
122
|
|
|
118
123
|
Write `request.md` (the request verbatim, `--quick` if given, the platform if stated). Then:
|
|
119
124
|
|
|
120
|
-
1. Resolve the kit (SKILL.md "Brand kit first": the named kit, else
|
|
121
|
-
|
|
125
|
+
1. Resolve the kit (SKILL.md "Brand kit first": the named kit, else the one pre-S0 question from
|
|
126
|
+
"One gate" when there is a choice to make), store its id in `run.json` as `brandKitId` (and the
|
|
127
|
+
look as `slideshowStyle.styleKitId`, null = native), and write `get_brand_kit({kitId})` ->
|
|
122
128
|
`context/brand-kit.json`. Use that kit's `knowledgePagePath` and copy rules below. If `configured` is false and the person already
|
|
123
129
|
skipped setup in the command, note that in the brief's constraints.
|
|
124
130
|
2. Knowledge, for `context/knowledge.md`: `read_knowledge_pages` for the kit's `knowledgePagePath`
|
|
@@ -201,7 +207,7 @@ Draft each finalist the judge named (up to three).
|
|
|
201
207
|
A slideshow finalist has no cheap draft: judge it from its idea text (archetype and slide-by-slide
|
|
202
208
|
text) unless its slides can be composed from photos already on hand. In that case write its spec to
|
|
203
209
|
`<run>/drafts/finalist-<id>/slideshow-spec.json`, call `compose_slideshow` with `draftDir` set to
|
|
204
|
-
that folder and judge from the first slide and the `checks`. For every other `RENDER` finalist, call `preview_creative_draft` (with `brandKitId` from `run.json`) with that idea's draft spec (map the
|
|
210
|
+
that folder, passing `slideshowStyle.styleKitId` as `brandKitId` and/or `slideshowStyle.style` as `style` (as at S6), and judge from the first slide and the `checks`. For every other `RENDER` finalist, call `preview_creative_draft` (with `brandKitId` from `run.json`) with that idea's draft spec (map the
|
|
205
211
|
draft-spec block to the tool's fields) and `draftDir` set to `<run>/drafts/finalist-<id>`. Use
|
|
206
212
|
`full: false`. Record each draft dir in `run.json`. For a finalist whose draft spec carries an
|
|
207
213
|
`imagePrompt`, write the prompt by the prompt-writing rules in `references/realism-check.md` and
|
|
@@ -330,8 +336,10 @@ any placement is fixed now, not shown.
|
|
|
330
336
|
returned `draftDir` as `drafts.final`. Local files (`photoPath`, `clipPath`, `audioPath`) go in
|
|
331
337
|
as given in the spec.
|
|
332
338
|
**Slideshow winner:** `compose_slideshow({specPath})` on `slideshow-spec.json`; while `passed` is
|
|
333
|
-
false, fix the spec and compose again.
|
|
334
|
-
|
|
339
|
+
false, fix the spec and compose again. Pass `slideshowStyle.styleKitId` as `compose_slideshow`'s `brandKitId` (omit for native) and/or `slideshowStyle.style` as `style`
|
|
340
|
+
(layers: native, then the kit, then the spec's own top-level `style`, then the inline `style`); keep the
|
|
341
|
+
result's `style`. Then
|
|
342
|
+
`preview_creative_draft({kind: "CAROUSEL", brandKitId: <run.json brandKitId, the Creative's brand kit>, slidePaths, slideStyle: style, caption, slideAltText})` with the returned `slidePaths` (`9x16` for TikTok, `4x5` for Instagram),
|
|
335
343
|
the caption from `publish-pack.json` and the alt text from `direction.md`. Record the preview's
|
|
336
344
|
`draftDir` as `drafts.final`.
|
|
337
345
|
**Music:** a slideshow or clip with music uses `audio` on the Creative, and a track from
|