agentleFS
evanmmcanulty-blipevanmmcanulty-blip/claude-skills/design-critique/SKILL.md

design-critique

Skill0 starsChanged 6 months agoNo licenceView on GitHub

Brand-agnostic design audit skill. Runs a structured critique against any design artifact (web surface, native app screen, print piece, deck, packaging) and any brand spec you supply. Combines universal craft criteria (typography, color, layout, hierarchy, motion, performance, imagery), horizon-positioning audit (against the three-pressures thesis from horizon-check), and brand-compliance audit (against the spec you paste in or reference). Use when reviewing a design surface for any project, brand, or client. Trigger on `#design-critique`, "design audit", "design check", "is this on-brand", "audit this design", "review this design", "design QA", or whenever a visual artifact needs a senior pass. For APAR work, use `apar-design-critique` instead — it pre-loads APAR brand context. For brand-system creation (not audit), this skill is the wrong tool — use a strategy skill.

37 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use color-system, presentation-design 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.
  • launchapp-devSkill

    color-system

    Build a comprehensive color system with palette generation, semantic mapping, and accessibility compliance.

    Also in 3 projects that use this

  • ArnavPuriSkill

    presentation-design

    Design slide decks as HTML/CSS (custom or reveal.js): slide layouts on a fixed 16:9 canvas, presentation typography, slide charts, builds and transitions, speaker notes, and PDF export. Use for decks presented or shared from the browser; for native .pptx files use a PowerPoint-specific tool. Trigger phrases: "presentation", "slide deck", "slides", "pitch deck", "keynote", "reveal.js", "slide design", "presentation template", "speaker notes"

    Also in 3 projects that use this

  • brianciouSkill

    ux-writing

    UX writing guidelines for reviewing and optimizing interface copy. Use when the user asks to review, improve, or rewrite UI text including button labels, error messages, onboarding flows, or any interface copy. Apply when auditing microcopy for web apps, mobile apps, or any digital product requiring clear, user-centered communication.

    Also in 5 projects that use this

  • jpoindexterSkill

    design-system-audit

    Audit code for design system violations - grid spacing, tokens, existing components

    Also in 3 projects that use this

  • agentes100xSkill

    brand-identity

    Proporciona la fuente única de verdad para lineamientos de marca, tokens de diseño y voz/tono. Usa esto para mantener consistencia visual y de comunicación.

    Also in 3 projects that use this

  • nandanosqlSkill

    design-brief

    Create a design brief that clearly communicates the product context, user needs, constraints, and success criteria to the design team — bridging PM requirements and design execution.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 10 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 31 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.

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.