taste-brand-identity
Skill1 starsChanged 3 months agoMITView on GitHub
Brand identity generation for agents: logo mark concepting, wordmark typography, lockups, clear space and minimum sizes, color application, favicon and og-image construction, and the one-page brand sheet. Use when asked to create a logo, identity, or brand assets for a product or site. Stack on the design-taste core skill.
In this repository23 other files it gives its agents.
- brutalist-industrialSkill
- cinematic-motionSkill
- corporate-trustSkill
- dark-techSkill
- design-tasteSkill
- editorial-minimalSkill
- japanese-minimalSkill
- neo-brutalismSkill
- playful-colorSkill
- quiet-luxurySkill
- retro-printSkill
- taste-accessibilitySkill
- taste-code-craftSkill
- taste-code-reviewSkill
- taste-colorSkill
- taste-design-reviewSkill
- taste-design-systemSkill
- taste-gsapSkill
- taste-landing-pageSkill
- taste-motionSkill
- taste-typographySkill
- taste-ux-copySkill
- taste-web-performanceSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Prefer modifying a strong existing face over inventing a font: letterspacing (−0.03em), case, a punctuation detail (.
- Distinctive: line 30
Test the wordmark in: caps, sentence case, and at 12px.
- Distinctive: line 31
Never letterspace lowercase (it breaks the word shape).
- Distinctive: line 45
If the logo is a wordmark, its color rule is: same ink as headings — never a rainbow of per-section colors.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
taste-brand-identity
A logo is a memory aid, not a drawing. This skill makes sure the identity survives a favicon and a billboard.
1. THE CONCEPT (Before Any Drawing)
- One idea, two words: the mark reduces to a single association ("north + needle", "record + flower"). If you can't say it in two words, the concept isn't there yet.
- Literal is the last resort: a generic icon of the product category (spark, rocket, chat bubble, gear) is what every other mark does. Reach for the abstract idea behind the product.
- Test at 16px before loving it: the mark must read as a favicon first. If the concept needs 3 colors or fine detail to live, it fails the test.
- Two colors, hard ceiling: one ink + one accent (or monochrome). A mark that needs its gradient to exist is not a mark.
2. WORDMARK TYPOGRAPHY (The Half Nobody Checks)
- Prefer modifying a strong existing face over inventing a font: letterspacing (
−0.03em), case, a punctuation detail (.in "skittie.dev"), or one cutout/glyph swap. - One typographic move per wordmark: track tight OR case change OR a single altered glyph. Two moves = a novelty logo.
- Test the wordmark in: caps, sentence case, and at 12px. If it doesn't survive small, tighten or accept a secondary lockup.
- Never letterspace lowercase (it breaks the word shape). Never stretch type (use the real condensed family).
3. THE LOCKUP (Mark + Wordmark, Formalized)
- Build on a construction grid: mark and wordmark on shared optical centers, clear space = height of the mark's smallest element (or 1/4 the mark width) on all sides.
- Three lockups, defined once: horizontal (mark + wordmark), stacked (mark above wordmark), compact (mark + short wordmark, for small spaces).
- Minimum sizes: mark ≥ 16px (favicon), ≥ 24px (in-app), ≥ 12px wordmark in compact lockups only.
- Banned lockup crimes: shadowed marks, gradient marks, outlined marks at small sizes, mark alone without the brand name on the first view.
4. COLOR APPLICATION
- The identity lives in ink + one accent (from the palette the page uses). A reversed (light-on-dark) variant is required — define both.
- Accent distribution: the accent is a signal (links, one button, active states, the logo's accent detail) — never a background fill.
- Provide a "monochrome only" fallback: every brand asset exists in 100% ink as a default.
- If the logo is a wordmark, its color rule is: same ink as headings — never a rainbow of per-section colors.
5. THE DELIVERABLE SET (Ship All of These)
- Primary lockup — SVG, currentColor-compatible.
- Favicon — 32px and 180px (apple-touch): the mark alone, centered, its own square tile.
- og-image — 1200×630 canvas: mark or wordmark top-left or centered, one accent detail, clear space ≥ 80px margins; this is the most-viewed brand asset on the internet — never let it be a screenshot of the site.
- One-page brand sheet — mark, wordmark, clear space diagram, min sizes, palette (with tokens), type pair, do/don't rows. This becomes the agent's own brand guideline file.
6. DO / DON'T (The Fast Filter)
| Do | Don't |
| Simplify until one element remains | Add a stroke, shadow, and gradient "for depth" |
| Test at 16px, 48px, 400px | Design only at 400px and pray |
| One typographic move | Custom-draw letters that fight the font |
| Provide the reversed variant | Ship only the version that works on white |
| Make the og-image deliberately | Let socials crop a screenshot |
7. CHECKLIST (Fail the Identity If…)
- The concept can't be stated in two words.
- More than two colors (plus neutrals).
- Any gradient, shadow, or outline needed for legibility.
- The mark at 16px is ambiguous with the competition's.
- No reversed variant exists.
- No clear-space/min-size rule defined.
- The og-image is missing or is a page screenshot.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

