markdown-drafts

From README

Markdown Drafts When the user asks you to draft, write, or compose content that will be copied into an external system — GitHub issues, pull request descriptions, Jira tickets, wiki pages, design documents, RFCs, or similar — always use markdown syntax so that formatting survives the copy-paste. When This Applies GitHub issues and pull request descriptions Jira ticket descriptions and comments Confluence / wiki page drafts Design documents and RFCs Slack messages (Slack renders a subset of markdown) Any content the user explicitly says will be copied elsewhere Formatting Rules Use #, ##, ### headers to create structure Use - or for unordered lists, 1. for ordered lists Use triple-backtick fenced code blocks with language tags (e.g., ## My Heading bullet one bold text and code This ensures the user sees and can copy the exact markdown source. Never render the draft as formatted text outside a code fence — the markup will be silently consumed by the chat UI.