uikit

Build and audit frontend UI to eliminate AI-generated design defaults.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/mimukit/skills --skill uikit-mimukit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: uikit
Source: https://github.com/mimukit/skills/tree/main/skills/uikit
Command: npx skills add https://github.com/mimukit/skills --skill uikit-mimukit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated UI has recognizable tells: violet gradients, three equal feature cards, Inter on slate-900, fake dashboards built from divs. No test catches these because they are defaults, not bugs. This Skill supplies the design constraints that make UI decisions deliberate for a specific project, and audits shipped UI for the signatures that give generated work away. ## Core Features & Use Cases - Build mode: Generates UI grounded in a four-rung precedence ladder (DESIGN.md tokens, shipped components, the product's subject matter, or declared stack defaults), with a five-word design read stated before any code is written. - Audit mode: Read-only sweep of named paths or branch diffs against a capped anti-slop catalog and an accessibility floor, reporting findings as blocker, should-fix, or nit with file and line references. - Stack correctness layer: Enforces Tailwind v4 and shadcn/ui rules that prevent silent rendering errors, such as renamed utility classes and semantic token usage. - Use Case: Ask it to build a settings page in a repo with existing components, and it matches the shipped component conventions, declares one signature element, runs a written pre-flight critique, and hands off with the design read repeated for the PR body. ## Quick Start Ask the agent to build the settings page for this project using uikit, or to audit the current UI for AI-generated design tells.

Frequently Asked Questions about uikit

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

FAQPage Schema
How do I make AI-generated UI not look generic?

Ground every decision in a constraint: the project's DESIGN.md tokens, its shipped components, or the product's own subject matter. Declare a five-word design read before writing code, and give each surface exactly one signature element instead of reaching for default aesthetics.

How do I audit a frontend for AI-generated design tells?

Run the audit mode against named paths or the branch diff. It sweeps a capped catalog of banned patterns filtered by surface type (product vs marketing) plus an accessibility floor, and reports findings by severity with file and line references.

What changed between Tailwind v3 and v4 class names?

Several utilities were renamed and silently render smaller in v4: shadow-sm became shadow-xs, rounded became rounded-sm, ring became ring-3, and bg-gradient-to-r became bg-linear-to-r. Theme configuration also moved from JS config into CSS via @theme.

Does the audit mode modify my code?

No. Audit is strictly read-only and writes nothing, ever. It reports findings and routes the worst one to a separate build invocation, so fixing is always a deliberate second step.

When should I not use this UI skill?

Skip it for code-level review concerns like dead abstractions or correctness, which belong to a general code review. It also never writes DESIGN.md, installs browsers, starts dev servers, or commits changes.