Use Cliche Data in Documentation

When updating or writing documentation for a tool, never include real data that was provided in prompts, local configuration, scripts, task files, or any other implementation-specific source. Documentation must use only generic, commonly recognized placeholder data that cannot expose sensitive information.

When to Use This Skill

• Writing or updating README.md files
• Creating documentation in docs/ folders
• Adding code examples to markdown files
• Writing CHANGELOG.md entries
• Adding code comments in committed source files

Why This Matters

A tool's source code and local configuration often contain real names, real email addresses, real organization details, and real domain names. These values are necessary for the tool to function, but they have no place in public-facing documentation. Leaking real data into docs can expose: