design-audit

Audit UI screens against a 15-point design checklist and generate phased improvement plans.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/cmbays/mokumo --skill design-audit-cmbays
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-audit
Source: https://github.com/cmbays/mokumo/tree/main/.claude/skills/design-audit
Command: npx skills add https://github.com/cmbays/mokumo --skill design-audit-cmbays

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that user interface designs are not only aesthetically pleasing but also adhere to strict design system principles, focusing on simplicity, clarity, and user-centricity, much like the philosophies of Steve Jobs and Jony Ive.

Core Features & Use Cases

  • Systematic Design Review: Audits screens against a comprehensive 15-point checklist derived from design system standards.
  • Jobs Filter Application: Applies core principles like "Can this be removed without losing meaning?" to distill designs to their essence.
  • Phased Improvement Plan: Generates actionable, phased plans for design improvements, prioritizing critical fixes.
  • Use Case: After a major development checkpoint, use this Skill to audit a new set of screens, ensuring they align with the established design system and the core tenets of simplicity and user focus before proceeding to user acceptance testing.

Quick Start

Use the design-audit skill to audit the screens defined in PROGRESS.md against the 15-point checklist.

Frequently Asked Questions about design-audit

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

FAQPage Schema
How do I conduct a UI design audit against design system principles?

A UI design audit evaluates interface screens against a 15-point quality checklist focused on design system principles, simplicity, and user-centricity. It applies Steve Jobs and Jony Ive's philosophy to identify unnecessary elements and generate actionable improvement plans for frontend agents.

What is the Jobs and Ive design philosophy for UI review?

The Jobs and Ive design philosophy for UI review focuses on radical simplicity and user experience clarity. It applies a critical filter asking if elements can be removed without losing meaning, distilling designs to their essential components while maintaining strict adherence to design system standards.

How do I generate a phased improvement plan for frontend implementation?

You generate a phased improvement plan by auditing your UI screens against the 15-point quality checklist. The skill identifies critical fixes first, prioritizing specific implementation changes required for frontend agents to systematically elevate UI quality and align with your design system.

Can I use this design audit for screens documented in a progress file?

Yes, you can use this design audit for screens documented in a progress file. The quick start specifically mentions auditing screens defined in PROGRESS.md against the 15-point checklist to ensure alignment with established design system principles before user acceptance testing.

When do I need a systematic UX quality review for my interface?

You need a systematic UX quality review after a major development checkpoint to ensure new screens align with your established design system. This prevents design drift and verifies that the interface maintains simplicity and user focus before proceeding to user acceptance testing.

What are the limitations of using a checklist-based design audit approach?

A checklist-based design audit limits evaluation to 15 predefined design system points and the specific philosophy of Jobs and Ive. It focuses on element justification and simplicity rather than quantitative usability metrics, meaning it may not capture complex interactive user flow issues or accessibility compliance gaps.