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

How to critique an existing brand identity with measured checks with Brand Identity Skill

Get contrast, colour-blindness, glyph and licence checks on a logo, type and palette you already use.

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

Who it is forA designer or brand owner reviewing an identity they already have and needing evidence before changing it.

The problemJudging an existing identity by eye misses contrast failures, missing language glyphs and font licence issues.

The outcomeA critique of the current identity with measured results, with failed checks marked as gates and heuristics marked as warnings.

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. Install the plugin with /plugin marketplace add fatihaydost/brand-identity-skill and /plugin install brand-identity@brand-identity-skill in Claude Code.
  2. Share your current logo, fonts and colours with Claude Code.
  3. Ask: Critique our brand identity.
  4. Read the measured results and note which items are gates that failed and which are warnings or judgement.

Prompt for your agent

Using the repo fatihaydost/brand-identity-skill, critique the existing identity described in <files or description> and report contrast (WCAG 2.2), colour-blindness, glyph coverage and font licence results. Expected output: a critique that separates failed measurements from warnings and judgement. Verify that each failed measurement names the colour pair or font it refers to.

Caveat. The critique covers measured checks only, and any judgement on taste is labelled as judgement rather than fact.

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