design-handoff-review

Review a design handoff for implementation readiness by checking source artifacts, flows, states, responsive behavior, components, tokens, content, accessibility, assets, interaction details, and unresolved decisions.

Ir para a instalação

Repositório: Dadmin88/hermes-agency
Última atividade na origem: 16 de agosto de 2026 às 06:25
Idioma detectado do SKILL.md: inglês
Estrelas: 8
Forks: 2

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/Dadmin88/hermes-agency --skill design-handoff-review

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

Design Handoff Review

Use immediately before or during engineering handoff when the design must contain enough detail to implement without reconstructing intent from scattered artifacts.

Procedure

Confirm the authoritative design/spec source, product requirements, target platforms, current design-system version, and the exact scope being handed off.

Walk the complete primary and alternate flows and verify each screen/view/component is connected to an explicit state and user action rather than a gallery of disconnected mockups.

Check responsive/adaptive behavior: breakpoints or layout rules, content priority, overflow, resizing, orientation, density, long/short content, and component rearrangement where relevant.

Verify component and token use: canonical components/variants, typography, spacing, color, iconography, motion, and documented exceptions that require new design-system work.

Check interaction details that static images cannot communicate: hover/focus/pressed/disabled/selected states, keyboard behavior, transitions, drag/gesture rules, loading/progress, confirmation, undo, and error recovery.

Check content and data assumptions: realistic strings/data ranges, truncation/wrapping, empty/large lists, dates/numbers/localization, optional fields, and placeholders that should not reach production.

Check accessibility annotations or requirements for semantics, accessible names, focus, announcements, contrast/adaptation, alternatives, and custom widget behavior.

Verify required assets and specifications are available in implementable formats with naming/export guidance where design owns them.

List unresolved decisions, their owner, and whether they block implementation. Separate product/design decisions from engineering implementation choices.

Produce a concise handoff-readiness result with blocking gaps, non-blocking clarifications, source links/artifacts, and what engineering can safely decide independently.