docs: Add inline {.prompt} dialog for user-to-LLM prompts

Enable MyST attrs_inline extension for [content]{.class} syntax.
This allows full nested markup (code, links, bold) inside inline
styled spans — something standard Sphinx roles can't do.

- Add span.prompt CSS: italic text + curly quote marks via ::before/::after
- Apply to prompting guide tables (effective patterns + anti-patterns)
- WCAG AA contrast preserved via --color-foreground-primary/muted

Syntax: [Run `pytest` in my build pane]{.prompt}
Renders: "Run `pytest` in my build pane" (italic, styled quotes)

Author: tony

docs/_static/css/custom.css

@@ -246,6 +246,27 @@ div.admonition.agent-thought > p:last-child {
   margin-bottom: 0;
 }
 
+/* ── Inline prompt dialog ────────────────────────────────
+ * Inline styled span for user-to-LLM prompts. Supports
+ * full nested markup via MyST attrs_inline extension:
+ *   [Run `pytest` in my build pane]{.prompt}
+ * No line-height or word-wrap disruption. WCAG AA contrast.
+ * ────────────────────────────────────────────────────────── */
+span.prompt {
+  font-style: italic;
+  color: var(--color-foreground-primary);
+}
+
+span.prompt::before {
+  content: "\201C";
+  color: var(--color-foreground-muted);
+}
+
+span.prompt::after {
+  content: "\201D";
+  color: var(--color-foreground-muted);
+}
+
 /* ── Labeled code panels ─────────────────────────────────
  * Copyable prose in labeled dark panels. Two variants:
  * .system-prompt — user-authored fragments for AGENTS.md

docs/conf.py

@@ -54,6 +54,7 @@
     "replacements",
     "strikethrough",
     "linkify",
+    "attrs_inline",
 ]
 
 templates_path = ["_templates"]

docs/topics/prompting.md

@@ -36,21 +36,21 @@ These natural-language prompts reliably trigger the right tool sequences:
 
 | Prompt | Agent interprets as |
 |--------|-------------------|
-| "Run `pytest` in my build pane and show results" | {toolref}`send-keys` → {toolref}`wait-for-text` → {toolref}`capture-pane` |
-| "Start the dev server and wait until it's ready" | {toolref}`send-keys` → {toolref}`wait-for-text` (for "listening on") |
-| "Check if any pane has errors" | {toolref}`search-panes` with pattern "error" |
-| "Set up a workspace with editor, server, and tests" | {toolref}`create-session` → {toolref}`split-window` (x2) → {toolref}`set-pane-title` (x3) |
-| "What's running in my tmux sessions?" | {toolref}`list-sessions` → {toolref}`list-panes` → {toolref}`capture-pane` |
-| "Kill the old workspace session" | {toolref}`kill-session` (after confirming target) |
+| [Run `pytest` in my build pane and show results]{.prompt} | {toolref}`send-keys` → {toolref}`wait-for-text` → {toolref}`capture-pane` |
+| [Start the dev server and wait until it's ready]{.prompt} | {toolref}`send-keys` → {toolref}`wait-for-text` (for "listening on") |
+| [Check if any pane has errors]{.prompt} | {toolref}`search-panes` with pattern "error" |
+| [Set up a workspace with editor, server, and tests]{.prompt} | {toolref}`create-session` → {toolref}`split-window` (x2) → {toolref}`set-pane-title` (x3) |
+| [What's running in my tmux sessions?]{.prompt} | {toolref}`list-sessions` → {toolref}`list-panes` → {toolref}`capture-pane` |
+| [Kill the old workspace session]{.prompt} | {toolref}`kill-session` (after confirming target) |
 
 ## Anti-patterns to avoid
 
 | Prompt | Problem | Better version |
 |--------|---------|---------------|
-| "Run this command" | Ambiguous — agent may use its own shell instead of tmux | "Run `make test` in a tmux pane" |
-| "Check my terminal" | Which pane? Agent must discover first | "Check the pane running `npm dev`" or "Search all panes for errors" |
-| "Clean up everything" | Too broad for destructive operations | "Kill the `ci-test` session" |
-| "Show me the output" | Capture immediately? Or wait? | "Wait for the command to finish, then show me the output" |
+| [Run this command]{.prompt} | Ambiguous — agent may use its own shell instead of tmux | [Run `make test` in a tmux pane]{.prompt} |
+| [Check my terminal]{.prompt} | Which pane? Agent must discover first | [Check the pane running `npm dev`]{.prompt} or [Search all panes for errors]{.prompt} |
+| [Clean up everything]{.prompt} | Too broad for destructive operations | [Kill the `ci-test` session]{.prompt} |
+| [Show me the output]{.prompt} | Capture immediately? Or wait? | [Wait for the command to finish, then show me the output]{.prompt} |
 
 ## System prompt fragments