agentsclimarketplace

Harden

Skill educlopez/ui-craft/.codex/skills/harden

Design engineering system for AI coding agents — ship UI with craft-level quality. Install as an agent skill.

Install
npx -y skills add educlopez/ui-craft --skill harden

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

What its author says it does

Copied from the file, not written here

Production-readiness pass — audits and implements the full non-happy-path matrix: loading skeletons, empty states, error messages, partial data, i18n, offline, permissions, and first-run guidance. Use when preparing a surface for production or when the user says "it crashes on empty data" / "there's no loading state" / "harden this". Invoke when the user asks for harden on their UI, or mentions 'harden' alongside design / UI / frontend work.

SKILL.md

3.0 KB, 609 tokens by cl100k_base, as published. Nobody here has run it

<!-- HARNESS MIRROR — do not edit here. Canonical source: skills/ or commands/. After editing source, copy into cli/assets/<harness>/ and repo-root harness mirrors. -->

Context: this sub-skill is one lens of the broader ui-craft skill. If the ui-craft skill is also installed, read its SKILL.md first for Discovery + Anti-Slop + Craft Test, then apply the specific lens below.

Harden the UI at $ARGUMENTS for production. Load the ui-craft skill.

Coverage matrix — check every key surface:

  1. Loading — skeletons match the final layout (no CLS on resolve), shown after ~200ms to avoid flash on fast responses. Never a generic centered spinner when a skeleton is possible.
  2. Empty — purposeful: one line explaining why it's empty + one clear primary action. Illustration optional, CTA mandatory.
  3. Error — inline, actionable. "Save failed. Try again / Copy error / Contact support" — never just "Something went wrong." Surface the what and the next step.
  4. Partial data — — (em dash) for missing metrics, never N/A or null or 0 when the value is truly unknown.
  5. Long content — truncation with title tooltip, text-overflow: ellipsis, container queries for constrained regions. Test with a 120-character name.
  6. i18n — no hardcoded strings, ~1.3× text expansion slack for German, narrower glyphs for CJK, RTL flip consideration for icons with direction.
  7. Offline / slow — optimistic UI with reconciliation on failure; skeleton persists past timeout with a "still loading…" affordance.
  8. Permission — what happens when the user lacks access: disabled vs hidden. Always surface a "why" (tooltip, inline helper) when disabled.
  9. Zero-state → first-run — inline hints beat 5-step tours. Guide within the surface, not over it.

Knob-agnostic — correctness is not tunable. Run the full matrix regardless of CRAFT_LEVEL / MOTION_INTENSITY / VISUAL_DENSITY.

References to read: references/accessibility.md (keyboard + screen reader paths), references/copy.md (error and empty-state voice), references/motion.md Rendering Performance section (skeleton motion + reduced-motion).

Output: a per-surface checklist marking each of the 9 items as present / missing / partial. Then edit the code to fix what's missing. Print the Review Format table showing fixes. End with a "still at risk" list for anything you couldn't safely auto-fix (requires backend, requires design decision, requires translation files).

Next step: /finalize — the pre-ship gate (rung 3).

Gives 0 of the 12 instructions most design frontend skills give in 609 tokens

Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07

  • use css variables for color consistencyin 72 of 1169, across 23 files
  • commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
  • match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
  • add atmospheric background effects and texturesin 57 of 1169, across 9 files
  • use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
  • implement real working codein 55 of 1169, across 7 files
  • vary themes and aesthetics across different designsin 48 of 1169, across 7 files
  • launch chromium in headless modein 47 of 1169, across 4 files
  • close the browser when donein 47 of 1169, across 4 files
  • run provided scripts with help flag firstin 47 of 1169, across 4 files
  • wait for network idle statein 47 of 1169, across 4 files
  • use descriptive selectors for elementsin 47 of 1169, across 4 files

Said here and by no other author read

  • load the ui-craft skill
  • Provide one reason and one action for empty states
  • check every key surface against the matrix
  • use layout-matched skeletons instead of generic spinners
  • delay skeleton rendering by two hundred milliseconds
  • use an em dash for missing metrics

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. 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.