Best Practices
Guidelines for getting the most out of Zonia
Communication Guidelines
Effective Practices
- ✓Be specific and clear in your requests
- ✓Provide relevant context
- ✓Break complex tasks into smaller steps
- ✓Use follow-up questions for clarification
Common Mistakes
- ✗Vague or ambiguous requests
- ✗Missing important details
- ✗Asking multiple unrelated questions
- ✗Ignoring Zonia's clarifying questions
Example Interactions
Good Examples
✓ Specific Request:
"Help me write a professional email to schedule a team meeting for next Tuesday at 2 PM to discuss the Q4 marketing strategy."
✓ With Context:
"I'm using React 18 with TypeScript. Can you help me implement a custom hook for handling form validation?"
Poor Examples
✗ Vague Request:
"Help me with my website"
Better: "Help me design a responsive navigation menu for my React-based e-commerce website"
✗ Lacking Context:
"Fix this error"
Better: "I'm getting a 'TypeError: Cannot read property of undefined' in my React component. Here's the code..."
Task-Specific Guidelines
Code Assistance
- • Include programming language and version
- • Share relevant code snippets
- • Describe expected vs actual behavior
- • Mention any error messages
Content Writing
- • Specify target audience
- • Define tone and style
- • Provide key points to cover
- • Mention length requirements
Advanced Tips
- 🔍Use the chat history feature to maintain context in long conversations
- 💡Leverage quick actions for common tasks to save time
- 🔄Iterate on responses by providing feedback and asking for adjustments
- 📝Save useful responses for future reference