Agent skill

Waza UI Skill: Distinctive Interfaces and Screenshot Polish

The waza-ui skill is the ui habit from the Waza set. It makes an AI coding agent lock a design direction first, then build or fix interfaces against real screenshots.

Install
/plugin marketplace add tw93/Waza
/plugin install waza@waza
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the waza-ui skill?

The waza-ui skill is the ui skill inside tw93's Waza plugin set. It makes an agent resolve five direction questions before writing code, routes bounded fixes, screenshots and generated images to separate modes, and bans common AI-default looks. It targets frontend work, not backend logic or data pipelines.

Waza is a set of eight small skills, each a habit for one engineering job. The ui skill is the one for frontend work, and its description promises distinctive production UI and visual polish grounded in screenshots.

Its main idea is that a default-prompt result is not good enough. Before code, the agent has to commit to a point of view, and afterwards it re-reads that thesis to see whether the screen drifted.

Four paths for four kinds of request

  1. A bounded fix to an existing screen, such as cramped spacing, loads a quick-fix mode file.
  2. A supplied screenshot as the evidence to improve against loads the screenshot iteration mode.
  3. A generated image asset, such as a cover or social card, loads the generated-asset mode.
  4. A new page, component or visual system goes through direction lock, with no mode file needed.

The five direction questions

  • Who uses this, and in what context? A dashboard differs from a landing page.
  • What is the aesthetic direction? Clean and modern does not count as one.
  • What is the design signature, such as a typeface, a color system or an unexpected motion?
  • What are the hard constraints: framework, bundle size, contrast and keyboard access?
  • What is the signature micro-interaction, and how exactly is it implemented?

Who the waza-ui skill is for

Best for

  • Building or restyling pages and components where the result must not look like a generic template. For related guardrails, see anti-ui-slop.
  • Iterating from a screenshot of a rendered screen with a visual complaint, in English or Chinese.
  • Adding a new panel or dialog to a mature app, where the skill says to reuse the existing sibling component first.

Not for

  • Backend logic or data pipelines, which the skill description rules out directly.
  • Reports, slide decks, resumes and print-oriented documents. The skill hands document typography to a typesetting skill if one is installed.
  • Full redesigns when you only want a bounded fix. Ask for its quick-fix mode instead, and see also polish.

Use it with UiChemy

The skill produces code and visual fixes in your project, not a WordPress page. To bring a design into WordPress, build it in Figma and use UiChemy Figma to WordPress, or use AI to WordPress. Click Get Started on uichemy.com and review the result.

The skill expands multi-page work into a written design file. See also design-md and motion-system.