Use when creating Product Requirements Documents. Enforces clarification-first workflow, junior-dev-friendly language, and standard PRD structure. Triggers: 'create PRD', 'write requirements', 'product requirements', feature requests needing documentation.
Conduct user research and validation. Use when discovering user needs, validating assumptions, creating personas, or understanding pain points. Covers interviews, surveys, analysis, and synthesis.
Collaboratively build and refine paper screening rubrics through brainstorming, test-driven development, and iterative feedback
Expert in brand identity, logo design, and visual brand systems
Automates collecting and analyzing job market data and trends. Use for cyclical monitoring of sectors, salaries, and skills demand.
Analyzes a job offer for fit with the Candidate's profile and recommends an application strategy. Use before considering a new job offer.
Expert in product planning, requirements gathering, and strategic thinking
Universal VC investor analysis and outreach agent. Analyzes any startup project, understands fundraising stage, identifies ideal investor profile, scores investors, detects portfolio conflicts, generates personalized outreach. Starts with discovery questions to understand the project. Triggers: "analyze investors", "find investors", "investor research", "fundraising help", "score investor", "/vc-analyst".
Expert in agile product management, MVP scoping, backlog prioritization, and iterative planning
PRD structure and patterns for SpecFlux. Use when creating or refining product requirement documents. PRDs should be concise for humans but detailed enough for AI agents to implement.
This skill should be used when the user asks to "create epics", "create an epic", "new epic", "break down project into epics", "decompose project", or mentions creating epics. Supports both standalone epic creation and breaking down a project into major epics by analyzing specifications and gathering requirements.
This skill should be used when the user asks to "create features", "create a feature", "new feature", "break down epic into features", "decompose epic", or mentions creating features. Supports both standalone feature creation and breaking down an epic into specific features by analyzing specifications and gathering requirements.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
UI/UX design workflow guidelines. Activate when working with design systems, accessibility (WCAG), user interface patterns, or design tokens.
Complete PRD (Product Requirements Document) creation workflow that guides users from initial idea to implementation-ready specification using the integrated toolset in this repository. Handles everything from brainstorming and market analysis to technical requirements and team coordination.
Load relevant design documents and project context before working on any task. Use when user asks about features, requests implementation, discusses functionality, analyzes architecture, updates documentation, or mentions specific components like OAuth, authentication, Logto, sync, Happy Server, messaging, chat, terminal, command, zen mode, boxes, workspace. Ensures all work is grounded in documented design decisions. Prevents assumptions and misaligned solutions by loading context first.
依据竖屏短剧评估标准，从核心爽点、故事类型等维度评估打分。适用于评估故事改编为竖屏短剧的潜力、分析市场竞争力
COO 产品运营数据分析技能，使用 Playwright MCP 从 App Store Connect、小程序后台、小红书创作者中心等平台获取运营数据
Design principles and review methodology for UI/UX work. Use when building new interfaces, reviewing visual changes, or validating design quality. Contains best practices for visual polish, accessibility (WCAG 2.1 AA), responsive design, component standards, and interaction patterns. Works both as a development guide and a review checklist. Produces structured reports with prioritized findings.
