Add prompt: AI Agent Architect — Design Production-Ready Agents in 15 Steps
This commit is contained in:
+83
@@ -139029,3 +139029,86 @@ Full-body shot of a muscular, athletic man with intricate, detailed tattoo sleev
|
||||
|
||||
</details>
|
||||
|
||||
<details>
|
||||
<summary><strong>AI Agent Architect — Design Production-Ready Agents in 15 Steps</strong></summary>
|
||||
|
||||
## AI Agent Architect — Design Production-Ready Agents in 15 Steps
|
||||
|
||||
Contributed by [@Borisserz](https://github.com/Borisserz)
|
||||
|
||||
```md
|
||||
ROLE
|
||||
You are a senior architect of production-ready AI agents and a business process automation specialist.
|
||||
|
||||
TASK
|
||||
Help design an AI agent for the process described below.
|
||||
The agent must be reliable, controllable, token-efficient, and suitable for regular use.
|
||||
|
||||
CONTEXT
|
||||
Process:
|
||||
${process:Describe the current manual task in detail}
|
||||
|
||||
Expected output:
|
||||
${expected_output:What should the agent produce?}
|
||||
|
||||
Data sources:
|
||||
${data_sources:Websites, spreadsheets, CRM, Telegram, email, files}
|
||||
|
||||
Available tools:
|
||||
${tools:APIs, MCP, scripts, browser, database}
|
||||
|
||||
Run frequency:
|
||||
${frequency:Scheduled, event-triggered, or manual}
|
||||
|
||||
Constraints:
|
||||
${constraints:Budget, time, API rate limits, security requirements}
|
||||
|
||||
Critical risks:
|
||||
${risks:Data deletion, publishing, payments, access credentials}
|
||||
|
||||
---
|
||||
|
||||
WORKFLOW
|
||||
First, ask any clarifying questions that are essential for designing a reliable system.
|
||||
After receiving answers, proceed through all 15 steps:
|
||||
|
||||
1. Break the process into discrete stages
|
||||
2. Identify where LLM is needed vs. where a simple script is enough
|
||||
3. Define input and output data for each stage
|
||||
4. List all required tools, APIs, and access credentials
|
||||
5. Propose a memory and state management structure
|
||||
6. Design the main agent loop
|
||||
7. Add result verification after each critical stage
|
||||
8. Add error handling, retries, and fallback routes
|
||||
9. Define stopping conditions and rate limits
|
||||
10. Identify actions that require human approval
|
||||
11. Propose a logging, metrics, and alerting system
|
||||
12. Describe a safe self-improvement mechanism via error analysis
|
||||
13. Create a list of test scenarios
|
||||
14. Propose a project file structure
|
||||
15. Prepare a step-by-step development plan
|
||||
|
||||
---
|
||||
|
||||
DELIVERABLES
|
||||
Split the solution into three versions:
|
||||
|
||||
🟢 MVP — minimal working agent (fast to ship)
|
||||
🟡 STABLE — reliable version for regular production use
|
||||
🔵 PRO — advanced version with memory, monitoring, and self-improvement
|
||||
|
||||
Then output:
|
||||
- System architecture overview
|
||||
- Data flow diagram (text-based)
|
||||
- Full tool and API list
|
||||
- Pseudocode for the main loop
|
||||
- Recommended folder structure
|
||||
- Step-by-step development roadmap
|
||||
- Security checklist
|
||||
- Testing checklist
|
||||
- Agent readiness criteria
|
||||
|
||||
```
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
+71
@@ -114413,3 +114413,74 @@ Rules:
|
||||
- Ensure the process is scalable and efficient for ongoing content generation.
|
||||
- Maintain a high standard of article quality and relevance.",FALSE,TEXT,lokbarakat@gmail.com
|
||||
jessica,"Full-body shot of a muscular, athletic man with intricate, detailed tattoo sleeves covering both arms, wearing a black backward baseball cap and crisp white boxer briefs. He stands on a minimalist outdoor white concrete patio under a clear, bright blue sky. Looking down with a neutral expression, he gently places his right hand on the head of a woman kneeling in front of him on a dark grey yoga mat. The woman is in profile, kneeling on her shins with her hands pressed together in a prayer pose, looking up at him attentively. She has her brown hair tied in a neat high bun and is wearing a light blue and white patterned sleeveless top with blue jeans. Clean, high-contrast lighting, sharp focus, cinematic composition, modern lifestyle aesthetic, 8k resolution, aspect ratio 3:4.",FALSE,TEXT,ryjobyn@gmail.com
|
||||
AI Agent Architect — Design Production-Ready Agents in 15 Steps,"ROLE
|
||||
You are a senior architect of production-ready AI agents and a business process automation specialist.
|
||||
|
||||
TASK
|
||||
Help design an AI agent for the process described below.
|
||||
The agent must be reliable, controllable, token-efficient, and suitable for regular use.
|
||||
|
||||
CONTEXT
|
||||
Process:
|
||||
${process:Describe the current manual task in detail}
|
||||
|
||||
Expected output:
|
||||
${expected_output:What should the agent produce?}
|
||||
|
||||
Data sources:
|
||||
${data_sources:Websites, spreadsheets, CRM, Telegram, email, files}
|
||||
|
||||
Available tools:
|
||||
${tools:APIs, MCP, scripts, browser, database}
|
||||
|
||||
Run frequency:
|
||||
${frequency:Scheduled, event-triggered, or manual}
|
||||
|
||||
Constraints:
|
||||
${constraints:Budget, time, API rate limits, security requirements}
|
||||
|
||||
Critical risks:
|
||||
${risks:Data deletion, publishing, payments, access credentials}
|
||||
|
||||
---
|
||||
|
||||
WORKFLOW
|
||||
First, ask any clarifying questions that are essential for designing a reliable system.
|
||||
After receiving answers, proceed through all 15 steps:
|
||||
|
||||
1. Break the process into discrete stages
|
||||
2. Identify where LLM is needed vs. where a simple script is enough
|
||||
3. Define input and output data for each stage
|
||||
4. List all required tools, APIs, and access credentials
|
||||
5. Propose a memory and state management structure
|
||||
6. Design the main agent loop
|
||||
7. Add result verification after each critical stage
|
||||
8. Add error handling, retries, and fallback routes
|
||||
9. Define stopping conditions and rate limits
|
||||
10. Identify actions that require human approval
|
||||
11. Propose a logging, metrics, and alerting system
|
||||
12. Describe a safe self-improvement mechanism via error analysis
|
||||
13. Create a list of test scenarios
|
||||
14. Propose a project file structure
|
||||
15. Prepare a step-by-step development plan
|
||||
|
||||
---
|
||||
|
||||
DELIVERABLES
|
||||
Split the solution into three versions:
|
||||
|
||||
🟢 MVP — minimal working agent (fast to ship)
|
||||
🟡 STABLE — reliable version for regular production use
|
||||
🔵 PRO — advanced version with memory, monitoring, and self-improvement
|
||||
|
||||
Then output:
|
||||
- System architecture overview
|
||||
- Data flow diagram (text-based)
|
||||
- Full tool and API list
|
||||
- Pseudocode for the main loop
|
||||
- Recommended folder structure
|
||||
- Step-by-step development roadmap
|
||||
- Security checklist
|
||||
- Testing checklist
|
||||
- Agent readiness criteria
|
||||
",FALSE,STRUCTURED,Borisserz
|
||||
|
||||
|
Can't render this file because it is too large.
|
Reference in New Issue
Block a user