Product Designer

Use when the user asks to review a design, critique a UI or mockup, give design feedback, or check a screen for usability and accessibility issues. Do NOT use for visual brand or aesthetic preference debates, or for reviewing copy before layout is settled.

116 stars 35 forksFrontend & Design

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add aakashg/pm-claude-skills --skill product-designer
Manual install
git clone --depth 1 https://github.com/aakashg/pm-claude-skills.git /tmp/pm-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-claude-skills/skills/product-designer ~/.claude/skills/product-designer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Product Design Reviewer

Review a design across 6 dimensions and return prioritized, actionable feedback.

## Step 0 — Read first

| Source | Path | What to extract |
|--------|------|-----------------|
| The design | screenshot, image, or Figma link the user shares | The actual screen — never review from a text description alone |
| Project context | `CLAUDE.md` | Product, target users, platform, current focus |
| Screen-type checklist | `references/screen-checklists.md` | The issues specific to forms, tables, onboarding, settings, modals |
| AI UX checks | `references/ai-ux-review.md` | Extra checks when the design includes AI features |
| Prior feedback | any doc the user names | What was already flagged — do not re-flag resolved issues |

If the user describes the design in words only, request a screenshot before reviewing. Reviewing a described design means inventing one.

## Constraints

Mandatory.

- Every issue gets all three: what is wrong, why it matters to the user, and a concrete fix.
- Never give aesthetic preference as feedback. "I don't like this blue" is a preference. "This CTA is 2.1:1 against the background, WCAG AA needs 4.5:1" is feedback.
- Never list a problem without a fix. Problems without solutions are complaints.
- Never redesign the whole page. Work within the current design direction.
- Never flag more than 3 Must Fix items. Prioritize ruthlessly — 3 high-impact issues beat 15 nitpicks.
- Never assume platform or user type. If unstated, ask.
Read the full skill on GitHub

Details

Skill name
product-designer
Path
skills/product-designer/SKILL.md
License
MIT
Repo updated
8 August 2026

FAQ

What does the Product Designer skill do?

Use when the user asks to review a design, critique a UI or mockup, give design feedback, or check a screen for usability and accessibility issues. Do NOT use for visual brand or aesthetic preference debates, or for reviewing copy before layout is settled.

How do I install the Product Designer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add aakashg/pm-claude-skills --skill product-designer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Product Designer popular?

It lives in aakashg/pm-claude-skills, which has 116 GitHub stars and 35 forks.

Related skills

Idea Validator

116

aakashg/pm-claude-skills

Use when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something. Do NOT use for prioritizing an existing backlog or reviewing a shipped feature — those need RICE scoring or a design review instead.

Testing & QA35

Linkedin Post Writer

116

aakashg/pm-claude-skills

Use when the user asks to write, draft, or rewrite a LinkedIn post, turn notes or an article into a LinkedIn post, or fix a hook that is not landing. Do NOT use for X/Twitter threads, newsletters, or blog posts — those need different length and hook rules.

Writing & Content35

Prompt Engineer

116

aakashg/pm-claude-skills

Use when the user asks to improve, optimize, rewrite, debug, or shorten a prompt, or asks why a prompt is producing bad output. Do NOT use for writing a Claude Code SKILL.md — that needs skill structure rules, not prompt techniques.

AI, LLMs & Agents35

Shader for Interfaces

120

v2space-labs/shader-for-interfaces

Decide whether an interface effect should stay in CSS, SVG, or Canvas 2D or needs WebGL or WebGPU, then create, integrate, diagnose, and visually verify focused GPU effects inside product interfaces. Use for contained Three.js/WebGL2/GLSL or vgpu/WebGPU/WGSL surfaces, modest particles, GPU data views, and responsive canvases in TypeScript or React. Do not use for dependent passes, persistent simulations, formal render graphs, adaptive-quality systems, or renderer migrations.

Frontend & Design

Nerf to 3dgs Migrator

188

jaccen/Awesome-Gaussian-Skills

Migrate NeRF-based methods to 3DGS via the SLAT unified encode-decode framework. Analyzes component compatibility, provides code templates, identifies issues. Covers encoding, deformation, appearance, geometry. Use when: migrating NeRF method to 3DGS, comparing NeRF vs 3DGS components, designing hybrid NeRF-3DGS approaches, NeRF迁移3DGS/高斯泼溅转换/代码模板.

Frontend & Design13

Chatgpt Search

116

SeifBenayed/cloclo

Search ChatGPT and extract the full response + hydration JSON that powers the UI. Attaches to a running Chrome instance (port 9222 by default), opens ChatGPT, submits a query, waits for the streamed response, and returns structured data: messages, product cards, hydration JSON, and API calls. Use when asked to "search chatgpt", "ask chatgpt", "chatgpt search", "get chatgpt response", or "scrape chatgpt".

Frontend & DesignIn 1 list32

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.