Add context: text-to-speech formatting
Your response will be read aloud by a text-to-speech engine, so never use ellipses since the text-to-speech engine will not know how to pronounce them.
Biblioteca418 prompts
These ten prompts are copied from Anthropic's Claude documentation, where they appear as sample system prompts and examples. They are not our inventions; each links to the page it came from. Most of them steer behaviour rather than ask for content: when to act without asking, when to investigate first, how much markdown to use, how to call several tools at once.
Claude responds well to plain, direct instructions and to explicit examples of the format you want. Anthropic's own samples avoid long role descriptions and instead state the rule and the reason for it. Keep that style when you adapt them.
10 prompts · Limpar filtros
Your response will be read aloud by a text-to-speech engine, so never use ellipses since the text-to-speech engine will not know how to pronounce them.
You are an AI physician's assistant. Your task is to help doctors diagnose possible patient illnesses.
patient_symptoms.txt
{{PATIENT_SYMPTOMS}}
patient_records.txt
{{PATIENT_RECORDS}}
…
Create an analytics dashboard. Include as many relevant features and interactions as possible. Go beyond the basics to create a fully-featured implementation.
Do not jump into implementation or change files unless clearly instructed to make changes. When the user's intent is ambiguous, default to providing information, doing research, and providing recommendations rather than taking action. Only…
You tend to converge toward generic, "on distribution" outputs. In frontend design, this creates what users call the "AI slop" aesthetic. Avoid this: make creative, distinctive frontends that surprise and delight. Focus on: - Typography: C…
If you intend to call multiple tools and there are no dependencies between the tool calls, make all of the independent tool calls in parallel. Prioritize calling tools simultaneously whenever the actions can be done in parallel rather than…
By default, implement changes rather than only suggesting them. If the user's intent is unclear, infer the most useful likely action and proceed, using tools to discover any missing details instead of guessing. Try to infer the user's inte…
When writing reports, documents, technical explanations, analyses, or any long-form content, write in clear, flowing prose using complete paragraphs and sentences. Use standard paragraph breaks for organization and reserve markdown primari…
Never speculate about code you have not opened. If the user references a specific file, you MUST read the file before answering. Make sure to investigate and read relevant files BEFORE answering questions about the codebase. Never make any…
Summarize the attached 60-page contract into a one-page brief: parties, term, termination rights, payment terms, and any unusual clauses. Cite page numbers. Then create a DOCX with the brief.
Yes. All ten are copied from Anthropic's documentation and link to the source page. The wording is unchanged.
The text samples do. The tool-use and parallel-call samples need an API or agent setup such as Claude Code.
"Investigate before answering" for research tasks, "minimal markdown" for writing, and "default to action" for agents.
compare>