860 B
860 B
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| feedback-command-formatting | Howard needs commands formatted as multi-line scripts, not one-liners — one-liners wrap in the chat window and break when copy-pasted |
|
Always write shell/PowerShell commands as multi-line scripts, never as semicolon-separated one-liners.
Why: When long one-liners are displayed in the Claude chat window, they wrap visually. When Howard copy-pastes them (e.g. into ScreenConnect), the line breaks become real newlines, breaking operators like & onto their own lines and causing parse errors (e.g. "AmpersandNotAllowed").
How to apply: Any time you're giving Howard a PowerShell or shell command longer than ~60 characters, write it as a multi-line script in a code block. Each statement on its own line. No semicolons to chain statements — use newlines instead.