agentsclimarketplace
Sign in

Ui

Skill panda850819/verbs/skills/productivity/ui

Production UI craft route when a page or component needs a committed visual direction, or a taste complaint such as 不好看、突兀、死板、沒回饋感 needs correction. Name the direction, implement required states, and verify rendered locales. Use `prototype` while direction is open, `debug` for render failures, and `qa` for browser acceptance evidence.From its SKILL.md

Install
npx -y skills add panda850819/verbs --skill ui

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.2 KB, as published. Nobody here has run it

UI

Native frontend tooling can render a surface; this skill adds a committed visual direction, craft review, and rendered evidence. Load references/craft.md before writing CSS, not after. A CJK gut-feel complaint (很傻 / 突兀 / 丑 / 乱) is taste, not a bug — keep the word, name the defect, fix; do not send it to debug.

  • Evidence over taste. A preference is not a finding. Name the observable defect and its user impact, then confirm it in the rendered surface. Keep a deliberate choice that meets the task, accessibility and acceptance contract.
  • Keep ownership clear. prototype answers an open visual question, ui chooses and implements the direction, qa proves browser acceptance, and review checks the code diff. Do not turn a visual preference into a code-review finding.
  • Fight your defaults. Your first draft is the AI-default — Inter, purple→blue gradient, centered hero with two CTAs, a grid of identical cards. Lock one named direction, then scan the first screen against the default-trap checklist in craft.md and replace what drifted.
  • Verify the render, not the source. Screenshot at 375px and 1280px in every shipped locale before "done". Wraps, overflow, and widows are invisible in code.
  • Build past the happy path. States (loading/empty/error) and the shippability layer a visual pass skips — 404, back-nav, form validation, skip-link, footer legal — are in craft.md.

Done when the named direction passes the default-trap scan, required states are covered, every visual claim has rendered evidence, and 375px/1280px screenshots are captured for every shipped locale.

Everything else — fonts, CJK type, OKLCH, CSS bans, motion, spacing, content rules — is craft you cannot derive: references/craft.md.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.