Mike Swanson
0c000109dc
Compressed memory store 104 -> 71 files via four passes: - Syncro: 19 scattered feedback_syncro_* files merged into 3 rule files (api/billing/workflow) + an on-demand feedback_syncro_history.md for incident detail, quotes, and tech/product ID tables. - Four near-duplicate merges: Howard paste-safety, Pluto build server, Howard backend deferral, IX server access (ssh+tailscale). - Per-cluster rule/state/history split applied to GuruConnect (2->1), Dataforth (3->2), Cascades (7->3), GuruRMM (13->3). - New reference_resource_map.md: single auto-loaded cheatsheet for "do I have access to X and how do I connect from this machine?" - MEMORY.md rewritten to match the new layout. Health: broken backlinks 8->7, overlap clusters 12->5, orphans 17->0.
27 lines
1.5 KiB
Markdown
27 lines
1.5 KiB
Markdown
---
|
|
name: Paste-safe command formatting for Howard
|
|
description: Format all shell/PowerShell commands for safe copy-paste — multi-line scripts (never semicolon one-liners) AND all code starts at column 0 inside fences (no indentation). Both rules exist because Howard copy-pastes directly from chat and any visual artifact (wrapping or leading whitespace) becomes a real parse error.
|
|
metadata:
|
|
type: feedback
|
|
---
|
|
|
|
Two clauses, same root cause. Howard copy-pastes commands directly from the Claude chat window into PowerShell (often via ScreenConnect). Any visual artifact in the rendered output becomes a real character in the paste and breaks the parse.
|
|
|
|
---
|
|
|
|
## 1. Multi-line, never one-liners
|
|
|
|
Write commands longer than ~60 characters as multi-line scripts in a fenced code block — one statement per line, newlines instead of semicolons.
|
|
|
|
**Why:** long semicolon-chained one-liners wrap visually in the chat window. On paste, the visual wraps become real newlines, breaking operators (`&`, etc.) onto their own lines → `AmpersandNotAllowed` and similar parse errors.
|
|
|
|
---
|
|
|
|
## 2. No leading whitespace inside code fences
|
|
|
|
All code starts at **column 0** inside the fences. No leading spaces or tabs, even when the surrounding markdown is indented (e.g. inside a list item).
|
|
|
|
**Why:** indented code blocks consistently fail when pasted into PowerShell — Howard had to manually strip the indentation every time.
|
|
|
|
**Apply:** every PowerShell, bash, or other code block — column 0 for the first non-fence character on every line.
|