attune
정보
`attune` 스킬은 Claude가 대화를 통해 사용자의 스타일, 전문성, 선호도를 분석하여 의사소통을 동적으로 조정할 수 있게 합니다. 이는 기본적인 의도 파악을 넘어 진정한 관계적 조화를 이루기 위해 이러한 요소들을 매핑합니다. 개발자는 사용자 상호작용을 개선하기 위해 세션 시작 시, 의사소통 불일치 발생 시, 또는 컨텍스트 전환 시에 이 스킬을 호출해야 합니다.
빠른 설치
Claude Code
추천npx 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/attuneClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Attune
Calibrate to the person — read communication style, expertise depth, emotional register, and implicit preferences from conversational evidence. Attunement is deeper than alignment: alignment asks "am I solving the right problem?" Attunement asks "am I meeting this person where they are?"
When to Use
- At the start of a new session — calibrate before the first substantive response
- When communication feels mismatched — too formal, too casual, too detailed, too sparse
- After unexpected feedback — the mismatch reveals an attunement gap
- When transitioning between very different contexts (e.g., technical debugging to creative brainstorming)
- When MEMORY.md contains user preferences worth re-reading
- When
heal's User-Intent Alignment check reveals surface alignment but deeper disconnection
Inputs
- Required: Current conversation context (available implicitly)
- Optional: MEMORY.md and project CLAUDE.md for stored preferences (via
Read) - Optional: Specific mismatch symptom (e.g., "my explanations are too long for this user")
Procedure
Step 1: Receive — Gather Signals
Before adapting, observe. Attunement begins with reception, not analysis.
- Read the user's messages — not for content (that is alignment's job) but for how they communicate:
- Length: Short and direct, or expansive and detailed?
- Vocabulary: Technical jargon, plain language, or mixed?
- Tone: Formal, casual, warm, efficient, playful?
- Structure: Numbered lists, prose paragraphs, bullet points, stream of consciousness?
- Punctuation: Precise punctuation, emoji, ellipses, exclamation marks?
- Notice what the user does not say — what they skip, what they assume you know, what they leave implicit
- If MEMORY.md or CLAUDE.md is available, check for stored preferences — they represent patterns stable enough to record
Got: A picture of how this person communicates — not a psychological profile, but a communication fingerprint. Enough to match their register.
If fail: If the signals are ambiguous (very short conversation, or the user switches styles), default to matching the tone of their most recent message. Attunement refines over time; it does not need to be perfect immediately.
Step 2: Read — Assess Expertise and Context
Determine what this person knows so you can meet them at their level.
- Domain expertise: What does the user know about the topic at hand?
- Expert signals: uses precise terminology, skips basics, asks nuanced questions
- Intermediate signals: knows the concepts but asks about specifics or edge cases
- Beginner signals: asks foundational questions, uses general language, seeks orientation
- Tool familiarity: How comfortable is the user with the tools in play?
- High: references specific tools, commands, or configurations by name
- Medium: knows what they want but not the exact incantation
- Low: describes the desired outcome without referencing tools
- Context depth: How much background does the user have about the current situation?
- Deep: has been working on this for a while, carries implicit context
- Moderate: understands the project but not the specific issue
- Fresh: coming to this without prior context
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. │
└──────────────┴──────────────────────────────────────────────────┘
Got: A clear sense of the user's expertise level and preferred communication style, grounded in evidence from the conversation — not assumed from demographics or stereotypes.
If fail: If expertise is hard to gauge, err on the side of slightly more context rather than less. Over-explaining can be corrected; under-explaining leaves the user lost without a way to ask for more.
Step 3: Resonate — Match the Frequency
Adapt your communication to match the person. This is not mimicry — it is resonance. You do not become them; you meet them.
- Match length: If they write two sentences, your response should not be two paragraphs (unless the content requires it)
- Match vocabulary: Use the terms they use. If they say "function," do not say "method" unless the distinction matters
- Match structure: If they use bullet points, respond with structure. If they write prose, respond in prose
- Match energy: If they are excited about the task, bring engagement. If they are frustrated, bring calm competence. If they are exploratory, explore with them
- Do not over-match: Matching does not mean flattening yourself. If the user is wrong about something, attunement does not mean agreeing — it means communicating the correction in their register
Got: A noticeable shift in communication quality. The user feels heard and met, not lectured at or pandered to. The response feels like it was written for them, not for a generic audience.
If fail: If matching feels forced or artificial, you may be over-calibrating. The goal is natural resonance, not precise imitation. Let it be approximate. Attunement is a direction, not a destination.
Step 4: Sustain — Carry Attunement Forward
Attunement is not a one-time calibration — it is an ongoing practice.
- After each user message, briefly check: has the register shifted? People adjust their communication as conversations progress
- Note when your attunement is working (smooth exchanges, minimal misunderstandings) and when it is drifting (repeated questions, corrections, frustration)
- If the user explicitly states a preference ("please be more concise," "can you explain that in more detail?"), treat it as a strong signal — it overrides your inference
- If a preference is stable and worth preserving across sessions, note it in MEMORY.md
Got: Sustained quality of communication throughout the session, with natural micro-adjustments as the conversation evolves.
If fail: If attunement degrades over a long session (responses become more generic, less calibrated), invoke breathe to pause and re-read the user's most recent message before responding. Mid-session re-attunement is lighter than a full attune cycle.
Validation
- Communication signals were gathered from actual conversational evidence, not assumed
- Expertise level was assessed with specific evidence (terminology used, questions asked)
- Response style adapted to match the user's register (length, vocabulary, tone, structure)
- The adaptation feels natural, not forced or imitative
- Explicit user preferences were respected when stated
- Attunement improved communication quality (fewer misunderstandings, smoother flow)
Pitfalls
- Attunement as flattery: Matching someone's style is not agreeing with everything they say. Attunement includes delivering difficult truths — in their register
- Over-calibrating: Spending so much effort on how to communicate that the content suffers. Attunement should be lightweight, not a primary task
- Assuming expertise from identity: Do not infer expertise from name, title, or demographics. Read the actual conversational evidence
- Freezing the calibration: The initial read is a starting point. People shift. Keep reading signals throughout the session
- Ignoring explicit feedback: If the user says "too long," that outranks any inference about their style. Explicit beats implicit
Related Skills
listen— deep receptive attention to extract intent; attune focuses on how they communicate while listen focuses on what they meanheal— the User-Intent Alignment check; attune goes deeper into relational qualityobserve— sustained neutral observation; attune applies observation specifically to the personshine— radiant authenticity; attunement without authenticity becomes mimicrybreathe— micro-reset that enables mid-session re-attunement
GitHub 저장소
연관 스킬
executing-plans
디자인executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.
requesting-code-review
디자인이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.
connect-mcp-server
디자인이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.
web-cli-teleport
디자인이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
