Skip to content

Commit f2dd765

Browse files
committed
chore: use the brief to extract the palette from
1 parent f391947 commit f2dd765

1 file changed

Lines changed: 6 additions & 4 deletions

File tree

skills/draft-logo/SKILL.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ SVG is the medium for exploration in this skill — the right format for showing
1616
2. **Brief first, slate next, SVG last.** Run-to-run variance comes from skipped briefs. Confirm a slate of *named ideas in plain English*, with each concept's SVG technique committed in words, before writing any path data. That's the cheapest place to kill bad directions.
1717
3. **Diverge in round 1 across stylistic territories.** Round 1's concepts must occupy *different visual modes* — modular grid, monogram, negative-space figure-ground, organic curve, brush-feel, geometric-abstract, soft-luminous, sharp-cut. Six versions of the same style with different shapes is not divergence; it's six versions of the same idea. Later rounds variate within the user's picks only — color, weight, geometry tweaks — never new ideas.
1818
4. **Test at the worst case: favicon size, on both light and dark.** A mark that only works at 200px on white is half a logo. Every card renders the same SVG at three sizes on both backgrounds to expose marks that die when shrunk or inverted.
19-
5. **The full SVG vocabulary is yours — deploy with intent.** Cubic and quadratic Beziers, arcs, dashed and rounded strokes, linear and radial gradients, patterns, blur and drop-shadow and color-matrix and morphology filters, masks and clip-paths for negative space, `symbol` + `use` for symmetry and reuse, `textPath` for wordmarks that follow the mark. Effects are right when they *are* the concept (a sunrise gradient on a horizon mark; a soft blur on a lantern's halo; `feMorphology` to bulk up a strokes for chunky impact); wrong when they decorate a mark that lacks one. The slop signature is *gradient + drop-shadow + outer glow + outline* stacked on a generic shape to make it feel modern.
19+
5. **The full SVG vocabulary is yours — deploy with intent.** Cubic and quadratic Beziers, arcs, dashed and rounded strokes, linear and radial gradients, patterns, blur and drop-shadow and color-matrix and morphology filters, masks and clip-paths for negative space, `symbol` + `use` for symmetry and reuse, `textPath` for wordmarks that follow the mark. Effects are right when they *are* the concept (a sunrise gradient on a horizon mark; a soft blur on a lantern's halo; `feMorphology` to bulk up a strokes for chunky impact); wrong when they decorate a mark that lacks one. The slop signature is *gradient + drop-shadow + outer glow + outline* stacked on a generic shape to make it feel modern. The same discipline applies to palette: color is sourced from the brief — explicit palette input, the existing artifacts the user pointed at, or a justified choice when the user says "you pick" — never inherited from a default or from this skill's own examples.
2020
6. **Match concept to execution.** If a named concept ("clouds", "watercolor wash", "fog") can't be rendered honestly in SVG without looking like a fluffy lozenge, drop or rename it — don't ship the mismatch. The card's name and one-line description must match what the eye actually sees in the SVG. Honesty about what the medium expresses well beats over-promising.
2121
7. **No pastiche.** A mark shaped like the Stripe wave, the Vercel triangle, the Linear chevron, or any well-known mark — even subconsciously — is homework, not a logo. If a direction starts to echo a known mark, name the echo and pivot.
2222
8. **Name the idea, code the reference.** Every concept carries both a name that captures its visual idea ("the aperture", "the inverted Y") and a short pick code — `A` through `F` per round, prefixed with the round number when crossing rounds (`1A`, `2C`). The name forces one-idea-per-concept discipline on the model; the code makes the user's picks effortless to type. Not "Option 1, Option 2" — that's neither.
@@ -30,13 +30,14 @@ SVG is the medium for exploration in this skill — the right format for showing
3030
- 1–2 existing logos the user admires whose *character* (not look) is adjacent to what they want — useful as a vector for the model's aim, not as material to copy
3131
- One stretch word for the mark's personality (sly, scalpel-sharp, watchful, mischievous, quiet-authoritative, generous)
3232
- Visual constraints (motifs to include or avoid; mono-mode requirement; horizontal-lockup-with-wordmark needed?)
33+
- Palette — explicit colors, or "match my existing artifacts" (point me at the CSS/theme/logo file), or "you pick" (in which case each concept must declare and justify its palette in step 2)
3334
- Format hints (square favicon priority? wordmark needed alongside the mark?)
34-
If the user passed arguments to `/draft-logo`, treat them as initial brief and ask only for what's missing. Once confirmed, write the brief to `logos/brief.md` (product + essence, tone words, stretch word, admired marks, constraints, format hints) so future sessions and convergence rounds have a stable anchor.
35+
If the user passed arguments to `/draft-logo`, treat them as initial brief and ask only for what's missing. Once confirmed, write the brief to `logos/brief.md` (product + essence, tone words, stretch word, admired marks, constraints, palette, format hints) so future sessions and convergence rounds have a stable anchor.
3536
2. **Propose the slate.** List 4–6 concept *ideas* in plain English. Each concept entry must include:
3637
- **Code**`A`, `B`, `C`, ... in the order presented; round-prefixed when referring across rounds (`1A`, `2C`)
3738
- **Name** — the visual idea ("the aperture")
3839
- **One-line description** — what the eye sees and why ("concentric arcs forming an opening; focus and clarity")
39-
- **SVG technique** — what path commands, fills, filters, masks, or symmetries this concept will use ("cubic Beziers for the arcs, `feGaussianBlur` for the inner edge softness, radial gradient stop from warm-amber to deep-orange")
40+
- **SVG technique** — what path commands, fills, filters, masks, or symmetries this concept will use, **and the palette with its justification** — colors must trace back to the brief's palette input, the artifacts the user pointed at, or the brief's tone words; never inherited from the example below or from a default. E.g. "cubic Beziers for the arcs, `feGaussianBlur` for the inner edge softness, radial gradient from warm-amber to deep-orange — brief asked for warmth; tone word 'glowing'" (palette here is illustrative; substitute one that traces to the actual brief)
4041
- **Stylistic territory** — which mode it occupies ("soft-luminous"), so the slate as a whole spans different modes
4142
Before sending, self-check: *which of these would I forget by tomorrow? Replace those.* Wait for the user to confirm or trim the slate. Do not write any SVG yet.
4243
3. **Determine the round number.** Read `logos/` in the current working directory. If it doesn't exist, the round is 1. Otherwise pick the next available `logos/round-N.html`. Pick codes (`A` through `F`) restart each round.
@@ -143,7 +144,7 @@ Each concept appears in one `.card`. The *same* SVG is reused across all six swa
143144

144145
- A brief elicitation in one short pass at the start of round 1, including admired-marks and a stretch-word for personality
145146
- The confirmed brief persisted to `logos/brief.md` so future sessions and convergence rounds have a stable anchor
146-
- A named slate of 4–6 concept *directions*, each with pick code (`A``F`), name, one-line description, committed SVG technique, and stylistic territory — confirmed by the user before any SVG is written
147+
- A named slate of 4–6 concept *directions*, each with pick code (`A``F`), name, one-line description, committed SVG technique, declared palette traced back to the brief, and stylistic territory — confirmed by the user before any SVG is written
147148
- A self-check on the slate before sending: drop any concept you'd forget by tomorrow
148149
- A self-check on each SVG before embedding: does it actually render the thing the card names?
149150
- A self-contained HTML gallery at `logos/round-N.html`, one card per concept, every SVG shown at large/medium/favicon on light + dark
@@ -166,6 +167,7 @@ Each concept appears in one `.card`. The *same* SVG is reused across all six swa
166167
- Stacking multiple unrelated effects on one mark (the slop signature: gradient + shadow + glow + outline + texture all at once)
167168
- Detail that disappears below medium size — fine pinstripes, micro-textures, three-layer gradients meant to be seen at 200px
168169
- Marks that echo known brands (Stripe wave, Linear chevron, Vercel triangle) without naming the echo
170+
- Inheriting palette from the skill's example concept ("warm-amber to deep-orange") or any default the brief didn't ask for — every color must trace back to the brief's palette input, matched artifacts, or tone words
169171
- Using "Option 1, Option 2" style numbering, or letting the pick code (`A`, `B`) substitute for the concept name — the card needs both
170172
- Pre-ranking the gallery or telling the user which concept is best
171173
- Adding palettes, type pairings, taglines, or brand-voice guides alongside the mark

0 commit comments

Comments
 (0)