agentleFS
ZmokiZmoki/zmoki-astro-starter/.claude/skills/brand/SKILL.md

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

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.
  • Rayan55050Skill

    content

    Создание контента: посты, статьи, тексты

    Also in 3 projects that use this

  • CesarjoquinSkill

    competitors

    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

  • hardikpandyaSkill

    stop-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

  • OpenAISkill

    image-to-code

    Implement a selected image, screenshot, mockup, or Image Gen reference as a faithful, responsive frontend.

    Also in 5 projects that use this

  • AnasX7Skill

    brandkit

    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

  • AnasX7Skill

    minimalist-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

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
  1. Distinctive:

    Agree the direction with the user: when it's open (which color, which font, what voice).

    line 35
  2. Very specific:

    Add a new guide (iconography, imagery, motion, …) → references/adding-a-guide.md

    line 41
  3. Very specific:

    Update the docs: if conventions changed: AGENTS.md → Styling and SETUP.md → Brand.

    line 42
  4. Very specific:

    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).

    line 49
  5. Very specific:

    WCAG AA: Every text/background pair needs at least 4.5:1 (normal text) or 3:1 (large text, borders, focus rings, UI).

    line 50

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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/…)FileCovers
index/src/pages/-/astro/brand/index.astroHome: section cards and summaries
color/src/pages/-/astro/brand/color.astroPalette, swatches, usage conventions
typography/src/pages/-/astro/brand/typography.astroTypefaces, roles, prose specimen
forms/src/pages/-/astro/brand/forms.astroInputs, labels, action button, states
components/src/pages/-/astro/brand/components.astroNav, footer, hero, cards, links, buttons
voice/src/pages/-/astro/brand/voice.astroVoice pillars, house style, rewrites
og/src/pages/-/astro/brand/og.astroOG / social cards: templates and anatomy

Where each guideline is implemented

GuidelineImplemented in
Colorsrc/design-tokens.mjs (the zmoki-* scales) → Tailwind utilities
Typographysrc/design-tokens.mjs (fonts: names + CSS variables), astro.config.mjs (fonts: provider + axes), tailwind.config.mjs (fontFamily, headingFontStack)
Voice & tonevoice.astro itself; nothing else
Components/formsThe real components in src/components/ and src/layouts/

Workflow

  1. Orient. /run and open the guideline page you're changing. Its .astro frontmatter usually holds the data you'll edit.
  2. Agree the direction with the user when it's open (which color, which font, what voice).
  3. 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
  4. Update the docs if conventions changed: AGENTS.md → Styling and SETUP.md → Brand.
  5. 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 in src/design-tokens.mjs (and src/og/theme.ts reads 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 build

Then /run and compare the guideline page you changed with a couple of real pages (/, a blog post). Each task reference adds its own checks.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.