← ClaudeAtlas

brand-identitylisted

Build a complete brand identity for an app, website, or UX project the user has already designed or built. Covers logo direction, color palette, typography, imagery style, component styling rules, voice and tone, and a moodboard, delivered as a written brand guide, design tokens, and an interactive HTML style guide. Use this skill whenever the user points at a project (a Figma file, a repo, a live URL, a set of screens) and asks for branding, a brand identity, a visual identity, a style guide, a design system, a color palette, a logo direction, or asks to "make this look like a real product," "give this a brand," "make this feel cohesive," or "what should the colors and fonts be" — even if they never say the word "brand."
wl3512-lab/brand-identity-skill · ★ 0 · Web & Frontend · score 70
Install: claude install-skill wl3512-lab/brand-identity-skill
# Brand Identity Build a brand identity from an existing project rather than from a blank page. The project already contains most of the answers: what it does, who uses it, what it currently looks like. The job is to read that, decide what the brand should be, and then hand back something specific enough to build with. Work as a design lead who gives every client a distinct identity. Do not produce the default AI look (cream background, high-contrast serif, terracotta accent; or near-black with one acid accent; or identical rounded cards with soft grey shadows). If `/mnt/skills/public/frontend-design/SKILL.md` is available, read it before designing anything visual. ## Phase 1 — Look at the project Never design before seeing the work. Get real material in front of you first. See `references/inputs.md` for how to pull from each input type (Figma, repo, live URL, screenshots). Minimum before moving on: - What the product does, in one sentence, in the user's words - At least one screenshot or rendered view of the current UI - The current de facto palette, typefaces, spacing, and radii, extracted as actual values - A sample of the existing copy (button labels, headings, empty states) If you can only get a description and no visual, say so and ask for a screenshot or link before continuing. Designing blind is the main failure mode here. ## Phase 2 — Audit Write a short audit, 6-10 bullets, covering: - What the current visuals are already communicating, honestly - Where it's