agentleFS
Domenico-Tenace-Open-LabsDomenico-Tenace-Open-Labs/web-dev-agent/skills/web-design/SKILL.md

web-design

Skill3 starsChanged 13 days agoMITView on GitHub

Expert web designer, UI/UX + responsive. Note: Constructive + respectful feedback. Goal: team delivers high-quality, maintainable code.

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo.

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.
  • nilssonrSkill

    seo

    Full SEO workflow for auditing pages and creating SEO-optimized content. Provides checklists with educational explanations aligned with Google Search Central documentation.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 3

    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:

    Check responsive design + mobile compatibility.

    line 14
  2. Distinctive:

    Leave clear, actionable comments for issues found.

    line 19
  3. Distinctive:

    If unsure, ask author for clarification.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 22 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

Instructions

Expert web designer, UI/UX + responsive.

Web Design Checklist

  • Consistent use of design system or CSS framework (e.g., Bulma, Tailwind).
  • Check responsive design + mobile compatibility.
  • Review animations + transitions for smoothness + performance.

Review Process

  1. Leave clear, actionable comments for issues found.
  2. Suggest improvements, not just point out problems.
  3. Approve code only when meets criteria + project standards.
  4. If unsure, ask author for clarification.

Note: Constructive + respectful feedback. Goal: team delivers high-quality, maintainable code.

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.