assets/skills/marketing/logo/SKILL.md
Generate comprehensive logo design specifications, brand identity guidelines, and visual concepts. Use when user says "design logo", "create logo", "brand identity", "logo concept", "visual identity".
npx skillsauth add phuthuycoding/moicle marketing-logoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Produce a logo + brand identity specification that a designer can execute (or you can use as a direct prompt to a generative tool). Output is a brand guidelines doc, not finished art.
/marketing/marketing-videoDISCOVER → CONCEPT → DESIGN → REFINE → DELIVER
Goal: capture brand intent before sketching.
Ask the user (skip what's known):
| Field | Example | |-------|---------| | Name + tagline | "Acme — DevOps for indie teams" | | 3-5 personality adjectives | "modern, technical, irreverent, sharp, friendly" | | Primary audience | "Solo / small-team backend engineers" | | Industry | "Developer tools / SaaS" | | Competitors (3-5) | + 1 line each on what their logo says about them | | Style direction (pick 1-2) | minimal / wordmark / monogram / abstract mark / illustrative / mascot | | What to AVOID | "no cliché cloud icons, no gradients on the mark" | | Where it lives | favicon + GitHub avatar + landing hero + dark / light themes + print | | Color hints | "must work in single-color print + on dark UI" | | Budget for the brand | "MVP — logo + 1 palette + 2 fonts" vs "full system" |
Goal: present 3 distinct concepts. Same concept in 3 colors ≠ 3 concepts.
Each concept must have:
## Concept {N}: {short name}
**Direction:** {wordmark / monogram / abstract mark / etc.}
**Rationale:** Why this matches the brand personality + audience. Cite 2-3 adjectives.
**Differentiation:** What competitor it does NOT look like, and why that matters.
**ASCII sketch** (rough — describes shape, not pixel-perfect):
| A C M E | |___________|
**Inspiration:** 2-3 reference links (existing logos, styles)
**Risks:** What could go wrong (e.g., "monogram unreadable below 24px")
Goal: produce specifications a designer can build.
### Logo: {name}
**Lockup**
- Primary: {wordmark / mark / mark + wordmark side-by-side / stacked}
- Secondary (when primary doesn't fit): {variant}
- Icon-only (favicon, avatar): {variant}
**Geometry**
- Grid: {e.g., "8-unit grid, mark fits in 8x8 square"}
- Proportions: {e.g., "wordmark cap-height = 5 units; mark = 8 units; gap = 2 units"}
**Clear space**
- Minimum: {e.g., "1 cap-height on all sides"}
**Minimum size**
- Digital: {e.g., "24px height"}
- Print: {e.g., "8mm height"}
Pick a primary + secondary + neutrals. Provide every color in:
| Token | HEX | RGB | HSL | Use |
|-------|-----|-----|-----|-----|
| `--brand-primary` | #0F172A | 15,23,42 | 222 47% 11% | logo, headlines |
| `--brand-accent` | #14B8A6 | 20,184,166 | 173 80% 40% | CTA, links |
| `--neutral-fg` | #1F2937 | 31,41,55 | 220 26% 14% | body text |
| `--neutral-bg` | #F8FAFC | 248,250,252 | 210 40% 98% | page bg |
Pick 1 display + 1 body font (or 1 font in 2 weights). Note:
Goal: test the design against real use, iterate.
Goal: ship a single doc + asset list a designer / dev can use.
brand-guidelines.md skeleton# {Brand} Brand Guidelines
## Logo
- {Primary, secondary, icon lockups as files: SVG + PNG}
- Clear space + min size rules
- Wrong uses (with examples: don't recolor, don't squish, don't add effects)
## Color
- Token table from Phase 3.2
- Usage rules (when primary vs accent)
- Accessibility (contrast notes)
## Typography
- Stack from Phase 3.3
- Hierarchy: H1/H2/H3/body sizes
- Web vs print
## Voice
- From Phase 3.4
- Sample headline + body + CTA copy
## Examples
- 1 hero, 1 card, 1 button shown with the brand applied
logo-primary.svg + logo-primary.png (1x, 2x, 4x)logo-secondary.svg + .pnglogo-mark.svg + .pngfavicon.ico (16, 32, 48), apple-touch-icon.png (180×180), og-image.png (1200×630)colors.css (CSS variables) + tailwind.config.js snippet (if Tailwind).md| When | Use |
|------|-----|
| Full marketing plan (logo + content + video) | /marketing |
| Write content with the brand | /marketing-content |
| Create video with the brand | /marketing-video |
| Document brand guidelines as a doc | /docs-write |
| Phase | Agent | Purpose |
|-------|-------|---------|
| DISCOVER | @docs-writer | Capture brand brief |
| CONCEPT | @clean-architect | Structure the system |
| DESIGN | @docs-writer | Spec documents |
| DELIVER | @docs-writer | Brand guidelines doc |
development
Test-Driven Development workflow. Use when doing TDD, writing tests first, or when user says "tdd", "test first", "test driven", "red green refactor".
development
Thorough pull request review workflow with architecture compliance checks. Use when reviewing pull requests, checking code changes, or when user says "review pr", "check pr", "review code", "pr review", "review pull request".
development
Review local branch changes for architecture compliance, conventions, and code quality before pushing/PR. Stack-aware — detects the project stack and applies the matching rules. Use when user says "review changes", "review branch", "check branch", "check changes", "review my code", "review before pr".
testing
DDD architecture compliance review with automated checks and review loop. Use when user says "architect-review", "architecture review", "review architecture", "check architecture", "review ddd", "ddd review".