Grounded Product Copy

Copy that overstates the product is a recurring, expensive correction ("we dont have a mobile app cmon look at what we actually do", "we dont have any testimonials though", "we dont measure cost we give insights based on current usage"). Only claim what is real.

Before writing any user-facing copy

1. Find the ground truth. Read the project's PRODUCT.md (or equivalent) if it exists. If it does not, read the actual site, the README, and the code to learn what the product genuinely does. Do not write from an assumption of what a product in this space usually does.
2. List what you may not claim. No mobile app if there is no mobile app. No testimonials, case studies, logos, or metrics you cannot point to. No feature that is not shipped. No market or capability the team does not actually serve.
3. Describe the real value, precisely. If the product gives usage insights, say that, do not say it "cuts costs". If it covers commercial plans too, do not narrow it to one. Match the copy to the actual scope, no wider and no narrower.

Create a PRODUCT.md when one is missing

If a project has none, offer to create a short PRODUCT.md that states, in plain words: