Ideas from live markets
We look for demand in Google and paying analogues. An empty niche with no traffic is a weak start for vibe coding.
PeelBrief
Specs for vibe coding: Cursor, Claude Code, Codex + demand check
Describe an idea, validate demand in Google, pick an MVP feature list — get a product brief and tech spec for Cursor, Claude Code, and Codex. 3 free specs.
PRD & tech spec templateDemand in Google3 free specs
Real value in the idea first — speed in the code second
AI removed the engineering queue. What’s left is a niche with demand — plus a PRD template and tech spec an agent can ship.
One feature, not a clone
Break a suite into parts. Take a high-demand feature and ship it as a standalone — a tighter MVP feature list.
Value = time saved
Users don’t care how hard it was to build. They care how many hours you give back.
Product brief for coding agents
MVP, stack, and acceptance criteria — a Cursor prompt / Claude Code prompt / Codex-ready tech spec.
Under the hood
How an idea is scored against the market
Not “the model said OK”. Keywords and intent, SERP and Trends, then peel one feature and ship the software requirements document.
- 1
Keywords & intent
Semantic core: tech spec, PRD template, product brief, vibe coding — each with traffic and competition.
- 2
SERP · Yandex / Google
Who ranks: suite vs dedicated tool, density of narrow clones around one feature.
- 3
Google Trends
Interest over time and related queries — heat and rising niche phrasings.
- 4
LLM · write the PRD
Peel the suite → MVP feature list → Cursor / Claude Code prompt as a tech spec.
Signal tools
Yandex / Google SERP
Organic: title, snippet, suite vs dedicated
Google Trends
Interest over time + rising / top related
Keyword density
Strong queries around the feature — not an empty niche
Keyword competition
High/medium/low dedicated around the peel
Public signals
Wikipedia / Reddit / HN
Sample score board
78/100
Traffic82
Competition68
Trend74
Niche (peel)79
Formula weights
Niche score
- Traffic+45%
main boost to viability
- Suite dominance+30%
room to peel a feature
- Trend+15%
interest / rising
- Head-to-head-25%
penalty for crowded dedicated clones
Overall score
- Niche score55%
- Traffic35%
- Trend10%
Catalog
Free PRD examples and ideas land in a public catalog
On Free, every idea and tech spec is published with market metrics, evaluation criteria, and a full product brief you can reuse as a template.
Free → publish
Studio
Idea / spec
Research
Metrics + LLM
Public
/catalog card
How to write a PRD for vibe coding
Same flow as the studio: demand and competitors first, then a product brief and tech spec when the niche is clear.
01
Prove the theme already earns
Don’t flee competition. Find products with Google traffic — proof people already pay for the pain.
02
Peel one feature
Take a suite, pick a narrow feature with its own query and weak dedicated competition — your MVP feature list.
03
Simplify for time saved
Cut the rest. Faster value means people pay more willingly — tighter than a full software requirements document.
04
Ship a Cursor / Claude Code prompt
PRD template: MVP, stack, acceptance criteria — so Cursor, Claude Code, or Codex build exactly that product.
Don’t judge by yourself: vibe coding is rare
What you ship in an evening, a doctor or accountant won’t build alone. They need a simple tool — and a clear product brief, not chat noise.
- Validate demand in Google first
- One feature under its own search intent
- Simple MVP feature list = faster time saved
- PRD / tech spec for Cursor, Claude Code, Codex
Progress
From demand to PRD
- ✓Find a live market and traffic
- ✓Peel one feature from a suite
- Simplify MVP for time saved
- Export the tech spec to an agent
Write a PRD where demand already exists
Check demand via SERP and Trends, peel a narrow feature, get a tech spec template for Cursor, Claude Code, or Codex. 3 free specs — in the catalog with scores.