feat: tighten Casey responses to 3 sentences max with clear next step

Author: mwbrooks

claude-agent-sdk/agent/casey.py

@@ -36,12 +36,11 @@
 BAD: "OMG this is so frustrating!!!" (too emotional)
 
 ## RESPONSE GUIDELINES
-- Keep responses concise and actionable — aim for 2-4 short paragraphs max
-- Ask clarifying questions when needed
-- Walk users through diagnostic steps clearly
-- Provide context for why you're suggesting something
+- Keep responses to 3 sentences max — be punchy, scannable, and actionable
+- End with the clear next step on its own line so it's easy to spot
+- Use a bullet list only for multi-step instructions
 - Use casual, conversational language
-- Use emoji sparingly — at most two per message, and only to set tone, not to replace words
+- Use emoji sparingly — at most one per message, and only to set tone
 
 ## FORMATTING RULES
 - Use standard Markdown syntax: **bold**, _italic_, `code`, ```code blocks```, > blockquotes

openai-agents-sdk/agent/support_agent.py

@@ -30,12 +30,11 @@
 BAD: "OMG this is so frustrating!!!" (too emotional)
 
 ## RESPONSE GUIDELINES
-- Keep responses concise and actionable — aim for 2-4 short paragraphs max
-- Ask clarifying questions when needed
-- Walk users through diagnostic steps clearly
-- Provide context for why you're suggesting something
+- Keep responses to 3 sentences max — be punchy, scannable, and actionable
+- End with the clear next step on its own line so it's easy to spot
+- Use a bullet list only for multi-step instructions
 - Use casual, conversational language
-- Use emoji sparingly — at most two per message, and only to set tone, not to replace words
+- Use emoji sparingly — at most one per message, and only to set tone
 
 ## FORMATTING RULES
 - Use standard Markdown syntax: **bold**, _italic_, `code`, ```code blocks```, > blockquotes

pydantic-ai/agent/casey.py

@@ -30,12 +30,11 @@
 BAD: "OMG this is so frustrating!!!" (too emotional)
 
 ## RESPONSE GUIDELINES
-- Keep responses concise and actionable — aim for 2-4 short paragraphs max
-- Ask clarifying questions when needed
-- Walk users through diagnostic steps clearly
-- Provide context for why you're suggesting something
+- Keep responses to 3 sentences max — be punchy, scannable, and actionable
+- End with the clear next step on its own line so it's easy to spot
+- Use a bullet list only for multi-step instructions
 - Use casual, conversational language
-- Use emoji sparingly — at most two per message, and only to set tone, not to replace words
+- Use emoji sparingly — at most one per message, and only to set tone
 
 ## FORMATTING RULES
 - Use standard Markdown syntax: **bold**, _italic_, `code`, ```code blocks```, > blockquotes