Research Shows Effective AI Prompting Is Cooperative Communication, Not Engineering

Communication Principles Over Engineering
A Reddit analysis of 80+ real user complaints about AI interactions reveals that roughly 60% of frustrations have a significant user communication component. These issues include vague prompts with no context about audience or purpose, no examples of what "good" looks like, unclear goals, and feedback loops where users say "make it better" without specifying what "better" means.
The remaining ~40% are genuine model limitations including hallucination, sycophancy, performance regression, context window drift, and safety over-filtering. Lakera, an AI security company whose platform processes millions of LLM interactions, independently reached the same conclusion: "most prompt failures come from ambiguity, not model limitations."
The Communication Framework
Researchers across linguistics, HCI, and AI have found that the principles that make human conversation work are the same principles that make AI prompting work. In 1975, philosopher Paul Grice identified four maxims of cooperative communication:
- Quantity: Be informative enough
- Quality: Be truthful
- Relation: Be relevant
- Manner: Be clear
In 2024, IBM researchers Miehling et al. extended this framework with two new maxims specifically for AI interaction:
- Benevolence: Don't generate harmful content
- Transparency: Acknowledge what you don't know
Every major AI failure mode maps to one of these six maxims. Hallucinations represent Quality violations. Overly verbose answers represent Quantity violations. Sycophancy represents Benevolence and Transparency violations.
Understanding these communication principles helps distinguish between "I gave a bad prompt" and "this is a real model limitation," allowing developers to stop endlessly rephrasing vague requests and instead recognize limitations, reduce blast radius, and work around them.
📖 Read the full source: r/ClaudeAI
👀 See Also

Anthropic publishes Champion Kit for Claude Code adoption
A playbook for engineers pushing Claude Code at their company: share reusable prompts, answer in public channels, and host a weekly show-and-tell thread — ~40 minutes total per week.

Claude Code Structure That Survived Multiple Real Projects
A developer shares a Claude Code setup that held up across 2-3 real projects with multiple skills, MCP servers, and agents. Key findings include using CLAUDE MD for consistency, splitting skills by intent, implementing hooks, and keeping context usage under 60%.

Guide: Running GitHub Copilot with Local LLM on Windows via Lemonade Server
A developer created a walkthrough for setting up GitHub Copilot to work with a local LLM on a Framework Desktop using Lemonade Server, addressing the lack of simple instructions for this configuration on Windows.

Optimizing Qwen3.5-9B on RTX 3070 Mobile with ik_llama.cpp: Config Tweaks and Benchmarks
A developer shares optimization findings for running Qwen3.5-9B Q4_K_M on an RTX 3070 Mobile 8GB GPU using ik_llama.cpp, achieving ~50 tokens/second generation speed and significant prompt evaluation improvements through configuration adjustments.