agentleFS
Sign inStart free
ceilf6ceilf6/FrontAgent/skills/frontend-design/SKILL.md

frontend-design

Skill124 starsChanged 5 months agoMITView on GitHub

Create distinctive, production-grade frontend interfaces with a clear visual direction while respecting project design specification constraints, existing design systems, and minimal-diff engineering boundaries. Use when building or restyling pages, landing screens, dashboards, marketing surfaces, or other frontend UI where visual quality materially affects the result.

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

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to produce frontend work that feels intentionally designed rather than generic.

    line 28
  2. Very specific:

    If the request is visually underspecified, ask only the next 1-3 questions needed to clarify audience, tone, and acceptance criteria.

    line 51
  3. Very specific:

    Read references/design-direction.md to choose one clear visual direction before coding.

    line 52
  4. Very specific:

    Read references/aesthetics-guidelines.md for typography, color, motion, composition, and background treatment.

    line 53
  5. Very specific:

    Read references/integration-guardrails.md before modifying an existing codebase, design system, or shared component surface.

    line 54
  6. Very specific:

    Read references/delivery-checks.md before handing off.

    line 57
  7. Distinctive:

    Keep the implementation cohesive:

    line 63
  8. Distinctive:

    When editing an existing product, preserve the established system unless the user explicitly wants a stronger redesign.

    line 68
  9. Distinctive:

    Prefer minimal diffs for scoped tasks.

    line 74
  10. Distinctive:

    Do not add new dependencies, font loaders, or animation libraries unless the task clearly justifies them.

    line 75
  11. Distinctive:

    Avoid generic AI aesthetics:

    line 76
  12. Distinctive:

    default-looking font stacks for new standalone surfaces

    line 77
  13. Distinctive:

    Do not optimize for ornament over clarity.

    line 81

“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

Use this skill to produce frontend work that feels intentionally designed rather than generic. The goal is not maximalism by default. The goal is a clear visual point of view that matches the product context and still ships as maintainable code.

Trigger

  • New frontend surfaces where look and feel matter:
    • landing pages
    • dashboards
    • product pages
    • hero sections
    • marketing sites
    • polished application views
  • Requests to beautify, restyle, refine, or modernize an existing UI
  • Cases where the code must be working and production-usable, not just a mockup

Do Not Use

  • Pure bug fixes, refactors, or backend tasks
  • Review or audit requests
  • Small code changes where the user did not ask for visual improvement
  • Existing design-system work where the user only wants strict conformance and no meaningful visual interpretation

Workflow

  1. If the request is visually underspecified, ask only the next 1-3 questions needed to clarify audience, tone, and acceptance criteria. Use requirement-interviewer when the ambiguity is material.
  2. Read references/design-direction.md to choose one clear visual direction before coding.
  3. Read references/aesthetics-guidelines.md for typography, color, motion, composition, and background treatment.
  4. Read references/integration-guardrails.md before modifying an existing codebase, design system, or shared component surface.
  5. For a new page or major redesign, use assets/templates/visual-brief.md to form a short visual brief before implementation.
  6. Implement working code that matches the chosen direction and stays within project constraints.
  7. Read references/delivery-checks.md before handing off.

Output Contract

  • State the chosen visual direction in one short sentence when it meaningfully affects implementation.
  • Produce working frontend code, not mood-board prose.
  • Keep the implementation cohesive:
    • typography should support the direction
    • color should feel intentional
    • motion should be meaningful, not noisy
    • layout should feel composed rather than assembled from defaults
  • When editing an existing product, preserve the established system unless the user explicitly wants a stronger redesign.

Guardrails

  • Project design specification constraints, protected files, project stack rules, and user requirements remain hard boundaries.
  • Respect the existing design system first. Only deviate when the request explicitly calls for redesign or the current surface clearly lacks a defined visual direction.
  • Prefer minimal diffs for scoped tasks. Do not turn a local UI tweak into a whole-app restyle.
  • Do not add new dependencies, font loaders, or animation libraries unless the task clearly justifies them.
  • Avoid generic AI aesthetics:
    • default-looking font stacks for new standalone surfaces
    • timid palettes
    • predictable card grids with no visual idea
    • purple-gradient-on-white defaults
  • Do not optimize for ornament over clarity. If visual flair hurts usability, accessibility, or maintainability, scale it back.

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