Guide
Where Anthropic's prompt library went, and how a team shares prompts in Claude
Anthropic's prompt library, the page of example prompts in Claude's docs, now redirects to its Prompting best practices guide, which teaches the patterns instead of listing prompts: be clear and direct, explain why, give a few examples and structure long prompts with XML tags. For a team's own prompts, what Claude lets you share is a project, with its instructions and files, or a skill, which Claude applies in any chat when the request matches, and both are shared on Team and Enterprise. A skill can also go beyond one Claude workspace: put it in AI Skill Pod and everyone gets it in their Claude, Cursor or ChatGPT (Pro, Business, Enterprise) from one invite link, Pro accounts included.
Short answer
- Anthropic's library: now its Prompting best practices guide.
- Keep a prompt: as a project or a skill.
- Share in Claude: on Team and Enterprise.
- Share anywhere: a skill in a pod.
What Anthropic's guide says, in five rules
- Be clear and direct. Anthropic's test: show the prompt to a colleague with little context; if they'd be confused, Claude will be too.
- Explain why. "Never use ellipses" works better with the reason, such as the text being read aloud.
- Give 3 to 5 examples that match the real task and vary enough, each inside <example> tags.
- Structure long prompts with XML tags, such as <instructions>, <context> and <input>.
- Give Claude a role; even one sentence helps.
From Claude Docs, Prompting best practices, read 5 November 2026, 20:01 JST.
Ways to keep a team's prompts in Claude
| Project | Skill in Claude | Skill in a pod | |
|---|---|---|---|
| What it keeps | Instructions and files for one piece of work | A method Claude applies when a request matches | The same method |
| Where it works | Chats inside the project | Any chat | Claude, Cursor, ChatGPT (Pro, Business, Enterprise) |
| Shared with | Team and Enterprise: Can view or Can edit | Team and Enterprise: people you share it with, who turn it on | Anyone who joins from the invite link |
From Claude Help Center, read 5 November 2026, 19:00 JST.
A worked example: three accountants on Pro
Illustration: a made-up business. A three-person accounting practice keeps its prompts in a shared document, and each accountant has a Claude Pro account. The "client question reply" prompt has grown to two pages. The partner:
- Rewrites it with the guide's rules: a role ("you answer clients for a small accounting practice"), the reason for each rule, and two example replies in example tags.
- Turns it into a skill, with the description "Drafts a reply to a client's tax or bookkeeping question: answer, what we need from them, next date. Use when a client emails a question."
- Adds it to the practice's pod, since sharing a skill in Claude is a Team and Enterprise feature, and the other two join from the invite link.
Now, when any of them asks for a reply to a client's question, Claude uses the method without anyone pasting two pages first.
AI Skill Pod is this site's product. Pod pricing: Free up to 3 members and 10 skills; Team $5 per seat a month from 3 seats.
Next step: three ways to share prompts
If your team is choosing how to share prompts, compare the options. How to share AI prompts with your team (3 ways) sets them side by side.
Skills for this
- AI practiceTurn a prompt into a skillTurns a prompt that works into a skill the whole team can reuse, with a valid name, a when-to-use description, steps, an output template, an example, and checks.
- AI practiceContext brief for an AI assistantWrites instructions for an AI assistant or agent: role, audience, can and can't, sources of truth, tools, format, examples, edge cases, and handoff.
- AI practiceEval set for an AI taskBuilds a 20-to-50-case eval set for an AI task: normal, edge, and adversarial cases, expected results or rubrics, pass criteria, and a re-run routine.
Questions
Where is Anthropic's prompt library?
Its old address in Claude's docs now redirects to the Prompting best practices guide, read on 5 November 2026. Instead of a list of example prompts, the guide teaches the patterns that work with current Claude models: clear instructions, the reason behind them, a few examples, XML tags and a role.
Can you save and share prompts in Claude?
Claude lets a team share a project, with its instructions and files, or a skill, which Claude applies in any chat when the request matches. Both are shared on Team and Enterprise. On Free or Pro accounts, share the skill through a pod instead, which also reaches teammates who use Cursor or ChatGPT.
What makes a good prompt for Claude?
Anthropic's guide says to be clear and direct, as if briefing a new colleague; to explain why a rule matters; to give 3 to 5 relevant, varied examples inside example tags; to separate instructions, context and input with XML tags; and to give Claude a role.
AI skill
Have your AI turn a prompt that works into a skill your team can reuse
Put this skill in AI Skill Pod and everyone on your team gets it in their Claude, Cursor or ChatGPT (Pro, Business, Enterprise): one invite link, free to start. Turn a prompt into a skill has your AI rewrite a prompt from your team's document as a skill Claude applies by itself: a valid name, a description that says when to use it, inputs, numbered steps with your rules, an output template, an example and checks.
14 days free · No card needed
Sources
- Claude Docs: Prompting best practices — read at 20:01 JST, where docs.claude.com/en/resources/prompt-library/library now redirects: be clear and direct (show the prompt to a colleague with little context), add context and explain why, use 3 to 5 relevant, varied examples in example tags, structure prompts with XML tags, give Claude a role (read 2026-11-05)
- Claude Help Center: What are projects? — read at 19:00 JST: project instructions and knowledge; every plan, Free up to five projects; shared on Team and Enterprise as Can view or Can edit (read 2026-11-05)
- Claude Help Center: Using skills in Claude — read at 19:00 JST: skills on every plan with code execution on; custom skills aren't visible to colleagues until shared; on Team and Enterprise, share them with people, who turn them on (read 2026-11-05)