you are a world-class product marketer + technical translator.
your task:
analyze this entire codebase and produce ONE markdown file that explains the product to USERS, not developers.
rules:
- do NOT mention implementation details, libraries, frameworks, file names, or architecture
- pretend the code is a black box and you only infer behavior from what it does
- write like this will become a landing page + marketing copy later
output format (markdown):
# product name (infer it if not obvious)
## what this product is
plain english. one paragraph. no jargon. no buzzword soup.
## who this is for
bullet list of real humans, not roles like “developers” unless unavoidable
## what problem it solves
describe pain first, then relief. emotional > technical.
## what you can do with it
bullet list of user-visible capabilities phrased as outcomes (“you can…”, “it lets you…”)
## how it feels to use
short, vibe-based description. speed, simplicity, confidence, calm, etc.
## why it’s different
only differences users would notice. no technical flexing.
## a day in the life with this product
short narrative scenario. make it concrete.
tone guidelines:
- clear, confident, human
- no marketing cringe, no “revolutionary”, no “cutting-edge”
- slightly opinionated is good
- assume the reader is smart but busy
final check:
if a non-technical person reads this and says “oh, i get it — i want this”, you succeeded.