ck:web-design-guidelines

Review UI code against Web Interface Guidelines and report issues in file:line format.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/jangtrinh/demo-Lam --skill ck-web-design-guidelines-jangtrinh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:web-design-guidelines
Source: https://github.com/jangtrinh/demo-Lam/tree/main/.claude/skills/web-design-guidelines
Command: npx skills add https://github.com/jangtrinh/demo-Lam --skill ck-web-design-guidelines-jangtrinh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you find UI and accessibility issues by checking your interface code against an authoritative Web Interface Guidelines checklist, so you can fix problems before they reach users.

Core Features & Use Cases

  • Guideline-backed UI review: Fetches the latest Web Interface Guidelines from the configured source and applies all rules to your code.
  • Targeted file or pattern auditing: Reviews specific files when you pass a file or pattern argument, making it practical for focused iterations.
  • Actionable findings output: Reports issues in the terse file:line format required by the fetched guidelines, so fixes are fast and traceable.

Use cases include reviewing UI code for accessibility and UX best practices, auditing a site against current guidelines, and performing iterative design audits during development.

Quick Start

Ask the skill to review your UI code files by running: review my UI and check accessibility for ./path/to/files.

Frequently Asked Questions about ck:web-design-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my UI code for accessibility and UX best practices?

To audit your UI code for accessibility and UX best practices, run a UI review against an authoritative Web Interface Guidelines checklist. This process scans your specified files and returns actionable findings to fix interface issues before production.

How does a UI audit against web interface guidelines work?

A web interface guidelines audit works by fetching the latest rule set and applying each rule to your front-end codebase. It scans user-specified files or patterns to identify accessibility and design issues for production readiness.

Can I review specific files for accessibility checks during development?

Yes, you can review specific files for accessibility checks by passing a file or pattern argument. This allows targeted UI auditing for focused iterations during development, ensuring only the relevant code is scanned against the guidelines.

What is the best way to format UI code review findings for quick fixes?

The best way to format UI code review findings for quick fixes is using the file:line format. This terse output structure reports exact issue locations, making accessibility and UX problems fast and traceable to resolve in your codebase.

Do I need a specific framework to perform a static site accessibility audit?

No specific framework is required to perform a static site accessibility audit. The review applies standard Web Interface Guidelines rules directly to your front-end codebase, checking for compliance regardless of the underlying static site generator or framework.

What are the limitations of using web interface guidelines for a UI audit?

A limitation of using web interface guidelines for a UI audit is that it only checks front-end code against the fetched rule set. It does not test dynamic runtime interactions or visual rendering, requiring manual verification for complex UX behaviors.