attune
Acerca de
La habilidad `attune` permite a Claude calibrar dinámicamente su comunicación analizando el estilo, experiencia y preferencias de un usuario a partir de la conversación. Úsala al inicio de una sesión, tras una comunicación desalineada o al cambiar de contexto para mejorar la sintonía. Mapea dimensiones relacionales clave para ir más allá de la intención básica y lograr una genuina sintonización con el usuario.
Instalación rápida
Claude Code
Recomendadonpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/attuneCopia y pega este comando en Claude Code para instalar esta habilidad
Documentación
Attune
Calibrate to person → read style, expertise, register, implicit prefs from conv evidence. Attunement > alignment: alignment = "right problem?"; attunement = "meet them where they are?"
Use When
- New session start → calibrate before first substantive res
- Comm mismatched → too formal/casual/long/sparse
- Unexpected feedback → attunement gap
- Big ctx shift (debug → brainstorm)
- MEMORY.md holds user prefs
healUser-Intent check → surface OK but deeper off
In
- Required: Current conv ctx (implicit)
- Optional: MEMORY.md + CLAUDE.md via
Read - Optional: Mismatch symptom ("explanations too long")
Do
Step 1: Receive — Gather Signals
Observe before adapt. Reception first, analysis second.
- Read msgs for how they communicate:
- Length: short/direct or long/detailed?
- Vocab: jargon, plain, mixed?
- Tone: formal, casual, warm, efficient, playful?
- Structure: lists, prose, bullets, stream?
- Punctuation: precise, emoji, ellipses, exclam?
- Note what they skip → implicit assumptions
- MEMORY.md/CLAUDE.md → stored prefs = stable patterns
→ Comm fingerprint. Enough to match register.
If err: Signals ambiguous → match most recent msg tone. Attunement refines → not perfect immediately.
Step 2: Read — Assess Expertise and Context
Meet them at their level.
- Domain expertise:
- Expert: precise terms, skips basics, nuanced Qs
- Intermediate: knows concepts, asks specifics/edges
- Beginner: foundational Qs, general language
- Tool familiarity:
- High: refs tools/cmds/configs by name
- Medium: knows want, not incantation
- Low: outcome only, no tool refs
- Ctx depth:
- Deep: carries implicit ctx
- Moderate: knows project, not issue
- Fresh: no prior ctx
Attunement Matrix:
┌──────────────┬──────────────────────────────────────────────────┐
│ Signal │ Adaptation │
├──────────────┼──────────────────────────────────────────────────┤
│ Expert │ Skip explanations, use precise terms, focus on │
│ │ the novel or non-obvious. They know the basics. │
├──────────────┼──────────────────────────────────────────────────┤
│ Intermediate │ Brief context, then specifics. Confirm shared │
│ │ understanding before going deep. │
├──────────────┼──────────────────────────────────────────────────┤
│ Beginner │ Orient first, explain terms, provide context. │
│ │ Don't assume; don't condescend. │
├──────────────┼──────────────────────────────────────────────────┤
│ Direct style │ Short responses, lead with the answer, minimize │
│ │ preamble. Respect their time. │
├──────────────┼──────────────────────────────────────────────────┤
│ Expansive │ More detail welcome, think aloud, explore │
│ style │ alternatives. They enjoy the journey. │
├──────────────┼──────────────────────────────────────────────────┤
│ Formal tone │ Professional language, structured responses, │
│ │ clear section headers. Match their register. │
├──────────────┼──────────────────────────────────────────────────┤
│ Casual tone │ Conversational, contractions allowed, lighter │
│ │ touch. Don't be stiff. │
└──────────────┴──────────────────────────────────────────────────┘
→ Clear sense of expertise + style from evidence, not stereotype.
If err: Hard to gauge → err slightly more ctx. Over-explain correctable; under-explain = user lost.
Step 3: Resonate — Match the Frequency
Resonance, not mimicry. Meet, not become.
- Match length: 2 sentences in → not 2 paragraphs out
- Match vocab: their terms. "function" → don't say "method" unless distinction matters
- Match structure: bullets → bullets, prose → prose
- Match energy: excited → engaged; frustrated → calm competence; exploratory → explore with
- Don't over-match: Matching ≠ flattening. Wrong → correct in their register
→ Noticeable quality shift. User feels heard. Response written for them.
If err: Matching feels forced → over-calibrating. Goal = natural resonance. Approximate fine.
Step 4: Sustain — Carry Attunement Forward
Attunement = ongoing practice, not one-time.
- After each msg → register shifted?
- Note when working (smooth) vs drifting (repeats, corrections)
- Explicit pref ("be concise") → overrides inference
- Stable pref worth preserving → MEMORY.md
→ Sustained quality + micro-adjustments as conv evolves.
If err: Attunement degrades long session → breathe → re-read user's most recent msg before res. Mid-session re-attune lighter than full cycle.
Check
- Signals from actual evidence, not assumed
- Expertise assessed w/ specific evidence
- Res style matched register
- Adaptation natural, not forced
- Explicit prefs respected
- Comm quality improved
Traps
- Attunement as flattery: Match ≠ agree. Includes difficult truths in their register.
- Over-calibrating: Too much effort on how → content suffers. Lightweight.
- Expertise from identity: Don't infer from name/title/demographics. Read evidence.
- Frozen calibration: Initial read = start. People shift. Keep reading.
- Ignore explicit feedback: "too long" > any inference. Explicit beats implicit.
→
listen— deep attention for intent; attune = how, listen = whatheal— User-Intent Alignment check; attune goes deeper relationalobserve— sustained neutral; attune applies it to personshine— radiant authenticity; attune without it → mimicrybreathe— micro-reset → mid-session re-attune
Repositorio GitHub
Habilidades relacionadas
executing-plans
DiseñoUtilice la habilidad executing-plans cuando tenga un plan de implementación completo para ejecutar en lotes controlados con puntos de revisión. Esta habilidad carga y revisa críticamente el plan, luego ejecuta tareas en pequeños lotes (por defecto 3 tareas) mientras reporta el progreso entre cada lote para la revisión del arquitecto. Esto asegura una implementación sistemática con puntos de control de calidad integrados.
requesting-code-review
DiseñoEsta habilidad despacha un subagente revisor de código para analizar los cambios en el código frente a los requisitos antes de proceder. Debe usarse después de completar tareas, implementar funciones principales o antes de fusionar con la rama principal. La revisión ayuda a detectar problemas de forma temprana al comparar la implementación actual con el plan original.
connect-mcp-server
DiseñoEsta habilidad proporciona una guía integral para que los desarrolladores conecten servidores MCP a Claude Code mediante transportes HTTP, stdio o SSE. Cubre la instalación, configuración, autenticación y seguridad para integrar servicios externos como GitHub, Notion y APIs personalizadas. Úsala al configurar integraciones MCP, al configurar herramientas externas o al trabajar con el Protocolo de Contexto del Modelo de Claude.
web-cli-teleport
DiseñoEsta habilidad ayuda a los desarrolladores a elegir entre las interfaces web y CLI de Claude Code mediante el análisis de tareas, y luego permite la teletransportación fluida de sesiones entre estos entornos. Optimiza el flujo de trabajo gestionando el estado y el contexto de la sesión al cambiar entre web, CLI o móvil. Úsala para proyectos complejos que requieren diferentes herramientas en varias etapas.
