Automated summary
This guide provides principles and a structure for crafting effective system prompts for AI agents and assistants.
Strengths
- Clear, actionable principles (e.g., say what to do, not what not to do).
- Recommended prompt structure (role, responsibilities, constraints, format).
- Concrete examples illustrating each principle.
- Table of common pitfalls with solutions.
Limitations
- Does not cover advanced techniques like few-shot learning or chain-of-thought.
- Examples are generic and may need adaptation for very specific use cases.
- Assumes the user already has a good understanding of the AI domain.
When you need to write or improve a system prompt for an AI agent to get consistent, high-quality responses.
If you are looking for advanced prompt engineering techniques (e.g., few-shot, CoT) or if the desired behavior is very simple and doesn't require formal structure.
Security analysis
SafeThis skill provides writing guidance only; no executable commands, code execution, or risky actions are involved. It is a purely instructional document.
No concerns found
How this analysis is madeExamples
Help me create a system prompt for an AI assistant that reviews pull requests. It should focus on security, performance, and best practices, and output comments in a specific format.I have this system prompt: 'Be helpful and concise.' How can I improve it using the principles from prompt-creator? Rewrite it with explicit instructions and constraints.I need to write a system prompt for a customer support bot. Use the recommended structure (role, responsibilities, constraints, output format) and include an example.name: prompt-creator description: Guide for creating effective system prompts for AI agents and assistants. Use when writing, reviewing, or improving system prompts, agent instructions, or assistant configurations.
Prompt Creator
Guidelines for designing effective system prompts for AI agents and assistants.
Core Principles
Start Simple, Iterate
Begin with minimal instructions and add complexity only as needed. Prompt design is iterative—test with real inputs and refine based on results.
For complex agent behaviors, break the task into simpler subtasks first. Build up gradually rather than front-loading complexity.
Use Clear Instructions
Structure prompts with explicit commands: "Write", "Classify", "Summarize", "Translate", "Extract", "Analyze".
Place instructions at the beginning. Use separators to distinguish sections:
### Instructions ###
[Core behavior and responsibilities]
### Context ###
[Domain knowledge and constraints]
### Output Format ###
[Expected response structure]
Be Specific and Direct
Vague:
Keep responses short and helpful.
Specific:
Respond in 2-3 sentences. Include one actionable recommendation.
The more descriptive and detailed the prompt, the better the results. Include:
- Exact output formats
- Specific constraints
- Concrete examples of desired behavior
Say What To Do, Not What Not To Do
Weak (focuses on prohibitions):
DO NOT ask for personal information.
DO NOT make assumptions.
DO NOT provide medical advice.
Strong (focuses on actions):
Recommend from the top 10 trending items.
Ask clarifying questions before proceeding.
Direct health questions to qualified professionals.
Positive instructions are more effective than negative constraints.
Provide Examples for Desired Formats
When a specific output structure is needed, show it:
Extract entities from the input text.
Desired format:
- People: <comma_separated_list>
- Places: <comma_separated_list>
- Organizations: <comma_separated_list>
Example input: "Dr. Sarah Chen presented findings at MIT yesterday."
Example output:
- People: Dr. Sarah Chen
- Places: MIT
- Organizations: MIT
Balance Detail with Relevance
Include only details that contribute to the task. Unnecessary context dilutes the signal.
Ask: "Does this information change how the agent should behave?" If not, remove it.
System Prompt Structure
Effective system prompts typically follow this order:
- Role/Identity - Who the agent is
- Core Responsibilities - Primary tasks and behaviors
- Constraints - Boundaries and limitations
- Output Format - How to structure responses
- Examples - Concrete demonstrations (if needed)
You are a [role] that [primary function].
## Responsibilities
- [Responsibility 1]
- [Responsibility 2]
## Constraints
- [Constraint 1]
- [Constraint 2]
## Response Format
[Structure specification]
Common Pitfalls
| Pitfall | Problem | Solution | |---------|---------|----------| | Vague quantities | "a few", "short", "brief" | Use exact numbers: "2-3 sentences" | | Double negatives | "don't avoid" | Use positive framing | | Contradictory rules | "be concise" + "be thorough" | Prioritize or scope each rule | | Missing edge cases | Undefined behavior | Add fallback instructions | | Excessive length | Context dilution | Remove non-essential content |
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/prompt-creator-mma3js56/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/prompt-creator-mma3js56' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/prompt-creator-mma3js56/download' --output '.skill-downloads/prompt-creator-mma3js56/SKILL.md.part' && mv '.skill-downloads/prompt-creator-mma3js56/SKILL.md.part' '.skill-downloads/prompt-creator-mma3js56/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/prompt-creator-mma3js56/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.