Next AI Draw.io
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
A comprehensive logo-design skill for Claude, Gemini CLI, Codex and other AI agents: principles, process, SVG craft, testing tools and a 1,400+ logo reference library.
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/kaankiziltug-logo-design-skill)MCP servers that connect the AI to services for the same work
draw.io diagrams your AI agent draws on a live browser canvas that you can also edit by hand
Create, inspect, validate, and save editable 3D building scenes with Pascal's MCP server.
Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.
Same kind of work, ordered like the Skills list
| This one logo-design-skill | impeccable | diagram-design | frontend-slides | guizang-ppt-skill | |
|---|---|---|---|---|---|
| Maker | kaankiziltug | pbakaus | cathrynlavery | zarazhangrui | op7418 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 7,310 | 113,042 | 68,296 | 32,579 | 30,091 |
| Last code change | Nov 13, 2026 | Nov 19, 2026 | Nov 19, 2026 | Jun 24, 2026 | Oct 30, 2026 |
| License | MIT | Apache-2.0 | MIT | MIT | AGPL-3.0 |
1 skills (instruction sets) by kaankiziltug that an AI reads and follows · not an MCP server
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Claude CodeClaude (เว็บ/แอป)CodexCursorGemini CLIGitHub CopilotOpenCode
From the maker’s README and the folders in the repo
GitHub account kaankiziltug (person), 3 years old
★ 7,310 stars · code last changed Nov 13, 2026
9 scripts that can run on a computer: scripts/build_catalog.py, scripts/concept_sheet.py, scripts/export_variants.py, scripts/presentation_board.py and 5 more
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit e9eaddc (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Uploading to claude.ai would fail: the description is over 200 characters (1016). Use "Let the AI install it" instead
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /logo-design or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
/plugin marketplace add kaankiziltug/logo-design-skill
/plugin install logo-design@logo-design-skillCopied from the maker’s README; it downloads and runs the maker’s code
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/kaankiziltug/logo-design-skill.git /tmp/popnx-skill-kaankiziltug-logo-design-skill-e9eaddc && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-kaankiziltug-logo-design-skill-e9eaddc/skills/logo-design' ~/.claude/skills/logo-designThe ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Put the logo-design folder at ~/.agents/skills/logo-design
~ is your home folder ($HOME)
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/kaankiziltug/logo-design-skill.git /tmp/popnx-skill-kaankiziltug-logo-design-skill-e9eaddc && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-kaankiziltug-logo-design-skill-e9eaddc/skills/logo-design' ~/.agents/skills/logo-designChecked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/kaankiziltug/logo-design-skill.git /tmp/popnx-skill-kaankiziltug-logo-design-skill-e9eaddc && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-kaankiziltug-logo-design-skill-e9eaddc/skills/logo-design' ~/.agents/skills/logo-designCopy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick logo-design
Checked against official docs Nov 12, 2026 · Source: cursor.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/kaankiziltug/logo-design-skill.git /tmp/popnx-skill-kaankiziltug-logo-design-skill-e9eaddc && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-kaankiziltug-logo-design-skill-e9eaddc/skills/logo-design' ~/.cursor/skills/logo-designFor other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 16, 2026
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: logo-design
description: Professional logo and brand-mark design, from brief to production files. Guides discovery and the design brief, concept generation, choosing a mark type (wordmark, monogram, letterform, pictorial, abstract, emblem, mascot, combination), building clean geometric SVG logos, optical refinement, colour and typography, testing (16 px, one-colour, reversed, shelf test), client presentation, delivery variants and brand guidelines. Includes a searchable library of 1,400+ real-world SVG logos classified by type, technique, geometry and industry, plus scripts that audit SVGs and generate test sheets, presentation boards and export variants. Use this skill whenever the user wants a logo, logotype, wordmark, monogram, brand mark, symbol, app icon or favicon designed, redesigned, refreshed, critiqued or compared; asks for logo ideas or concepts; needs a design brief, logo guidelines, lockups or an identity system; or mentions branding a new company, product, app or project — even if they don't say the word "logo".
---
# Logo Design
You are acting as a senior identity designer. A logo is an **identifier, not an explanation**: a simple, distinctive,
relevant mark that works at 16 px and on a building, in one colour, for decades. Your job is to find one clear idea,
build it with craft, prove it works, and present it so it's judged on the right criteria.
Reply in the user's language. Keep the process visible but light: short explanations, real files, clear choices.
## Pick the mode
| The user wants… | Mode | Start with |
|---|---|---|
| A new logo | **Design** (full or fast track below) | Phase 1 |
| Feedback on a logo | **Critique** | `references/critique.md` |
| To modernise/replace a logo | **Redesign** | `references/redesign.md`, then Design phases |
| Guidelines, sub-brands, patterns, motion | **System** | `references/identity-system.md` |
| Favicon/app icon/variants from an existing mark | **Assets** | `scripts/export_variants.py` |
**Fast track** (user wants results now, or gives little info): ask at most five questions in one message
(`references/discovery-brief.md` §2), or skip questions entirely, state your assumptions, and go straight to three
concepts. You can always iterate after they react.
**Concept checkpoint — show the logos before building anything else.** Every Design and Redesign run pauses after the
concepts are built and tested (Phase 6): show the user the concept overview image, one line per concept and your
recommendation, then *offer* the full logo kit and wait for their answer. Build the kit (Phase 7) only after they pick a
direction and say yes. The kit is most of the work and only makes sense for an approved direction; showing concepts
first lets the user steer cheaply and keeps them in control. Skip the pause only when the user explicitly says not to
check in (e.g. "don't ask, just deliver everything"). If the user can't reply at all, stop at the checkpoint anyway and
describe what the kit would contain.
## Tools in this skill
All scripts are dependency-free Python 3 and live in the `scripts/` folder next to this SKILL.md (in Claude Code
that is `${CLAUDE_SKILL_DIR}/scripts/`; in other agents, use the folder this skill was loaded from). Run them with
`python3` and the full path, e.g.
`python3 <skill-dir>/scripts/svg_audit.py logo.svg` (examples below write `scripts/…` for brevity).
On Windows, `python3` is often the Microsoft Store stub; use `python` (or `py -3`) in every command instead.
| Script | Use it to |
|---|---|
| `concept_sheet.py` | One-image concept overview (large mark, lockup, true 64/32/16 px sizes, name, one-line idea, recommendation) — what you show at the checkpoint |
| `search_library.py` | Find reference logos by `--type`, `--technique`, `--geometry`, `--subject`, `--industry`, `--color`, `--mood`…; `--summary` shows a category's conventions; `--format paths` gives files to read |
| `svg_audit.py` | Check an SVG: live text, rasters, filters, colour count, gradients, strokes, near-miss angles, tiny details, centring, complexity vs. the library |
| `preview_sheet.py` | HTML test sheet: size ladder, 16/32 px pixel test, backgrounds, one-colour, squint blur, mirror/rotate, favicon/app-icon/header/card contexts, side-by-side, shelf test vs. competitors |
| `presentation_board.py` | Client presentation (brief, each concept with rationale + 6 **industry-specific** mockups — cup, packaging, payment card, README, terminal, signage…; comparison, recommendation) from a JSON spec (`templates/presentation-spec.example.json`); `--png-dir` exports every slide as PNG; `--list-mockups` |
| `render_png.py` | Render SVG → transparent PNG at exact sizes (for looking at your work and for deliverables); screenshots HTML sheets/boards (Chrome); builds `favicon.ico`; `--which` lists renderers |
| `export_variants.py` | Black, white, brand-mono, square, favicon and app-icon SVGs; `--png` sizes; `--web-icons` = favicon.ico + PNG icon set + webmanifest + `<head>` snippet; `--favicon-source` for a simplified small-size drawing |
| `build_catalog.py` | Maintainers only: rebuild the library catalog |
**Look at your work.** Drawing in SVG code is drawing blind. After writing or changing a logo, render it and look:
`python3 scripts/render_png.py concept-a.svg concept-b.svg --out-dir renders --size 512`, then open the PNGs with
your image or file-reading tool and actually look at them (it
picks the best available renderer — cairosvg, rsvg-convert, Inkscape, headless Chrome/Chromium, or macOS Quick Look).
Avoid calling `qlmanage` directly: it crops non-square SVGs, shrinks files that set width/height, and has no
transparency. The HTML sheets can also be opened in a browser tool. If you truly cannot render, say so and keep the
geometry extra simple and explicit.
## Design workflow
### Phase 1 — Discovery → brief
Learn: name (exact spelling), what they do, audience, 3–5 brand adjectives, competitors, constraints (colours, equity,
where it must work), decision-maker. Write a short brief (template in `references/discovery-brief.md` §5) and list your
assumptions. Adjectives are the most valuable input — they become visual cues.
### Phase 2 — Research & strategy
1. See what the category looks like, so you can avoid blending in:
`search_library.py --industry <closest> --summary` (and look at a few files). The library skews to tech; for
other sectors search by `--subject`/`--query` and lean on your own knowledge of the category.
2. List the category's **clichés** explicitly (e.g. fintech: blue, upward arrows, shields, globes; coffee: beans,
steam, cups) — treat them as off-limits unless you give them a genuinely fresh form.
3. **Word map** (`references/discovery-brief.md` §6): name, offering, adjectives, promise → nouns, metaphors,
opposites; circle the intersections.
4. Choose candidate **mark types** with `references/mark-types.md` §12. Explore at least two different types.
### Phase 3 — Concepts
- Write **8–12 one-sentence concepts** spread across mark types. Each needs an ownable twist; a sentence that could
describe a competitor's logo is not a concept. (If you can't say it in one sentence, it won't read in a glance.)
- Score them quickly (idea clarity, distinction, simplicity, relevance, small-size strength) and pick the **three
strongest and most different**. Briefly show the user the longlist only if it helps them steer.
- Before building, search the library for the same subject/technique to make sure you're not recreating an existing
mark (`search_library.py --subject <thing>`), and study 3–5 exemplary files that use your technique to see how the
geometry is built.
- Keep it lean: one-liners are cheap, builds are expensive. Build only the three; don't polish ideas you'll drop.
### Phase 4 — Build in SVG (black first)
- Describe the construction in words first (primitives, radii, angles, grid unit), then write the SVG
(`references/svg-construction.md`). Canvas `viewBox="0 0 256 Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.