product-review

Name: product-review
Author: sendaifun

162stars45forks

How to install product-review?

sendaifun/solana-new/product-review

$npx -y skills add sendaifun/solana-new --skill product-review

Installs into the current project.

Summary

Product quality review — UX flows, onboarding, feature completeness, and user value. Use when a user says "product review", "review my product", "UX review", "is my product good", "product quality", "user experience review", "onboarding review", or "feature audit". Different from

Files · 1

View on GitHub

SKILL.md

1	## Preamble (run first)
2
3	```bash
4	_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"telemetryTier": "[^"]"' \| head -1 \| sed 's/."telemetryTier": "//;s/"$//' \|\| echo "anonymous")
5	_TEL_TIER="${_TEL_TIER:-anonymous}"
6	_TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" \|\| echo "no")
7	_TEL_START=$(date +%s)
8	_SESSION_ID="$$-$(date +%s)"
9	mkdir -p ~/.superstack
10	echo "TELEMETRY: $_TEL_TIER"
11	echo "TEL_PROMPTED: $_TEL_PROMPTED"
12	if [ "$_TEL_TIER" != "off" ]; then
13	_TEL_EVENT='{"skill":"product-review","phase":"build","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}'
14	echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null \|\| true
15	_CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"convexUrl":"[^"]*"' \| head -1 \| cut -d'"' -f4 \|\| echo "")
16	[ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"product-review","phase":"build","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 &
17	true
18	fi
19	```
20
21	If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry.
22	Use AskUserQuestion:
23
24	> Help superstack get better! We track which skills get used and how long they take —
25	> no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`.
26
27	Options:
28	- A) Sure, help superstack improve (anonymous)
29	- B) No thanks
30
31	If A: run this bash:
32	```bash
33	echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
34	_TEL_TIER="anonymous"
35	touch ~/.superstack/.telemetry-prompted
36	```
37
38	If B: run this bash:
39	```bash
40	echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
41	_TEL_TIER="off"
42	touch ~/.superstack/.telemetry-prompted
43	```
44
45	This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow.
46
47	> Wrong skill? See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills.
48
49	## Overview
50
51	Structured product quality evaluation. Walk through the product as a new user, evaluate every touchpoint, and produce an actionable improvement roadmap. Balanced — highlight strengths AND weaknesses.
52
53	This is NOT a code review (use `/review-and-iterate` for that) and NOT a harsh roast (use `/roast-my-product` for that). This is a structured, balanced evaluation that helps you understand where your product stands and what to improve next.
54
55	## Workflow
56
57	### Step 1: Gather Context
58
59	Always start by asking — use `AskUserQuestion`:
60
61	- What is the product? (URL, description, or demo)
62	- Who is the target user?
63	- What's the core use case — the ONE thing users should be able to do?
64	- What stage? (prototype, MVP, beta, launched)
65
66	Do NOT proceed without answers. You need to understand what you're reviewing and through whose eyes.
67
68	### Step 2: Read Existing Context
69
70	Read `.superstack/idea-context.md` and `.superstack/build-context.md` if available. These contain prior decisions about target market, tech stack, competitive landscape, and build progress.
71
72	### Step 3: Load the Evaluation Framework
73
74	Read `references/product-quality-rubric.md` for the 8 quality dimensions. This is your scoring framework.
75
76	### Step 4: Walk Through as a First-Time User
77
78	Put yourself in the shoes of the target user described in Step 1. Use `references/onboarding-checklist.md` to systematically evaluate the first-time experience:
79
80	- What do you see first?
81	- How quickly do you understand what this product does?
82	- How many steps to the first meaningful action?
83	- Where do you get confused?
84	- Where do you get delighted?
85
86	Document every friction point and every moment of clarity.
87
88	### Step 5: Evaluate Each Quality Dimension
89
90	Go through each dimension from `references/product-quality-rubric.md`:
91
92	1. Onboarding Flow
93	2. Core Experience
94	3. Error Handling
95	4. Information Architecture
96	5. Visual Design & Polish
97	6. Performance
98	7. Accessibility
99	8. Feature Completeness
100
101	For each dimension:
102	- Score 1-10 with specific evidence
103	- Note what's working well
104	- Note what needs improvement
105	- Suggest a specific fix for the biggest issue in this dimension
106
107	### Step 6: Reference Web3 Best Practices
108
109	Cross-reference the product against `references/crypto-ux-patterns.md` for web3-specific best practices. Note which patterns are implemented well and which are missing.
110
111	### Step 7: Synthesize Findings
112
113	Compile your evaluation into a structured report:
114
115	1. Executive Summary — 2-3 sentences on the product's overall quality
116	2. Scorecard — all 8 dimensions with scores
117	3. **

People who liked this also viewed

6 picks

Type

product-review

162stars45forks

View on GitHub

How to install product-review?

sendaifun/solana-new/product-review

$npx -y skills add sendaifun/solana-new --skill product-review

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Preamble (run first)
2
3	```bash
4	_TEL_TIER=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"telemetryTier": "[^"]"' \| head -1 \| sed 's/."telemetryTier": "//;s/"$//' \|\| echo "anonymous")
5	_TEL_TIER="${_TEL_TIER:-anonymous}"
6	_TEL_PROMPTED=$([ -f ~/.superstack/.telemetry-prompted ] && echo "yes" \|\| echo "no")
7	_TEL_START=$(date +%s)
8	_SESSION_ID="$$-$(date +%s)"
9	mkdir -p ~/.superstack
10	echo "TELEMETRY: $_TEL_TIER"
11	echo "TEL_PROMPTED: $_TEL_PROMPTED"
12	if [ "$_TEL_TIER" != "off" ]; then
13	_TEL_EVENT='{"skill":"product-review","phase":"build","event":"started","ts":"'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}'
14	echo "$_TEL_EVENT" >> ~/.superstack/telemetry.jsonl 2>/dev/null \|\| true
15	_CONVEX_URL=$(cat ~/.superstack/config.json 2>/dev/null \| grep -o '"convexUrl":"[^"]*"' \| head -1 \| cut -d'"' -f4 \|\| echo "")
16	[ -n "$_CONVEX_URL" ] && curl -s -X POST "$_CONVEX_URL/api/mutation" -H "Content-Type: application/json" -d '{"path":"telemetry:track","args":{"skill":"product-review","phase":"build","status":"success","version":"0.2.0","platform":"'$(uname -s)-$(uname -m)'","timestamp":'$(date +%s)000'}}' >/dev/null 2>&1 &
17	true
18	fi
19	```
20
21	If `TEL_PROMPTED` is `no`: Before starting the skill workflow, ask the user about telemetry.
22	Use AskUserQuestion:
23
24	> Help superstack get better! We track which skills get used and how long they take —
25	> no code, no file paths, no PII. Change anytime in `~/.superstack/config.json`.
26
27	Options:
28	- A) Sure, help superstack improve (anonymous)
29	- B) No thanks
30
31	If A: run this bash:
32	```bash
33	echo '{"telemetryTier":"anonymous"}' > ~/.superstack/config.json
34	_TEL_TIER="anonymous"
35	touch ~/.superstack/.telemetry-prompted
36	```
37
38	If B: run this bash:
39	```bash
40	echo '{"telemetryTier":"off"}' > ~/.superstack/config.json
41	_TEL_TIER="off"
42	touch ~/.superstack/.telemetry-prompted
43	```
44
45	This only happens once. If `TEL_PROMPTED` is `yes`, skip this entirely and proceed to the skill workflow.
46
47	> Wrong skill? See [SKILL_ROUTER.md](../../SKILL_ROUTER.md) for all available skills.
48
49	## Overview
50
51	Structured product quality evaluation. Walk through the product as a new user, evaluate every touchpoint, and produce an actionable improvement roadmap. Balanced — highlight strengths AND weaknesses.
52
53	This is NOT a code review (use `/review-and-iterate` for that) and NOT a harsh roast (use `/roast-my-product` for that). This is a structured, balanced evaluation that helps you understand where your product stands and what to improve next.
54
55	## Workflow
56
57	### Step 1: Gather Context
58
59	Always start by asking — use `AskUserQuestion`:
60
61	- What is the product? (URL, description, or demo)
62	- Who is the target user?
63	- What's the core use case — the ONE thing users should be able to do?
64	- What stage? (prototype, MVP, beta, launched)
65
66	Do NOT proceed without answers. You need to understand what you're reviewing and through whose eyes.
67
68	### Step 2: Read Existing Context
69
70	Read `.superstack/idea-context.md` and `.superstack/build-context.md` if available. These contain prior decisions about target market, tech stack, competitive landscape, and build progress.
71
72	### Step 3: Load the Evaluation Framework
73
74	Read `references/product-quality-rubric.md` for the 8 quality dimensions. This is your scoring framework.
75
76	### Step 4: Walk Through as a First-Time User
77
78	Put yourself in the shoes of the target user described in Step 1. Use `references/onboarding-checklist.md` to systematically evaluate the first-time experience:
79
80	- What do you see first?
81	- How quickly do you understand what this product does?
82	- How many steps to the first meaningful action?
83	- Where do you get confused?
84	- Where do you get delighted?
85
86	Document every friction point and every moment of clarity.
87
88	### Step 5: Evaluate Each Quality Dimension
89
90	Go through each dimension from `references/product-quality-rubric.md`:
91
92	1. Onboarding Flow
93	2. Core Experience
94	3. Error Handling
95	4. Information Architecture
96	5. Visual Design & Polish
97	6. Performance
98	7. Accessibility
99	8. Feature Completeness
100
101	For each dimension:
102	- Score 1-10 with specific evidence
103	- Note what's working well
104	- Note what needs improvement
105	- Suggest a specific fix for the biggest issue in this dimension
106
107	### Step 6: Reference Web3 Best Practices
108
109	Cross-reference the product against `references/crypto-ux-patterns.md` for web3-specific best practices. Note which patterns are implemented well and which are missing.
110
111	### Step 7: Synthesize Findings
112
113	Compile your evaluation into a structured report:
114
115	1. Executive Summary — 2-3 sentences on the product's overall quality
116	2. Scorecard — all 8 dimensions with scores
117	3. **

People who liked this also viewed

6 picks

Type