Prompt Library
Ready-to-use instructions for AI tools — from a single-sentence tweak to a full system prompt. Each entry explains what it does, where to paste it, and when to use it.
System prompts give persistent instructions that govern every reply in a session. Custom Instructions (ChatGPT) or Skills (Copilot) persist across all sessions. Quick prompts are one-shot nudges you paste inline to correct a specific reply.
Understanding Prompt Types
Different tools use different names, but the concept is the same: persistent instructions vs. per-message instructions. Knowing which type you're using tells you where it applies, how long it lasts, and which use case it fits before you pick an example below.
System Prompt
A block of instructions set before the first user message. It governs every reply in that session. Most powerful: the AI cannot see it as a user request, so it follows it more reliably.
Available in: OpenAI API, Claude API, most local model UIs, Copilot Studio.
Scope: current session or API call.
Custom Instructions
ChatGPT's persistent system-level setting. Applies to every new conversation automatically. Set it once, forget it. Two fields: about you, and how you want responses.
Available in: ChatGPT (Plus and free).
Scope: all future conversations.
Skills / Prompt Library
Saved reusable prompts you can invoke with a slash-command or from a menu. Not always persistent — you call them when needed. Useful for standardized tasks (e.g., "summarize this email").
Available in: Microsoft 365 Copilot (Skills), Notion AI, various enterprise tools.
Scope: on-demand, per invocation.
Quick / Inline Prompt
A plain-language instruction included in your regular message. No special setup. Least reliable because the model treats it as user content, but it works for one-off corrections and quick adjustments.
Available in: Every AI tool, everywhere.
Scope: that message only.
The NoAIBloat Core System Prompt
Paste this as a System Prompt or Custom Instruction to make any AI tool default to direct, human communication. It covers all the main failure modes: filler openers, synthetic empathy, meta-commentary, and banned vocabulary.
Where to use it
- ChatGPT Custom Instructions — Settings → Personalization → Custom Instructions → "How would you like ChatGPT to respond?"
- Microsoft 365 Copilot — Paste as the first message in any chat, or save as a reusable prompt in Copilot Studio / Prompt Library.
- Claude (Anthropic) — Projects → Project Instructions field (persistent), or paste at the top of any conversation.
- Local / self-hosted models (Ollama, LM Studio, etc.) — Set as the System prompt field in the model configuration or the chat interface.
- Any other tool — Look for "System message", "System prompt", "Instructions", or "Pre-prompt" in the settings. Paste there.
Quick Anti-Bloat Prompts
Inline nudges for when you don't have a system prompt set, or need to correct a single reply. Append to your message or paste after a bloated response.
Stop filler openers
Use when the AI keeps opening with "Certainly!" or "Great question!".
Cut the closing remarks
Use when responses always end with "Let me know if you need anything else!" or "I hope that helps!".
No meta-commentary
Use when the AI keeps announcing what it's about to do instead of just doing it.
Human tone
Use when responses feel like a customer-support chatbot instead of a knowledgeable colleague.
Shorten this
Paste after any AI reply that is longer than it needs to be.
Task-Specific Prompts
Full, ready-to-paste prompts built for one specific job — a complete instruction set for a recurring task, not just a tone fix.
You are processing a meeting transcript. Your only function is to extract concrete decisions and assigned action items. Do not do anything else.
ABSOLUTE PROHIBITIONS — violating any rule is a failure:
• Do not write an executive summary, overview, or introduction of any kind
• Do not describe who said what, who raised a point, or how the conversation unfolded
• Do not use attribution phrases: "X said," "Y highlighted," "Z mentioned," "the team agreed"
• Do not write opening lines ("Here are the notes:") or closing remarks of any kind
• Do not pad, contextualise, or frame any output
OUTPUT FORMAT — reproduce this structure exactly, with no additions:
**DECISIONS:**
* [Decision stated as a plain fact — 1–2 sentences maximum]
**ACTION ITEMS:**
* [@Name] - [Specific task] - [Deadline or context if explicitly stated]
RULES:
• Names appear only as owners of action items — never as speakers or contributors
• If no decisions were made, output: **DECISIONS:** None.
• If no action items were captured, output: **ACTION ITEMS:** None.
• Output nothing outside this structure — no headings, no commentary, no sign-off