agentleFS
Sign inStart free
LukeJMaddenLukeJMadden/Veltrix-skills/skills/frontend/design/SKILL.md

frontend-design

Skill1 starsChanged 8 months agoMITView on GitHub

Production-grade frontend design skill. Creates distinctive, polished interfaces that avoid generic AI aesthetics. Use when building any web page, component, or 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

8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 5

    Distinctive

    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:

    Create distinctive, production-grade frontend interfaces.

    line 7
  2. Distinctive:

    Every design starts with a deliberate aesthetic choice:

    line 11
  3. Distinctive:

    Commit to a cohesive palette.

    line 24
  4. Very specific:

    Use CSS custom properties (--color-primary, etc.) for every colour.

    line 25
  5. Distinctive:

    Every section should have a clear visual hierarchy: what do you see first, second, third?

    line 33
  6. Very specific:

    All CSS must be inline or in a <style> block — no external stylesheet references.

    line 43
  7. Very specific:

    All fonts loaded via CDN <link> tags.

    line 44
  8. Distinctive:

    No placeholder images — generate them first or use CSS gradients/patterns.

    line 45

“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

Create distinctive, production-grade frontend interfaces. No generic AI slop.

Before Coding: Choose a Direction

Every design starts with a deliberate aesthetic choice:

  • Purpose — What problem does this solve? Who uses it?
  • Tone — Pick one: brutally minimal, maximalist, retro-futuristic, organic, luxury, playful, editorial, brutalist, art deco, soft/pastel, industrial. Commit fully.
  • Differentiation — What's the one thing someone will remember about this design?

Typography

  • Choose fonts that are distinctive, not default. Never use Arial, Inter, or Roboto as your primary display font without a specific reason.
  • Pair a display font (headlines) with a body font (text). They should contrast but complement.
  • Load from Google Fonts, Fontshare, or similar CDN — always include the <link> tag.

Colour

  • Commit to a cohesive palette. 2-3 colours max, used consistently.
  • Use CSS custom properties (--color-primary, etc.) for every colour.
  • One dominant colour + one sharp accent outperforms an evenly-distributed palette.
  • Dark themes: true dark backgrounds (#060610-#111) read as "premium tech." Light themes: generous whitespace reads as "editorial."

Layout

  • Break the grid sometimes. Asymmetry, overlap, and unexpected spacing create visual interest.
  • Generous negative space is a design choice, not laziness.
  • Every section should have a clear visual hierarchy: what do you see first, second, third?

Motion

  • One well-orchestrated page load (staggered reveals) creates more delight than scattered micro-interactions.
  • CSS-only animations for HTML. Use animation libraries for React.
  • prefers-reduced-motion media query on ALL animations — non-negotiable.

Self-Contained Output

  • All CSS must be inline or in a <style> block — no external stylesheet references.
  • All fonts loaded via CDN <link> tags.
  • No placeholder images — generate them first or use CSS gradients/patterns.
  • The HTML file must work when opened directly in a browser.

What NOT to Do

  • Purple gradient on white background
  • Cookie-cutter card layouts
  • "Hero section with stock photo"
  • Same font for everything
  • Buttons that all look the same
  • Missing accessibility (focus states, contrast, alt text)

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