Skip to content

find-ui-inconsistencies

skill

A frontend-review skill for Codex and Claude Code that evaluates typography, spacing, color, layout, shared UI, responsive behavior, skeletons, motion, and visible accessibility states while preserving intentional design direction.

A frontend-review skill for Codex and Claude Code that evaluates typography, spacing, color, layout, shared UI, responsive behavior, skeletons, motion, and visible accessibility states while preserving intentional design direction.

find-ui-inconsistencies is a AI-agent skill created to make a real workflow clearer, faster, and easier to trust. It turns a focused product idea into something people can use, evaluate, and understand without needing to inspect the source code.

Why find-ui-inconsistencies exists

Visual inconsistencies are often reported from one screenshot without provenance, comparison points, responsive states, or a systemic root cause.

The goal is not simply to add another tool. find-ui-inconsistencies is designed to reduce the friction around that problem and give people a more dependable way to complete the work.

What it delivers

  • Agents can produce reproducible UI findings.
  • Distinguish observed defects from inferred causes.
  • Propose the smallest systemic fix.
  • Recheck affected viewports, states, motion, focus, tests, and builds when implementation is requested.

The experience

Audits visual and interaction consistency across frontend routes, states, themes, and viewports.

The project brings the important parts of the workflow into one coherent experience. Its interface and behavior are shaped around the people using it, while the implementation stays focused on predictable results and honest feedback.

What to know

Every product has boundaries. These are the most important considerations for find-ui-inconsistencies:

  • Screenshots must be tied to route, viewport, time/build, and state.
  • Responsive/a11y behavior needs multiple widths and interaction states.
  • An audit request alone does not authorize implementation.

These limitations are presented openly so visitors can understand where the project works well, what it depends on, and what may change in future versions.

Current status

Published npm package v0.1.0. The current release demonstrates the core value of the project and the main end-to-end experience.

My role was agent workflow design and automation engineering, covering agent workflow, validation automation, and packaging. The related case study explains the decisions and delivery process in greater depth for visitors who want the engineering story behind the product.

Project stack

  • Agent Skills
  • JavaScript
  • Node.js
  • npm
  • GitHub Actions
  • CI/CD
  • Git

Need help with this project? Get project support

Working through something similar?

Share your challenge, scope, and timeline to start a focused conversation.

Discuss a project