An X-but-Y product description anchors an unfamiliar product to a familiar reference product, then names one concrete difference. The constraint turns repository analysis away from tech-stack summaries and toward product intent. section 5.3
Use the technique as a reverse-engineering prompt:
- Ask for one sentence: “It’s [a familiar product], but [one concrete difference].” section 5.3
- Reject vague claims, feature lists, and descriptions such as “a Next.js monorepo using Prisma and Postgres.” section 5.3
- Apply the reproduce-it test: a stranger should be able to picture and rebuild the core product from the sentence. section 5.3
- Check the repository’s schemas, routes, and dependencies against the claimed business difference. section 5.3
From vague pitch to concrete product
“We transform the relationship between individuals and information” is unusable. “Calendly, but open-source and embeddable” immediately suggests a recognizable scheduling surface and a specific differentiator.
