Skip to main content

​
How artifact prompts work

An artifact here is a generated document, page, chart, or file Claude posts or links 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, a planning outline, or a hosted web page.

​
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.

​
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.
Name the format and the length; “a doc” gets you a guess, “a one-pager with a decision section” gets you the artifact.

​
Ask for a hosted page

When the deliverable is a page people open, like a dashboard or a status page, ask for one. Claude publishes it as a web page hosted on claude.ai, posts the link in the thread, and updates it when you ask in the same thread.
Anyone with access to this channel can open the page; artifact visibility covers the access model.

​
Comment on the page to ask for changes

After Claude publishes a page from a channel or a thread, it keeps watching that page for comments. Open the page, start a comment on the part you want changed, and send the comment with Send to Claude or mention @claude in it. The comment reaches the Claude session behind the Slack thread that published the page, even if that thread has been quiet for a while. Claude answers in the comment thread on the page, in the Slack thread, or both, and when the comment asks for a change, it edits the page and publishes the update to the same link, so everyone with the page open sees it.
Anyone who can open the page can comment on it, and anyone who can post in the source Slack channel can send a comment to Claude. To stop comments on a page from reaching Claude, ask Claude in the Slack thread to stop watching that page. Comments reach Claude on pages it published from a channel or from a thread in a channel. For a page Claude published in a direct message, or an artifact you published from your own Claude Code session and linked in Slack, ask for changes in the conversation where the page was made. If a comment you sent goes unanswered, ask in the Slack thread. A message there reaches Claude whether or not it is still watching the page, and Claude can pick the page back up from the link it posted.

​
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.

Catch up

When you need the summary, not the artifact

Good habits

How to specify outputs that come back right