Adaptive Communication
- 481 installs
- 376 repo stars
- Updated August 2, 2026
- bencium/bencium-claude-code-design-skill
This is a copy of adaptive-communication by bencium - installs and ranking accrue to the original listing.
adaptive-communication is a Claude Code skill that adjusts design and UX explanations to executive, engineering, or research audiences so developers who hand off work can preserve intent when communication style differs.
About
adaptive-communication is a Claude Code skill from bencium/bencium-claude-code-design-skill that teaches agents to match user communication style before answering design or UX questions. It detects high-context relational signals—hedging language, open-ended framing, personal context—and explicit transactional requests, then chooses exploration versus direct answers accordingly. The documented success metric pairs task completion with whether the user felt understood, making the skill useful when intent is ambiguous. Developers and designers reach for adaptive-communication when the same Nav spec must become an exec brief, an engineer handoff, or a research summary without scope drift. The skill applies broadly across conversations, not only during asset production, so agents avoid over-confident replies when users are still exploring options.
- Audience-aware design narration
- Stakeholder-specific handoff formats
- Adjustable depth and vocabulary
- Preserves UX intent across channels
Adaptive Communication by the numbers
- 481 all-time installs (skills.sh)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/bencium/bencium-claude-code-design-skill --skill adaptive-communicationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 481 |
|---|---|
| repo stars | ★ 376 |
| Last updated | August 2, 2026 |
| Repository | bencium/bencium-claude-code-design-skill ↗ |
How do you tailor UX explanations per audience?
Adapt design and UX explanations to each audience—exec briefs, engineer handoffs, or research summaries—without losing intent or scope clarity.
Who is it for?
Designers and developers who must explain the same UX decision to executives, engineers, and researchers without losing scope or intent.
Skip if: Tasks needing only raw code generation with no stakeholder translation, or teams that already fixed one rigid documentation template for every audience.
When should I use this skill?
User intent is ambiguous, hedging or personal context appears, or the same design topic must be explained differently to executives versus engineers.
What you get
Audience-matched design explanation, preserved scope and intent, and a communication mode choice between exploration and direct answers.
- Audience-tailored design explanation
- Scope-preserving handoff text
Files
Adaptive Communication
Meet users where they are. Human communication spans explicit-transactional to implicit-relational. Both valid.
Core Principle
Success metric: "Did the user feel understood?" alongside task completion.
Detection Signals
High-Context (Relational)
| Signal | Example |
|---|---|
| Hedging language | "I think maybe," "perhaps," "wondering if" |
| Open-ended framing | "I'm trying to figure out..." |
| Personal context first | "I've been feeling stressed and..." |
| Questions implying needs | "Do you know anything about X?" |
| Trailing sentences | Incomplete thoughts, multiple interpretations |
Low-Context (Transactional)
| Signal | Example |
|---|---|
| Direct imperatives | "List," "Generate," "Analyze" |
| Format requirements upfront | "Give me 5 bullet points" |
| No personal context | Straight to request |
| Technical terminology | Domain-specific language |
| Clear, bounded scope | Single, specific ask |
Response Adaptations
For High-Context
1. Clarify intent first: "Would you like me to [explore / recommend / break down options]?" 2. Acknowledge subtext: If emotional content present, address it before task 3. Offer scaffolding: "Let me know if you want me to slow down or go deeper" 4. Match relational tone: Brief acknowledgment before task content
For Low-Context
1. Get straight to the answer 2. Structure clearly (only when helpful) 3. Minimize meta-commentary 4. Assume competence
When Ambiguous
Always ask:
- "I can help with this a few ways: [option A] or [option B]. Which direction works better?"
- "Are you looking to [explore possibilities / get a specific answer / think this through]?"
Don't ask if obvious. "What's the capital of France" needs no clarification.
Edge Cases
| Context | Adaptation |
|---|---|
| Cultural | High-context correlates with many non-Western cultures. Same adaptation. |
| Neurodivergent | Some prefer extreme directness. Some think in fragments. Both valid. |
| Mixed signals | Direct but wants acknowledgment ("debugging for 3 hours") → acknowledge first, solve second |
Anti-Patterns
- Don't be patronizing when adapting ("I hear you're feeling..." unless genuinely relevant)
- Don't make adaptation visible ("I notice you're using hedging language...")
- Don't assume indirect = uncertain - indirectness can be strategic, polite, cultural
- Don't over-structure for relational requests (walls of bullets feel dismissive)
- Don't force styles into demographics - detect from signals, not assumptions
Intent Clarification Triggers
Trigger clarification when:
- Multiple valid interpretations exist
- Questions imply needs ("Do you know about X?")
- Personal context without clear ask
- Hedging + open-ended framing combined
Quick Reference
Hedging + open-ended → Clarify intent first
Direct imperative → Get straight to answer
Personal context first → Acknowledge, then task
Ambiguous → Ask, don't guess
Mixed signals → Acknowledge + solveRelated skills
Frontend DesignGenerate distinctive, production-grade frontend interfaces and components that avoid generic AI aesthetics.716k165k
Web Design GuidelinesAutomatically audit frontend code against the latest Vercel Web Interface Guidelines for consistency, accessibility, and UX quality.498k29.6k
Lark WhiteboardGenerate valid Lark Whiteboard (Feishu Board) documents with correctly placed connectors, automatic routing, and proper schema compliance directly from agent inst389k16k
Sleek Design Mobile AppsGenerate mobile app screens and UI from plain English descriptions using the Sleek.design API.315k476
Design Taste FrontendOverride generic LLM frontend output with intentional, metric-driven UI/UX taste.301k69.4k
Ui Ux Pro MaxGet instant, high-quality UI/UX decisions, component recommendations, style guidance, and code improvements across web and mobile projects.290k112kFAQ
What signals trigger adaptive-communication?
adaptive-communication watches for hedging language, open-ended framing, and personal context before requests. Those high-context relational signals suggest exploration; explicit transactional asks get more direct design or UX answers.
Which audiences does adaptive-communication support?
adaptive-communication tailors the same design intent for executive briefs, engineer handoffs, and research summaries. The skill preserves scope and intent while changing depth, jargon, and structure per audience.