Run any Skill in Manus with one click

product-review

Stars0

Forks0

UpdatedJune 14, 2026 at 14:47

Use when the user wants a product/design/UX critique (e.g. "product-review", "/product-review", "is this the right thing to build / the right UX?"). Questions what to build and how users will perceive it, not just code correctness.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

skyhook-io

skyhook-io/skyhook-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

SKILL.md

readonly

name	product-review
description	Use when the user wants a product/design/UX critique (e.g. "product-review", "/product-review", "is this the right thing to build / the right UX?"). Questions what to build and how users will perceive it, not just code correctness.
metadata	{"short-description":"Critique what & how to build, not just whether it's correct"}

Product Review (Codex)

Product/design/UX critique — same workflow as Claude's /product-review.

Canonical procedure: read ~/.codex/skills/skyhook-skills-commands/product-review.md and follow it (premise → journeys (8–10, ranked 0–10) → UX shape → comprehension → states → AI-slop/design-system → 0–10 + "what a 10 looks like" + severity triage). Codex notes:

This is model-driven critique — no special tools needed; apply the forcing functions directly. Take a skeptical product+design lead's voice; question the premise and the chosen shape before execution.
For the rendered-UI lens, use the repo's visual-test if available (see .claude/commands/qa.md).
Surface taste/product decisions to the user — never silently "fix" them. Lead with premise/journey problems; a beautiful implementation of the wrong thing is still wrong. Don't ping-pong with prior reviewers.

More from this repository

same repository

autodev

skyhook-io/skyhook-skills

Use when the user asks to take a task end-to-end autonomously (e.g. "autodev", "/autodev", "build this on autopilot"). Runs the full chain — plan → implement → review → PR → converge — stopping only at real decisions.

2026-07-010

claude-review

skyhook-io/skyhook-skills

Use when the user asks for a cross-review by Claude (e.g. types "claude-review", "/claude-review", or "have Claude review this"). Invokes Claude Code headlessly to review the current branch/changes, prints Claude's findings verbatim, then triages them skeptically instead of auto-agreeing.

2026-07-010

review-loop

skyhook-io/skyhook-skills

Use when the user wants the current code proactively reviewed and fixed (e.g. "review-loop", "/review-loop", "review what I have and fix it"). Self + cross-model review → triage → fix → update PR, loop until clean.

2026-07-010

plan-loop

skyhook-io/skyhook-skills

Use when the user asks to plan a task before coding (e.g. "plan-loop", "/plan-loop", "plan this out first"). Draft a detailed plan, cross-review it with Claude, triage skeptically, iterate, then gate for sign-off.

2026-06-140

name	product-review
description	Use when the user wants a product/design/UX critique (e.g. "product-review", "/product-review", "is this the right thing to build / the right UX?"). Questions what to build and how users will perceive it, not just code correctness.
metadata	{"short-description":"Critique what & how to build, not just whether it's correct"}

Product Review (Codex)

Product/design/UX critique — same workflow as Claude's /product-review.

This is model-driven critique — no special tools needed; apply the forcing functions directly. Take a skeptical product+design lead's voice; question the premise and the chosen shape before execution.
For the rendered-UI lens, use the repo's visual-test if available (see .claude/commands/qa.md).
Surface taste/product decisions to the user — never silently "fix" them. Lead with premise/journey problems; a beautiful implementation of the wrong thing is still wrong. Don't ping-pong with prior reviewers.