agentleFS
kazemcodeskazemcodes/skill-tree/skills/frontend-design/SKILL.md

frontend-design

Skill1 starsChanged 5 months agoMITView on GitHub

Design distinctive, intentional UIs — avoid AI defaults, make deliberate aesthetic choices

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

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

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 6

    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:

    If any part reads like generic default → revise that part, explain what changed and why.

    line 35
  2. Distinctive:

    Follow revised plan exactly.

    line 39
  3. Distinctive:

    Ask: "What would a real designer change?"

    line 44
  4. Distinctive:

    All legitimate for some briefs, but they're defaults not choices.

    line 72
  5. Distinctive:

    Write from end user's side: "Notifications" not "webhook config"

    line 77
  6. Distinctive:

    Not taking a risk can be a risk itself

    line 87

“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

Approach as design lead at a small studio. Every client gets a visual identity no one else has.

Design Philosophy

  • Make deliberate, opinionated choices about palette, typography, layout
  • Take one real aesthetic risk you can justify
  • Reject templated defaults — the brief's own words always win

Process: Brainstorm → Explore → Plan → Critique → Build → Critique Again

1. Ground It in the Subject

Before designing:

  • Name the concrete subject, audience, page's single job
  • The subject's own world (materials, instruments, artifacts) is where distinctive choices come from
  • Build with real content throughout

2. Brainstorm Plan

Compact token system:

  • Color: 4-6 named hex values
  • Type: 2+ roles (display, body, accent)
  • Layout: ASCII wireframe
  • Signature element: one memorable thing

3. Review Against Brief

If any part reads like generic default → revise that part, explain what changed and why.

4. Build Code

Follow revised plan exactly. Derive every decision from it.

5. Critique

  • Take screenshots (picture = 1000 tokens)
  • Ask: "What would a real designer change?"
  • Chanel's advice: before leaving the house, remove one accessory

Design Principles

Hero is a Thesis

Open with the most characteristic thing in the subject's world. Be deliberate — big number with small label + gradient accent is the template answer, only use if truly best.

Typography Carries Personality

Pair display and body faces deliberately. Set clear type scale with intentional weights, widths, spacing. Make type treatment memorable.

Structure is Information

Structural devices (numbering, eyebrows, dividers) should encode something true about content, not decorate.

Leverage Motion Deliberately

Orchestrate one moment that lands harder than scattered effects. Sometimes less is more — extra animation = AI-generated feel.

Match Complexity to Vision

Maximalist needs elaborate execution; minimal needs precision. Elegance = executing the chosen vision well.

AI Design Defaults to Avoid

These cluster around three looks:

  1. Warm cream (#F4F1EA) + high-contrast serif + terracotta accent
  2. Near-black background + single acid-green/vermilion accent
  3. Broadsheet layout + hairline rules + zero border-radius + dense columns

All legitimate for some briefs, but they're defaults not choices. Where brief leaves an axis free, don't spend it on these.

Writing in Design

  • Words are design material, not decoration
  • Write from end user's side: "Notifications" not "webhook config"
  • Active voice default: "Save changes" not "Submit"
  • Same vocabulary through whole flow: button "Publish" → toast "Published"
  • Errors: explain what went wrong and how to fix it, never apologize
  • Empty screen = invitation to act

Restraint

  • Spend boldness in ONE place
  • Cut decoration that doesn't serve the brief
  • Not taking a risk can be a risk itself
  • Build quality floor: responsive, visible keyboard focus, reduced motion respected

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.