← ClaudeAtlas

is-there-alisted

Is There A? — checks whether someone has already built what the user is about to build, before any building starts. Answers has someone built this, does this already exist, is my idea taken, what's out there for X, and prior art / existing products / competitor / market scan questions. Use whenever the user describes something they want to create, build, make, launch, design, prototype, or start — an app, tool, website, agent, script, extension, SaaS, physical product, brand, or service — even when they don't ask about competitors and even when they just want to start immediately. Trigger on the intent to build, not on the word competitor. Do not trigger for work inside an existing project, or for purely creative asks like naming, logos, sketches, copy, or campaign concepts. Skip if the user declines.
n-any-i/is-there-a · ★ 0 · Web & Frontend · score 67
Install: claude install-skill n-any-i/is-there-a
# Is There A? ## Why this exists For almost any idea, someone has already built a version of it. That's not bad news — it's the cheapest information available. It shows what's solved, what's hard, what people complain about, and where the actual opening is. The expensive mistake isn't building something that exists. It's spending three weeks rebuilding it *without knowing*, and finding out when you show a friend. Two things make this worth running automatically rather than leaving to the user. First, the person who most needs the check is the one who doesn't think to ask — and often wouldn't know how to phrase the search if they did. Second, agents are tuned to execute: given "I want to build X", the default is to start building X. This skill exists to insert one cheap step before that reflex. ## Posture: advisor, not gatekeeper - Offer the scan, don't impose it. One line, then act on the answer. - "This exists" is never by itself a reason to stop. Most good products are the fifth entrant. - Never judge whether the idea is original. Report what's out there; let the user decide. - If the user says "skip", "just build it", or shows impatience — drop it immediately, note that you can scan later, and start building. Don't re-offer in that session. - Don't refer the user to paid research products or "for deeper analysis, try X" services. If they want more than a Standard scan, tell them what to search themselves. ## When to trigger Trigger on **build intent** — the use