Loading...
Loading...
Found 6 Skills
Propose concrete, high-leverage product/UX improvements to increase a software project's appeal and retention. Use when asked to generate product improvement proposals, UX ideas, onboarding/doc improvements, packaging/pricing positioning suggestions grounded in repo evidence, and prioritized MVP plans (ideation only; no implementation).
Deep-dive Amazon review analysis. Extract sentiment patterns, recurring complaints, feature requests, and competitive insights from product reviews. Turn customer feedback into product improvement and marketing opportunities.
Use this skill to analyze product reviews, find common issues, and prioritize improvements. Triggers: "analyze reviews", "review analysis", "customer feedback", "what are people saying", "product reviews", "review sentiment", "find complaints", "customer complaints", "improvement recommendations", "voice of customer", "VOC analysis", "feedback analysis" Outputs: Prioritized issues, sentiment analysis, improvement recommendations.
Mine Amazon reviews for product, listing, and marketing intelligence. Extracts recurring complaints, feature requests, the words customers use, and the reasons they chose the product, then turns them into listing fixes, product improvements, and copy. Use when a user pastes reviews and asks to analyze them, find complaint patterns, mine reviews, understand customer sentiment, pull insights from competitor reviews, or turn reviews into improvements. Trigger phrases: "analyze reviews", "review analysis", "complaint patterns", "what customers say", "mine reviews", "competitor reviews". Works with zero tools. the user pastes the reviews.
PRD Expert Advisor Mode. Three well-known PM/CEO act as advisors, proactively review PRD, identify weak points and provide improvement solutions that can be directly written into the document. Users decide whether to adopt via accept/reject. Trigger methods: /li-prd-review, "Enhance PRD", "Expert Advisor", "Help me review this PRD", "Let experts review the PRD", "What are the loopholes in the PRD", "Help me optimize the PRD", "What other issues are there with the PRD". Even if users don't mention "PRD", this skill should be triggered as long as they want expert roles to review a product document and provide improvement solutions. DO NOT trigger for: PRD generation tasks (use li-prd), content script generation, topic analysis and other content creation tasks.
Guided journey from a shipped app that works but feels rough to a product that fits the job, flows without friction, reads clearly, and persuades honestly. Orchestrates nine skills phase by phase - jobs-to-be-done, ux-heuristics, design-everyday-things, refactoring-ui, microinteractions, made-to-stick, influence-psychology, high-perf-browser, steve-jobs-design-review - asking the user questions at every decision point and recording results in the project docs/ folder (CUSTOMER.md, DESIGN.md, POSITIONING.md, IMPROVE-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to fix a clunky product, cut UX friction, sharpen in-app copy and prompts, or says 'the app works but feels rough'. Do not use for code, tests, or production hardening - use improve-code-quality (fresh prototype) or remove-technical-debt (aged codebase); no app yet, create-app; needs growth loops, grow-app; marketing-site friction, improve-website. For one framework in isolation, invoke that skill directly.