REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A Claude Code skill that designs a brand identity as one system: logo, typography and colour palette built together from one brief, measured, compared as identity cards, and delivered as a brand guidelines kit.
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/skills/fatihaydost-brand-identity-skill)같은 작업에서 AI를 서비스에 연결하는 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
같은 종류의 작업, Skill 목록과 같은 순서
| 이 항목 brand-identity-skill | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 제작자 | fatihaydost | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 수 | 1 | 1 | 1 | 1 | 1 |
| GitHub 별 | 411 | 468,733 | 234,332 | 150,287 | 144,566 |
| 마지막 코드 변경 | 2026년 11월 16일 | 2026년 11월 19일 | 2026년 4월 20일 | 2026년 11월 18일 | 2026년 11월 18일 |
| 라이선스 | MIT | MIT | – | Apache-2.0 | MIT |
fatihaydost의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
Claude CodeClaude (เว็บ/แอป)
제작자 README와 repo 폴더 기준
GitHub account fatihaydost (person), 5 years old
★ 411 stars, few users so far · code last changed 2026년 11월 16일
26 scripts that can run on a computer: scripts/brand.py, scripts/build_catalog.py, scripts/cdplib.py, scripts/colorlib.py and 22 more
Scripts that go online: scripts/pydeps.py, scripts/typelib.py, scripts/render_png.py
No hooks or writes to machine settings found
Checked automatically from the repo files at commit af7ba40 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
먼저: 어떤 AI를 쓰시나요
쓰는 앱을 고르면 그 앱의 설치 방법만 보여 드립니다
Uploading to claude.ai would fail: the description is over 200 characters (494). Use "Let the AI install it" instead
이 문장을 복사해 Claude Code 채팅에 붙여 넣으세요
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
Claude Code를 다시 열고 /brand-identity를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요
Checked against official docs 2026년 11월 12일 · Source: code.claude.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
제작자 README에서 가져온 명령으로, 제작자 코드를 내려받아 실행해요
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
ChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다
ChatGPT 데스크톱 앱에서 Codex를 열고 이 문장을 채팅에 붙여 넣으세요
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
brand-identity 폴더를 ~/.agents/skills/brand-identity에 넣으세요
~는 홈 폴더($HOME)입니다
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
직접 설치한 Skill은 쓸 수 없고, 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
이 문장을 복사해 Codex 채팅에 붙여 넣으세요 · ChatGPT 데스크톱 앱 안의 Codex, Codex CLI, IDE 확장 프로그램에서 모두 쓸 수 있습니다
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는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요 · 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
이 문장을 복사해 Cursor 채팅에 붙여 넣으세요
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
Cursor Agent 채팅에서 /를 입력하고 brand-identity 선택
Checked against official docs 2026년 11월 12일 · Source: cursor.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
명령을 확인하는 중 · 확인을 통과하면 복사 버튼이 나타나요
Skill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 Claude Code, Codex, Cursor 경로가 들어 있어 AI가 쓰는 앱에 맞게 고릅니다 · 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 2026년 11월 12일 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 SKILL.md가 있는 폴더를 복사하세요.
2026년 11월 11일에 Claude Code, Codex, Cursor 공식 안내로 skill 폴더 확인
아래 글은 제작자 repo에서 온 것이며 PopNx MCP의 지시가 아니에요
처음 8,000자 표시 · GitHub에서 전체 파일 열기
---
name: brand-identity
description: Brand identity sets from one brief - logo, typography and colour palette built together, measured (contrast, colour blindness, glyph coverage, font licences, small-size logo renders) and compared side by side as identity cards, shown on the user's own site, then a brand guidelines kit (PDF, logo files, tokens) for the chosen set. Use for a new brand or any part of one (logo, fonts, colours, or a mix), for refreshing an identity, or for critiquing one, even if the user only says "branding".
license: MIT
---
# Brand Identity
You are the designer. Scripts measure what is broken; you decide what is good. Every claim you make about a
colour, typeface or mark is either measured by a script or labelled as judgement.
## 1. Intake: one message, only what blocks you
Ask in one message (skip anything the user or their site already answered):
- For **logo, type, palette** each: `new` · `refresh` (they have one, evolve it) · `keep` (use as-is) · `none`.
- How many sets: **3** (default), 2, 1 or 4.
- Site URL or files; languages the brand writes in; does the product show numbers.
- Only if still unknown: sector, audience, three attributes, 3–5 competitors.
With a site, run `site extract` first and ask only about what it could not tell you. Details:
`references/discovery-brief.md`.
## 2. Flow and turn plan (~16–20 turns to the checkpoint)
Scripts: `python3 <skill>/scripts/brand.py <command>` (`--help` on each). Put independent commands in one turn.
With uv the scripts fetch their own packages; if `check` lists missing ones, give the user its install line.
1. `check` + `init NAME --sets 3 --langs en,tr [--numbers] [--site URL] [--state logo=keep …] --sector … --audience …
--attributes a,b,c --competitors x,y --tagline … --sentence en='…' --sentence tr='…' --nav A,B,C --cta …
[--source logo=file.svg --source palette=#hex,#hex]` (one turn). Sentence (one per brand language), nav and CTA are
real brand copy for specimens and mocks, in the brand's voice. `--source` gives the asset of a keep/refresh part.
2. Read `references/cohesion.md`, `type.md`, `logo.md`, `ai-defaults.md`, and `color.md` when a palette is
wanted (one turn, ≤ 24 KB). Other cards only when their topic comes up.
3. `fonts search --class … --exclude-defaults` and `site competitors WORK url…` when there are competitors.
4. Write **all sets in one `sets.json`** (format: `templates/sets.example.json`): per set the identity fields,
a partial palette (`brand[]` seeds, name, direction) and the symbol SVG inline.
5. `logos WORK` → look at the contact sheet → fix one defect per mark (name it in `logo.defect`) → `logos WORK`
→ look. Two rounds; a third only to clear a gate or a cliché reading. Letter positions for details are in
`sets/X/logo/build/wordmark-glyphs.json`.
6. `build WORK` → look at `review.png` (not `board.png`, the user's large copy) → fix gates (re-run only
the failing set with `--sets X`).
7. Present the checkpoint (§5) and **stop**. Never pick for the user.
8. After the pick: add 1–2 misuses of this mark (`references/kit.md`), then `kit WORK/sets/X` (`--full` for the
long kit). Say which files are where.
`mix WORK A:logo A:type B:palette --as D` when the user asks for parts of different sets. `critique` for an
existing identity (`references/critique.md`).
## 3. Making the sets
- **One mechanism per set**: a single visual idea that produces the mark, the type choice and the palette
together. Write it as one sentence before choosing anything. One **expression move**: the only loud thing.
- Pick 2–4 decision axes for this brief and place each set on them (−2..+2). Sets should stand apart on at least
two axes; inside a set the three parts sit at the same position.
- **Differentiate against the user's real competitors**, not a generic list. Say in `differs_by` where
the set stands apart.
- **Reflex test**: for each font, colour and mark idea ask "would I propose this for another brand in this
sector?" If yes, justify it from the brief in `defaults_used[]` (id = the flag's id or its logo tag) or change it. At least one set uses nothing
from `ai-defaults.md`. "Feels warm" or "feels premium" is not a reason.
- `keep` parts are constraints: build the new parts to fit them. If a kept part clashes, say so as a suggestion;
never change it.
- Mark `recommended: true` on the set you would defend, and know why.
- Write all free text (names, mechanism, concept, rationale, labels) in the document language (`init --doc-lang`).
## 4. Component craft
**Logo** (`references/logo.md`): a mark identifies, it does not explain. Write 4–6 one-sentence ideas per set,
build one. Draw the symbol on a 100-unit grid from filled primitives; use `data-op="subtract|union|intersect"`
for cut-outs and `data-color="<palette role>"` for colour; never `<text>`. Wordmarks come from the set's display
face automatically; set `case`, `tracking` (1/1000 em) and `tags` (structure vocabulary in `ai-defaults.md`).
Look at 16 and 32 px every round. Add `symbol_small_svg` when the mark clogs at small size.
A **wordmark-only** set still needs (1) one ownable detail drawn on the outlined type with `wordmark_detail_svg`
(wordmark coordinates: cap top y=0, baseline y=100, x in `data-advance` units; each shape is a `data-op` step,
`data-glyph="n"` limits it to the n-th character) and (2) a designed small mark (`symbol_small_svg` or
`logo.monogram`) for 16–48 px. Plain type with a first-letter favicon reads as stock. A detail shape with its own
`data-color` stays a separate colour; `data-glyphs` elements take `data-wght`/`data-opsz` for a sturdier small cut.
Role names resolve to UI tones; brand ids (`brand-1`) keep the exact brand hex; a main part under 3:1 on a ground is
drawn in that ground's ink. `app_icon_svg` (100-unit
grid) lets the tile be part of the icon. When the idea is a dark or coloured surface, set `card.ground` (`dark` or
a role / brand id) so the card shows it.
**Type** (`references/type.md`): display carries the voice, text carries the reading. Pin every variable axis in
`location` (large `opsz` for display, text size for text). Prefer Google Fonts (OFL); Fontshare is link-only;
for a commercial face give the licence note and a rendered free alternative.
**Colour** (`references/color.md`): colour = hue + chroma + lightness + ground. Seeds go in the partial palette;
`palette_build` options in `identity.palette_build` (`extra`: `"#hex:Name:usage"` for a colour with its own job). Logo colours are palette roles, never raw hex.
## 5. Checkpoint message (then stop)
Show the board image path and, per set, in this shape:
```
### A — <Set name> ← recommended
<Mechanism, one sentence.> <Where it differs from the competitors.>
Logo: <idea> · Type: <display / text> · Colour: <2–3 named colours>
Checks: <gates passed or what failed> · <warnings worth knowing, AI-default flags with their reasons>
```
Then: "Pick a set (or ask for parts of different sets). I'll build the guidelines kit for it."
## 6. Honesty
- Gates are measured failures: contrast, licence, glyph coverage, file validity, renders. Warnings are
uncalibrated heuristics; say so when you mention them. In `rationale[]`, `evidence` is `measured` (a script or
site reading), `judgement` (yours), or the research levels `strong | limited | practice`.
- Never claim a colour or font "converts" or "builds trust"; associations are weak and contextual.
- Do not show a set you would not defend. Do not fake approval. Mock data is labelled as such.
## 7. Reference map
| Card | Read when |
|---|---|
| `cohesion.md` | every Create run (axes, mechanism, mixing) |
| `type.md` · `logo.md` · `ai-defaults.md` | every Create run with that component |
| `color.md` | a palette is `new` or `refresh` |
| `discovery-brief.md` | intake is unclear |
| `site-preview.md` | site extract or apply misbehaves |
| `kit.md` | after the pick |
| `accessibility.md` · `reproduction.md` · `tokens-export.md` | contrast q질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.