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:

• Internal business names and contacts
• Email addresses and domain names
• Client or customer identifiers
• Account names and credentials
• Organization-specific terminology that reveals private operations

Core Rule

If data came from a prompt, a local file, a script, a config, or a task — it does NOT go into documentation.

Documentation examples use only well-known, fictional, or obviously placeholder data.

What Counts as Real Data

Any value that originates from:

• Local configuration files (e.g., config.json, .env, account modules)
• Scripts and task files (e.g., batch scripts, shell scripts, task runners)
• Prompt context (e.g., data the user supplies when asking an agent to build or update the tool)
• Map or filter files (e.g., JSON mappings, data extraction rules)
• Git-ignored files (e.g., files excluded from version control that contain environment-specific values)

Approved Placeholder Data for Documentation

Use these generic, cliche substitutes in all documentation and examples:

How to Apply This Rule

When Adding a Feature

If you add a feature using real account data (e.g., a script named after a real client), document the feature using a fictional account name instead.

Real implementation file: an account module configured for a specific business

Documentation example:

// accounts/acme.mjs — Example account configuration
export default {
  name: 'Acme Corp',
  email: 'reports@example.com',
  folder: 'INBOX',
};

When Updating Configuration Docs

If a config file references real domains, real paths, or real credentials, replace every real value with a placeholder before including it in documentation.

Documentation example:

{
  "host": "imap.example.com",
  "user": "admin@example.com",
  "folder": "INBOX/Reports",
  "outputDir": "./downloads"
}

When Writing Script Examples

If a script automates a task for a specific organization, the documentation example must use a generic organization name and generic parameters.

Documentation example:

@echo off
REM Example: Run the extraction task for Acme Corp
node extractEmail.mjs --account acme --task download

The Boundary Between Code and Docs

One Exception

A word from real data may appear in documentation only if it is a common English word used in its ordinary sense and not in the context of an example. For instance, the word "development" is acceptable in a sentence like "This tool is under active development" even if it also appears in a real organization name.

Summary

Documentation is public. Implementation data is private. Keep them separate. Every example in every doc file should pass a simple test: could a stranger read this and learn nothing about the real users, clients, or organizations behind this tool? If the answer is no, replace the data with cliche placeholders.