¿Qué hace brand-kit?
Four outputs, one look, after a sportswear brand board. examples/kiln/ is a
complete kit for a fictional ceramics studio made with these skills — its
brand.json, moodboard, brand book pages and logo files; open
examples/kiln/moodboard.jpg to see the target quality before starting.
| Command | Delivers |
|---|---|
/moodboard | moodboard.png (3200 × 2000) + moodboard.jpg + moodboard.html |
/logo | transparent PNGs: wordmark for dark backgrounds, wordmark for light backgrounds, monogram tile, mark alone; SVGs of the mark and monogram; favicon.ico; logo.html |
/brand-kit | everything from /logo and /moodboard, plus <slug>-brand-guidelines.pdf (10 pages + "In use" pages of the brand on the business's products, packaging, signage and stationery), a cover PNG, tokens.css, tokens.json and a README.md listing the files |
/merch-mockup | the brand on the merch the person picks (tees, hoodies, caps, totes, mugs…): merch-mockups.png sheet, one PNG per piece in merch/, the print files in merch/print/ — coded, or photo-real with a connected image generator |
/brand-identity | (its own skill) interviews the person, writes the strategy, lets them pick a direction and a logo, then runs this skill |
Everything is drawn in HTML/CSS/SVG and rendered locally, so every output is
the person's to use. The coded path is complete and 100% free.
Photo-real mockups are optional and need an image generator the person
connects: offer them where this file says to, always with the disclaimer in
references/applications.md (credits, more than one try, a tally at the
end), and never generate without their yes.
Files in this skill
SKILL_DIR below is the folder this file is in (usually ~/.claude/skills/brand-kit).
templates/moodboard.html·logo.html·brandbook.html— the three kit outputstemplates/items/*.html— 24 drawn applications (box, bag, storefront, letterhead, product, hoodie, cap, tote…) used in moodboard slots and the brand book's "In use" pages;templates/items-gallery.htmlshows any set of them as a menutemplates/merch.html— the merch sheet for /merch-mockup;references/merch.md— the merch menu, what to suggest, colourways and photo-real scenesreferences/applications.md— the item list, which items suit which business, how to draw the product, and the image-generator optiontemplates/directions.html·concepts.html·strategy.html— used by brand-identityscripts/fill.mjs <template> <brand.json> <out.html>— fills{{PLACEHOLDERS}}, fails if any are leftscripts/render.mjs <file.html> --shot "#id=out.png" [--transparent] [--pdf out.pdf] [--scale 2]— PNG/JPG shots and PDFs with the local Chromescripts/capture.mjs <url> <dir>—site-desktop.jpg+site-mobile.jpgof a live sitescripts/palette.mjs Name=#hex …— RGB, HSL and WCAG contrast for every pairscripts/composite.py photo overlay out --corners …— lays the logo/headline onto a generated photo in perspective (needs Pillow);templates/overlays.htmlrenders those transparent piecesexamples/kiln/brand.json— every placeholder filled; copy it as the starting point
Run scripts as node SKILL_DIR/scripts/<script>.mjs. They need playwright-core
(installed in SKILL_DIR by the installer; if it is missing run
npm install there) and Google Chrome at its usual path, or CHROME_PATH.
Step 1 · Gather the brand (every command)
Look before asking. In the current project read, when present: content files
(brand.ts, site.config.*, package.json name), theme tokens (globals.css,
Tailwind config), icon.svg/logo files, the fonts in use, the live URL. Then
fill a brand.json:
- Name (
BRAND,BRAND_UPPER,slug), city/country, category (what the business does, in a few words) - Palette in this pattern: a quiet base (
BASE), a light that is never pure white (LIGHT, e.g. #f2f1ec), an ink that is never pure black (INK), and one loud accent (ACCENT) plusACCENT_DEEP, the accent darkened until it reads onLIGHT. Give each a short name (e.g. Clay, Bisque, Char, Ember). - Type: a display face (
DISPLAY_FONT), one serif italic for a single emphasised word (ACCENT_FONT), a mono for labels (MONO_FONT). Google Fonts go inFONT_LINKS; licensed local files go inassets/and are declared inFONT_FACES. Note each font's licence in the brand book. - The mark (
MARK_SVG, drawn in a 32 × 32 box withcurrentColorand the accent asfill="var(--accent)") and the wordmark (WORDMARK_HTML). Use the brand's real ones. If there are none, design a simple wordmark (one distinctive detail, marked up with.accor.dot-over) and a monogram from its first letter, and say clearly that these are proposals — or suggest/brand-identity. - Headline for the billboard: who it's for and the outcome, never an empty slogan; its last word goes in the serif italic, then the accent dot.
- Brand book words (positioning, three values, voice do/don't) restate what the brand already says and does. Never invent clients, numbers, reviews or history. If something is unknown, write a neutral line and list it as a placeholder in the reply.
Ask only for what can't be found and blocks the work (usually: which accent, when there is no palette at all). Otherwise use sensible defaults, mark them as proposals, and keep going.
Output folder: the project's brand/ folder if it has one, else
<cwd>/<slug>-brand-kit/. Keep brand.json there so later runs reuse it.
Never overwrite an earlier kit: write into a dated subfolder or ask.
Step 2 · Applications: what the brand appears on (/moodboard and /brand-kit)
The moodboard and the brand book show the brand on the things this business
makes, sells and uses — read references/applications.md now.
- Work out the business: what it sells (a physical product? a service? a venue? software?), where customers meet it, and where the person said the brand will be seen.
- Propose a set: 5 items for the moodboard slots (in slot order) and the
extra ones for the brand book's "In use" pages, from the starting sets in
references/applications.md. Lead with the product itself when there is one. Two tiles are the same for everyone, always: the mark and the summary card (category, type and palette —item:summary). Never drop them. - Let the person shape it (
AskUserQuestion): show the proposed list in words and ask: Use this set · Add or remove items · Show me more options.- "Add or remove": take their edits (plain text is fine).
- "Show me more options": fill
templates/items-gallery.htmlwith every item that could fit this business (in their colours, with the product drawn), render it, send it, and let them pick (multiSelect). Nothing is drawn for the final boards until the list is agreed. When nobody is there to answer (an automated run), use the proposal and say so.
- Coded or photo-real? Coded is the default and free. Photo-real
(the mark embroidered on a real hoodie, debossed in a mug, a billboard in
a real street) needs an image generator. Look for one in this session (an
MCP tool like
generate_image, or a skill like Higgsfield's). Always ask, every run (AskUserQuestion), whatever you know or suspect about their plan, balance or licence: Coded, stylised (free) · Photo-real with (better results; uses your credits, can take 2–3 tries per piece). Never decide for the person and never reduce the offer to a line in your message: the question is the offer.- Put what you know inside the photo-real option, not instead of it: a low balance, a free plan, a licence that may not allow commercial use ("your free plan has 0.45 credits, about 0.5 per image; top up first"). The person decides with that in front of them.
- None connected: still ask, as Coded (free) · Photo-real (connect an image generator first, e.g. an image MCP server or Higgsfield's skill; uses its credits). If they pick photo-real, say how to connect one, make the coded version meanwhile, and generate in a later session.
- If they pick photo-real, check the plan
and the model first (
references/applications.md→ "Check the plan and the model first"; free plans often block the best models), then give the disclaimer fromreferences/applications.md→ "Photo-real" and get a second, explicit yes before the first image. Then follow that section: reference mode (the real mark and wordmark as reference images, exact colours and finish in the prompt), check every image against the real files, overlay only as a fallback, and end with the tally.
- The product: if it sells a physical product, draw it as
PRODUCT_SVG(see "Drawing the product") or generate it — the board isn't finished without it.
/moodboard
- Do Step 2. Then set
SLOT_2…SLOT_6inbrand.jsonto the chosen items ("SLOT_2": "{{item:storefront}}", …) plus the values those items use (MATERIAL,STORE_WINDOW,CARD_LINE,PHONE_SCREEN,LAPTOP_SCREEN,PRODUCT_SVG). Filltemplates/moodboard.htmlwithfill.mjs.- Phone/laptop: with a live site, run
capture.mjs <url> <folder>/assetsand use the<img>; otherwise the drawn screens. - With a reference image, follow its layout tile for tile.
- Phone/laptop: with a live site, run
- Render:
render.mjs moodboard.html --shot "#board=moodboard.png" --shot "#board=moodboard.jpg". - Look at the PNG (Read it) before showing it. Fix, re-render, look again:
- every slot shows its item whole and recognisable (the product reads as the product);
- the billboard's giant mark sits in the right half, never under the headline or fine print;
- nothing is clipped that shouldn't be (the giant mark and its dot should be cropped);
- hyphenated words use non-breaking hyphens (
‑) so "30-min" never splits; - no hosting URLs (like
*.vercel.app) printed on mockups; - every text colour reads on its tile.
- Send the PNG and say in a line or two what each tile shows, and which items are stylised drawings.
/logo
- Fill
templates/logo.html. - Render with
--transparent:#wordmark-light,#wordmark-dark,#monogram,#mark→<slug>-wordmark-light.pngetc. (2×: about 1600 px wordmarks, 1200 px squares). - Save
<slug>-mark.svgand<slug>-monogram.svg(colours written as hex, notvar()), andfavicon.ico(16/32/48/64) from the monogram PNG — Python PIL:Image.open(png).save("favicon.ico", sizes=[(16,16),(32,32),(48,48),(64,64)]). - Look at the dark-letter PNG (the light one looks blank on a white viewer — expected; say so). On light backgrounds the accent uses
ACCENT_DEEP. - Send the files.
/brand-kit
- Do
/logoand/moodboardin the same folder (Step 2 decides the items for both). - Run
palette.mjson the four colours. Use its numbers for*_RGBandCONTRAST_PAIRS(the useful pairs: light on base, ink on light, ink on accent, accent on base; each<div class="pair" style="background:…;color:…">Text <small>7.5:1 AA</small></div>). Never estimate a ratio. - Fill
templates/brandbook.html. In use pages:IN_USE_PAGES= one page per 2–3 items, every agreed item that isn't only on the moodboard, largest first:(<section class="page inuse"><div class="head"><span class="mono">08 · In use</span><span class="mono">{{BRAND_UPPER}}</span></div> <div class="grid3"><figure class="t"><figcaption>Box</figcaption>{{item:box}}</figure><figure class="t"><figcaption>Bag</figcaption>{{item:bag}}</figure><figure class="t"><figcaption>Cards</figcaption>{{item:cards}}</figure></div> <div class="foot"><span class="mono">The brand on what we sell</span><span class="mono pn"></span></div></section>grid3= one big + two;grid2= two side by side).TOC_FILES= the files page number (10 + number of in-use pages, two digits). Also:MOODBOARD_SRC=moodboard.png;PROPORTION_BAR= four<span style="flex:N;background:…">, e.g. 60/25/10/5;VOICE_DO,VOICE_DONT,FILE_LIST=<li>items;TOKENS_CSS= the:rootblock). Render:render.mjs brandbook.html --pdf <slug>-brand-guidelines.pdf --shot "#p-cover=<slug>-brand-cover.png" - Write
tokens.cssandtokens.json(colours, fonts, radii 14/22/28, the glow) and aREADME.mdlisting every file. - Check the pages: render
--scale 1 --shot ".page:nth-of-type(N)=page-N.jpg"for each and look; fix overflow (long names can overrun the big headings), re-render. - Send the PDF, the moodboard and the folder path. Name anything that is a proposal, a placeholder or a stylised drawing.
/merch-mockup
The brand on merch. Read references/merch.md first.
- Gather the brand assets. Look for a kit this skill already made: the
project's
brand/folder or<slug>-brand-kit/(itsbrand.json, the logo PNGs/SVGs,tokens.css). Tell the person in one line what you found ("Using kiln-brand: the mark, the wordmark, Clay/Bisque/Char/Ember, Space Grotesk"). If there is no kit, do "Step 1 · Gather the brand" (or suggest/brand-identitywhen there is no brand yet). Write into<kit folder>/merch/(a dated subfolder if one exists already). - Ask what merch (
AskUserQuestion,multiSelect, before drawing anything). Suggest first what suits the business (references/merch.md→ "Which ones to suggest first"), and mark those "(Suggested)". Up to four questions of up to four options each, by group: Apparel (t-shirt chest · t-shirt back print · hoodie · cap/beanie), Bags & drinkware (canvas tote · mug · water bottle · takeaway cup), Desk & small things (notebook · enamel pin · stickers · hang tag/pass), and a last one: Show me all of them drawn first · No, that's the list. "Other" takes anything else (socks, an apron…: draw or generate it). "Show me all drawn": filltemplates/items-gallery.htmlwith every merch item, render, send it, ask again. - Code or image generator? Always ask before generating
(
AskUserQuestion): Image generator — photo-real (Recommended for the best results) — the mark embroidered on a real hoodie, a cap on a head, a tote on a shoulder; uses that tool's credits, and a piece can take 2–3 tries · Code — stylised, like the rest of the kit (100% free, instant). Look for an image tool in this session first (an MCP tool such asgenerate_image, or a skill such as Higgsfield's) and name it in the option. Always ask this, every run, whatever their plan, balance or licence: put a known limit inside the option ("free plan, 0.45 credits: top up first"), never skip the question because of it. If there is none connected, still offer it; if they pick the generator, say how to connect one (an image-generation MCP server or skill, then start a new session) and offer to make the coded sheet meanwhile. If they pick the generator, check their plan's balance, which models it can run and the real price per image (references/applications.md→ "Check the plan and the model first"), then give the disclaimer fromreferences/applications.md→ "Photo-real" with the real numbers (N pieces → N images, up to about 3N tries), check the tool's licence allows commercial use, and get a second, explicit yes before the first image. - Make it.
- Coded: in a copy of
brand.jsonsetMERCH_NOTE("Coded mockups · stylised") andMERCH_TILES, one tile per piece in the order chosen:<figure class="t" id="m-hoodie"><figcaption>Hoodie</figcaption>{{item:hoodie}}<p class="spec">Heavyweight hoodie · Clay · chest print</p></figure>. The summary card (type & palette) closes the sheet by itself — it is always there. Filltemplates/merch.html. - Photo-real: make the coded sheet first (free, so they always have
it), then follow "Photo-real merch" in
references/merch.md: render the overlays, generate each piece in reference mode with the real mark as the reference image, check each against the real files (retry at most 3 times, then fall back to the overlay or the coded piece), and keep the tally; then the tile is<figure class="t" id="m-hoodie"><figcaption>Hoodie</figcaption><div class="app app-photo"><img class="bg" src="merch/photo-hoodie.jpg" alt="" /></div><p class="spec">…</p></figure>andMERCH_NOTEnames the tool ("Photographs made with …"). Mixing is fine (photo for worn pieces, code for a pin).
- Coded: in a copy of
- Render the sheet and every piece:
render.mjs merch.html --scale 2 --shot "#board=merch-mockups.png" --shot "#board=merch-mockups.jpg" --shot "#m-hoodie=merch/hoodie.png" … - Print files in
merch/print/: fill and rendertemplates/overlays.html(transparent mark, wordmark, lockup, tag lines, light and dark ink, at--scale 4) and copy the SVG mark/monogram. Name which file goes on which piece inmerch/README.md(e.g. hoodie chest →ov-wordmark-light.png, about 25 cm wide; cap front →<slug>-mark.svg, 6 cm, embroidery). - Look at the sheet (Read it): every piece whole and recognisable, the print centred and readable, nothing clipped, no stray letters in photos. Fix and re-render. Then send the sheet, list the files, and say which pieces are stylised drawings or generated photos. After photo-real, end with the tally: images generated, with which tool, and which pieces took more than one try.
House style
- Simple, never plain: few elements, each catchy and art-directed.
- A near-black or quiet base, one big colour, one loud accent that glows.
- Light surfaces are never pure #fff; dark ones never pure #000.
- One serif italic word per headline, closed with the accent dot.
- Show the result as an image in the chat (Read it, then send it) before talking about it; keep the reply short and concrete.
- Never open working files or previews in the person's browser pane — boards are 1600 px wide and look oversized there. Render, check, and send the image.
