跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

review

User-invoked review that coordinates the humane review skills — layout-rules, ux-writing, typography, nielsen-heuristics, walkthrough, design-tokens contrast — into one prioritized verdict, and marks the domains it cannot cover instead of improvising them. Supports quick and full modes. Identifies the artifact first and runs a reduced document pipeline for a README, PRD, or docs page rather than stretching a UI pipeline over it. Use when explicitly asked for a holistic review of a screen, flow, feature, product, or document. Triggers on humane review, full review, review the whole thing, holistic UI audit, cross-skill design review, "review this properly", "полный ревью".

glebis · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add glebis/humane-agentic-design --skill review

技能说明


name: review description: User-invoked review that coordinates the humane review skills — layout-rules, ux-writing, typography, nielsen-heuristics, walkthrough, design-tokens contrast — into one prioritized verdict, and marks the domains it cannot cover instead of improvising them. Supports quick and full modes. Identifies the artifact first and runs a reduced document pipeline for a README, PRD, or docs page rather than stretching a UI pipeline over it. Use when explicitly asked for a holistic review of a screen, flow, feature, product, or document. Triggers on humane review, full review, review the whole thing, holistic UI audit, cross-skill design review, "review this properly", "полный ревью". accepts:

  • from: brand-illustrate
  • from: design-frameworks orchestrates:
  • layout-rules
  • ux-writing
  • typography
  • nielsen-heuristics
  • walkthrough
  • design-tokens

Review the whole thing, once

Announce at start: "I'm using the humane:review skill to run the review cycle and consolidate one verdict."

Six separate audits stapled together is not a review — it is six reports the reader has to reconcile. This skill runs the domains, lets each owning skill apply its own rules, and consolidates the evidence into one ranked verdict.

This skill owns orchestration only. It never restates or overrides a domain rule. Structure and defect classes belong to layout-rules; wording to ux-writing; usability principles to nielsen-heuristics; task completion to walkthrough; color measurement to design-tokens; mechanical English and Russian text polish to typography. If you find yourself writing a rule here, it belongs in the skill that owns it.

1. Identify the artifact before anything else

This pipeline is built for an interface. Given something else it will happily stretch — returning a table of N/A and one strained domain — so decide what you are holding first, and say so in the output.

ArtifactWhat to run
Screen, flow, feature, running app, UI sourceThe full pipeline below
Document — README, docs page, PRD, spec, proposalThe document pipeline: ux-writing for the prose, typography for language-appropriate mechanics and editorial flags, layout-rules for structure and hierarchy only (rules 1–4, 39), plus persona-review if the reader's objections matter more than the wording. Skip walkthrough, nielsen-heuristics, and contrast — mark them N/A (not an interface), not Clear
Copy in isolation — a tagline, a hero, brand valuesNot a review. Hand it to respondent-panel, and to ux-writing for the rewrite
Spec for an unbuilt interfacenielsen-heuristics design-risk mode, which produces unscored risk flags. Never severity-score a thing that does not run
Token set with no UIdesign-tokens contrast alone

A document still gets the full contract — findings table, considered-but-rejected, verification, verdict — just over fewer domains. State the reduced pipeline in Scope and Coverage so the reader knows what was and was not possible.

Why 1–4 and 39, and not 5, 8, 9, 38. Those four are wording rules living in the layout-rules file — "a summary line must add a conclusion", "link the entity", "empty states teach", "copy slop". ux-writing owns wording, and it already covers each of them. Routing them here would review the same sentence twice under two owners and risk two different rewrites of it. Send anything about what a string says to ux-writing; keep layout-rules on structure, hierarchy, and the boldness budget.

If the artifact is a document that describes an interface (a README for a UI tool, a design doc), review the document as a document. Do not review the interface it describes from its description alone — that is a claim you cannot evidence.

2. Resolve scope and mode

Infer the screen, flow, feature, document, or repository scope from the request and the workspace. State the resolved scope in the output. Default to full.

ModeCoverageFinding cap
quickThe primary path and highest-traffic states; report HIGH and MEDIUM only5
fullThe whole requested scope across every available domain, including empty, loading, error, and narrow-width states where they exist15

In full mode on a runnable interface, the mobile device tier is part of the scope: the primary flow is driven at the mobile tier per walkthrough's references/driven.md (which owns the tool ladder, device matrix, and screenshot contract). If no browser tool rung is available, the mobile tier is reported Not reviewed in Scope and Coverage — never silently narrowed to desktop.

If the scope is too large to inspect credibly, narrow it to the highest-traffic complete flow and state the boundary. Never imply that uninspected surfaces were reviewed.

3. Recon before judgment

Identify the stack, styling system, component library, token file, supported viewports, and any preview or test command. Read the project's jtbd.json if one exists — it tells you which flows matter and which outcomes are underserved, and a review that ranks findings without it is ranking by taste.

Follow the project's established conventions. Conflict precedence, as everywhere in humane: the user's explicit words > the skill's ruleset > the project's existing system > personal taste.

4. Run the domains in this order

Foundational failures first, so polish never hides them:

#DomainOwnerSkip when
1Task completionwalkthroughThere is nothing operable to attempt
2Usability principlesnielsen-heuristics—
3Structure and defect classeslayout-rules—
4Interface copyux-writing—
5Microtypography and editorial polishtypographyThe text is not English or Russian, or language/standard is unresolved and materially changes the review
6Color
阅读完整来源 ↗