← Plugin catalog
Creativity

HardenUI

Saul Martí v2.0.0

Harden UI edge cases

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Harden UI edge cases

Not specified in the available declarations: limitations, pricing & account requirements.

Onboarding example

Harden this UI for production edge cases
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 18, 2026. Package observed Nov 17, 2026.

View package source →

Description

From the marketplace listing

Uses the real vendored Impeccable workflow. Specialized for production hardening of error states, overflow, internationalization, unusual content, and interface edge cases.

Language: English · Automatically detected from descriptions.

Matches for “UI”

Exact text from the indicated source. A mention alone does not establish support for your task.

Plugin name

HardenUI

Package name

engineering-suite-harden-ui

Publisher subtitle

Harden UI edge cases

Publisher keywords · listing

engineering-suite harden-ui skills

What changed

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package80 files · 804 KBBrowse files →
Skill instructions
entry-harden-ui764 Bytes

View saved version →

---
name: entry-harden-ui
description: "Use whenever the HardenUI plugin is selected. Route the request to the intended bundled workflow while keeping all dependencies internal to this plugin."
---

# HardenUI

This is the public entry workflow for this plugin. The bundled skills below are dependencies, not competing entry points.

## Mandatory routing

Invoke impeccable with the harden command. Focus on production edge cases, errors, overflow, i18n, and resilience; do not broaden into visual redesign.

If a bundled workflow calls another bundled skill, invoke that local bundled copy. Never require the user to install another plugin to complete this workflow.

## Allowed Impeccable commands

Only route to: `harden`.

## Bundled workflows

- `impeccable`
impeccable11.7 KB

View saved version →

---
name: impeccable
description: Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
version: 4.3.1
user-invocable: true
argument-hint: "[shape · audit|critique · animate|bolder|colorize|delight|layout|overdrive|quieter|typeset · adapt|clarify|distill · harden|onboard|optimize|polish · init|document|extract|live] [target]"
license: Apache 2.0
disable-model-invocation: true
---

This skill gives you the tools and permission to create design that earns to be called out-of-distribution craft: Whereas before, your design work would have been safe, timid and measured, you now approach every design task as an award-winning design director with impeccable understanding for what makes exceptional design work: production-grade code, peak creativity, a clear POV, deep understanding of the needs of the client and users, and exceptional craft.

Core principles:
- Go all out. No hedging, no shortcuts. The deliverable must be complete (except assets the user must provide).
- Dream big and bold. Distinct, beautiful, outstanding and highly inspiring work.
- Verify in bounded passes, not a loop, and the ceiling covers the whole cycle: screenshots, defect scans, micro-edits, and rebuilds alike. Build fully, inspect once with a batched round (desktop and mobile together on the web; the shipped device classes on a native platform), fix everything it shows in one batch, confirm with at most one more round, and stop polishing. Open-ended self-QA burns the user's money doing worse what the finish handoffs do better.

## Setup

1. Run `"${CLAUDE_SKILL_DIR}/scripts/impeccable" context` once per session, where `${CLAUDE_SKILL_DIR}` is the directory that contains this SKILL.md (the skill folder, not a plugin root two levels above it); keep cwd at the user's project. Every `"${CLAUDE_SKILL_DIR}/scripts/impeccable" <verb>` command in this skill and its references resolves against that base directory. In reference files, replace the skill-base-dir placeholder with this directory before running commands; it is not a shell variable. On a Windows shell without `sh`, call `"${CLAUDE_SKILL_DIR}/scripts/impeccable.cmd"` instead. The launcher runs a self-contained binary that ships next to it or is downloaded once on first run; no Node or other runtime is required. Pass a named source file or route as `--target <path>`. It loads PRODUCT.md, DESIGN.md, the matching surface brief, and native-platform guidance when applicable; follow its directives and do not rerun it.
2. Load the request's playbook: its Commands-table reference for an explicit/implied sub-command, or [reference/new-work.md](reference/new-work.md) for a new surface or replacement visual world. Inspect target and incumbent visual truth before editing. When the app cannot run, start with committed visual-regression goldens or screenshot fixtures; verify target and freshness against current tokens, CSS, components, or assets, resolve conflicts, and compare theme/variant captures.
3. After resolving analysis and direction, read [reference/craft-floor.md](reference/craft-floor.md) immediately before any UI edit, including small refinements. It carries the quality floor, the a

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 50 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
Saul Martí
Keywords
See keywords

Declared capabilities

  • Harden UI edge cases

Package observed Nov 17, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 18, 2026 · 06:00 UTC
Collection status
Collected

plugins_6aa3091ad9208191a48b9fc2276e2751

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.