brand
Skill4 starsChanged 20 days agoMITView on GitHub
Work on the site's brand guidelines. The living guideline is the internal style guide under /-/astro/brand/ (color, typography, forms, components, voice & tone) — this skill orients you there and helps you improve or adapt it, keeping the implementation in sync. Use when the user wants to evolve the brand: recolor/re-skin, define a custom brand color, swap fonts, rewrite voice/tone or house style, adapt components/forms, add a new guide/section, or edit any brand page.
64 other projects use a version of this.
Adopted by
Most recently taken up by
- irank786/Claude-skillstheir own version, first seen Nov 16, 2026
- zstvns/design-skillstheir own version, first seen Nov 15, 2026
- kobiniv888-ai/Claude-codetheir own version, first seen Nov 15, 2026
- nextlevelbuilder/ui-ux-pro-max-skilltheir own version, first seen Nov 15, 2026
- whoamnesia/astudio-aiotheir own version, first seen Nov 8, 2026
- caiopizzol/brand.mdtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use content, competitors and 10 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.
Rayan55050Skillcontent
Создание контента: посты, статьи, тексты
Also in 3 projects that use this
CesarjoquinSkillcompetitors
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.
Also in 3 projects that use this
hardikpandyaSkillstop-slop
Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.
Also in 4 projects that use this
OpenAISkillimage-to-code
Implement a selected image, screenshot, mockup, or Image Gen reference as a faithful, responsive frontend.
Also in 5 projects that use this
AnasX7Skillbrandkit
Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional logo concepting, refined composition, sparse typography, strong symbolic meaning, premium mockups, art-directed imagery, and flexible grid layouts.
Also in 5 projects that use this
AnasX7Skillminimalist-ui
Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.
Also in 5 projects that use this
- +1 more from AnasX7
Other versions64 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 64
- nextlevelbuilder/ui-ux-pro-max-skill★ 150ksame name
- joye61/pic-smaller★ 2.9ksame name
- Ohh-889/skyroc-admin★ 795same name
- cdavid817/vanehub-ai★ 116same name
- saksham10arora-dotcom/everything-claude-codex★ 96same name
- cofoundy/brand-skills★ 79same name
- caiopizzol/brand.md★ 39same name
- zstvns/design-skills★ 33same name
- b1rdmania/claude-brand-skills★ 20same name
- rylsherdamz-rgb/stellar-forge★ 17same name
54 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.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyticsSkill
- imagesSkill
- og-imagesSkill
- redirectsSkill
- runSkill
- structured-dataSkill
- update-depsSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
Agree the direction with the user: when it's open (which color, which font, what voice).
- Very specific: line 41
Add a new guide (iconography, imagery, motion, …) → references/adding-a-guide.md
- Very specific: line 42
Update the docs: if conventions changed: AGENTS.md → Styling and SETUP.md → Brand.
- Very specific: line 49
No inline hex in templates: Use zmoki-* utilities. Raw hex lives only in src/design-tokens.mjs (and src/og/theme.ts reads from it).
- Very specific: line 50
WCAG AA: Every text/background pair needs at least 4.5:1 (normal text) or 3:1 (large text, borders, focus rings, UI).
“Common” is measured: kept by at least 6 in 10 of the 19 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
The brand guideline is the internal, noindex style guide under /-/astro/brand/. It's the source of truth for how the site looks and sounds. Change a guideline page and the code it describes in the same pass, so they never drift. If they disagree, that's the bug to fix.
The pages read the site name from site.name (src/site.config.ts); the rest of the copy is written in the pages themselves.
Guideline pages
Page (/-/astro/brand/…) | File | Covers |
index/ | src/pages/-/astro/brand/index.astro | Home: section cards and summaries |
color/ | src/pages/-/astro/brand/color.astro | Palette, swatches, usage conventions |
typography/ | src/pages/-/astro/brand/typography.astro | Typefaces, roles, prose specimen |
forms/ | src/pages/-/astro/brand/forms.astro | Inputs, labels, action button, states |
components/ | src/pages/-/astro/brand/components.astro | Nav, footer, hero, cards, links, buttons |
voice/ | src/pages/-/astro/brand/voice.astro | Voice pillars, house style, rewrites |
og/ | src/pages/-/astro/brand/og.astro | OG / social cards: templates and anatomy |
Where each guideline is implemented
| Guideline | Implemented in |
| Color | src/design-tokens.mjs (the zmoki-* scales) → Tailwind utilities |
| Typography | src/design-tokens.mjs (fonts: names + CSS variables), astro.config.mjs (fonts: provider + axes), tailwind.config.mjs (fontFamily, headingFontStack) |
| Voice & tone | voice.astro itself; nothing else |
| Components/forms | The real components in src/components/ and src/layouts/ |
Workflow
- Orient.
/runand open the guideline page you're changing. Its.astrofrontmatter usually holds the data you'll edit. - Agree the direction with the user when it's open (which color, which font, what voice).
- Change the guideline and its implementation together, following the task reference:
- Recolor, re-skin, custom brand color →
references/colors.md - Swap fonts →
references/typography.md - Rewrite voice, tone, house style →
references/voice.md - Adapt components or forms →
references/components.md - Add a new guide (iconography, imagery, motion, …) →
references/adding-a-guide.md
- Recolor, re-skin, custom brand color →
- Update the docs if conventions changed:
AGENTS.md→ Styling andSETUP.md→ Brand. - Verify (below).
OG cards read the brand tokens, so color and font changes reach them automatically. For card-specific tuning, use /og-images.
Rules
- No inline hex in templates. Use
zmoki-*utilities. Raw hex lives only insrc/design-tokens.mjs(andsrc/og/theme.tsreads from it). - WCAG AA. Every text/background pair needs at least 4.5:1 (normal text) or 3:1 (large text, borders, focus rings, UI). Fix the shade; don't ship a failing pair. Details in
references/colors.md. - No role tokens (
zmoki-primary,-accent, …). The system is built on palette groups. - Font names live once, in
src/design-tokens.mjs. The layouts'<Font>tags and Tailwind read the CSS variables from there; don't hard-code a family in a layout.
Verify
npm run format # Tailwind class order is plugin-enforced
npm run check
npm run buildThen /run and compare the guideline page you changed with a couple of real pages (/, a blog post). Each task reference adds its own checks.
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.

