Salt Shaker Press: Formatting output

Here is a list of 100 command prompts for formatting output, categorized by their application.

Format the string to all uppercase.
Format the string to all lowercase.
Format the string to "Title Case" (capitalize the first letter of each word).
Format the string to "Sentence case" (capitalize only the first letter of the string).
Wrap the text to a maximum width of [80] characters.
Strip all leading and trailing whitespace from the output.
Remove all newline characters to collapse text into a single line.
Replace all instances of [find_string] with [replace_string].
Left-pad the string with [character] to a total length of [N].
Right-pad the string with [character] to a total length of [N].
Format the output using a template string (e.g., "User: {name}, ID: {id}").
Remove all punctuation from the string.

Format the list as a bulleted (unordered) list using [*] or [-].
Format the list as a numbered (ordered) list.
Format the list as a single comma-separated string.
Format the list as a [pipe/semicolon] delimited string.
Format the key-value pairs (dictionary) as a simple two-column list (e.g., "Key: Value").
Format the nested data structure as an indented tree structure.
Format the data as an ASCII table.
Set the column widths of the table to [10, 20, 15].
Left-align all text columns in the table.
Right-align all numerical columns in the table.
Center-align the headers of the table.
Add a header row and row separators to the table.

Add ANSI color to the output based on status (e.g., red for error, green for success).
Format the [title/key] text as bold.
Format the [help/note] text as italic or dimmed.
Use a progress bar to show the status of a long-running task.
Display a spinner or throbber for indeterminate waiting periods.
Format the log message with a timestamp (e.g., [YYYY-MM-DD HH:MM:SS]).
Format the log message with the [severity level] (e.g., INFO, WARN, ERROR).
Prepend the [module/function name] to the log line.
Format the log output as a single-line JSON object for structured logging.
Align log messages into columns (e.g., timestamp, level, message) for readability.
Indent child processes or sub-tasks in the log output.
Paginate the output (e.g., pipe to lessormore).
Truncate long strings in CLI table columns to [N] characters.
Add an ellipsis (...) to truncated text.
Format the output to be grep-able (e.g., consistent, simple lines).

Generate the output as a Markdown (.md) file.
Format the data as a Markdown table.
Format the [text] as a Markdown blockquote.
Format the [code] as a Markdown fenced code block with syntax highlighting.
Generate the output as an HTML file.
Embed the data within an HTML <table> structure.
Format the output into an HTML <ul>or<ol> list.
Apply a CSS class to the [main/error] output element.
Generate a print-friendly version of the output (e.g., using @media print CSS).
Generate the output as a PDF document.
Add a header and footer to each page of the PDF.
Set the page orientation to [landscape/portrait].
Add page numbers to the document output.
Format text into [2] columns.
Generate a Table of Contents for the document.

Wrap the API response in a consistent JSON envelope (e.g., {"data": ..., "error": ...}).
Set the correct HTTP Content-Typeheader (e.g.,application/json, text/plain).
Format error responses using a standard (e.g., RFC 7807 problem details).
Implement pagination fields in the API response (e.g., count, next, previous).
Format the error message to be user-friendly (avoid technical jargon).
Include a unique error code (e.g., E-1024) in the error output.
Provide a verbose/debug version of the output when a [--verbose] flag is set.
Format a "success" message with a summary of the action completed.

Salt Shaker Press