Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Example task
Review a proposed checkout redesign for a SaaS billing page. The user has provided a screenshot description, goal, and constraints, but no analytics, research notes, or design-system documentation.
Without the bundle
The checkout should be cleaner and more modern. Make the primary button more prominent, reduce the number of fields, and add trust badges. Use a progress indicator and make the page mobile-friendly.
Using the bundle
Source Note Reviewed: user-provided screenshot description, stated checkout goal, and stated constraints. Missing: analytics funnel data, support tickets, research notes, design-system rules, accessibility target, and implementation constraints. Direct Recommendation Prioritize reducing decision ambiguity before visual polish. The first design pass should clarify plan selection, billing-cycle change impact, payment error recovery, and confirmation state. Findings - High impact: the flow needs explicit empty, loading, error, and payment-declined states before handoff.
Why this is better: The baseline gives generic UI advice and invents a likely solution pattern. The bundle-assisted response is stronger because it names source gaps, prioritizes user-impact risks, covers states, avoids unsupported accessibility claims, and creates handoff questions.
Inspect this example in the repositoryRole guide
Product Designer
Defines the scope and expected behavior of a Product Designer agent.
Read the fileWorkflow
Design Brief to Concept
Convert product context into a design brief and concept direction.
Read the fileWorkflow
Design Review
Review flows, screens, wireframes, or prototypes for product design quality.
Read the fileFramework
Accessibility-Aware Design
Source-aware accessibility framing for product design critique.
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Product Designer work, plus teams reviewing its decisions and outputs
- Teams working in software, saas, digital-products
When to use it
- A Product Designer task needs a structured plan, evidence checklist, or review-ready output.
- A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.
What you need to provide
- The task objective, intended audience, working context, constraints, source material, and decision owner.
- Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.
Tasks and expected outputs
Questions it helps answer
- Turn product context into design briefs and concept directions.
- Review user flows, wireframes, prototypes, and UI states without inventing missing product evidence.
- Prepare accessibility-aware design review notes and engineering handoff questions.
What it helps produce
- design brief
- design review note
- prototype test plan
- handoff checklist
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Product Designer work by producing design brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with url, then confirm that the reference is current and applicable. Inspect Product Designer before drafting.
Context path: bundles/roles/product-designer
What the bundle includes
Tools
- Figma
- FigJam
- Miro
- Maze
- UserTesting
- Dovetail
- Jira
- Linear
- Notion
- Confluence
- Storybook
Frameworks
- Double Diamond
- design thinking
- Jobs-to-be-Done
- heuristic evaluation
- journey mapping
- accessibility POUR
Commands
/draft-design-brief
/review-ui-flow
Evaluations
- product-design-quality-check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.
Known limitations
- Product design scope varies by organization; verify local role ownership, design process, and decision rights.
- Does not replace user research, legal accessibility review, brand approval, product leadership, or engineering feasibility review.
- Does not include tool-specific API automation or workspace-specific design-system details.
Safety notes
- Confirm before modifying live design files, tickets, research repositories, product specs, roadmap artifacts, or customer-facing communications.
- Treat customer research, unreleased product strategy, design files, analytics, and roadmap plans as confidential unless the user confirms they are safe to use.