AI System Agent Designer
Design comprehensive system prompts for AI agents with structured role definitions, tool usage guidelines, and behavioral parameters
Design comprehensive system prompts for AI agents with structured role definitions, tool usage guidelines, and behavioral parameters
The Prompt
You are an specialist AI System Architect specializing in designing powerful AI agents. Create a comprehensive system prompt that:
## Role Definition
- Define a clear, specific role for the AI agent
- Establish experience domains and knowledge boundaries
- Set communication style and personality traits
## Capabilities & Tools
- List available tools and functions
- Define tool usage guidelines and restrictions
- Specify decision-making frameworks
## Behavioral Guidelines
- **Response Format**: Use Markdown headings for structure
- **Error Handling**: Define fallback behaviors
- **Ethics**: Include safety and ethical considerations
- **Context Awareness**: Specify how to handle context and memory
## Performance Optimization
- Include efficiency guidelines
- Define quality metrics
- Set response time expectations
## Custom XML Tags (if needed)
<rules>
Define specific operational rules
</rules>
<examples>
Include relevant examples
</examples>
Agent Requirements:
[Describe the specific agent you need: purpose, target users, main tasks, interaction style]
How to Use This Prompt
- Be extremely specific about the agent’s purpose and limitations
- Include concrete examples of desired behaviors
- Define clear success metrics
- Consider edge cases and error scenarios
- Test the prompt with various inputs
Example Input
Create a system prompt for a Technical Documentation AI Agent that helps developers write API documentation. Target users: Software developers. Main tasks: Generate API docs, create code examples, explain technical concepts. Style: Professional but approachable.
Example Output
Technical Documentation AI Agent System Prompt
Role Definition
You are a Senior Technical Writer specializing in API documentation and developer resources. Your experience spans REST APIs, GraphQL, WebSockets, and modern programming paradigms. You communicate with clarity, precision, and developer empathy.
Core Capabilities
Available Functions
- Documentation Generation: Create comprehensive API endpoint documentation
- Code Example Creation: Generate working code samples in multiple languages
- Schema Definition: Design and document data models and request/response schemas
- Error Documentation: Catalog and explain error codes and handling strategies
Tool Usage Guidelines
- Always validate technical accuracy before generating documentation
- Include rate limiting and authentication details for every endpoint
- Generate examples in at least 3 programming languages (JavaScript, Python, cURL)
- Use OpenAPI/Swagger specifications when applicable
Behavioral Guidelines
Response Format
# Endpoint Name
## Overview
[Brief description]
## Request
- **Method**: GET/POST/PUT/DELETE
- **URL**: `/api/v1/resource`
- **Headers**: Required headers
- **Parameters**: Query/Path/Body parameters
## Response
- **Success Response**: Status code and body
- **Error Responses**: Common error scenarios
## Examples
[Language-specific code examples]
Quality Standards
- Completeness: Every endpoint must include authentication, parameters, responses, and examples
- Clarity: Use simple language for complex concepts
- Accuracy: Verify all code examples are syntactically correct
- Consistency: Maintain uniform formatting and terminology
Good: Include rate limiting headers in response examples Bad: Omit operational details
Performance Metrics
- Documentation completeness score: >95%
- Code example success rate: 100% compilable/runnable
- Average time to document endpoint: <2 minutes
- Developer satisfaction rating: >4.5/5
When This Prompt Is Most Useful
Use this prompt when you need help with ai system agent designer but do not want a generic answer. It works best for designers, writers, creators, and teams who need stronger creative direction before generating or reviewing assets who already have some context and want the AI to organize it into a creative brief, image prompt, concept directions, revision notes, or selection criteria. The prompt is intentionally written to slow the model down: it asks for the goal, missing information, assumptions, reasoning, and a review checklist instead of jumping straight to a polished answer.
This is especially useful when the task has tradeoffs. A simple prompt may produce a confident answer that sounds good but misses constraints. This version makes the model surface those constraints before it gives recommendations, which makes the output easier to edit, verify, and reuse.
Inputs to Prepare
Before running the prompt, gather:
- The real goal or decision you are trying to support
- The audience, customer, learner, stakeholder, or user involved
- Any source material the AI should use instead of guessing
- Constraints such as deadline, format, budget, word count, platform, or policy
- Examples of good and bad outputs if you have them
- The exact tone you want the final answer to use
For this page, the most important context is: style references, audience, brand constraints, format, composition, mood, forbidden elements, and final use case. If you leave that out, the model may still respond, but the result will usually be generic.
Example Input
Use case: product hero image. Audience: freelance designers. Mood: focused, warm, precise. Avoid: generic neon AI visuals.
How to Review the Output
Do not use the first answer blindly. Check whether it:
- gives direction that can be evaluated
- defines exclusions clearly
- connects creative choices to the audience or product goal
- makes assumptions visible instead of hiding them in confident language
- gives you something you can act on, test, or revise within the same work session
If the answer feels generic, reply with: “Make this more specific to my context. Remove generic advice, name the tradeoffs, and show the exact changes you would make.” If the answer is too long, ask for a shorter version that keeps the checklist and decision points.
Common Failure Modes
- Too little context: the AI fills gaps with generic advice.
- No review criteria: the output sounds polished but is hard to judge.
- Unclear audience: the answer may optimize for the wrong reader or use the wrong tone.
- Overclaiming: the model may invent certainty when the source material is weak.
The fix is to add concrete inputs and ask for assumptions, alternatives, and review criteria before you use the final output.
Practical Variations for AI System Agent Designer
- Brief mode: Turn a rough idea into a creative brief with mood, constraints, and exclusion rules.
- Generation mode: Ask for variants that change composition, medium, lighting, or narrative angle.
- Critique mode: Paste the draft concept and ask what to keep, remove, and test.
Follow-Up Prompts
Use these after the first answer:
- “Rewrite this using only the context I provided. Label assumptions instead of hiding them.”
- “Give me a conservative version, a direct version, and a version optimized for speed.”
- “Create a final review checklist I can use before I publish, send, ship, or present this.”
What Makes This Page Different
This page is useful when you are working on ai system agent designer and need more than a blank chat box. It gives you a starting prompt, context checklist, review criteria, and practical variations so the answer can be tested instead of merely accepted. If your task is broader, start with a workflow guide first, then come back to this prompt once the input, audience, and success criteria are clear.
Input checklist
Before You Run This Prompt
- Define the exact outcome you want from AI System Agent Designer.
- Add the audience, use case, constraints, deadline, and preferred format.
- Include one strong example of the style or quality level you expect.
- State what the AI should avoid, such as unsupported claims, generic advice, or off-brand tone.
Quality bar
What a Good Output Should Include
- A clear structure that can be used without heavy rewriting.
- Specific recommendations tied to your provided context.
- Tradeoffs, assumptions, and missing information called out explicitly.
- Next steps or validation checks so you can judge whether the output is usable.
Iteration workflow
How to Improve the First Answer
1. Tighten the context
Ask the AI to identify missing inputs before it rewrites the answer.
2. Request alternatives
Generate two or three variants for different audiences, tones, or levels of detail.
3. Run a critique pass
Ask for risks, weak assumptions, and edits that would make the result more actionable.
Best Use Cases
- Projects where Technical context needs a repeatable starting point.
- Projects where AI Development context needs a repeatable starting point.
- Workflows where you want a reusable template instead of starting from a blank chat.
- Situations where the output still needs human review before publishing or sending.
When to Be Careful
- Do not treat the answer as final when legal, medical, financial, or safety decisions are involved.
- Check facts, names, links, prices, dates, and citations before using the output externally.
- Remove any invented evidence, exaggerated claims, or details that were not present in your input.
Workflow guides
Make This Prompt More Reliable
AI Prompt Quality Checklist
Review whether the prompt has enough context, constraints, examples, and quality criteria.
AI Prompt Evaluation Scorecard
Score AI outputs before you rely on them for customer-facing or decision-support work.
Turn a Prompt Into a Workflow
Convert a useful one-off prompt into a repeatable process with inputs and review steps.
Organize an AI Prompt Library
Keep prompts findable, reviewed, and useful as your collection grows.
Use This Prompt Responsibly
AI output quality depends on the context you provide. Treat this template as a structured starting point, then review the result for accuracy, tone, originality, and fit before using it in real work.