brandkit
Skill3 starsChanged 45 days agoMITView on GitHub
Generate premium brand-identity imagery, logo systems, brand-guideline boards, visual-world directions, and identity mockups. Use for image-based brand exploration and presentation systems. Produce brand visuals only; do not implement websites, design mobile product screens, or write application code.
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 72 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Create a coherent identity system with a defensible concept, not a collection of unrelated logo mockups.
- Distinctive: line 16
Check small-size recognition, monochrome behavior, consistency, legibility, and category distinctiveness.
- Distinctive: line 21
Keep logo geometry simple enough to recognize at favicon size.
- Distinctive: line 23
Use sparse, readable typography and realistic mockups that reveal how the identity behaves.
- Distinctive: line 24
Avoid generic orbit marks, random shields, meaningless hexagons, fake embossing, and crowded logo walls.
- Distinctive: line 25
Keep palette disciplined and provide monochrome or single-color behavior when relevant.
- Distinctive: line 26
Do not fabricate legal claims, awards, partnerships, or cultural symbolism without grounding.
- Distinctive: line 27
Treat reference brands as directional evidence, never as shapes to copy.
- Distinctive: line 31
Read only the relevant section of references/full-guide.md:
- Very specific: line 39
Use rg -n "<heading>" references/full-guide.md.
“Common” is measured: kept by at least 6 in 10 of the 72 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Brand Kit Image Generation
Create a coherent identity system with a defensible concept, not a collection of unrelated logo mockups.
Workflow
- Extract brand audience, category, positioning, personality, competitors, cultural constraints, and required applications.
- State a short strategic idea and derive two or three distinct logo concepts from meaning, not decoration.
- Choose one direction and lock logo logic, palette, typography, imagery, layout grid, and material language.
- Generate a focused board or requested identity assets using realistic, relevant applications.
- Check small-size recognition, monochrome behavior, consistency, legibility, and category distinctiveness.
Non-negotiables
- Build the symbol from a clear idea: monogram, product action, metaphor fusion, negative space, or construction geometry.
- Keep logo geometry simple enough to recognize at favicon size.
- Show one coherent system rather than many unrelated styles on one board.
- Use sparse, readable typography and realistic mockups that reveal how the identity behaves.
- Avoid generic orbit marks, random shields, meaningless hexagons, fake embossing, and crowded logo walls.
- Keep palette disciplined and provide monochrome or single-color behavior when relevant.
- Do not fabricate legal claims, awards, partnerships, or cultural symbolism without grounding.
- Treat reference brands as directional evidence, never as shapes to copy.
Detailed reference
Read only the relevant section of references/full-guide.md:
- Strategy and logo ideation: search
BRAND STRATEGY FIRSTorLOGO CONCEPT METHODS. - Board layouts: search
BOARD COMPOSITION DNA. - Category-specific directions: search
VISUAL MODES. - Typography, taglines, imagery, mockups, and color: search the matching heading.
- Prompt construction and final QA: search
PROMPT TEMPLATEorFINAL OUTPUT STANDARD.
Use rg -n "<heading>" references/full-guide.md; do not load the complete guide for a narrow request such as a logo concept or palette exploration.
Other versions78 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 78
- caorushizi/mediago★ 9.3ksame name
- plugin87/ux-ui-agent-skills★ 3.1ksame name
- hamzafarooq/claude-code-starter★ 145same name
- hushh-labs/hushh-research★ 39same name
- kresogalic8/unwatched★ 35same name
- jmxt3/gitscape.ai★ 33same name
- fathomise/MailFathom★ 20same name
- Krzysztof318/MailFathom★ 20same name
- ivanrvpereira/.agents★ 19same name
- rylsherdamz-rgb/stellar-forge★ 17same name
68 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use design-taste-frontend-v1, write-swift and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
HK-hubSkilldesign-taste-frontend-v1
The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.
Also in 30 projects that use this
sanmidableSkillwrite-swift
Also in 5 projects that use this
wxyhgkSkillfind-animation-opportunities
Search a codebase or UI for places that don't animate but should, and reject everything that shouldn't. Read-only; it proposes motion with exact values, it does not implement it. Use when the user asks "what could be animated here?" or wants to "make this feel more alive". For fixing existing animations, use improve-animations or review-animations instead.
Also in 10 projects that use this
attentiondotnetSkillanimation-vocabulary
Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.
Also in 11 projects that use this
cal1888Skillpick-ui-library
Pick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.
Also in 7 projects that use this
arkanSkillreview-animations
Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.
Also in 12 projects that use this
In this repository64 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/bro-skills.mdcCursor rule
- .agents/skills/llms.txtllms.txt
- bro-mcp-loopSkill
- ci-security-scanning-with-strixSkill
- design-taste-frontendSkill
- fix-security-vulnerabilities-with-strixSkill
- full-output-enforcementSkill
- gpt-tasteSkill
- high-end-visual-designSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- image-to-codeSkill
- industrial-brutalist-uiSkill
- managed-pentesting-with-strixSkill
- minimalist-uiSkill
- penetration-testing-with-strixSkill
- ponytailSkill
- redesign-existing-projectsSkill
- speckit.ai-engineerSkill
- speckit.analyzeSkill
- speckit.architectureSkill
- speckit.backendSkill
- speckit.backlogSkill
- speckit.checkerSkill
- speckit.checklistSkill
- speckit.clarifySkill
- speckit.constitutionSkill
- speckit.contentSkill
- speckit.databaseSkill
- speckit.dddSkill
- speckit.debugSkill
- speckit.devopsSkill
- speckit.diffSkill
- speckit.event-realtimeSkill
- speckit.frontendSkill
- speckit.game-embeddedSkill
- speckit.game-native-jsSkill
- speckit.geoSkill
- speckit.identity-accessSkill
- speckit.identitySkill
- speckit.implementSkill
- speckit.mapSkill
- speckit.migrateSkill
- speckit.payment-fintechSkill
- speckit.planSkill
- speckit.quizmeSkill
- speckit.reviewerSkill
- speckit.roadmapSkill
- speckit.securitySkill
- speckit.seoSkill
- speckit.specifySkill
- speckit.sre-observabilitySkill
- speckit.statusSkill
- speckit.tasksSkill
- speckit.taskstoissuesSkill
- speckit.testerSkill
- speckit.uatSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

