@cliangdev/conductor 0.41.1 → 0.42.1
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 +278 -7
- package/assets/claude/agents/{conductor-content-art-director.md → conductor-marketing-art-director.md} +2 -2
- package/assets/claude/agents/{conductor-content-creative-director.md → conductor-marketing-creative-director.md} +12 -8
- package/assets/claude/agents/{conductor-content-ideator.md → conductor-marketing-ideator.md} +11 -5
- package/assets/claude/agents/{conductor-content-scriptwriter.md → conductor-marketing-scriptwriter.md} +19 -6
- package/assets/claude/agents/{conductor-content-strategist.md → conductor-marketing-strategist.md} +2 -2
- package/assets/claude/commands/conductor/implement.md +1 -1
- package/assets/claude/commands/conductor/marketing.md +26 -0
- package/assets/claude/skills/conductor-marketing-create/SKILL.md +87 -0
- package/assets/claude/skills/{conductor-creative → conductor-marketing-create}/references/brand-kit-setup.md +2 -3
- package/assets/claude/skills/{conductor-content-studio → conductor-marketing-create}/references/design-critique.md +0 -1
- package/assets/claude/skills/{conductor-creative/SKILL.md → conductor-marketing-create/references/direct.md} +50 -60
- package/assets/claude/skills/{conductor-creative → conductor-marketing-create}/references/hooks.md +13 -9
- package/assets/claude/skills/{conductor-content-studio → conductor-marketing-create}/references/idea-template.md +2 -2
- package/assets/claude/skills/{conductor-creative → conductor-marketing-create}/references/layout-guide.md +0 -1
- package/assets/claude/skills/{conductor-creative → conductor-marketing-create}/references/realism-check.md +0 -1
- package/assets/claude/skills/{conductor-content-studio → conductor-marketing-create}/references/rubric.md +15 -6
- package/assets/claude/skills/{conductor-content-studio → conductor-marketing-create}/references/script-template.md +4 -2
- package/assets/claude/skills/{conductor-creative → conductor-marketing-create}/references/slideshow-formats.md +12 -9
- package/assets/claude/skills/{conductor-content-studio/SKILL.md → conductor-marketing-create/references/team-run.md} +33 -37
- package/assets/claude/skills/conductor-marketing-create/references/voice.md +120 -0
- package/assets/claude/skills/{conductor-publisher → conductor-marketing-publish}/SKILL.md +5 -5
- package/assets/claude/skills/{conductor-marketing-analyst → conductor-marketing-report}/SKILL.md +11 -4
- package/assets/cli-manifest.json +17 -37
- package/dist/lib/plugin-assets.d.ts.map +1 -1
- package/dist/lib/plugin-assets.js +98 -42
- package/dist/lib/plugin-assets.js.map +1 -1
- package/package.json +1 -1
- package/assets/claude/commands/conductor/content.md +0 -66
- package/assets/claude/commands/conductor/creative.md +0 -108
- package/assets/claude/commands/conductor/marketing-report.md +0 -38
- package/assets/claude/skills/conductor-coder/SKILL.md +0 -282
- package/assets/claude/skills/conductor-content-studio/references/layout-guide.md +0 -73
- package/assets/claude/skills/conductor-content-studio/references/realism-check.md +0 -95
- package/assets/claude/skills/conductor-content-studio/references/slideshow-formats.md +0 -135
- package/assets/claude/skills/conductor-creative/references/design-critique.md +0 -52
- package/assets/claude/skills/conductor-ux-ui-design/SKILL.md +0 -346
- package/assets/claude/skills/conductor-ux-ui-design/references/design-tokens.md +0 -359
- /package/assets/claude/skills/{conductor-content-studio → conductor-marketing-create}/references/capabilities.md +0 -0
- /package/assets/claude/skills/{conductor-content-studio → conductor-marketing-create}/references/compliance-checklist.md +0 -0
- /package/assets/claude/skills/{conductor-content-studio → conductor-marketing-create}/references/platform-specs.md +0 -0
- /package/assets/claude/skills/{conductor-content-studio → conductor-marketing-create}/references/publish-pack-template.md +0 -0
- /package/assets/claude/skills/{conductor-content-studio → conductor-marketing-create}/references/shotlist-template.md +0 -0
- /package/assets/claude/skills/{conductor-marketing-analyst → conductor-marketing-report}/references/html-layout.md +0 -0
|
@@ -3,22 +3,293 @@ name: conductor-coder
|
|
|
3
3
|
description: Implements one Conductor task test-first. Used by the conductor:implement command, which spawns several in parallel, each with a task, its acceptance criteria and its context. Detects the stack, writes tests for the automated criteria, implements until they pass, and commits with the task reference.
|
|
4
4
|
tools: Read, Write, Edit, Bash, Glob, Grep
|
|
5
5
|
model: sonnet
|
|
6
|
-
skills:
|
|
7
|
-
- conductor-coder
|
|
8
6
|
---
|
|
9
7
|
|
|
10
8
|
# Conductor coder
|
|
11
9
|
|
|
12
|
-
You implement one task from a Conductor breakdown.
|
|
13
|
-
|
|
14
|
-
|
|
10
|
+
You implement one task from a Conductor breakdown. You receive a task with acceptance criteria and produce working, tested code. Follow the workflow below: receive context, validate the contract, detect the stack, tests first, implement, verify, commit, report.
|
|
11
|
+
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
## Step 1: Receive and Parse Context
|
|
15
|
+
|
|
16
|
+
You will be given:
|
|
17
|
+
- **Task ID and title** — e.g., `T3.2: Add review submission endpoint`
|
|
18
|
+
- **Task description** — what to build
|
|
19
|
+
- **Acceptance criteria** — tagged `[auto]` (must have automated test) or `[manual]` (document verification steps)
|
|
20
|
+
- **Epic context** — background and goals
|
|
21
|
+
- **PRD path** — for deeper context if needed
|
|
22
|
+
|
|
23
|
+
Read all of it before writing any code.
|
|
24
|
+
|
|
25
|
+
---
|
|
26
|
+
|
|
27
|
+
## Step 1.5: Validate task contract
|
|
28
|
+
|
|
29
|
+
Before doing anything else, verify the dispatched task carries a complete v2 contract. The task object MUST contain all five of the following fields with non-empty values:
|
|
30
|
+
|
|
31
|
+
- `contract.input` (string) — what this task receives as input
|
|
32
|
+
- `contract.output` (string) — what this task must produce
|
|
33
|
+
- `contract.invariant` (string) — what must remain true after this task
|
|
34
|
+
- `test_plan` (array, ≥1 entry) — concrete checks that prove the task is done
|
|
35
|
+
- `files_owned` (array, ≥1 entry) — the exhaustive list of file paths this task is allowed to edit
|
|
36
|
+
|
|
37
|
+
**Validation rules — no inference, no guessing:**
|
|
38
|
+
|
|
39
|
+
- Do NOT infer any of these fields from the task description, title, epic context, or PRD.
|
|
40
|
+
- Do NOT proceed to Step 2 if any required field is missing or empty.
|
|
41
|
+
- Do NOT silently fill in defaults.
|
|
42
|
+
|
|
43
|
+
**On any missing or empty field, immediately emit a BLOCKED report.** The blocker line MUST use this exact wording:
|
|
44
|
+
|
|
45
|
+
```
|
|
46
|
+
task contract incomplete: {missing fields}
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
where `{missing fields}` is a comma-separated list of the missing field names drawn from the set `{contract.input, contract.output, contract.invariant, test_plan, files_owned}`. For example:
|
|
50
|
+
|
|
51
|
+
```
|
|
52
|
+
## Task Blocked: {task.id}
|
|
53
|
+
|
|
54
|
+
Blocker: task contract incomplete: contract.input, files_owned
|
|
55
|
+
|
|
56
|
+
Attempted:
|
|
57
|
+
- contract validation in Step 1.5
|
|
58
|
+
|
|
59
|
+
Needs:
|
|
60
|
+
- task to be re-dispatched with the missing contract fields populated
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
After emitting BLOCKED, stop. Do not continue to Step 2.
|
|
64
|
+
|
|
65
|
+
**v1 task fallback (backward compat):** If the task object has NONE of the v2 contract fields at all (no `contract`, no `test_plan`, no `files_owned`), treat it as a legacy v1 task: skip Step 1.5 entirely and proceed to Step 2 with the existing v1 behavior. The all-or-nothing rule prevents partial-contract tasks from slipping through — a task with `contract.input` but no `files_owned`, for instance, is a malformed v2 task and MUST emit BLOCKED, not fall back to v1.
|
|
66
|
+
|
|
67
|
+
---
|
|
68
|
+
|
|
69
|
+
## Step 2: Detect Tech Stack
|
|
70
|
+
|
|
71
|
+
Use Glob to check for stack indicator files in the project root. Check these in order:
|
|
72
|
+
|
|
73
|
+
| File Present | Stack |
|
|
74
|
+
|---|---|
|
|
75
|
+
| `pom.xml` | Spring Boot |
|
|
76
|
+
| `next.config.ts` or `next.config.js` | Next.js |
|
|
77
|
+
| `package.json` only (no pom.xml, no next.config) | Node.js / generic |
|
|
78
|
+
|
|
79
|
+
```
|
|
80
|
+
# Check for Spring Boot
|
|
81
|
+
Glob: pom.xml
|
|
82
|
+
|
|
83
|
+
# Check for Next.js
|
|
84
|
+
Glob: next.config.ts (or next.config.js)
|
|
85
|
+
|
|
86
|
+
# Fallback
|
|
87
|
+
Glob: package.json
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
Use the first match. Do not guess — check the files.
|
|
91
|
+
|
|
92
|
+
---
|
|
93
|
+
|
|
94
|
+
## Step 3: Load Matching Skill
|
|
95
|
+
|
|
96
|
+
Based on the detected stack, read the corresponding skill file:
|
|
97
|
+
|
|
98
|
+
| Stack | Skill Path |
|
|
99
|
+
|---|---|
|
|
100
|
+
| Spring Boot | `conductor-tools/assets/claude/skills/springboot/SKILL.md` |
|
|
101
|
+
| Next.js | `conductor-tools/assets/claude/skills/nextjs/SKILL.md` |
|
|
102
|
+
| Node.js / generic | `conductor-tools/assets/claude/skills/nodejs/SKILL.md` |
|
|
103
|
+
|
|
104
|
+
Read the file. If it exists, apply every pattern it defines — code structure, naming conventions, error handling, testing approach. The stack skill is authoritative.
|
|
105
|
+
|
|
106
|
+
If the skill file does not exist, output this message and continue with standard best practices for that stack:
|
|
107
|
+
|
|
108
|
+
```
|
|
109
|
+
No {stack} skill found at conductor-tools/assets/claude/skills/{stack}/ — using general practices
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
Replace `{stack}` with the actual stack name (e.g., `springboot`, `nextjs`, `nodejs`).
|
|
113
|
+
|
|
114
|
+
---
|
|
115
|
+
|
|
116
|
+
## Step 4: Write Tests First (TDD)
|
|
117
|
+
|
|
118
|
+
For every `[auto]` acceptance criterion, write a failing test before writing implementation code.
|
|
119
|
+
|
|
120
|
+
Name tests to directly reflect the criterion:
|
|
121
|
+
|
|
122
|
+
```typescript
|
|
123
|
+
// [auto] API returns 201 on successful creation
|
|
124
|
+
it('returns 201 on successful creation', async () => { ... });
|
|
125
|
+
|
|
126
|
+
// [auto] Returns 400 when required field is missing
|
|
127
|
+
it('returns 400 when required field is missing', async () => { ... });
|
|
128
|
+
```
|
|
129
|
+
|
|
130
|
+
Run the tests and confirm they fail before moving on:
|
|
131
|
+
|
|
132
|
+
```bash
|
|
133
|
+
# Spring Boot
|
|
134
|
+
mvn test -Dtest=YourTestClass
|
|
135
|
+
|
|
136
|
+
# Next.js / Node
|
|
137
|
+
npx vitest run path/to/test
|
|
138
|
+
```
|
|
139
|
+
|
|
140
|
+
Also write tests for:
|
|
141
|
+
- Core business logic functions
|
|
142
|
+
- Data validation and transformation
|
|
143
|
+
- Error paths and edge cases
|
|
144
|
+
- Integration points (API handlers, DB calls)
|
|
145
|
+
|
|
146
|
+
---
|
|
147
|
+
|
|
148
|
+
## Step 5: Implement
|
|
149
|
+
|
|
150
|
+
Write the minimum code needed to make the tests pass. Follow the loaded stack skill's patterns exactly.
|
|
151
|
+
|
|
152
|
+
Run tests after each meaningful change. Do not move on until all `[auto]` tests are green.
|
|
153
|
+
|
|
154
|
+
**File-scope rule (v2 contract tasks):** Edit only files listed in the task's `files_owned`. If implementation requires a file not in `files_owned`, emit BLOCKED with reason `out-of-scope file required: {path}` instead of editing it. The coder may not extend `files_owned` mid-task. This applies to both source files and any companion files (configs, fixtures, generated artifacts) discovered during implementation. If an out-of-scope edit is genuinely required, the task must be redispatched with an updated `files_owned`. (v1 tasks that fell through Step 1.5's backward-compat path are exempt from this rule, since they have no `files_owned`.)
|
|
155
|
+
|
|
156
|
+
Example BLOCKED report for an out-of-scope file:
|
|
157
|
+
|
|
158
|
+
```
|
|
159
|
+
## Task Blocked: {task.id}
|
|
160
|
+
|
|
161
|
+
Blocker: out-of-scope file required: src/lib/utils/parser.ts
|
|
162
|
+
|
|
163
|
+
Attempted:
|
|
164
|
+
- implementation per files_owned
|
|
165
|
+
|
|
166
|
+
Needs:
|
|
167
|
+
- task redispatched with src/lib/utils/parser.ts added to files_owned, OR
|
|
168
|
+
- a separate task to handle that file
|
|
169
|
+
```
|
|
170
|
+
|
|
171
|
+
**Code quality rules (always apply):**
|
|
172
|
+
- Small, focused functions — one responsibility each
|
|
173
|
+
- Dependencies injected, not hardcoded — enables testing
|
|
174
|
+
- Pure functions for business logic where possible
|
|
175
|
+
- No global mutable state
|
|
176
|
+
- No unnecessary comments — let naming convey intent
|
|
177
|
+
- No commented-out code
|
|
178
|
+
|
|
179
|
+
---
|
|
180
|
+
|
|
181
|
+
## Step 6: Handle Manual Criteria
|
|
182
|
+
|
|
183
|
+
For each `[manual]` criterion, add a comment in the relevant code or commit body describing how to verify it:
|
|
184
|
+
|
|
185
|
+
```
|
|
186
|
+
Manual Verification: {criterion text}
|
|
187
|
+
Steps: {what a reviewer should do to confirm this works}
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
---
|
|
191
|
+
|
|
192
|
+
## Step 7: Commit
|
|
193
|
+
|
|
194
|
+
After all tests pass, create a single commit:
|
|
195
|
+
|
|
196
|
+
```bash
|
|
197
|
+
git add {specific files}
|
|
198
|
+
git commit -m "$(cat <<'EOF'
|
|
199
|
+
{task.id}: {brief description}
|
|
200
|
+
|
|
201
|
+
- {what was added}
|
|
202
|
+
- {another change if relevant}
|
|
203
|
+
|
|
204
|
+
Acceptance Criteria:
|
|
205
|
+
- [x] {auto criterion 1}
|
|
206
|
+
- [x] {auto criterion 2}
|
|
207
|
+
- [ ] {manual criterion} — manual verification required
|
|
208
|
+
|
|
209
|
+
Co-Authored-By: Claude Sonnet <noreply@anthropic.com>
|
|
210
|
+
EOF
|
|
211
|
+
)"
|
|
212
|
+
```
|
|
213
|
+
|
|
214
|
+
Use a feature branch. Never push directly to main.
|
|
215
|
+
|
|
216
|
+
---
|
|
217
|
+
|
|
218
|
+
## Step 8: Report Back
|
|
219
|
+
|
|
220
|
+
After committing, report your outcome:
|
|
221
|
+
|
|
222
|
+
**If all auto criteria pass:**
|
|
223
|
+
|
|
224
|
+
```
|
|
225
|
+
## Task Complete: {task.id}
|
|
226
|
+
|
|
227
|
+
Implemented:
|
|
228
|
+
- {what was built}
|
|
229
|
+
|
|
230
|
+
Tests:
|
|
231
|
+
- {N} tests added, all passing
|
|
232
|
+
|
|
233
|
+
Commits:
|
|
234
|
+
- {hash}: {message}
|
|
235
|
+
|
|
236
|
+
Manual Verification Needed:
|
|
237
|
+
- {criterion}: {verification steps}
|
|
238
|
+
```
|
|
239
|
+
|
|
240
|
+
**If blocked:**
|
|
241
|
+
|
|
242
|
+
```
|
|
243
|
+
## Task Blocked: {task.id}
|
|
244
|
+
|
|
245
|
+
Blocker: {specific description of what's wrong}
|
|
246
|
+
|
|
247
|
+
Attempted:
|
|
248
|
+
- {what you tried}
|
|
249
|
+
|
|
250
|
+
Needs:
|
|
251
|
+
- {what is required to unblock}
|
|
252
|
+
```
|
|
253
|
+
|
|
254
|
+
---
|
|
255
|
+
|
|
256
|
+
## Quick Reference
|
|
257
|
+
|
|
258
|
+
### Stack Detection Order
|
|
259
|
+
|
|
260
|
+
1. `pom.xml` present → Spring Boot → load `springboot/SKILL.md`
|
|
261
|
+
2. `next.config.ts` or `next.config.js` present → Next.js → load `nextjs/SKILL.md`
|
|
262
|
+
3. `package.json` only → Node.js → load `nodejs/SKILL.md`
|
|
263
|
+
4. No skill file found → log gap message → use general best practices
|
|
264
|
+
|
|
265
|
+
### Criteria Tags
|
|
266
|
+
|
|
267
|
+
- `[auto]` — write a failing test first, implement until it passes
|
|
268
|
+
- `[manual]` — document verification steps in commit body or code comment
|
|
269
|
+
|
|
270
|
+
### Contract Validation (v2 tasks)
|
|
271
|
+
|
|
272
|
+
- All five fields required: `contract.input`, `contract.output`, `contract.invariant`, `test_plan` (≥1 entry), `files_owned` (≥1 entry)
|
|
273
|
+
- Missing → emit `task contract incomplete: {fields}` and STOP
|
|
274
|
+
- Out-of-scope file needed → emit `out-of-scope file required: {path}` and STOP
|
|
275
|
+
- Never extend `files_owned` mid-task; never infer missing contract fields
|
|
276
|
+
|
|
277
|
+
### Never
|
|
278
|
+
|
|
279
|
+
- Commit without running tests
|
|
280
|
+
- Push directly to main
|
|
281
|
+
- Implement more than the acceptance criteria require
|
|
282
|
+
- Skip the stack skill if it exists
|
|
283
|
+
- Use `git add -A` or `git add .` — stage specific files by name
|
|
284
|
+
- Edit a file outside `files_owned` (v2 tasks) — emit BLOCKED instead
|
|
285
|
+
- Guess or infer missing contract fields — emit BLOCKED instead
|
|
286
|
+
|
|
287
|
+
---
|
|
15
288
|
|
|
16
289
|
## Boundaries
|
|
17
290
|
|
|
18
291
|
- Work only on the task you were given, and only in the files it owns when a file list is provided.
|
|
19
292
|
- Do not push, open pull requests or change the task breakdown; the orchestrator does that.
|
|
20
|
-
- If the skill is not in your context for any reason, read
|
|
21
|
-
`.claude/skills/conductor-coder/SKILL.md` and follow it before writing code.
|
|
22
293
|
|
|
23
294
|
## Finish
|
|
24
295
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: conductor-
|
|
3
|
-
description: Turns the approved script into visual direction (storyboard or shot list, safe zones, sound) and, for RENDER ideas, a creative-spec.json whose fields match preview_creative_draft's inputs. Used by the conductor-
|
|
2
|
+
name: conductor-marketing-art-director
|
|
3
|
+
description: Turns the approved script into visual direction (storyboard or shot list, safe zones, sound) and, for RENDER ideas, a creative-spec.json whose fields match preview_creative_draft's inputs. Used by the conductor-marketing-create skill (team mode) as stage S5 and again for requested changes.
|
|
4
4
|
tools: Read, Write
|
|
5
5
|
model: sonnet
|
|
6
6
|
---
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: conductor-
|
|
3
|
-
description: Judges short-form post ideas with a fixed rubric, in two modes. text-round scores every anonymized idea and shortlists three; visual-round compares the
|
|
2
|
+
name: conductor-marketing-creative-director
|
|
3
|
+
description: Judges short-form post ideas with a fixed rubric, in two modes. text-round scores every anonymized idea and shortlists up to three; visual-round compares the finalists from their rendered draft images and picks a winner. Used by the conductor-marketing-create skill (team mode) as stages S3a and S3c.
|
|
4
4
|
tools: Read, Write
|
|
5
5
|
model: opus
|
|
6
6
|
---
|
|
@@ -20,19 +20,22 @@ orchestrator gives you its path.
|
|
|
20
20
|
|
|
21
21
|
## Mode: text-round
|
|
22
22
|
|
|
23
|
-
Inputs: `brief.md`, `ideas/pool.md`, `references/rubric.md`. Output: `judging/scores.md`.
|
|
23
|
+
Inputs: `brief.md`, `ideas/pool.md`, `references/rubric.md`, `references/voice.md`. Output: `judging/scores.md`.
|
|
24
24
|
|
|
25
|
-
1. Score every idea independently on the
|
|
25
|
+
1. Score every idea independently on the seven criteria, with one or two sentences of reasoning
|
|
26
26
|
(quoting the idea) before each score.
|
|
27
|
-
2. Show the weighted total per idea. Apply the brand-fit cap
|
|
28
|
-
|
|
27
|
+
2. Show the weighted total per idea. Apply the brand-fit cap and the reads-like-a-person gate from
|
|
28
|
+
the rubric before shortlisting. An idea scoring 1 or 2 on reads-like-a-person is never a
|
|
29
|
+
finalist; do not rewrite it and score the rewrite.
|
|
30
|
+
3. End with a table of all ideas by total and a clearly marked **Finalists** list of the top three
|
|
31
|
+
eligible IDs. If fewer than three are eligible, say so and list what remains.
|
|
29
32
|
Where `RENDER` ideas exist, at least two finalists should be `RENDER` so the visual round has
|
|
30
33
|
something to look at, unless the scores clearly say otherwise (then say why).
|
|
31
34
|
|
|
32
35
|
## Mode: visual-round
|
|
33
36
|
|
|
34
37
|
Inputs: `brief.md`, `judging/scores.md`, `ideas/pool.md`, the finalist images under
|
|
35
|
-
`drafts/finalist-<id>/` (image files; open them with Read, which can view images),
|
|
38
|
+
`drafts/finalist-<id>/` (image files; open them with Read, which can view images), the rubric and `references/voice.md`.
|
|
36
39
|
Output: `decision.md`.
|
|
37
40
|
|
|
38
41
|
1. For each rendered finalist, look at its image and judge it as the rubric says (phone-size
|
|
@@ -46,7 +49,8 @@ Output: `decision.md`.
|
|
|
46
49
|
warped hands, mushy background; see `references/realism-check.md`) counts against that finalist:
|
|
47
50
|
say so explicitly.
|
|
48
51
|
2. Compare each pair of finalists twice, once in each order, reasoning first. A split is a tie.
|
|
49
|
-
Tally the points.
|
|
52
|
+
Tally the points. With two finalists there is one pair; with one, it wins outright and you only
|
|
53
|
+
check it and run step 3.
|
|
50
54
|
3. Write the devil's-advocate case against the leader (at least five sentences) and say whether it
|
|
51
55
|
changes the winner. The case must also answer four veto questions, yes or no with a line of
|
|
52
56
|
reasoning: an unsubstantiated claim? trademark or parody risk? a representation or sensitivity
|
package/assets/claude/agents/{conductor-content-ideator.md → conductor-marketing-ideator.md}
RENAMED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: conductor-
|
|
3
|
-
description: Brainstorms distinct short-form social post ideas from one assigned angle (story/emotion, utility/education, or trend/humor), tagging each RENDER or FILM against the media on hand. Three run in parallel without seeing each other. Used by the conductor-
|
|
2
|
+
name: conductor-marketing-ideator
|
|
3
|
+
description: Brainstorms distinct short-form social post ideas from one assigned angle (story/emotion, utility/education, or trend/humor), tagging each RENDER or FILM against the media on hand. Three run in parallel without seeing each other. Used by the conductor-marketing-create skill (team mode) as stage S2.
|
|
4
4
|
tools: Read, Write, WebSearch
|
|
5
5
|
model: sonnet
|
|
6
6
|
---
|
|
@@ -13,8 +13,8 @@ ideas from your angle, not a safe average.
|
|
|
13
13
|
|
|
14
14
|
## Boundaries
|
|
15
15
|
|
|
16
|
-
- Read only the files you are given: `brief.md`, `context/media.json
|
|
17
|
-
(`references/idea-template.md` in the
|
|
16
|
+
- Read only the files you are given: `brief.md`, `context/media.json`, the idea template
|
|
17
|
+
(`references/idea-template.md` in the conductor-marketing-create skill) and `references/voice.md`. The orchestrator gives you the paths.
|
|
18
18
|
- Write only your output file (`ideas/angle-<n>.md`).
|
|
19
19
|
- Never call Conductor or any MCP tool.
|
|
20
20
|
- WebSearch is only for the trend/humor angle, at most 3 searches, to find a format or reference
|
|
@@ -48,7 +48,13 @@ ideas from your angle, not a safe average.
|
|
|
48
48
|
see `references/slideshow-formats.md` when given) and the slide count (5 to 7), and put the slide 1
|
|
49
49
|
hook in the on-screen hook. Slide 1 is a human tension, never a feature, the app name or a price.
|
|
50
50
|
Put these in the Concept line; the draft spec may then be "slideshow, <archetype>, <n> slides".
|
|
51
|
-
7.
|
|
51
|
+
7. Write every hook the way `voice.md` describes: a person talking, one real detail, a reason to
|
|
52
|
+
care. Run its self-check on each hook and rewrite any line that fails before you save. No two of
|
|
53
|
+
your own hooks may share a sentence frame. A line's detail must be true (principle 2): from the
|
|
54
|
+
media, brief or knowledge; never invent a personal story, result, number, quote or customer
|
|
55
|
+
reaction. Tag each hook type from `voice.md`'s "Shapes, and the hookType each one is tagged"
|
|
56
|
+
table.
|
|
57
|
+
8. Do not name your angle inside an idea. Do not rank your ideas.
|
|
52
58
|
|
|
53
59
|
## Finish
|
|
54
60
|
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: conductor-
|
|
3
|
-
description: Writes the script for the winning idea (hook, timed beats, payoff, call to action, publish copy per platform with alternate hooks) in the fixed script template. Used by the conductor-
|
|
2
|
+
name: conductor-marketing-scriptwriter
|
|
3
|
+
description: Writes the script for the winning idea (hook, timed beats, payoff, call to action, publish copy per platform with alternate hooks) in the fixed script template. Used by the conductor-marketing-create skill (team mode) as stage S4, and again when the user picks a runner-up or asks for copy changes.
|
|
4
4
|
tools: Read, Write
|
|
5
|
-
model:
|
|
5
|
+
model: opus
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# Scriptwriter
|
|
@@ -13,7 +13,7 @@ anything.
|
|
|
13
13
|
## Boundaries
|
|
14
14
|
|
|
15
15
|
- Read only the files you are given: `brief.md`, `decision.md`, the winning idea from `ideas/pool.md`
|
|
16
|
-
and `references/script-template.md` (and `references/platform-specs.md` and `references/publish-pack-template.md
|
|
16
|
+
and `references/script-template.md`, `references/voice.md` (required; stop and say so if it is missing) and, when given, `references/platform-specs.md` and `references/publish-pack-template.md`.
|
|
17
17
|
- Write only your output file (normally `script.md`).
|
|
18
18
|
- Never call Conductor or any MCP tool.
|
|
19
19
|
|
|
@@ -40,7 +40,8 @@ anything.
|
|
|
40
40
|
"link in bio"), and a reminder to repost to Instagram Stories with a link sticker. Note the
|
|
41
41
|
branded-content or "your brand" setting the post needs. Then write 2 or 3 alternate hooks,
|
|
42
42
|
each tagged with a hookType (question, bold-claim, pattern-interrupt, relatable-pain, how-to,
|
|
43
|
-
number, curiosity-gap, story, social-proof
|
|
43
|
+
number, curiosity-gap, story, social-proof, tagged from `voice.md`'s "Shapes, and the hookType each
|
|
44
|
+
one is tagged" table) that differs from the main hook's type. The
|
|
44
45
|
orchestrator merges this section into `publish-pack.md`. Every factual claim must be one the
|
|
45
46
|
brief, knowledge or approved lines confirm; soften or drop any other. Every number or count on a
|
|
46
47
|
card or in a caption (ingredients, minutes, servings, kcal, macros) must match the record it came
|
|
@@ -53,7 +54,19 @@ anything.
|
|
|
53
54
|
knowledge, or be left out.
|
|
54
55
|
7. For a `FILM` idea, write for a person on camera: spoken lines in natural speech, with the
|
|
55
56
|
on-screen text separate. For a `RENDER` idea, keep the text short enough to read at phone size.
|
|
56
|
-
8.
|
|
57
|
+
8. Voice: every on-screen line, spoken line, caption and alternate hook reads like a person posted it
|
|
58
|
+
(`voice.md`). Run its self-check on each and rewrite what fails. A detail must be true (principle
|
|
59
|
+
2): from the media, brief, knowledge or the person; never invent a personal story, result,
|
|
60
|
+
number, quote or customer reaction. The winning hook may be reworded only to remove a tell or
|
|
61
|
+
meet the length rule, keeping its hookType and its promise; never swap it for a different shape.
|
|
62
|
+
Functional lines (CTA, save or follow ask, link in bio, pinned comment, the plain app mention,
|
|
63
|
+
disclosure, approved lines) are checked only against "Tells to cut", not the full self-check.
|
|
64
|
+
Add a "Voice check" line under the copy-rule check naming any line you changed (before and
|
|
65
|
+
after, including the hook) and why.
|
|
66
|
+
9. Apply the orchestrator's user change requests first and keep everything else. Wording the person
|
|
67
|
+
explicitly asked for wins over the voice check: keep it, and if it trips a tell, note that in the
|
|
68
|
+
Voice check instead of rewriting. Approved lines and copy rules still outrank it (`voice.md`,
|
|
69
|
+
"What wins over this guide"). Then run step 8 on the rest.
|
|
57
70
|
|
|
58
71
|
## Finish
|
|
59
72
|
|
package/assets/claude/agents/{conductor-content-strategist.md → conductor-marketing-strategist.md}
RENAMED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: conductor-
|
|
3
|
-
description: Turns a content request and a snapshot of workspace context (brand kit, knowledge, performance, media) into a one-page content brief. Used by the conductor-
|
|
2
|
+
name: conductor-marketing-strategist
|
|
3
|
+
description: Turns a content request and a snapshot of workspace context (brand kit, knowledge, performance, media) into a one-page content brief. Used by the conductor-marketing-create skill (team mode) as stage S1, before any ideas are generated. Reads files only; never calls Conductor.
|
|
4
4
|
tools: Read, Write, Glob
|
|
5
5
|
model: opus
|
|
6
6
|
---
|
|
@@ -281,7 +281,7 @@ For v1 tasks (no top-level `schema_version`, or no `files_owned` on tasks), beha
|
|
|
281
281
|
|
|
282
282
|
### Subagent Dispatch
|
|
283
283
|
|
|
284
|
-
For each batch, spawn `conductor-coder` subagents in parallel using the Agent tool, all calls in one message, each with `subagent_type: "conductor-coder"`. The agent (`.claude/agents/conductor-coder.md`)
|
|
284
|
+
For each batch, spawn `conductor-coder` subagents in parallel using the Agent tool, all calls in one message, each with `subagent_type: "conductor-coder"`. The agent (`.claude/agents/conductor-coder.md`) is self-contained and handles stack detection internally. Pass each agent this prompt:
|
|
285
285
|
|
|
286
286
|
```
|
|
287
287
|
# Task: {task.id} - {task.title}
|
|
@@ -0,0 +1,26 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: conductor:marketing
|
|
3
|
+
description: One entry point for marketing work. Make the artwork for a social post (from a headline, photo or clip, or from a goal), publish or schedule a post to a connected account, or build the whole-funnel marketing report. Routes to the matching skill.
|
|
4
|
+
argument-hint: "[create|publish|report] [request]"
|
|
5
|
+
allowed-tools: mcp__conductor__*, Agent, AskUserQuestion, Skill, WebSearch, WebFetch, Read, Write, Glob, Grep
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# /conductor:marketing
|
|
9
|
+
|
|
10
|
+
A router. Pick the skill, then hand off; each skill owns its own flow and checks.
|
|
11
|
+
|
|
12
|
+
1. **Explicit route.** If the first argument is `create`, `publish` or `report`, go to that skill.
|
|
13
|
+
2. **Infer from the request:**
|
|
14
|
+
- Making or designing artwork, an ad, a video, a slideshow or carousel, a post idea from a goal, or
|
|
15
|
+
brand setup: `create`.
|
|
16
|
+
- Posting, scheduling or publishing something to a connected account, or checking where a
|
|
17
|
+
scheduled post stands: `publish`.
|
|
18
|
+
- A report, the funnel, growth or acquisition numbers, "how is the app doing", benchmarks: `report`.
|
|
19
|
+
3. **No request, or genuinely ambiguous:** ask once with `AskUserQuestion` (single select), "What do
|
|
20
|
+
you want to do?":
|
|
21
|
+
- "Make a post": `create`.
|
|
22
|
+
- "Publish or schedule a post": `publish`.
|
|
23
|
+
- "Marketing report": `report`.
|
|
24
|
+
4. **Hand off** with `Skill(skill: "conductor-marketing-<x>")` (`create`, `publish` or `report`),
|
|
25
|
+
passing the rest of the request and any flags through: `--quick` for create, `7d` or `28d` for
|
|
26
|
+
report. Follow the skill from there.
|
|
@@ -0,0 +1,87 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: conductor-marketing-create
|
|
3
|
+
description: Makes the artwork for a social post through the Conductor MCP tools, rendered locally as a draft and approved before anything is saved. Direct mode, when a headline, photo, clip or finished images are in hand: make an ad, short video, slideshow, carousel or story sequence, post a clip as-is, write a headline variant, or set up the brand (Brand Kit). Team mode, when there is only a goal: a team of subagents brainstorms, judges, scripts and directs a short-form post and renders a draft. Ends at a committed Creative; never creates a Post. Entry point: /conductor:marketing create.
|
|
4
|
+
user-invocable: true
|
|
5
|
+
allowed-tools: mcp__conductor__*, Agent, AskUserQuestion, Skill, Read, Write, Glob, Grep, WebFetch
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Conductor Marketing Create
|
|
9
|
+
|
|
10
|
+
Produces the artwork for a Post: upload-ready media at every placement a workspace's Brand Kit
|
|
11
|
+
enables, either from a concept the person already has (Direct) or from a goal the team turns into
|
|
12
|
+
one (Team). This is the front half of Conductor's marketing pillar; `conductor-marketing-publish` takes the
|
|
13
|
+
committed Creative from here through review and out to each destination. You make the artwork; you
|
|
14
|
+
do not post it.
|
|
15
|
+
|
|
16
|
+
## Rules that hold in both modes
|
|
17
|
+
|
|
18
|
+
- **Brand kit first.** Call `get_brand_kit`. If `configured` is `false` the workspace has never set
|
|
19
|
+
up its brand: follow `references/brand-kit-setup.md` and offer setup before making anything.
|
|
20
|
+
Copy and visuals come from the Brand Kit and its Knowledge page, not from invention.
|
|
21
|
+
- **Draft first, save after approval.** `preview_creative_draft` renders on this machine and writes
|
|
22
|
+
nothing to Conductor. Only after the person has seen the draft and approved it does
|
|
23
|
+
`commit_creative_draft` upload the media, save the Creative and run the full render. Never commit
|
|
24
|
+
a draft the person has not seen and approved.
|
|
25
|
+
- **A run never creates a Post.** It ends at a committed Creative (or a shoot script). Hand off to
|
|
26
|
+
`conductor-marketing-publish` for the Post, scheduling and review.
|
|
27
|
+
|
|
28
|
+
## Which mode
|
|
29
|
+
|
|
30
|
+
| The person has | Mode | Read |
|
|
31
|
+
|---|---|---|
|
|
32
|
+
| A headline, photo, clip or finished images, an existing Creative to vary, or wants the brand set up | **Direct** | `references/direct.md` |
|
|
33
|
+
| 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` |
|
|
34
|
+
|
|
35
|
+
Infer the mode from the request. A concrete headline, photo, clip or existing Creative (including a
|
|
36
|
+
headline variant or brand setup) is Direct. A goal or topic ("a post about X for TikTok") is Team.
|
|
37
|
+
`--quick` applies to Team only. If it is unclear, ask once with `AskUserQuestion` (single select),
|
|
38
|
+
"What are we making?", with two options: "I have the headline/photo/clip" (Direct) and "Come up with
|
|
39
|
+
an idea" (Team). Team mode finishes through the Direct flow's
|
|
40
|
+
preview, check and commit steps (S6 reads `references/direct.md`).
|
|
41
|
+
|
|
42
|
+
## References
|
|
43
|
+
|
|
44
|
+
- `references/direct.md`: the Direct flow (read the brand, angle, headline, photo, preview, critique, commit), sequences, video, finished images, short videos, music, cleanup.
|
|
45
|
+
- `references/team-run.md`: the Team flow (run folder, stages S0 to S6, FILM ideas, final message, failure handling).
|
|
46
|
+
- `references/brand-kit-setup.md`: check the Brand Kit and set it up from a website, a brand doc or direct answers.
|
|
47
|
+
- `references/hooks.md`: writing and scoring headline candidates.
|
|
48
|
+
- `references/voice.md`: making every line read like a person posted it, with the self-check every
|
|
49
|
+
hook, card and caption passes (both modes).
|
|
50
|
+
- `references/layout-guide.md`: choosing a layout, resolution and safe zones.
|
|
51
|
+
- `references/design-critique.md`: the six-criterion score applied to every draft before it is shown.
|
|
52
|
+
- `references/realism-check.md`: the check every generated or library photo passes.
|
|
53
|
+
- `references/slideshow-formats.md`: native slideshow spec, archetypes and text rules for organic posts.
|
|
54
|
+
- `references/rubric.md`: the judging rubric the creative director uses (Team).
|
|
55
|
+
- `references/capabilities.md`: what Conductor can render, and what needs filming (Team).
|
|
56
|
+
- `references/platform-specs.md`: per-platform formats, lengths and limits (Team).
|
|
57
|
+
- `references/idea-template.md`, `script-template.md`, `shotlist-template.md`: the fixed formats the team's agents write in (Team).
|
|
58
|
+
- `references/compliance-checklist.md`: pre-publish checks for disclosure, AI label, music, claims, third-party material, accessibility (Team).
|
|
59
|
+
- `references/publish-pack-template.md`: the publish pack `conductor-marketing-publish` later pre-fills a Post from (Team).
|
|
60
|
+
|
|
61
|
+
## Failures that are silent
|
|
62
|
+
|
|
63
|
+
Automated checks are real but incomplete. These are the ones worth looking for by eye:
|
|
64
|
+
|
|
65
|
+
- **A photo with text, a logo or a claim burned into its pixels** passes every copy-rule and render
|
|
66
|
+
check, because none of them read pixels for meaning. Open and look at every photo.
|
|
67
|
+
- **A generated image depicting a product, result or claim that is not real** (a made-up app screen,
|
|
68
|
+
a before/after, an invented package) passes every check. Only looking catches it.
|
|
69
|
+
- **A structurally valid render is not necessarily a good one.** The checks cover spill, safe zones,
|
|
70
|
+
fonts and contrast, never whether the headline reads at a glance or the copy sits on a face. The
|
|
71
|
+
design critique exists for this gap.
|
|
72
|
+
- **A Brand Kit with no copy rules, or no accent-phrase requirement, never fails a save on that
|
|
73
|
+
account.** That is permissive by design, which makes the model the only check on brand voice until
|
|
74
|
+
someone configures rules.
|
|
75
|
+
- **A draft is not a saved Creative.** A Creative or media id does not exist until
|
|
76
|
+
`commit_creative_draft` runs; do not hand a draft's folder to `attach_creative_to_post` or a Post.
|
|
77
|
+
- **A stale write is refused, not overwritten.** `update_creative` requires the current `version`; a
|
|
78
|
+
409 names the conflict. Reread with `get_creative` and reapply, do not retry blind.
|
|
79
|
+
- **Rejected copy stays rejected.** Copy rules with ids starting `banned-` are lines or visuals the
|
|
80
|
+
person rejected earlier; never reuse them.
|
|
81
|
+
|
|
82
|
+
## Related
|
|
83
|
+
|
|
84
|
+
- `conductor-marketing-publish`: schedules and tracks the Post the artwork attaches to, through review and out
|
|
85
|
+
to each destination. This skill hands off to it, never the reverse.
|
|
86
|
+
- `conductor-marketing-report`: the whole-funnel marketing report; its next actions can feed new
|
|
87
|
+
posts made here.
|
|
@@ -1,8 +1,7 @@
|
|
|
1
1
|
# Brand Kit check and setup
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
Brand Kit has been set up, and offer to set it up if not.
|
|
5
|
-
unchanged.
|
|
3
|
+
Used by the `conductor-marketing-create` skill (both modes): check whether this workspace's
|
|
4
|
+
Brand Kit has been set up, and offer to set it up if not.
|
|
6
5
|
|
|
7
6
|
## Step 1 — Check the brand
|
|
8
7
|
|
|
@@ -1,4 +1,3 @@
|
|
|
1
|
-
<!-- Keep identical to the copy in the other creative skill (conductor-creative / conductor-content-studio references/design-critique.md). Skills install independently and cannot reference each other. -->
|
|
2
1
|
# Design critique
|
|
3
2
|
|
|
4
3
|
Passing checks does not make an ad good. `checks` and `passed` cover text spill, safe zones, contrast
|