151 skills · sorted by relevance
Structure problem solving around clear goals, competing explanations, experiments, and measurable results. Use the cycle to diagnose bugs, validate features, compare prompts, or evaluate an early product, then choose the next step based on evidence.
Plan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phase
The English summary is being prepared. Showing the original description.
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
The English summary is being prepared. Showing the original description.
Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", "test assumptions", "innovation accounting", "build-measure-learn", "minimum viable experiment", "should we pivot", "test a business idea cheaply", or "build the smallest version first". Also trigger when deciding what to include in a first version, measuring startup progress, or evaluating whether to change direction on a product bet. Covers innovation accounting and actionable metrics. For 5-day prototype testing, see design-sprint. For customer motivation analysis, see jobs-to-be-done.
The English summary is being prepared. Showing the original description.
Build the actual product — from landing page to deployed MVP with payment integration, QA testing, and post-deploy canary monitoring. Handles code generation, deployment, database setup, authentication, Stripe/payment integration, systematic QA protocol, and production health scoring. Use when the user needs to build something, deploy a product, set up payments, create a landing page, or says 'build this', 'deploy', 'create MVP', 'set up payments', or 'ship it'.
The English summary is being prepared. Showing the original description.
Discover and validate product ideas, analyze markets, scope MVPs, and optimize app store presence for iOS/macOS apps. Use when user asks to discover, validate, assess, scope, or analyze product ideas, market opportunities, or when they mention "product agent", "app idea validation", "should I build this", "MVP", "market analysis", or "ASO".
The English summary is being prepared. Showing the original description.
Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty. Use when iterating toward product/market fit, designing MVPs, deciding whether to pivot or persevere, setting up actionable metrics, or accelerating the Build-Measure-Learn loop. Triggers include 'how do we test this idea fast', 'what should our MVP look like', 'our metrics look good but we're not growing', 'should we pivot', 'we're building features no one uses', 'how do we measure validated learning', 'vanity metrics vs real metrics', 'how to do innovation accounting'. NOT for companies with proven product/market fit scaling a known playbook (use Crossing the Chasm), not for determining Market Type (use Four Steps), not for sales methodology (use SPIN Selling), not for pricing strategy (use Monetizing Innovation).
The English summary is being prepared. Showing the original description.
Turn a complete beginner's app idea into a buildable plan, then keep them oriented while they build. Use it whenever someone who has never coded wants to build or "vibe code" an app, has an idea but no idea where to start, or wants it turned into a plan, MVP scope, tech stack, user flows, or blueprint. It has three on-ramps: the full journey, a validate-only pass ("is my idea worth building", "reality-check this idea"), and a plan-only path for someone arriving with validation done ("I already validated my idea", "I have the research, just plan my MVP", "skip the research"). ALSO use it when a non-coder needs build-time basics: what Git and GitHub are, making an account, "commit and push," local vs. staging vs. production, putting an app online (deploy/ship), or keeping API keys safe. AND use it in Checkup Mode when someone who built with AI says it became a mess, the AI keeps breaking things or going in circles, they're scared to touch their code, or they ask "is my code organized" or "can you clean it up." Built for people who don't know what an API, database, or GitHub is, so reach for it when they never say "plan" or "architecture." Not for an experienced dev debugging, refactoring, or setting up CI/CD.
The English summary is being prepared. Showing the original description.
Construct statistical arguments for MVP/awards. Narrative framing, comparison to past winners, advanced metrics, counter-arguments.
The English summary is being prepared. Showing the original description.
Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model. Triggers on requests to define features, prioritize capabilities, scope MVP, map features to pricing tiers, identify parity vs. delta features, or when user asks "what features do we build?", "what's in MVP?", "which features matter?", "feature priority", "parity features", "what's our delta?". Consumes KPI- (Outcome Definition), BR- (Pricing Model, Moat), and CFD- (Market Moat Analysis) from v0.3. Outputs FEA- entries with strategic traceability and BR-FEA- governance rules. Feeds v0.4 User Journeys.
The English summary is being prepared. Showing the original description.
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when "micro saas, indie hacker, small saas, side project, saas mvp, ship fast, " mentioned.
The English summary is being prepared. Showing the original description.
A strict code reviewer, pair programmer, debugger, and mentor for Python, Bash, Google Apps Script, JavaScript, and Swift/Apple platforms. Use when writing, reviewing, debugging, planning, or securing code, or for senior-level rigor, a security review, or mentoring. Mode triggers — REVIEW: (critique + refactor), EXPLAIN: (teach), MVP:/PROTOTYPE: (lean-but-safe), DEBUG: (root-cause), AUDIT: (report-first); default is pair-programming. Drives a spec→plan→TDD→verify loop with a deterministic-first, verify-before-asserting (anti-hallucination) discipline. Enforces a security floor (secrets, injection, input validation, isolation, least privilege, authn) and a backup/continuity floor on a phase-aware rigor ladder (Prototype→MVP→Production) — cheap ≠ insecure. Covers testing & fuzzing, SAST/secret-scan/type-check/supply-chain gates, multi-tenant data protection, resilience & DR, scalability, CI/CD, cloud/containers/DBs, and accessible UI — deep references read on demand.
The English summary is being prepared. Showing the original description.
Master SaaS orchestrator for greenfield MVP launch (0 to 1) and legacy application SaaS transformation (1 to N) / Master orkestrator SaaS untuk peluncuran MVP dari nol (0 ke 1) dan transformasi aplikasi menjadi SaaS (1 ke N).
The English summary is being prepared. Showing the original description.
Plan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phase
The English summary is being prepared. Showing the original description.
A step-by-step playbook for early-stage startups going from pre-seed to their first 1000 users. Covers MVP validation, initial traction channels, and founder-led growth tactics. By @WeiYipei — follow on X for more startup growth insights.
The English summary is being prepared. Showing the original description.
划分 MVP 范围、明确非目标范围时使用。适用于第一版功能定义、范围控制、需求收敛。优先使用 MoSCoW 四级分类 + 非目标范围明示。
The English summary is being prepared. Showing the original description.
用生物演化逻辑（遗传变异+自然选择）应对不确定性，通过MVP启动→市场反馈筛选→变异创新→积累优势的循环来迭代产品或团队。适用于目标不明确、环境变化快、无法提前规划的场景。不适用于目标明确、路径清晰的确定性项目（用计划更高效）。计划与演化是阴阳互补：计划=阳（效率），演化=阴（应对不确定）。关键触发信号："不确定用户要什么"、"市场变化太快"、"计划赶不上变化"、"先跑起来再说"。
The English summary is being prepared. Showing the original description.
Use when starting a new project. Genesis finds real production failures from similar GitHub repos, then builds a working MVP immediately - not just documents. Two modes: fast-mvp (5 min research cap, builds right after) and deep-research (full analysis). Success = user can run the project. Triggers on: "genesis init [vision]", "I want to build X", "scaffold", "new project", "set up project", "start building", "create a tool", "make a CLI", "bootstrap", "בנה פרויקט", "צור פרויקט", "התחל פרויקט".
The English summary is being prepared. Showing the original description.
MVP 开发专家团运维工程师（卜宕机）。负责自动化部署（CloudBase/Docker）、环境验证、健康检查、回滚策略、交付包组装。确保每次部署可验证、每次交付可追溯。 触发词：由 mvp-dev-team-lead 主理人调度执行 Phase 4 部署任务时激活。不直接面向用户。
The English summary is being prepared. Showing the original description.
MVP 开发专家团 UI/UX 设计师（颜好看）。擅长 67 种 UI 风格、161 色调色板、57 种字体配对。输出完整设计系统 Token 和页面设计提示词。 触发词：由 mvp-dev-team-lead 主理人调度执行 Phase 1 调研或 Phase 2 设计细化任务时激活。不直接面向用户。
The English summary is being prepared. Showing the original description.
MVP 开发专家团产品经理（许清楚）。擅长竞品研究、用户画像、PRD 撰写、RICE 评分。 触发词：由 mvp-dev-team-lead 主理人调度执行 Phase 1 调研任务时激活。不直接面向用户。
The English summary is being prepared. Showing the original description.
MVP 开发专家团前端工程师（贾思敏）。负责 Token 化 UI 实现、Lucide 图标、微交互、11 项视觉自查。以 "pro max" 级别精益求精的态度交付前端代码。 触发词：由 mvp-dev-team-lead 主理人调度执行 Phase 3 开发任务时激活。不直接面向用户。
The English summary is being prepared. Showing the original description.
MVP 开发专家团架构师（高见远）。擅长技术选型对比矩阵、系统架构设计、RESTful API 设计、DB Schema 设计、技术可行性验证。 触发词：由 mvp-dev-team-lead 主理人调度执行 Phase 1 调研或 Phase 2 设计细化任务时激活。不直接面向用户。
The English summary is being prepared. Showing the original description.
MVP 开发专家团测试工程师（严过关）。负责测试策略制定、功能验证、P0 缺陷归零门禁、端到端测试。交付前确保所有验收标准通过。 触发词：由 mvp-dev-team-lead 主理人调度执行 Phase 4 测试任务时激活。不直接面向用户。
The English summary is being prepared. Showing the original description.