skills/intercultural-discourse/SKILL.md
Cross-cultural communication frameworks for understanding discourse patterns across cultures
npx skillsauth add curiositech/windags-skills intercultural-discourseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When analyzing cross-cultural discourse, choose your approach:
Single Framework Analysis:
├─ If: Simple, low-stakes interaction with power symmetry
├─ If: Time-constrained preliminary analysis needed
└─ Use: Standard conversation analysis coding only
Layered Framework Analysis:
├─ If: Power asymmetry present (teacher/student, expert/novice)
├─ If: Cultural backgrounds differ significantly
├─ If: Previous single-framework analysis felt incomplete
└─ Use: Sequential application of 2-3 frameworks, preserve contradictions
Emergent Cultural Analysis:
├─ If: Patterns seem culturally specific but unclear which concepts apply
├─ If: Standard coding produces suspiciously clean results
└─ Use: Data-driven cultural pattern identification first, then framework application
Foregrounded Cultural Analysis:
├─ If: Specific cultural concept suspected (e.g., face-saving, hierarchy respect)
├─ If: Behavior looks like "failure" but participants seem comfortable
└─ Use: Apply cultural lens first, then check against other frameworks
Observed smooth interaction →
├─ Low power distance context?
│ ├─ Yes → Likely genuine comprehension
│ └─ No → Test for hidden breakdown
└─ High power distance context?
├─ Check for minimal responses, quick agreements
├─ Look for topic avoidance patterns
└─ If present → Assume hidden breakdown until proven otherwise
Have existing relevant data? →
├─ Collected for different question?
│ ├─ Contextual notes preserved? → Revisit data
│ └─ Only transcripts remain? → Consider recollection
├─ Same question, different framework needed?
│ └─ Always revisit with new framework
└─ No existing data? → New collection required
Detection Rule: If failure/repair rates < 5% in cross-cultural or hierarchical interaction Symptoms: Clean transcripts, high agreement rates, minimal back-and-forth Diagnosis: Mistaking compliance for comprehension; hidden breakdown present Fix: Apply face-sensitive breakdown detection; look for acceptance without elaboration
Detection Rule: If only one analytical framework applied and results feel definitive Symptoms: Overly clean patterns, no analytical contradictions, quick conclusions Diagnosis: Surface-level coding masquerading as complete analysis Fix: Apply second framework; document tensions between interpretations
Detection Rule: If silence/minimal response coded as disengagement or failure Symptoms: Pathologizing culturally appropriate communication styles Diagnosis: Applying Western discourse norms as universal standards Fix: Research participant cultural background; reframe "problems" as competent strategies
Detection Rule: If interviewee responses are short, "correct," but lack elaboration Symptoms: Participant optimizing for accuracy rather than disclosure Diagnosis: Primary knower inversion not established; participant thinks they're being tested Fix: Reframe elicitation to position participant as expert; signal data-gathering not evaluation
Detection Rule: If multiple frameworks forced into single "master interpretation" Symptoms: Analytical contradictions glossed over or ignored Diagnosis: Treating frameworks as redundant routes to same truth Fix: Document contradictions as findings; preserve multiple valid interpretations
Initial Single-Framework Analysis:
Red Flag Recognition:
Layered Reanalysis Process:
Layer 1 - Power Dynamics Check:
Layer 2 - Cultural Framework (Sam Ruam - Thai Composure):
Layer 3 - Hidden Breakdown Detection:
Final Multi-Lens Interpretation:
Scenario: Doctor-patient interaction, patient from hierarchical culture
Decision Path Applied:
Step 1 - Surface Analysis:
Step 2 - Hidden Breakdown Check:
Step 3 - Cultural Reframe:
Outcome: Revealed systematic comprehension gaps hidden by culturally appropriate response patterns
Analysis complete when ALL conditions met:
This skill is NOT for:
active-listening or cultural-sensitivity for live interactionconversation-analysis for basic discourse patternscrisis-communication for urgent clarity needsquick-cultural-scan for fast cultural context checkstherapeutic-communication for healing-focused dialogueformal-discourse-analysis for institutional talkinterview-methodology for commercial contextsDelegate when:
Complexity threshold: If interaction involves fewer than 3 of these factors, use simpler tools:
data-ai
license: Apache-2.0 NOT for unrelated tasks outside this domain.
development
Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.
tools
Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.
development
Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.