DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to get design tokens and a font sheet for a product with Brand Identity Skill

Export the chosen palette and type as CSS, SCSS, Tailwind or DTCG JSON tokens with a font sheet.

  • Content
  • Intermediate
  • 45 minutes
  • From the README
  • Claude Code

Who it is forA front-end developer building a product who needs brand colours and type in code and no manual copying.

The problemBrand values are often copied by hand into stylesheets, so they drift from the approved palette and fonts.

The outcomeDesign token files in the formats the README lists, plus a font sheet with embed code, from the chosen set.

What you need first

  • Claude Code, or another agent that reads Agent Skills (the README tests end to end in Claude Code only)
  • Python 3.10+ and a Chromium-based browser (Chrome, Chromium, Edge or Brave)
  • uv, ideally, so the scripts install their own Python packages on first use
  • Internet access to Google Fonts and PyPI during setup and measurement

Steps

  1. Run git clone https://github.com/fatihaydost/brand-identity-skill.
  2. Run mkdir -p ~/.claude/skills.
  3. Run ln -s "$PWD/brand-identity-skill/skills/brand-identity" ~/.claude/skills/brand-identity.
  4. Run python3 skills/brand-identity/scripts/brand.py check from the clone to see what is missing.
  5. After picking a set, ask Claude Code for the kit and use the design tokens and font sheet in your project.

Prompt for your agent

Using the repo fatihaydost/brand-identity-skill, build the kit for the set I pick from <brief> and export its design tokens as CSS and Tailwind. Expected output: token files and a font sheet with embed code. Verify that the font sheet links to the fonts rather than redistributing them.

Caveat. The brand's fonts are never subset or redistributed, so the project must load them through the links and embed code the kit provides.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page