agentleFS
Sign inStart free
BAKUGOS1BAKUGOS1/SkilledAgents-Toolkit/skills/codex/frontend-design/SKILL.md

frontend-design

Skill0 starsChanged 5 months agoMITView on GitHub

Production frontend design and implementation guardrails for web apps, pages, dashboards, landing pages, React components, HTML/CSS layouts, and UI polish. Use when creating, redesigning, beautifying, or reviewing frontend interfaces that need a distinctive visual direction, strong UX, responsive behavior, accessibility basics, and avoidance of generic AI-looking design.

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, 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. Very specific:

    Use this skill to make frontend work feel intentional, domain-specific, and production-quality.

    line 10
  2. Distinctive:

    Before coding or reviewing:

    line 14
  3. Distinctive:

    Avoid generic AI defaults: centered sameness, purple gradients, over-rounded cards, random glassmorphism, and decorative blobs.

    line 19
  4. Distinctive:

    Use real controls for real actions: icon buttons, menus, tabs, toggles, sliders, inputs, and clear command buttons.

    line 25
  5. Distinctive:

    Keep text fitted inside its container on mobile and desktop.

    line 26
  6. Distinctive:

    Use stable dimensions for boards, tiles, toolbars, cards, and counters to avoid layout shifts.

    line 27
  7. Distinctive:

    Prefer CSS variables or existing tokens for repeatable color, spacing, and type.

    line 29
  8. Distinctive:

    Verify responsive behavior when the change affects UI.

    line 30

“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

Overview

Use this skill to make frontend work feel intentional, domain-specific, and production-quality. It is adapted from useful patterns in Anthropic's Apache-2.0 frontend-design skill, but tuned for Codex and local project work.

Design Direction

Before coding or reviewing:

  • Identify the product purpose, primary user, and workflow pressure.
  • Choose one clear visual point of view that fits the domain.
  • Match density to the product: operational apps should be calm, scannable, and efficient; editorial or creative pages may be more expressive.
  • Avoid generic AI defaults: centered sameness, purple gradients, over-rounded cards, random glassmorphism, and decorative blobs.
  • Preserve existing design system conventions unless the user asked for a redesign.

Implementation Rules

  • Build the actual usable screen first, not a marketing wrapper.
  • Use real controls for real actions: icon buttons, menus, tabs, toggles, sliders, inputs, and clear command buttons.
  • Keep text fitted inside its container on mobile and desktop.
  • Use stable dimensions for boards, tiles, toolbars, cards, and counters to avoid layout shifts.
  • Make empty, loading, error, disabled, and success states feel designed.
  • Prefer CSS variables or existing tokens for repeatable color, spacing, and type.
  • Verify responsive behavior when the change affects UI.

Review Checklist

  • Does the screen communicate the primary task within a few seconds?
  • Are actions positioned where users naturally expect them?
  • Is there one clear hierarchy instead of many competing cards?
  • Does typography match the container size?
  • Are colors balanced, accessible, and not one-note?
  • Are hover/focus states and keyboard paths covered where relevant?
  • Does the implementation avoid extra dependencies and fragile layout tricks?

Final Handoff

Report the visual direction, changed files, verification performed, remaining UX risks, and any assumptions.

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