growth-design-review
9
总安装量
9
周安装量
#33346
全站排名
安装命令
npx skills add https://github.com/woakin/growth-design-review --skill growth-design-review
Agent 安装分布
kimi-cli
9
gemini-cli
9
amp
9
github-copilot
9
codex
9
opencode
9
Skill 文档
ð§ Growth Design Review Skill
Review UI designs or code against Product Psychology & Growth Design frameworks. Propose a prioritized development plan following each framework’s best practices to maximize the Net Perceived Value.
ð Frameworks Overview
This skill applies five core frameworks. CRITICAL: You must read the full definitions in reference/frameworks.md before performing any review.
- Psych Framework â Maximize Net Perceived Value (Motivation – Friction).
- B.I.A.S. Framework â Behavioral audit: Block, Interpret, Act, Store.
- C.L.E.A.R. Scorecard â Copywriting, Layout, Emphasis, Accessibility, Reward.
- UI Rules of Thumb â Page-type specific patterns (e.g., Landing, Dashboard, Onboarding).
- Psychological Triggers â Utilization of the IKEA Effect, Zeigarnik Effect, and Loss Aversion.
ð Review Process
Whenever a user requests a review, strictly follow these steps:
- Diagnostic Routing: Determine if the interface involves AI (LLMs, generative UI, or autonomous agents).
- If standard SaaS/Web: Apply the Psych Framework, B.I.A.S. Audit, and C.L.E.A.R. Scorecard.
- If AI-Native: Read
reference/shape-of-ai.md. Apply standard frameworks to diagnose friction, but you MUST propose solutions using specific Shape of AI patterns.
- Load Context: Read the
reference/frameworks.mdfile from this skill’s directory. - Understand the Target: Read the target UI files (components, pages, styles) the user wants reviewed. If none are provided, ask the user which files to evaluate.
- Systematic Audit: Evaluate the UI against all applicable frameworks systematically.
- Scoring: Rate each C.L.E.A.R. dimension (Copy, Layout, Emphasis, Accessibility, Reward) on a strict 1â5 scale.
- Actionable Output: Generate the output exactly matching the format below.
- Next Steps: Offer to implement the Priority 1 (Critical) items immediately for the user.
ð Required Output Format
You must format your response exactly as follows:
## ð Growth Design Audit
### 1. Psych Framework Analysis
**Net Perceived Value Assessment:**
- **Motivation signals found:** [List any]
- **Friction points found:** [List any]
- **Psych Additions present:** [Rewards, progress markers, delighters]
- **Psych Subtractions to fix:** [Redundant fields, cognitive load, jargon]
- **Labor Illusion usage:** [Present/missing, recommendation]
### 2. B.I.A.S. Behavioral Audit
| Dimension | Status | Finding |
| :--- | :---: | :--- |
| **Block** (Visual Hierarchy & Trust) | [Pass/Fail] | [Brief explanation] |
| **Interpret** (Clarity over Cleverness) | [Pass/Fail] | [Brief explanation] |
| **Act** (Decision Simplicity) | [Pass/Fail] | [Brief explanation] |
| **Store** (Peak-End Rule) | [Pass/Fail] | [Brief explanation] |
### 3. C.L.E.A.R. Scorecard
| Dimension | Score (1-5) | Finding |
| :--- | :---: | :--- |
| **C** - Copywriting | X/5 | [Brief explanation] |
| **L** - Layout | X/5 | [Brief explanation] |
| **E** - Emphasis | X/5 | [Brief explanation] |
| **A** - Accessibility | X/5 | [Brief explanation] |
| **R** - Reward | X/5 | [Brief explanation] |
| **Total Score** | **XX/25** | |
### 4. UI Rules of Thumb
- **Page Type Identified:** [Landing / Dashboard / Onboarding / Component / Other]
- **Compliance Analysis:** [Findings per applicable rule based on the page type]
### 5. Psychological Triggers
- **IKEA Effect:** [Present / Missed Opportunity] - [Explanation]
- **Zeigarnik Effect:** [Present / Missed Opportunity] - [Explanation]
- **Loss Aversion:** [Present / Missed Opportunity] - [Explanation]
### 6. Shape of AI Analysis (If AI-Native)
| Dimension | Friction Point | NPV Impact | Recommended Shape of AI Pattern |
| :--- | :--- | :--- | :--- |
| [Category] | [Brief Description] | [Impact] | **[Pattern Name]:** [Execution suggestion] |
---
## ð Development Plan
### ð´ Priority 1 â Critical (High Impact, Low Effort)
| # | Action | Framework | File(s) | Rationale |
|---|--------|-----------|---------|-----------|
| 1 | [Action] | [Framework] | [File path] | [Why this matters] |
### ð¡ Priority 2 â Important (High Impact, Higher Effort)
| # | Action | Framework | File(s) | Rationale |
|---|--------|-----------|---------|-----------|
| 1 | [Action] | [Framework] | [File path] | [Why this matters] |
### ð¢ Priority 3 â Nice to Have (Lower Impact)
| # | Action | Framework | File(s) | Rationale |
|---|--------|-----------|---------|-----------|
| 1 | [Action] | [Framework] | [File path] | [Why this matters] |