plugin87/ux-ui-agent-skills

observe

Show whether the agent followed the kit''s rules in recent sessions: pages edited and measured, Stop hook blocks, findings left open.

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 observe

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? Check once: ls ${CLAUDE_SKILL_DIR}/../../../scripts/observe.mjs >/dev/null 2>&1 && echo KIT_OK || echo KIT_MISSING On KIT_MISSING only the skill folders were installed. Say so, point the user at the plugin install or npx ux-ui-agent-skills init, and stop.

Report what the hooks recorded - never a reconstruction from memory.

  1. Run node ${CLAUDE_SKILL_DIR}/../../../scripts/observe.mjs --project "$CLAUDE_PROJECT_DIR"

(or without --project when the user asks about every project, and with --days N when they name a window).

  1. Quote the summary lines it prints. If it says no session edited UI, say that

and stop: there is nothing to judge.

  1. For each session marked BROKE A RULE, run it again with --session <id> and

say which rule failed and the timeline line that shows it.

  1. If the user wants the page, run it with --html <path> and give the path.

What it measures, and what it does not: three counted rules per session - every edited page had a passing gate before the end, no fast-gate finding was left on a file's latest version, and the agent never finished while the Stop hook still had pages open. It says nothing about design quality, and an unfinished session is not counted for or against.

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