vellum-user-facing-copy

Identify all text users may read, then check terminology, privacy, and clarity against a fixed style guide. Verify the copy does not imply unavailable or flagged behavior, and add tests or snapshots when the copy is part of a stable interface.

Use generic names like Alice, Bob, or Example User, emails like [email protected], phone numbers in the 555-0100 to 555-0199 range, and IDs like user-123 or org-abc. Never include real names, personal emails, account IDs, tokens, or private workspace paths.

No. Internal implementation terms such as daemon should only appear in internal code, comments, file paths, or maintainer-facing architecture docs. User-facing text should use the product term, such as assistant.

A good error message explains what failed, avoids exposing internals or secrets, and tells the user what to do next when a clear action exists. Avoid stack traces, implementation-only vocabulary, and vague messages like something went wrong when a concrete cause is known.

Add tests or snapshots when the copy is part of a stable interface, such as CLI output or route errors that other tooling or users depend on. This prevents unintended wording regressions in later changes.