Skills for product
Deciding what to build: specs, roadmaps, user research synthesis, prioritization, product analytics
62 skills, newest first. Filter and sort all skills
Agent Architecture
GitHub
Design AI agent architectures through requirements discovery, or audit and diagnose architectural flaws in existing agents.
Conversational Ux
Owl-Listener
Design voice and conversational interfaces — dialog flows, error recovery, and persona.
User Persona
Owl-Listener
Build research-grounded personas with goals, frustrations, and behavioural patterns.
Search Ux
Owl-Listener
Design search — query input, zero results, refinement, and result presentation.
North Star Vision
Owl-Listener
Articulate a long-horizon product vision that aligns teams and anchors strategy.
Paywalls
coreyhaines31
create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.
Prd
GitHub
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features.
Shopify Review Triage
GitHub
someone wants public Shopify App Store reviews, low-star reviews, or merchant feedback triaged, prioritized, clustered, or turned into a product or support brief.
Breakdown Epic Arch
GitHub
Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.
Documentation Writer
GitHub
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
Diagnose
GitHub
Perform a systematic diagnostic scan of an AI workflow across 5 quality dimensions — prompt quality, context efficiency, tool health, architecture fitness, and safety — producing a scored report with prioritized remediation actions.
Breakdown Feature Prd
GitHub
Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.
Breakdown Epic Pm
GitHub
Prompt for creating an Epic Product Requirements Document (PRD) for a new epic.
Docs Sync Audit
GitHub
Run a read-only documentation drift audit for a feature, PR, branch, release, API, configuration change, workflow, CLI, package, or repository area.
service-blueprint
Owl-Listener
Map service delivery across frontstage actions, backstage processes, and supporting systems. Use when staff and operations are part of the experience. For the customer-visible layer only, use `experience-map`.
design-brief
Owl-Listener
Write a project brief — problem space, constraints, audience, and success criteria. Use at kickoff for one specific project. For long-horizon aspiration use `north-star-vision`; for reusable decision rules use `design-principles`.
error-handling-ux
Owl-Listener
Design error prevention, detection, and recovery across a product — message content, placement, and escape routes. Use when errors span multiple flows. For validation inside a single form, use `form-design`.
design-sprint-plan
Owl-Listener
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`.
design-debt-audit
Owl-Listener
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).
Research Source Finder
kostja94
find information sources for content ideation, competitor monitoring, or industry tracking.
Competitor Research
kostja94
analyze competitors for SEO, content, backlinks, or positioning.
business-design
Owl-Listener
Read financials, map competitive landscapes, and argue design decisions in the language of value. Use when defending design to commercial stakeholders. For the live negotiation itself, use `design-negotiation` (designer-toolkit).
behavioural-analytics
Owl-Listener
Read funnels, retention curves, and event data as a designer — separating a design problem from a tracking artefact. Use when handed product data you did not design and asked why people drop off. For choosing what to measure, use `metrics-definition` (ux-strategy); for running a controlled test, use `a-b-test-design` (prototyping-testing).
translation
kostja94
When the user wants to translate content, create translation workflows, manage terminology, or optimize translation quality. Also use when the user mentions "translate," "translation," "localization copy," "glossary," "terminology," "style guide translation," "machine translation," "human translation," "TMS," or "multilingual content." For strategy, use localization-strategy.
Skills by team
- Skills for operations84
- Skills for finance76
- Skills for sales45
- Skills for marketing133
- Skills for people & HR19
- Skills for customer support9
- Skills for customer success15
- Skills for engineering136
- Skills for product62
- Skills for design70
- Skills for legal & compliance29
- Skills for data & analytics28
- Skills for leadership & exec39
- Skills for IT & security47
- Skills for research32
- Skills for entrepreneurship21