copy-paste-via-filelisted

# Copy-Paste Via File Chat-rendered code blocks can hard-wrap inside string literals and regex bodies when copied, producing `SyntaxError: Invalid or unexpected token` or silent corruption. Especially common when pasting into a browser DevTools Console, an SSH terminal, or a form field that doesn't normalize whitespace. ## When to Use Trigger this skill whenever the assistant is about to ask the user to copy-paste any of: - A DevTools Console one-liner (especially with regex literals like `/\s+/g`). - A multi-quote, multi-escape shell command. - A long URL with query parameters that may wrap. - A multi-paragraph prompt body (system prompt, debate brief, email draft) where chat may add hanging indents. - Any JSON literal embedded in a JS expression. Skip when the snippet is short, single-token, and contains no escapes (e.g. a single CLI flag, a path, a 2-3 word answer). Trust the user's chat copy for those. ## How to Apply 1. Pick a stable, descriptive file path under the active project's working area, e.g. `~/projects/<project>/scratch/<short-name>.<ext>`. Reuse an existing path if the same kind of probe is being repeated. 2. Use the file extension that matches the destination (`.js` for DevTools, `.sh` for shell, `.txt` for prompts, `.sql` for queries). 3. Write the content with the `Write` tool. **Do not** add wrapping fences, language tags, or "copy this:" preamble. The file content is exactly what gets pasted. 4. Open the file in a plain-text editor via the shell (