这是一项Claude Code技能，能在你投入时间前检查你的想法是否已经被构建完成。它会搜索全景，汇聚现有内容，将你的角度与现有技术进行基准对比，并直接给出结论：构建、分叉、贡献、利用现有资源，或者调查别人放弃的原因。

安装

克劳德·科德

直接克隆到 Claude Code 的技能目录：

或者如果你已经克隆了这个仓库，可以手动复制技能文件：

开放代码

直接克隆到 OpenCode 的技能目录：

或者如果你已经克隆了这个仓库，可以手动复制技能文件：

注意：OpenCode 还会扫描 ~/.claude/skills/ 以保证兼容性，因此单一克隆到 ~/.claude/skills/who-built-this-before-me/ 对两种工具都有效。

用途

克劳德·科德

开放代码

或者直接在任一工具中描述想法——技能触发词汇如“我想建造…”、“我在考虑制作…”、“我应该建造X…”或“已经有没有…”这样的短语：

你能得到什么

包含以下部分的单屏报告：

• 观点，重申 ——你的推介被简化为一句话，这样你就能确认搜索针对的是正确的目标。

who-built-this-before-me

A skill for Claude Code that checks whether your idea has already been built before you invest time in it. It searches the landscape, clusters what exists, benchmarks your angle against prior art, and delivers a direct verdict: build, fork, contribute, use what’s out there, or investigate why someone else gave up.

Installation

Claude Code

Clone directly into Claude Code’s skills directory:

mkdir -p ~/.claude/skills
git clone https://github.com/iagochavarry/who-built-this-before-me.git ~/.claude/skills/who-built-this-before-me

Or copy the skill file manually if you already have this repo cloned:

mkdir -p ~/.claude/skills/who-built-this-before-me
cp SKILL.md ~/.claude/skills/who-built-this-before-me/

OpenCode

Clone directly into OpenCode’s skills directory:

mkdir -p ~/.config/opencode/skills
git clone https://github.com/iagochavarry/who-built-this-before-me.git ~/.config/opencode/skills/who-built-this-before-me

Or copy the skill file manually if you already have this repo cloned:

mkdir -p ~/.config/opencode/skills/who-built-this-before-me
cp SKILL.md ~/.config/opencode/skills/who-built-this-before-me/

Note: OpenCode also scans ~/.claude/skills/ for compatibility, so a single clone into ~/.claude/skills/who-built-this-before-me/ works for both tools.

Usage

Claude Code

/who-built-this-before-me

I'm thinking of building [your idea here]

OpenCode

/who-built-this-before-me

I'm thinking of building [your idea here]

Or just describe the idea directly in either tool — the skill triggers on phrases like “I want to build…”, “I’m thinking of making…”, “should I build X…”, or “is there already a…”:

I want to build a CLI that auto-generates database migrations from OpenAPI schemas. Has anyone done this?

What you get back

A one-screen report with these sections:

• The idea, restated — your pitch stripped to one sentence, so you can confirm the search is targeting the right thing.
• The landscape — a table of direct matches, adjacent solutions, partial solutions, and abandoned projects (max 3 per bucket).
• Standard patterns — what shows up repeatedly across the matches: architecture, libraries, pricing, naming conventions. The default playbook you’d be competing with or building on.
• Differentiator analysis — an honest paragraph on whether your angle is actually different, or whether the novelty is manufactured.
• Verdict — one of: Build it, Fork X, Contribute to Y, Use Z, or Investigate first, plus the concrete next step.

Sharpening the input

The more specific your pitch, the sharper the search. Compare:

Vague — the skill will ask one clarifying question before searching:

/who-built-this-before-me

I want to build a dev tool.

Specific — the skill goes straight to searching:

/who-built-this-before-me