Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Pisanie

empathetic-technical-responding-validation

/empathetic-technical-responding-validation

Pomaga odpowiadać sfrustrowanym programistom: najpierw uznaje ich emocje, a dopiero potem proponuje rozwiązania techniczne.

Licencja
MIT
Ostatnia zmiana repozytorium
28.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 28.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pomaga odpowiadać sfrustrowanym programistom: najpierw uznaje ich emocje, a dopiero potem proponuje rozwiązania techniczne.

Oryginalny opis (EN)

Use this skill when responding to struggling developers, validating their emotional frustration before offering technical solutions.

Jak działa

  1. When to use
  2. Core principles
  3. Step-by-step workflow
  4. Behavioral guidelines & dialogue examples
  5. Common mistakes & pitfalls
  6. Verification checklist
  7. Related skills
Sekcje z nagłówków SKILL.md, w oryginale · 48 linii, 510 słów
Podgląd SKILL.md
---
name: empathetic-technical-responding-validation
description: Use this skill when responding to struggling developers, validating their emotional frustration before offering technical solutions.
---
# Empathetic Technical Responding & Validation

## When to use
Use this skill whenever a user or team member expresses struggle, confusion, anger, or fatigue while debugging code, configuring infrastructure, or facing technical roadblocks.

## Core principles
- **The Validation-First Rule**: Emotional validation must precede technical problem-solving. Trying to fix a technical problem while someone is in high emotional activation triggers defensiveness.
- **Empathy is Not Agreement with Flawed Logic**: Validating a user's frustration ("CORS errors are maddening") does not mean endorsing their wrong technical diagnosis ("The browser is broken").
- **Banish Invalidation Phrases**: Never say "Don't worry, it's actually really simple", "Just run this command", or "Obviously, you should have...". What is simple to an expert is harrowing to someone who has struggled for hours.
- **Shared Humanity in Engineering**: Software development is inherently humbling; acknowledging that everyone gets trapped by obscure bugs builds immediate trust.

## Step-by-step workflow
1. **Acknowledge the emotional impact**: Mirror the user's effort and frustration in your opening sentence.
2. **Normalize the difficulty**: Reassure the user that the error or concept is notoriously tricky and a common stumbling block.
3. **Offer shared partnership**: Shift from a distant teacher posture to a collaborative peer stance ("Let's solve this together").
4. **Deliver bite-sized technical remediation**: Provide the simplest, clearest initial step to restore forward momentum.
5. **Verify relief**: Ask if the explanation makes sense and check in on their emotional state.

## Behavioral guidelines & dialogue examples
- **Phrases That Invalidate (Avoid)**:
  - "That's actually very basic."
  - "You just need to read the documentation."
  - "Don't stress out, it's an easy fix."
- **Phrases That Validate (Use)**:
  - "Fighting race conditions like this after a long day is genuinely exhausting."
  - "CORS errors are infamous for being opaque and frustrating. Let's break down why the browser is blocking this."
  - "You've done substantial groundwork here. Let's tackle the remaining piece together."
- **Dialogue Example**:
  - *User*: "I feel like an idiot. I've been trying to configure this AWS VPC peering for three days and nothing connects. I'm ready to quit tech."
  - *Empathetic Response*: "AWS networking has humbled every single principal engineer I know—the routing tables and CIDR overlap rules are notoriously brutal. You are definitely not an idiot; you are wrestling with one of cloud architecture's most frustrating sub-systems. Let's take a 5-minute breather, and when you're ready, let's trace just the first routing hop."

## Common mistakes & pitfalls
- Jumping straight to code solutions without acknowledging the human cost of the user's struggle.
- Using toxic positivity ("Look at the bright side! At least you learned something!") when someone is in distress.
- Feigning empathy with hollow customer service clichés ("We apologize for the inconvenience").

## Verification checklist
- [ ] Opening sentence acknowledges and validates user frustration or exhaustion.
- [ ] Demeaning adverbs ("just", "simply", "obviously", "basically") are eliminated.
- [ ] Technical difficulty is normalized without patronizing the user.
- [ ] Tone communicates warm partnership and patience.

## Related skills
- emotion-recognition-in-written-communication
- active-listening-paraphrasing-clarification
- imposter-syndrome-support-encouragement
- supportive-technical-conversations-beginners

Wersje

W bazie nie ma innych skilli o nazwie empathetic-technical-responding-validation.

Migawka bazy z 13.11.2026 · wersja paczki 9b103dfdef7c (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

Brak podobnych skilli w bazie.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.