Skill UI

This skill guides users through structured workshops to define comprehensive product features from scratch. It adopts dual perspectives (Product Manager and Developer) to gather detailed requirements, user stories, and non-functional needs. The output includes EARS-formatted functional requirements, testable acceptance criteria (Given/When/Then), and detailed implementation checklists, ensuring the feature is complete and ready for development.

Guides teams through writing Mike Cohn‑style user stories with Gherkin acceptance criteria so product needs become actionable, testable development work with shared understanding.

This framework provides a systematic methodology for engineering virality, moving beyond luck to design shareable products, ideas, and content. It utilizes the STEPPS model (Social Currency, Triggers, Emotion, Public, Practical Value, Stories) to systematically increase the likelihood of organic sharing and word-of-mouth marketing. Use it when optimizing for shareability or predicting user adoption patterns.

A comprehensive framework designed to help users craft messages, taglines, and value propositions that are not only understood but also remembered and actionable. It utilizes the SUCCESs model (Simple, Unexpected, Concrete, Credible, Emotional, Stories) to elevate ordinary communication into high-impact, sticky content. Ideal for copywriters, marketers, and product managers.

This technique allows users to locate game developers or projects indirectly by searching for highly distinctive biographical details. Instead of relying on game databases, it leverages unique phrases, historical events, or personal lifestyle details found in interviews, blogs, or conference talks. It is invaluable when the developer's identity is obscured, requiring deep research using exact-match queries on obscure information.

This skill synthesizes a comprehensive Product Requirements Document (PRD) from the current conversation context and understanding of the codebase. It guides the user through structuring the problem statement, defining detailed user stories, outlining implementation decisions, and suggesting test strategies. The final PRD is formatted and submitted directly as a GitHub issue, ensuring a structured handover from discussion to development specification.

This skill generates a comprehensive, one-page product specification document (PRD) or feature brief. It structures critical information—including problem statements, success metrics, user stories, and scope—into a professional, actionable markdown/HTML format. Ideal for formalizing product ideas and kickstarting development planning when presented with terms like 'PRD' or 'spec'.

Conducts Search Experience Optimization (SXO) by analyzing Google SERPs backwards. It detects page-type mismatches, derives user stories from search intent signals, and scores content alignment across multiple personas. Ideal for identifying why well-optimized pages fail to rank by understanding Google's true rewards for a given keyword.