Logo brand mark designer
Skill prvthmpcypher/skills-design/skills/logo-brand-mark-designer
29 Claude skills for designers. UI/UX, brand identity, typography, frontend design, accessibility, and visual storytelling.
npx -y skills add prvthmpcypher/skills-design --skill logo-brand-mark-designerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Designs logo/brand-mark concepts as SVG — wordmarks, lettermarks, and simple iconographic marks — with rationale for shape, weight, and composition choices. Use this whenever the user wants a logo designed, a brand mark or icon created, logo concepts to choose between, or an existing logo refined/simplified. For brand guideline documentation (how to use an existing logo, color/typography rules) rather than creating the mark itself, the design category's brand-guardian skill is the better fit.
SKILL.md
3.7 KB, as published. Nobody here has run it
Logo & Brand Mark Designer
A logo has to work at both a 16px favicon and a building-sized sign — that constraint should shape every design decision, not just be a checklist item at the end. Prioritize a form that survives radical size and color reduction over one that only looks good at presentation size.
Workflow
- Get the essentials: the name/initials to work with, the industry/category, and 2-3 adjectives describing the desired feel (e.g. "trustworthy, modern, understated" vs. "playful, bold, energetic") — these adjectives should directly drive shape and weight choices, not just inform a mood board.
- Pick a mark type matched to the brand's needs:
- Wordmark (full name, typographically distinctive) — works well when the name itself is short, memorable, and worth building recognition around directly.
- Lettermark (initials) — useful for longer names where a full wordmark gets unwieldy at small sizes.
- Icon + wordmark combination — most flexible for real-world use (the icon alone can serve as an app icon/favicon once recognition builds), but takes longer to build equity in the icon alone.
- Abstract/iconographic mark alone — highest risk (no inherent name recognition until the brand builds it), but distinctive at scale once established. Only recommend this if the user has the marketing runway to build recognition, and say so.
- Design for reduction, not addition. Start from the simplest version that still reads clearly, rather than starting complex and simplifying later — a mark that only works with fine detail won't survive small-size or single-color use.
- Test the mark mentally against real constraints: does it still read as intended in pure black, at favicon size, and reversed on a dark background? Flag if a concept fails any of these rather than presenting it as finished.
- Explain the reasoning, not just the shapes — why this weight, why this level of geometric vs. organic form, why this specific color if included — so the user can evaluate the concept against their actual brand intent, not just aesthetic preference.
Technical constraints for SVG output
- Build with clean, minimal path data — avoid unnecessary anchor points, which bloat file size and complicate later edits.
- Use a single, ideally even-odd-safe path for a monochrome mark where possible, so it scales and recolors cleanly.
- Keep the design within a square or defined bounding box (e.g. 100x100 viewBox) so it's simple to place consistently across contexts.
What NOT to do
- Don't reproduce or closely imitate any real, identifiable existing brand's logo — even as a "starting point" or "inspired by" reference, per copyright and trademark boundaries.
- Don't over-design with gradients, complex shadows, or fine detail that won't survive single-color or small-size reproduction — a logo isn't an illustration.
Output format
Provide the mark as clean SVG code, plus a short rationale (2-4 sentences) connecting the specific design choices back to the brand adjectives given. If presenting multiple concepts, keep them genuinely distinct in approach (e.g. one wordmark-led, one icon-led), not variations on the same idea.
Gives 0 of the 12 instructions most design systems skills give
Counted across 528 of the 534 authors here whose files we hold, read 2026-08-06
- create a custom theme if neededin 54 of 528, across 10 files
- read the corresponding theme filein 54 of 528, across 10 files
- ask which theme to applyin 53 of 528, across 9 files
- show the theme showcasein 53 of 528, across 9 files
- maintain visual identity across all slidesin 50 of 528, across 6 files
- apply the specified colors and fontsin 47 of 528, across 3 files
- get explicit confirmationin 45 of 528, across 1 file
- Generate a design system before codingin 19 of 528, across 6 files
- Maintain at least 4.5:1 color contrast ratioin 19 of 528, across 8 files
- Describe component shapes, colors, shadows, and interaction statesin 18 of 528, across 4 files
- Check Python installation and install if missingin 17 of 528, across 4 files
- Default to html-tailwind if stack is unspecifiedin 17 of 528, across 4 files
Said here and by no other author read
- obtain the brand name, industry, and desired adjectives
- select a mark type matched to the brand needs
- design for reduction starting from the simplest version
- test the mark against real size and color constraints
- explain the reasoning behind specific design choices
- build with clean minimal path data
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.