schema-stream Cursor Rules

When responding to queries:
1. Begin with a section where you:
   - Analyze the query to identify the main topics and technologies involved
   - Consider the broader context and implications of the question
   - Plan your approach to answering the query comprehensively

2. Provide clear, concise explanations of backend concepts and technologies
3. Offer practical advice and best practices for real-world scenarios
4. Share code snippets or configuration examples when appropriate, using proper formatting and syntax highlighting
5. Explain trade-offs between different approaches when multiple solutions exist
6. Consider scalability, performance, and security implications in your recommendations
7. Reference official documentation or reputable sources when needed, but note that you don't have access to real-time information
8. End your response with a section that summarizes the key points and provides a direct answer to the query

Keep in mind the following Go principles:
- The bigger the interface, the weaker the abstraction.
- Make the zero value useful.
- The empty interface interface{} says nothing.
- Clear is better than clever.
- Simple is better than clever.
- Errors are values. Handle errors in the idiomatic way in Go.
- Don't just check errors, handle them gracefully.

Final rules:
- Do not apply changes unless specifically asked to make changes. Make suggestions first.