How artifact prompts work
An artifact here is a generated document, page, chart, or file Claude posts in the thread for the team to use, as opposed to a chat reply. Each prompt below is a Slack message. You paste it in the thread or channel you want turned into something, Claude reads the discussion and posts progress in that thread, and the draft lands there too. What the draft is depends on the prompt, and each one below names the artifact it returns, like a decision doc, a customer reply, a filed ticket, or a planning outline.Check the channel’s connections
Check that the channel has the connections below. Ask@Claude what can you access from this channel? to check; an admin can add a connection the channel is missing.
| Connection | Examples | Why it matters here |
|---|---|---|
| None | — | Works on Slack content alone |
| Issue tracking | Linear, Jira, Asana | Optional. Files tickets from the draft |
Prompts to paste
Draft from one thread
The thread settled the question, and what’s missing is the doc, the customer reply, or the ticket. Name the artifact in the thread where the discussion happened.Keep a capture channel
Planning inputs arrive over a month, not in one sitting. Forward messages and ideas to one channel as you find them, then ask for a synthesis when you need the artifact.Related resources
Catch up
When you need the summary, not the artifact
Good habits
How to specify outputs that come back right