agentleFS
qyndexqyndex/claude-init/.claude/skills/front-end-design/SKILL.md

front-end-design

Skill2 starsChanged 5 months agoMITView on GitHub

Use when designing a new UI, redesigning a screen, building a landing/marketing page, or making something look better. Orchestrates the visual-craft skills (tailwind-discipline, typography, animation-discipline, image-generation, creative-web). Round 9 C.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Sketch with components: before pixels. List the components and their hierarchy.

    line 24
  2. Very specific:

    Design tokens from tokens.ts: No magic hex codes, no inline arbitrary values without comment.

    line 42
  3. Very specific:

    Dark mode is default-on: Use Tailwind class strategy + semantic tokens (--surface-1, NOT gray-900).

    line 44
  4. Distinctive:

    No AI-slop placeholders: Every visual choice ties to the spec's user story or concept.

    line 46
  5. Distinctive:

    Default Tailwind blues + grays everywhere

    line 51
  6. Very specific:

    If a spec explicitly says "high-artistic, modern, creative" or "stunning landing page" or similar, hand off to designer agent …

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Front-End Design

Mandate

Force a CONCEPTUAL DIRECTION before styling. The output should look intentional, not "generated default Tailwind." Apply Anthropic's Artifact aesthetic: clean, opinionated, content-forward.

Procedure

  1. State the concept FIRST (one paragraph in the spec):
    • Mood: editorial / brutalist / maximalist / retro-futuristic / minimalist / art-deco / playful
    • Voice: serious / friendly / technical / approachable
    • Hero archetype: dashboard / marketing / app / form / data / playground
    • Reference site(s) for inspiration
  2. Read design tokens from src/styles/tokens.ts (or Tailwind config). Add missing tokens to the file FIRST, then use them — no inline arbitrary values.
  3. Sketch with components before pixels. List the components and their hierarchy.
  4. Required states per screen (no "lonely success state"):
    • loading
    • empty
    • error
    • partial-data
    • success
  5. Responsive breakpoints: mobile-first; sm/md/lg/xl/2xl. Design at 375px AND 1440px minimum.
  6. Apply sister skills:
    • tailwind-discipline — utility class hygiene
    • typography — type scale + measure
    • animation-discipline — motion design
    • image-generation — when raster/illustration needed
    • creative-web — when "wow factor" justified

Hard rules

  • Concept BEFORE styling. "Modern minimal" is not a concept — that's a default.
  • Design tokens from tokens.ts. No magic hex codes, no inline arbitrary values without comment.
  • Required states. Loading / empty / error / success are non-negotiable.
  • Dark mode is default-on. Use Tailwind class strategy + semantic tokens (--surface-1, NOT gray-900).
  • a11y is invariant. Axe-core in CI must pass (Round 8 audit proposed this).
  • No AI-slop placeholders. Every visual choice ties to the spec's user story or concept.

Anti-patterns (immediate reject)

  • Lorem ipsum in shipped UI
  • Default Tailwind blues + grays everywhere
  • 1000px-wide text lines (no max-w-prose)
  • Fixed pixel font sizes everywhere (no responsive scale)
  • Hover states without focus states (a11y fail)
  • Animations without prefers-reduced-motion opt-out

When to delegate to designer agent

If a spec explicitly says "high-artistic, modern, creative" or "stunning landing page" or similar, hand off to designer agent (.claude/agents/specialists/designer.md) — they own this skill family and can iterate.

Done means

  • Concept statement documented in spec
  • Required states all implemented
  • Mobile + desktop both look intentional
  • Axe + Lighthouse pass
  • Reviewer signs off on visual craft, not just code correctness

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.