Wörtlich · mit Quelle

Bibliothek418 Prompts

Prompts mit Nachweis

24 Prompts, wörtlich übernommen aus den Prompt-Engineering-Leitfäden von Anthropic, OpenAI und Google sowie aus Googles Prompt-Galerie. 394 redaktionelle Beispiele, für unsere Tool-Ratgeber geschrieben, entsprechend gekennzeichnet und nicht beim Anbieter getestet. Jeder Prompt verweist auf seine Quelle.

6 Prompts · Filter zurücksetzen

Coding Anbieter-Bibliothek

Example: Creating an analytics dashboard

Create an analytics dashboard. Include as many relevant features and interactions as possible. Go beyond the basics to create a fully-featured implementation.
22 Wörter · für Claude
Coding Anbieter-Bibliothek

Sample prompt for conservative action

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…
46 Wörter · für Claude
Coding Anbieter-Bibliothek

Sample prompt for frontend aesthetics

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…
241 Wörter · für Claude
Coding Anbieter-Bibliothek

Sample prompt for maximum parallel efficiency

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…
111 Wörter · für Claude
Coding Anbieter-Bibliothek

Sample prompt for proactive action

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…
57 Wörter · für Claude
Coding Anbieter-Bibliothek

Sample prompt: investigate before answering

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…
58 Wörter · für Claude