You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 4ae048e
Browse filesBrowse the repository at this point in the historyBrowse files
Brings in #774 (the np.Preview Flow fix), so the repo is at zero Flow errors
with the strict check in place.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
description: Show actual markdown source (not rendered) for written CLI output
3
+
alwaysApply: true
4
+
---
5
+
6
+
# Raw Markdown for Written Output
7
+
8
+
When the user wants **written output** in the CLI (CHANGELOG summaries, release notes, docs drafts, copy-pasteable text, etc.) -- anything meant to be read or copied as markdown source -- show the **actual markdown characters**, not a rendered version.
9
+
10
+
## Why
11
+
12
+
Rendered replies hide `#` / `###` and turn `-` lists into bullet symbols (`•`). The user cannot verify or copy the source as intended.
13
+
14
+
## Do
15
+
16
+
- Put that content in a fenced code block (e.g. ` ```markdown ` ... ` ``` `) so `#`, `-`, and other markup stay as plain text.
17
+
- Apply this to final deliverable prose, not to agent build plans, tool traces, or normal conversational replies.
18
+
19
+
## Don't
20
+
21
+
- Rely on the chat UI's markdown rendering for copy-pasteable written deliverables.
22
+
- Use Unicode bullet characters (`•`, `●`, etc.) in place of markdown list markers.
23
+
24
+
```markdown
25
+
<!-- ❌ BAD: rendered in the reply as bullets / headings -->
26
+
### New
27
+
- Item one
28
+
29
+
<!-- ✅ GOOD: fenced so source is visible -->
30
+
### New
31
+
- Item one
32
+
```
33
+
34
+
(The good example must live inside a fenced code block in the real reply.)
0 commit comments