agentleFS
Sign inStart free
wtsi-hgiwtsi-hgi/agentskills/skills/frontend-design/SKILL.md

frontend-design

Skill1 starsChanged 40 days agoMITView on GitHub

Create distinctive, production-grade frontend interfaces that avoid generic AI aesthetics. Use when building web components, pages, dashboards, or styling web UI.

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use instantly-campaign, albert-dm 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.
  • yawningwhaleAISkill

    instantly-campaign

    Create a new Instantly cold-email campaign in the proven 5-email structure of the user's top-performing campaign (~16% reply rate). Use when the user wants to launch a new outbound campaign, write a cold email sequence, create an Instantly campaign, draft outreach for a new service or niche, or set up a sales sequence.

    Also in 6 projects that use this

  • yawningwhaleAISkill

    albert-dm

    Reply to DMs and messages the way Albert would. Use when the user asks "how would Albert reply to this", pastes a conversation and wants an Albert-style response, or asks you to draft/write a DM in Albert's voice. Albert sells AI voice agents / automations to local service businesses (Go High Level, lead follow-up, bookings).

    Also in 5 projects that use this

  • naman10parikhSkill

    ecosystem-reference

    Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.

    Also in 5 projects that use this

  • naman10parikhSkill

    fractal-delegation

    Also in 5 projects that use this

  • julianoczkowskiSkill

    brief-to-tasks

    Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".

    Also in 7 projects that use this

  • SeifBenayedSkill

    file-reading

    Use this skill when a file has been uploaded but its content is NOT in your context — only its path at /mnt/user-data/uploads/ is listed in an uploaded_files block. This skill is a router: it tells you which tool to use for each file type (pdf, docx, xlsx, csv, json, images, archives, ebooks) so you read the right amount the right way instead of blindly running cat on a binary. Triggers: any mention of /mnt/user-data/uploads/, an uploaded_files section, a file_path tag, or a user asking about an uploaded file you have not yet read. Do NOT use this skill if the file content is already visible in your context inside a documents block — you already have it.

    Also in 6 projects that use this

  • +6 more from naman10parikh

The file

We split this skill into the rules it gives an agent

4 rules. 1 is common, 3 are distinctive, and 0 are very specific to this project.

  • 1

    Common

    Most of the 181 edited versions we read keep these.

  • 3

    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. Common:

    Before coding, commit to a BOLD aesthetic direction:

    line 13
  2. Distinctive:

    NEVER: overused fonts, cliche purple-on-white gradients, predictable layouts, cookie-cutter components.

    line 37
  3. Distinctive:

    When building for a specific project, also read the project's conventions skill for tech stack, component patterns, and styling rules.

    line 46
  4. Distinctive:

    Test light/dark modes through the same mechanism the application uses in production.

    line 54

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

Frontend Design Skill

Build distinctive, production-grade frontend interfaces. Implement real working code with exceptional aesthetic attention.

Design Thinking

Before coding, commit to a BOLD aesthetic direction:

  • Purpose/audience. What problem does this interface solve?
  • Tone. Pick a strong direction: brutally minimal, maximalist, retro- futuristic, organic, luxury, playful, editorial, brutalist, art deco, soft pastel, industrial, etc. Use for inspiration but make it your own.
  • Differentiation. What makes this UNFORGETTABLE?

Execute with precision. Bold maximalism and refined minimalism both work - the key is intentionality.

Aesthetics

  • Typography: Distinctive, characterful fonts. NEVER generic (Arial, Inter, Roboto, system fonts). Pair a display font with a refined body font.
  • Color: Cohesive palette via CSS variables. Dominant colors with sharp accents > timid, evenly-distributed palettes.
  • Motion: CSS-first animations; Motion library for React. Focus on high- impact moments (staggered page-load reveals, surprising hover states).
  • Layout: Asymmetry, overlap, diagonal flow, grid-breaking elements, generous negative space OR controlled density.
  • Atmosphere: Gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, decorative borders, grain overlays.

NEVER: overused fonts, cliche purple-on-white gradients, predictable layouts, cookie-cutter components. No two designs should look the same. Vary themes, fonts, aesthetics across generations.

Match implementation complexity to vision: maximalist needs elaborate code; minimalist needs restraint and precision.

Project Integration

When building for a specific project, also read the project's conventions skill for tech stack, component patterns, and styling rules.

Visual Verification

  • Prove every perceptual result per testing-principles § Perceptual Requirements. Borders, focus rings, selection states, hover states, and animation end states all fall under it.
  • Test light/dark modes through the same mechanism the application uses in production. With Tailwind v4, confirm generated utilities and theme variables actually respond at runtime before tuning colours or specificity.

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