agentleFS
Sign inStart free
trac3r00trac3r00/agent-skills/skills/design/SKILL.md

design

Skill0 starsChanged 3 months agoMITView on GitHub

Claude-grade visual design outside Claude Code — distinctive web/UI design direction, poster and canvas art philosophy, and a 10-theme styling library, portable to any agent that reads SKILL.md. Use when building or restyling a UI, landing page, poster, slide deck, static art piece, or any artifact that must not look AI-generated.

197 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use banner-design, ui-styling 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.
  • seikaikyoSkill

    banner-design

    Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with optional generated or supplied visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage.

    Also in 38 projects that use this

  • MicrosoftSkill

    ui-styling

    Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components.

    Also in 39 projects that use this

  • seikaikyoSkill

    brand

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

    Also in 43 projects that use this

  • mayankjain1815-commitsSkill

    infra-audit

    Reads docker-compose, env files, ORM configs, and connection strings to map current infrastructure. Flags missing layers (cache, queue, analytics) based on observed access patterns. Outputs a structured infrastructure manifest.

    Also in 3 projects that use this

  • JetBrainsSkill

    slides

    Create and edit presentation slide decks (`.pptx`) with PptxGenJS and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding charts/diagrams/visuals, or diagnosing layout issues such as overflow, overlaps, and font substitution.

    Also in 42 projects that use this

  • AnthropicSkill

    design-system

    Audit, document, or extend your design system. Use when checking for naming inconsistencies or hardcoded values across components, writing documentation for a component's variants, states, and accessibility notes, or designing a new pattern that fits the existing system.

    Also in 49 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only then write code, deriving every decision from the plan.

    line 49

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

Design

Distinctive visual design guidance distilled from Anthropic's design skills (frontend-design, canvas-design, theme-factory), consolidated so any agent — not just Claude Code — can produce work with a deliberate point of view. The references below carry Anthropic's original guidance verbatim; they are the skill, not background reading.

Route by output type (MANDATORY: read the matched reference before designing)

TaskRead
Web UI, landing page, app screen, component redesignreferences/web-interfaces.md
Poster, album art, static PNG/PDF art piece, visual identityreferences/canvas-art.md
Styling an existing artifact (slides, docs, reports) with a coherent themereferences/themes.md

Generative/algorithmic art (p5.js, flow fields, particles) is its own skill: skills/algorithmic-art.

Core discipline (orientation only — never a substitute for the reference)

  1. Ground in the subject. Pin down what the thing is, who it's for, and its single job before designing. Distinctive choices come from the subject's own world — its materials, instruments, vernacular — not from a style library.
  2. Avoid the AI-default looks. Current AI design clusters around: cream background + high-contrast serif + terracotta accent; near-black + one acid accent; broadsheet hairlines + zero border-radius. Also: purple gradients, uniform rounded corners, excessive centering, Inter-for-everything. These are defaults, not choices — spend freedom elsewhere unless the brief asks for one.
  3. One signature element. Spend boldness in a single memorable place; keep everything around it quiet. Cut decoration that does not serve the brief.
  4. Typography carries personality. Pair display and body faces deliberately with a clear scale. Need font files? scripts/fetch_fonts.py downloads a curated OFL set (display/body/mono) on demand — run with no args to list.
  5. Plan, critique, then build. Draft a compact token system (4-6 named hex colors, 2+ type roles, layout concept, signature element). Review it against the brief: any part you'd produce for any similar prompt gets revised. Only then write code, deriving every decision from the plan.
  6. Quality floor, unannounced. Responsive to mobile, visible keyboard focus, reduced-motion respected, nothing overlapping or clipped.

Verify like a designer

Render the real artifact and look at it — screenshot web pages (the webapp-testing skill automates this), open generated PDFs/PNGs. Fix what you see, re-render. A static code read is not observation. Before shipping, remove one accessory (Chanel's rule): the last pass deletes, it does not add.

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.

Check your setup, free