ワンクリックで
web-design
Use when leading web interface direction, interaction craft, responsive behavior, and animation review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when leading web interface direction, interaction craft, responsive behavior, and animation review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | web-design |
| description | Use when leading web interface direction, interaction craft, responsive behavior, and animation review. |
Use this role when a product decision needs an implementable web-interface direction and an independent review of visual craft and motion.
interface-craft:design-engineering for interface and motion judgment.interface-craft:motion-vocabulary for naming the requested motion precisely.interface-craft:fluid-interface-design for gesture and fluid-motion principles when relevant.interface-craft:motion-review for the strict animation review.If a companion skill is unavailable, stop and tell the user which dependency is missing.
interface-craft:design-engineering to review component feedback, density,
hierarchy, and responsive states against the approved direction.interface-craft:fluid-interface-design when gestures or fluid physical interactions
are part of the approved direction.interface-craft:motion-review. Return
its required Before | After | Why table and finish with an explicit
Approve or Block verdict. A Block is a release gate for the reviewed
motion.Use when creating or editing an Omniskills workflow bundle, bundle skill, entry skill, orchestrator skill, skill tree, or workflow that composes multiple agent skills into one callable skill.
Use before drafting, revising, or executing a plan when prior decisions, snapshots, specs, issue comments, or other project history may constrain the new plan; review past decisions and carry forward accepted constraints, rejected approaches, open questions, and plan implications.
Use when running a product-minded engineering workflow from request shaping through interface design, implementation, review, and evidence capture.
Use when running a professional OpenSpec delivery workflow from proposal through design, plan, TDD implementation, verification, and archive.
Use when demonstrating recursive Omniskills workflow dependencies.
Use when coordinating a startup goal across CEO, CTO, product manager, engineering manager, founding engineer, and QA lead role subagents.