web-design-guidelines
The web-design-guidelines skill reviews UI code and markup files against a comprehensive set of Web Interface Guidelines covering accessibility, forms, animation, typography, images, keyboard navigation, dark mode, and internationalization. Use it when stakeholders request UI reviews, accessibility audits, design compliance checks, or UX best practice validation, but not for performance metrics, SEO issues, or comprehensive site audits.
git clone --depth 1 https://github.com/tech-leads-club/agent-skills /tmp/web-design-guidelines && cp -r /tmp/web-design-guidelines/packages/skills-catalog/skills/(design)/web-design-guidelines ~/.claude/skills/web-design-guidelinesSKILL.md
# 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
Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible". Do NOT use for SEO (use seo), performance (use core-web-vitals), or comprehensive site audits covering multiple areas (use web-quality-audit).
When the user wants to build an AI-powered outreach system, write cold emails, improve deliverability, or scale personalized outreach. Also use when the user mentions 'cold email,' 'cold outreach,' 'outreach automation,' 'Instantly,' 'Smartlead,' 'Clay,' 'email sequences,' 'deliverability,' 'personalization at scale,' 'reply rate,' or 'outreach stack.' This skill covers the complete AI cold outreach system from signal detection through conversion. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to price an AI product, choose a charge metric, design pricing tiers, or optimize margins. Also use when the user mentions 'AI pricing,' 'usage-based pricing,' 'consumption pricing,' 'outcome pricing,' 'BYOK,' 'bring your own key,' 'per-seat pricing,' 'pricing tiers,' 'AI margins,' 'cost per token,' or 'pricing model.' This skill covers pricing strategy, packaging, and margin management for AI-native products. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to deploy AI sales development reps, automate sales qualification, build signal-to-action routing, or design AI agent architecture for sales. Also use when the user mentions 'AI SDR,' 'AI sales agent,' 'automated qualification,' 'signal routing,' 'sales automation,' '11x,' 'Artisan,' 'AiSDR,' 'AI BDR,' or 'autonomous sales.' This skill covers AI SDR deployment, qualification automation, and agent architecture for sales development. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to build programmatic SEO with AI, create competitor alternative pages, optimize for AI Overviews, or scale content production. Also use when the user mentions 'SEO,' 'programmatic SEO,' 'AI content,' 'competitor alternative pages,' 'AI Overviews,' 'search optimization,' 'DataForSEO,' 'content at scale,' 'keyword strategy,' or 'organic traffic.' This skill covers AI-powered SEO strategy from keyword research through programmatic page generation. Do NOT use for technical implementation, code review, or software architecture.
When the user wants to create UGC ad campaigns, recruit UGC creators, generate AI UGC content, or scale with user-generated content. Also use when the user mentions 'UGC,' 'user-generated content,' 'creator ads,' 'Spark Ads,' 'whitelisting,' 'AI UGC,' 'Arcads,' 'Creatify,' 'creator brief,' or 'UGC testing.' This skill covers the UGC growth framework from creator recruitment through AI-powered scaling. Do NOT use for technical implementation, code review, or software architecture.
Expert AWS Cloud Advisor for architecture design, security review, and implementation guidance. Leverages AWS MCP tools for accurate, documentation-backed answers. Use when user asks about AWS architecture, security, service selection, migrations, troubleshooting, or learning AWS. Triggers on AWS, Lambda, S3, EC2, ECS, EKS, DynamoDB, RDS, CloudFormation, CDK, Terraform, Serverless, SAM, IAM, VPC, API Gateway, or any AWS service. Do NOT use for non-AWS cloud providers or general infrastructure without AWS context.
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities". Do NOT use for accessibility (use web-accessibility), SEO (use seo), performance (use core-web-vitals), or comprehensive multi-area audits (use web-quality-audit).