caveman

Ultra-brief technical answers reduce token usage by dropping filler, articles, and hedging while preserving technical correctness. This structured prompting style minimizes conversational overhead and keeps responses dense during problem solving.

An action-first prompting style using a structured pattern like [thing] [action] [reason] provides the best format for step-by-step problem solving. It minimizes drift and ensures high-precision technical briefing without unnecessary conversational filler.

Ultra-brief technical writing does not compromise safety, as the style temporarily relaxes for security warnings, irreversible confirmations, and multi-step sequences. This ensures high-risk instructions remain clear and prevent misunderstood execution order.

You can use ultra-compressed communication mode for detailed technical explanations, as it maintains full technical substance while trimming verbose context. It applies structured action-reason-next-step patterns to deliver dense, accurate answers efficiently.

Avoid using a terse prompting style when providing security warnings, irreversible action confirmations, or complex multi-step sequences where execution order might be misunderstood. The style temporarily relaxes to ensure safety and clarity in these specific edge cases.