菜单
Research existing products and competitors for a given product idea. Use when starting a new project, cloning an existing product, or analyzing competitive landscape. Returns feature analysis, gaps, and differentiation opportunities.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | market-research |
| description | Research existing products and competitors for a given product idea. Use when starting a new project, cloning an existing product, or analyzing competitive landscape. Returns feature analysis, gaps, and differentiation opportunities. |
Research existing products/competitors to inform product decisions.
For each competitor/reference product:
[MARKET RESEARCH COMPLETE]
Product space: [description]
Competitors analyzed:
1. [Product A]
- Core features: ...
- Strengths: ...
- Weaknesses: ...
2. [Product B]
- Core features: ...
- Strengths: ...
- Weaknesses: ...
Gap analysis:
- [Gap 1]: Description
- [Gap 2]: Description
Differentiation opportunities:
- [Opportunity 1]: How to stand out
- [Opportunity 2]: Underserved niche
Recommended baseline: [Product X] because [rationale]
Debug a real iPhone's Safari from a Linux (or Windows) workstation — no Mac required. Wraps libimobiledevice + ios-webkit-debug-proxy + a CDP driver into one workflow. Use when: a page works in desktop browsers but breaks on iPhone Safari, you need iPhone Safari Web Inspector but don't have a Mac, you need to evaluate JS or stream console logs from an iPhone tab, or you need to inspect crossOriginIsolated / SharedArrayBuffer / COOP / COEP / service-worker / bfcache behavior on a real iPhone. Triggers: "debug ios safari", "debug iphone safari", "iphone safari devtools", "iphone web inspector without mac", "inspect iphone safari", "ios remote debug", "ios webkit debug proxy", "iwdp", "crossOriginIsolated on ios", "SAB on iphone", "service worker not intercepting on safari".
Clone a local or remote git repo into a new folder with a short random hash suffix (e.g., -a1b2c3) and immediately create a new branch from a base branch. Use when a user wants a separate workspace to avoid conflicts, especially for parallel feature work or multiple local clones.
Break large tasks (>100 lines) into atomic, verifiable sub-tasks. Use when a task scope is unclear, touches multiple files/modules, or exceeds comfortable single-commit size. Returns structured breakdown without implementing code.
Author's cleanup checklist before committing or submitting a PR. Use before any commit or PR to ensure code is clean, focused, and ready for review. Checks for debug code, secrets, redundant changes, and scope creep.
9-section product specification template for defining software projects. Use when drafting a new spec.md, converting an idea into a structured specification, or reviewing spec completeness. Ensures consistent, comprehensive project definitions.