Ui Ux Review logo

Ui Ux Review

Community
thiientv
ui-ux-review

Audits an existing rendered interface or frontend diff for hierarchy, content clarity, interaction states, accessibility, responsive behavior, visual consistency, performance-sensitive UI patterns, and anti-generic design defects. Use for a UI/UX review, redesign audit, screenshot review, pre-release visual check, or design-system consistency pass. Not for building a new interface from scratch or for backend-only review.

Overview

Publisherthiientv
Repositorygodmode
Skill nameui-ux-review
Stars
99
Forks
76
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by thiientv on GitHub. Read the source before you install it.

Installation

Install the Ui Ux Review AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/thiientv/godmode/tree/main/skills/ui-ux-review
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/thiientv/godmode.git /tmp/godmode
mkdir -p .claude/skills
cp -r /tmp/godmode/skills/ui-ux-review .claude/skills/ui-ux-review
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Ui Ux Review in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Ui Ux Review on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Ui Ux Review is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

UI/UX Review

Review the interface users actually receive, not only the component source.

Establish the surface

  1. Identify routes, primary flows, target users, supported viewports, themes, content states, and the design system or brand constraints.

  2. Inspect the diff and direct consumers before forming findings.

  3. Run the deterministic audit helper against relevant HTML/CSS/JS when a static surface is available:

    bash
    python3 skills/ui-ux-review/scripts/audit_ui.py ./path/to/ui

    Zero supported source files is inconclusive and exits with status 2. Use --allow-empty only when an empty UI scope is intentional; it is not proof that a surface is clean.

  4. Extract the current token and component system with frontend-design when consistency claims depend on it; compare against existing tokens before proposing a redesign language.

  5. Render the surface in a browser. Capture normal, empty, error, loading, permission, narrow, intermediate, and desktop states that matter to the request. If runtime access is blocked, mark visual findings unverified.

Review passes

Experience and hierarchy

Check whether the first viewport explains the page, the primary action is obvious, copy is scannable, labels are specific, and repeated containers add meaning rather than noise.

Interaction and accessibility

Check semantics, names, keyboard order, focus visibility, contrast, target size, error recovery, reduced motion, screen-reader announcements, and whether color is the only signal. Run axe or the repository's equivalent when available, then manually traverse the primary flow by keyboard; automated accessibility scans do not prove task usability.

Responsive and visual system

Check narrow/intermediate/desktop reflow, long content, tables, dialogs, overflow, theme contrast, tokens, type rhythm, spacing, icon consistency, and layout stability.

Performance and trust

Check image dimensions and loading, layout shift, blocking work, feedback during async actions, destructive confirmation, and misleading placeholder or proof content.

Use review-checklist.md and report only actionable findings with priority, exact location/route, failure mode, impact, and the smallest correction. Separate static findings from unverified visual claims. Use the runtime state/viewport matrix supplied by frontend-design rather than treating a single desktop screenshot as evidence.

Completion condition

The report covers the requested surface and states, every finding is evidence-backed or marked unverified, and the next design or engineering action is clear.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Ui Ux Review AI skill do?

Audits an existing rendered interface or frontend diff for hierarchy, content clarity, interaction states, accessibility, responsive behavior, visual consistency, performance-sensitive UI patterns, and anti-generic design defects. Use for a UI/UX review, redesign audit, screenshot review, pre-release visual check, or design-system consistency pass. Not for building a new interface from scratch or for backend-only review.

Why use Ui Ux Review on TypingMind?

Because you install it once and use it with any model. Ui Ux Review is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Ui Ux Review in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/thiientv/godmode/tree/main/skills/ui-ux-review. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Ui Ux Review?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Ui Ux Review?

As many as you like. As long as a model supports skills, you can use Ui Ux Review with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Ui Ux Review AI skill free?

Yes. It is published on GitHub by thiientv under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇