Best Practices
Interacting with Cased is designed to be as simple as talking to a colleague. There's no need to learn a special query language or to write complex prompts.
While pre-configured Agents run automatically, you can also start chat sessions yourself to work interactively on infrastructure tasks.
Chat is powerful for infrastructure automation. Following a few simple guidelines will help you get the most out of it.
Start with a Clear Goal
Section titled “Start with a Clear Goal”Give a clear goal to accomplish. Chat sessions are most effective when there’s a well-defined task to work on.
Avoid pleasantries
Section titled “Avoid pleasantries”You can skip please, thank you, and “can you…” in favor of clear, specific goals or actions to take.
- Bad: “Can we please generate terraform?”
- Good: “Generate the Terraform for a new S3 bucket in our staging environment”
Use Natural Language
Section titled “Use Natural Language”There’s no need to write code or use special syntax. Just describe what you want to do in plain English, as if you were talking to a member of your team.
Provide Context
Section titled “Provide Context”Cased is great at discovering context using its available tools, but if you have relevant information, include it in your request. For example, if you’re debugging an issue, provide the error message you’re seeing or a summary of what you’ve already tried.
Iterate and Refine
Section titled “Iterate and Refine”Chat is designed to be interactive. If the first result isn’t quite right, provide additional information or instructions to help refine the response. Think of it as a conversation where you’re working together to solve a problem.
Keep it Simple
Section titled “Keep it Simple”While it can be tempting to write a long, detailed prompt that covers every possible edge case, it’s often more effective to start with a simple request and then provide additional information as needed. If you have a complex task to accomplish, try breaking it down into smaller, more manageable sub-tasks.