agentleFS
Sign inStart free
roborracleroborracle/agent-workflow-kit/skills/frontend-design/SKILL.md

frontend-design

Skill0 starsChanged 3 months agoMITView on GitHub

Create distinctive, production-grade frontend interfaces with high design quality. Use when building web components, pages, applications, React/Vue/Angular components, handling state management, or optimizing frontend performance. Generates creative, polished code avoiding generic AI aesthetics.

187 other projects use a version of this, 111 of them edited.

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

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics.

    line 9
  2. Distinctive:

    Before coding, commit to one clear aesthetic direction:

    line 13
  3. Distinctive:

    Avoid generic fonts (Arial, Inter, Roboto)

    line 23
  4. Distinctive:

    Commit to cohesive aesthetic with CSS variables

    line 27
  5. Distinctive:

    Use animations for effects and micro-interactions

    line 31
  6. Distinctive:

    Create atmosphere and depth, not solid colors

    line 41
  7. Very specific:

    Use the styling system named in the project's CLAUDE.md.

    line 47
  8. Distinctive:

    When a first draft lands on one of these anyway, add the specific pattern it used to this list rather than a general "less generic" note.

    line 78

“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 & Development

Create distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics.

Design Thinking

Before coding, commit to one clear aesthetic direction:

  • Purpose: What problem does this solve? Who uses it?
  • Tone: Pick an extreme - brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful, editorial, brutalist, art deco, soft/pastel, industrial
  • Constraints: Framework, performance, accessibility requirements
  • Differentiation: What will make this memorable for this audience?

Frontend Aesthetics Guidelines

Typography

  • Choose beautiful, unique, interesting fonts
  • Avoid generic fonts (Arial, Inter, Roboto)
  • Pair distinctive display font with refined body font

Color & Theme

  • Commit to cohesive aesthetic with CSS variables
  • Dominant colors with sharp accents outperform timid palettes

Motion

  • Use animations for effects and micro-interactions
  • Focus on high-impact moments: orchestrated page loads with staggered reveals
  • Scroll-triggering and surprising hover states

Spatial Composition

  • Unexpected layouts, asymmetry, overlap, diagonal flow
  • Grid-breaking elements
  • Generous negative space OR controlled density

Backgrounds & Visual Details

  • Create atmosphere and depth, not solid colors
  • Gradient meshes, noise textures, geometric patterns
  • Layered transparencies, dramatic shadows, decorative borders

Styling System

Use the styling system named in the project's CLAUDE.md. In Tailwind projects, style with utility classes rather than inline style props or CSS-in-JS, so every value stays on the design-token scale:

<div className="flex items-center justify-between p-4 bg-white rounded-lg shadow-md">

Performance Targets

Core Web Vitals:
  LCP: < 2.5s
  CLS: < 0.1
  INP: < 200ms
Bundle: Initial JS < 100KB gzipped
Runtime: 60fps animations

Accessibility (WCAG 2.1 AA)

  • Semantic HTML structure
  • ARIA labels and roles
  • Keyboard navigation
  • Color contrast validation (4.5:1)

Defaults to Avoid

  • Generic fonts (Inter, Roboto, Arial, system fonts)
  • Cliched color schemes (purple gradients on white)
  • Cream or off-white page backgrounds as the default canvas
  • Italic accent words inside headlines
  • Numbered "01 / 02 / 03" section labels
  • Monospace eyebrow labels
  • Pill-shaped buttons as the default button shape

When a first draft lands on one of these anyway, add the specific pattern it used to this list rather than a general "less generic" note.

Additional Resources

  • For design tokens (typography scale, spacing system, animation tokens, color strategy, breakpoints), see reference/design-tokens.md

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