product-designers-pack

Plugin product-designers-pack from marketplace 90n-skills in polar-bear-org/claude-skills. Commands read from the repo's manifest — 17 days ago.

Skills (32)

• pdes-accessibility-review

  Runs a design-stage Accessibility Review of one screen or flow against WCAG 2.2 at your team's level, marking each check pass, fail or cannot tell from a design, writing the fix for each fail as a design change, and listing what only code, assistive technology and disabled users can show. Use for "r

• pdes-accessible-test-sessions

  Plans how to bring disabled people and older users into a round of usability sessions, with an invitation that welcomes them, access needs asked in advance as an open question, their own assistive technology, consent in accessible formats and session adjustments. Use for "run pdes-accessible-test-se

• pdes-claude-design-prototype

  Plan a Claude Design prototype with the written brief to give it, the design system and look to specify, three or more directions to ask for and remix, and the copies to save at each milestone. Use for "run pdes-claude-design-prototype", "claude design prototype", "plan a prototype in claude design"

• pdes-critique-notes-to-actions

  Sorts raw critique notes into Critique Actions and Reply, with duplicates merged, every note placed as tied to an objective, preference, out of scope or open question, your call on each tied note (change, will not change and why, test), actions with owners and dates, and a three-line reply to the ro

• pdes-critique-session-brief

  Prepares a Critique Session Brief with two or three numbered objectives, the stage of the work, the one question for the room about a real user moment, what is out of scope today, a walkthrough cut to the timebox, a framing sentence to read aloud and prompts that turn reactions into questions. Use f

• pdes-design-decision-log

  Keeps a Design Decision Log with one short numbered record per significant design decision (title, context, decision, status, consequences), the decider by role, a link to the rationale, a revisit trigger and an index. Use for "run pdes-design-decision-log", "why did we decide this", "nobody remembe

• pdes-design-handoff-spec

  Writes a Design Handoff Spec that says which file, page and version is final, puts the behaviour rules beside each screen and runs a ready check before the walkthrough with engineering. Use for "run pdes-design-handoff-spec", "design handoff", "handoff spec", "spec for engineering", "is this ready f

• pdes-design-impact-writeup

  Writes a Design Impact Write-Up with three lines up front, what design changed with ship dates, before and after per metric from your data only, what else moved in the same window, a confidence level with its reason, results that got worse kept in and lessons, with missing numbers left as not measur

• pdes-design-options-tradeoffs

  Builds a Design Options Trade-off Table with two to four options that differ in structure, flow or scope, criteria taken from your principles and brief, consequences in words with no made-up score, and what each option gives up. Use for "run pdes-design-options-tradeoffs", "show the options not just

• pdes-design-principles

  Writes Design Principles for your product area with four to seven stands, what each one gives up, a "this, not that" pair from your own screens and a conflict check that says which principle wins where. Use for "run pdes-design-principles", "write design principles for my product", "every review is

• pdes-design-pushback-brief

  Writes a Design Pushback Brief with the request in its own words and the goal behind it, the risk to users and to the business from real evidence or a visible gap, two alternatives that meet the goal, what you will and will not do, who decides if you still disagree and how the disagreement is record

• pdes-design-quality-bar

  Writes a Design Quality Bar for the work you are held to, with yes or no checks by stage (explore, refine, ready to build) drawn from the ten usability heuristics, WCAG 2.2 at your team's level, design system use, content and the product's principles, plus a proposed must-pass list for the person wh

• pdes-design-rationale-doc

  Writes a Design Rationale Doc with the decision in one line, the options considered and why each lost, the principles applied, every claim linked to real evidence or marked as a gap, the trade-offs accepted, two or three pre-mortem risks and the signal that would reopen it. Use for "run pdes-design-

• pdes-design-review-deck

  Builds a Design Review Deck that puts the decision asked, your recommendation and the date on slide one, then the problem and outcome, the options and what the recommendation gives up, real evidence with gaps shown, the feedback in scope today and next steps with owners, in a short and a working ver

• pdes-design-sameness-check

  Builds a Design Sameness Check for one design, with an inventory of its default choices (typeface, colour and gradients, backgrounds, layout pattern, radius and shadow, iconography, motion, phrasing), each marked by you as chosen on purpose or inherited from a default, up to three places for a real

• pdes-design-self-critique

  Runs a Design Self-Critique on one task before a review, with your own pass against the ten usability heuristics, a separate second-opinion pass from Claude, the two merged into one issue list, and your call on each issue (fix before the review, deliberate trade-off, needs a real user). Use for "run

• pdes-design-system-change-record

  Writes a Design System Change Record for one proposed change, with the problem, what already exists, the "can it be built from what exists" check, who is affected and a decision field left for the system owner. Use for "run pdes-design-system-change-record", "propose a design system change", "add a

• pdes-design-system-rules-file

  Write your design system as a rules file Claude can follow, with tokens by name and role, component rules with states, layout rules, a list of what the system lacks and a five-prompt test. Use for "run pdes-design-system-rules-file", "design system rules file", "Claude keeps inventing hex values", "

• pdes-heart-metrics-plan

  Builds a HEART Metrics Plan with the two or three dimensions that matter, a goal, signal and metric for each, today's baseline or "baseline needed", the data owner, instrumentation asks and guardrails. Use for "run pdes-heart-metrics-plan", "HEART framework", "goals signals metrics", "what does desi

• pdes-portfolio-case-study

  Writes a Portfolio Case Study that tells one project through three to five decisions with the options you had and the trade-off you chose, your own role and who decided what, what real users did in testing, outcomes from real data, what you would do differently and a confidentiality check before any

• pdes-problem-framing-brief

  Writes a Problem Framing Brief with the request quoted as handed over, the problem as a user situation with no fix in it, evidence on hand and missing, a "not solving" list and "we believe" hypotheses placed by risk and value. Use for "run pdes-problem-framing-brief", "problem framing", "problem sta

• pdes-product-context-file

  Write the one file Claude reads before any design task, covering who the product is for, the jobs it does, voice and terms, principles, constraints, what the product never does and where each fact came from. Use for "run pdes-product-context-file", "product context file", "Claude does not know my pr

• pdes-prototype-brief

  Write a prototype brief with the one question the prototype must answer, the lowest fidelity that answers it, the real and faked parts and a pass line set before anyone sees it. Use for "run pdes-prototype-brief", "prototype brief", "just prototype it", "what is this prototype for", "what should the

• pdes-prototype-share-check

  Prepare a prototype share check with eight checks a person runs before a prototype leaves the team, the list of what is faked, the words to say when showing it and who owns what ships. Use for "run pdes-prototype-share-check", "prototype share check", "before I share this prototype", "is this protot

• pdes-stakeholder-feedback-log

  Builds a Stakeholder Feedback Log that puts every review comment in one table by role and objective, merges duplicates, sets conflicts side by side for the person who decides, proposes accept, decline or park with a reason, flags comments that undo an earlier round and drafts a reply per stakeholder

• pdes-ui-states-and-edge-cases

  Build a table of screens against nine states plus an edge-case sweep per screen, marking every cell designed, missing or not needed with the reason, and order the gaps by what would block the build first. Use for "run pdes-ui-states-and-edge-cases", "UI states", "edge cases", "empty state check", "w

• pdes-usability-findings

  Turns your usability session notes into findings with per task results counted as n of N against the criteria set before testing, what people did beside what they said, an observation sheet by participant id, issues with a proposed 0 to 4 severity and clips to pull. Use for "run pdes-usability-findi

• pdes-usability-test-plan

  Writes a moderated Usability Test Plan with test goals tied to design questions, task scenarios that leave the path unstated, success criteria set before testing, a moderator script with a think-aloud ask and neutral prompts, and an observer note grid with sample and pilot notes. Use for "run pdes-u

• pdes-user-flow

  Write one task as a user flow with entry points, numbered steps paired with system responses, lettered decision branches, error and recovery paths, exits and the assumption behind every branch, ready to draw as a wireflow. Use for "run pdes-user-flow", "user flow", "map the flow for this feature", "

• pdes-user-journey-map

  Builds a User Journey Map for one group and one scenario, with stages, actions, thoughts in participants' own words, feelings, touchpoints with owners and pain points, every cell tagged to its evidence and gaps marked "not researched". Use for "run pdes-user-journey-map", "user journey map", "map th

• pdes-ux-debt-register

  Builds a UX Debt Register for your product area with one row per issue written as user impact, a value against effort table, the short list to propose for the next planning round and the issues knowingly left. Use for "run pdes-ux-debt-register", "UX debt", "design debt backlog", "prioritise UX fixe

• pdes-ux-writing

  Write every string for one flow in a single copy deck, with labels, buttons, helper text, errors that say what happened and what to do next, empty states, length limits, a glossary check and the approvals still needed. Use for "run pdes-ux-writing", "UX writing", "write the microcopy", "copy deck fo

Similar plugins