plugin87/ux-ui-agent-skills

ship

Pre-release gate — run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog).

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/plugin87/ux-ui-agent-skills --skill ship

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Step 0 — is the kit here? This skill reads files from the kit. Check once: ls ${CLAUDE_SKILL_DIR}/../../../tokens >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING On KIT_MISSING only the skill folders were installed, which is what npx skills add does. Say so plainly, point the user at npx ux-ui-agent-skills init or the plugin install, and stop. Do not guess the contents of a file you could not open.

Gate first, then prepare the release. Do nothing destructive without explicit confirmation (no tag, no publish) — this command verifies and drafts only.

  1. Quality gate (must be fully green before continuing):
  • node ${CLAUDE_SKILL_DIR}/../../../scripts/accuracy_report.mjs — report the real N/N.
  • node ${CLAUDE_SKILL_DIR}/../../../scripts/verify_responsive.mjs examples — no overflow at 280/320/414.
  • python3 ${CLAUDE_SKILL_DIR}/../../../scripts/check_no_emoji.py — UI + taste + instruction surface.

If anything fails, stop and fix; do not proceed to the checklist.

  1. Release checklist (per the project release rule):
  • Update README.md: version badge, "current" line, and changelog entry.
  • Confirm the bump level (major/minor/patch) with the user — it is their call.
  • Confirm examples/apple-home stays gitignored (local IP).
  • List the commits since the last tag so the changelog is accurate.
  1. Output a ready-to-review summary: the green N/N line, the proposed version,

and the drafted changelog entry. Wait for the user to approve before any git tag / publish step.

from this repository

More skills

All skills
plugin87
Community

critique

Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.

1h installs
1
GitHub stars
3.2K
Updated
Nov 18
plugin87
Community

design-qa

Set up or run design QA gates for token + hardcoded-value lint, automated a11y (axe), contrast, visual regression across variants/states/themes/RTL, and the manual a11y checklist. Use when the user wants CI quality gates, to prevent design regressions, or to QA a component/screen before shipping.

1h installs
2
GitHub stars
3.2K
Updated
Nov 18
plugin87
Community

redesign

Upgrade an existing website or app to premium quality without breaking functionality. Audit the current design, identify generic/AI tells, then apply taste and system rules surgically. Use when the user wants to improve, modernize, polish, or "make better" an existing UI/codebase.

1h installs
2
GitHub stars
3.2K
Updated
Nov 18
plugin87
Community

data-dashboard

Build a dense, data-heavy screen - an analytics console or a trading terminal - with real charts drawn from tokens: candlestick, volume, depth, stacked area, waterfall, scatter, correlation matrix, donut, gauge, sparklines, heatmaps and order books. Use when the request is a dashboard, terminal, monitoring view, data console, or any screen whose job is to show many numbers at once. Covers the layout sequence, the SVG geometry, the accessibility contract per chart type, and the contrast traps tha

1h installs
1
GitHub stars
3.1K
Updated
Oct 27