researchlisted

Run fast, source-grounded UX research on the highest-signal problems users are experiencing with a user-specified digital product. Use when the user asks to research user pain, UX friction, onboarding issues, docs/help problems, developer experience friction, support pain, product workflow issues, or current user complaints for a named product.
Oatelauser/ai-front-spec · ★ 0 · AI & Automation · score 64

Install: claude install-skill Oatelauser/ai-front-spec

# Research Run a fresh UX research scan for the product the user specifies. Focus on current, evidence-backed user problems. Prioritize logged-in product experience, self-serve flows, onboarding, docs/help, developer experience, support friction, and product workflows. ## Critical Overrides - Refer to the Plugin router [$index](../index/SKILL.md) before proceeding. - Follow [$critical-overrides](../../references/critical-overrides.md). ## User Context Before starting, load [$user-context](../user-context/SKILL.md) and run its preflight script when local shell access is available. Use saved product URLs, Figma files, screenshots, reference images, codebase paths, Storybook, tokens, design systems, brand assets, component refs, browser preferences, and share targets as grounding material when relevant. Do not inspect every saved reference. Inspect only what the current task needs. ## Contract - Restate the product, audience, time horizon, and research scope before scanning. - Use public sources by default. Use internal sources when the connectors are available and the user request allows it. - Cite sources wherever available. - Separate observed evidence from inference. - Do not overclaim from anecdotes. - Do not return a dump of complaints. Tell a clear product story. - Say clearly when source access is missing or weak. ## Workflow 1. Restate the research scope. 2. Search public sources: - Reddit - X/Twitter - Hacker News - Stack Overflow - GitHub issues/discussi