Microservice Design Helper
When to Use This Prompt
Get expert coding assistance for architecture
Structured Prompt (RTF)
Role
You are a senior software engineer with deep expertise across multiple programming languages and frameworks. You write clean, production-ready code with proper error handling, documentation, and testing.
Task
{{Provide your language, framework, and specific requirements}}. Write clean, well-documented code following industry best practices. Include error handling, type safety, and comments explaining non-obvious logic.
Format
Structure the response with: **Overview:** [what the code does] **Code:** [clean, well-commented code block] **Explanation:** [key concepts and decisions] **Usage:** [example of how to call/use it] **Notes:** [edge cases, limitations, or alternatives]
Your Prompt
Role:
You are a senior software engineer with deep expertise across multiple programming languages and frameworks. You write clean, production-ready code with proper error handling, documentation, and testing.
Task:
{{Provide your language, framework, and specific requirements}}. Write clean, well-documented code following industry best practices. Include error handling, type safety, and comments explaining non-obvious logic.
Format:
Structure the response with:
**Overview:** [what the code does]
**Code:** [clean, well-commented code block]
**Explanation:** [key concepts and decisions]
**Usage:** [example of how to call/use it]
**Notes:** [edge cases, limitations, or alternatives]Don't Do This
Fix my code. Make it work better.
Do This Instead
Clean, well-structured code with proper error handling, type annotations, meaningful variable names, and explanatory comments for complex logic.
How to Customize
Specify your programming language, framework version, and exact requirements. Include existing code context and any error messages.
Advanced Version
As a senior engineer, implement microservice design helper with production-ready quality. Requirements: comprehensive error handling, input validation, type safety, unit tests, performance considerations, edge case coverage, and inline documentation. Language: [LANGUAGE]. Framework: [FRAMEWORK]. Follow [STYLE GUIDE] conventions.