Pantheon UX Audit (Harmonia)

Audit frontend UI patterns for design harmony and consistency against a Design Language Reference.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/jschulte/pantheon --skill pantheon-ux-audit-harmonia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Pantheon UX Audit (Harmonia)
Source: https://github.com/jschulte/pantheon/tree/main/src/skills/pantheon-ux-audit
Command: npx skills add https://github.com/jschulte/pantheon --skill pantheon-ux-audit-harmonia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining a consistent and harmonious user experience across an application by auditing UI patterns for design harmony and consistency.

Core Features & Use Cases

  • UX Pattern Auditing: Analyzes frontend components for adherence to established design language.
  • Bootstrap Mode: Establishes a Design Language Reference (DLR) for new projects.
  • Audit Mode: Identifies deviations from an existing DLR in new or modified components.
  • Use Case: When a new feature is developed, this Skill can be invoked to ensure all new UI elements (buttons, forms, navigation) match the existing design system, preventing visual and functional discord.

Quick Start

Run the Pantheon UX Audit skill on story key '1-3' using the artifacts found in '/path/to/sprint/artifacts'.

Frequently Asked Questions about Pantheon UX Audit (Harmonia)

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

FAQPage Schema
How do I audit UI patterns for design consistency across frontend files?

To audit UI patterns for design consistency, this Skill analyzes frontend components to verify adherence to a Design Language Reference, checking for accessibility gaps, responsive breakpoints, and interaction patterns. It categorizes findings by severity to highlight deviations.

What is a Design Language Reference and when do I need one for a UX audit?

A Design Language Reference (DLR) is the baseline standard for UI elements used during a UX audit. You need one to verify conformance of new features, or you can use BOOTSTRAP mode to establish a new DLR for projects lacking existing design system documentation.

How do I check my frontend components for accessibility gaps and responsive breakpoints?

Checking frontend components for accessibility gaps and responsive breakpoints is handled by extracting and documenting UI patterns during the audit. The Skill evaluates your files against the DLR and produces categorized findings for any detected issues.

Can I use this UX audit tool to establish a design system for a new project?

Yes, you can establish a design system for a new project using BOOTSTRAP mode. This mode analyzes your frontend files to extract and document existing UI patterns, creating a new Design Language Reference to govern future development and maintain harmony.

What is the best way to prevent visual discord when adding new UI elements to an existing application?

The best way to prevent visual discord when adding new UI elements is to run AUDIT mode after developing a feature. It identifies deviations from your existing Design Language Reference, ensuring new buttons, forms, and navigation match your established design system.

How do I categorize the severity of interaction pattern deviations in my frontend code?

To categorize the severity of interaction pattern deviations, the Skill evaluates your frontend files against the DLR and outputs findings categorized by severity. This allows you to prioritize fixes for design harmony and accessibility gaps effectively.