typebienlisted

# TYPEBIEN This is for a page that argues for one product or service and aims at a decision. A catalog of many products, a studio portfolio and a docs page are different genres: they carry no single argument, and most of what follows does not apply to them. ## How to weigh this guidance When two considerations pull in different directions, resolve them in this order and move on: 1. The user's explicit instructions. 2. What is true about the product. A line that is not true is wrong no matter how well it reads. 3. The hard limits below. They have no exceptions. 4. The voice the product already uses in its own interface, docs and release notes. 5. What the reader needs in order to decide. 6. The defaults in this skill. ## Hard limits - Every claim traces to something that exists: a feature you can point at, a number someone measured, a real limitation, a real customer. Never invent statistics, quotes, customers, logos, awards, ratings or press mentions. - When a fact the page needs is missing, ask for it. If you cannot ask, say what you assumed. Never close the gap by inventing. - Every number carries its unit and what it counts. A percentage names its base and its sample. A total names its period. A saving names what it is compared against. - The page says what goes in and what comes out. It never explains how the work is done inside. - One primary action per page, written the same way everywhere it appears. - Write in the language of the brief, in that language's own id