web-design-guidelines

tech-leads-club/agent-skills · updated May 23, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/tech-leads-club/agent-skills --skill web-design-guidelines
0 commentsdiscussion
summary

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit).

skill.md
name
web-design-guidelines
description
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". Focuses on visual design and interaction patterns. Do NOT use for performance audits (use core-web-vitals), SEO (use seo), or comprehensive site audits (use web-quality-audit).
metadata
author: vercel version: '1.0.0' argument-hint: <file-or-pattern>

Web Interface Guidelines

Review files for compliance with Web Interface Guidelines.

How It Works

  1. Read the guidelines from #[[file:references/guideline.md]]
  2. Read the specified files (or prompt user for files/pattern)
  3. Check against all rules in the guidelines
  4. Output findings in the terse file:line format

Guidelines Reference

All rules and output format instructions are in:

#[[file:references/guideline.md]]

The guidelines cover:

  • Accessibility (ARIA, semantic HTML, keyboard navigation)
  • Focus states and keyboard interaction
  • Forms (autocomplete, validation, labels)
  • Animation (reduced motion, performance)
  • Typography (proper characters, number formatting)
  • Content handling (overflow, empty states)
  • Images (dimensions, lazy loading)
  • Performance (virtualization, DOM reads)
  • Navigation & state (URL sync, deep linking)
  • Touch & interaction (tap delays, safe areas)
  • Dark mode & theming
  • Locale & i18n
  • Hydration safety
  • Common anti-patterns to flag

Usage

When a user provides a file or pattern argument:

  1. Read the guidelines from references/guideline.md
  2. Read the specified files
  3. Apply all rules from the guidelines
  4. Output findings using the format specified in the guidelines

If no files specified, ask the user which files to review.

Output Format

Follow the format in the guidelines:

  • Group findings by file
  • Use file:line format (VS Code clickable)
  • Terse, high signal-to-noise
  • State issue + location
  • Skip explanation unless fix is non-obvious
how to use web-design-guidelines

How to use web-design-guidelines on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add web-design-guidelines
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/tech-leads-club/agent-skills --skill web-design-guidelines

The skills CLI fetches web-design-guidelines from GitHub repository tech-leads-club/agent-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/web-design-guidelines

Reload or restart Cursor to activate web-design-guidelines. Access the skill through slash commands (e.g., /web-design-guidelines) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.674 reviews
  • Neel Taylor· Dec 24, 2024

    I recommend web-design-guidelines for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Chaitanya Patil· Dec 12, 2024

    web-design-guidelines reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Evelyn Zhang· Dec 12, 2024

    Registry listing for web-design-guidelines matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Michael Li· Dec 8, 2024

    Useful defaults in web-design-guidelines — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Isabella Anderson· Nov 27, 2024

    Registry listing for web-design-guidelines matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Advait Rahman· Nov 15, 2024

    web-design-guidelines reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Evelyn Abebe· Nov 11, 2024

    web-design-guidelines is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Advait Abbas· Nov 7, 2024

    Keeps context tight: web-design-guidelines is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Piyush G· Nov 3, 2024

    I recommend web-design-guidelines for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Mia Jain· Nov 3, 2024

    Useful defaults in web-design-guidelines — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

showing 1-10 of 74

1 / 8