team-ui-polish

Scan front-end UI for design anti-patterns and apply standards-based fixes.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/tcytan/tecton --skill team-ui-polish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-ui-polish
Source: https://github.com/tcytan/tecton/tree/main/.claude/skills/team-ui-polish
Command: npx skills add https://github.com/tcytan/tecton --skill team-ui-polish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies AI-looking UI issues (including color, typography, spacing, motion, and hierarchy) and helps you fix them using a structured scan → diagnose → optimize → verify workflow.

Core Features & Use Cases

  • Unified UI audit: Detects design “AI slop” and scores multiple quality dimensions against Impeccable standards.
  • Root-cause diagnosis: Groups findings into systemic vs one-off problems and builds a fix dependency plan.
  • Coordinated repair with verification: Applies targeted fixes, then re-scans to catch regressions using an optimizer↔verifier loop (up to 2 rounds).

Quick Start

Run the Skill on your UI target by asking: “team ui polish: polish this page and fix all design quality issues, then verify improvements.”

Frequently Asked Questions about team-ui-polish

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

FAQPage Schema
How do I fix AI slop and visual anti-patterns in my front-end UI?

To fix AI slop and visual anti-patterns in your front-end UI, use a scan, diagnose, optimize, and verify pipeline that detects design flaws across color, typography, spacing, motion, and hierarchy, then applies standards-based remediations.

What is the best way to audit UI design quality for a single-page URL?

The best way to audit UI design quality for a single-page URL is to run a unified scan that scores multiple visual dimensions against Impeccable standards, generating evidence artifacts and screenshots to identify systemic design issues.

How does root-cause diagnosis work for UI typography and color quality issues?

Root-cause diagnosis for typography and color quality issues works by grouping visual findings into systemic versus one-off problems, then building a fix dependency plan to coordinate targeted repairs across the front-end source.

Can I use an automated workflow to polish UI components and verify regressions?

Yes, you can polish UI components and verify regressions using a bounded generator-critic loop that applies targeted fixes and then re-scans the UI for up to two rounds to ensure regression-safe visual improvements.

Does UI polish support full-site front-end sources or only individual component paths?

UI polish supports both individual component paths and full-site front-end sources, ensuring consistent color, typography, spacing, motion, interaction states, hierarchy, and responsive behavior across the entire application.