بنقرة واحدة
intercultural-discourse
Cross-cultural communication frameworks for understanding discourse patterns across cultures
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Cross-cultural communication frameworks for understanding discourse patterns across cultures
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Instruction manual for agents driving Port Daddy multi-agent coordination. Use when an agent will edit a repo, recover work, coordinate with other sessions, inspect FleetBar/Fleet Control Center truth, package skill/docs surfaces, or leave a durable handoff. NOT for generic coding that does not need Port Daddy state.
Contributor manual for agents working ON the Port Daddy codebase itself — the daemon, MCP server, FleetBar / Fleet Control Center, website, CLI surface, distribution mirrors, internal recovery ledger, and the named internal actors (Coxswain / Navigator / Cartographer / Lookout / Quartermaster + Shipwright). Use when editing the port-daddy repo. NOT for agents using Port Daddy on other projects (use port-daddy-agent-skill for that), and NOT distributed to public skill catalogs — this skill is private to the port-daddy repo.
Decide which single operator surface — Scout, FleetBar, or pd-console — owns each capability by its distance-from-work (intake/ambient/deep), and audit that placement for authority spread, unenforceable controls, evidence overflow into FleetBar, and hot/cool bus-subscription mismatches. Use when placing a new capability on one of Agent Harbor's three operator surfaces, reconciling a mockup that duplicates a capability across two surfaces, or auditing an existing operator-surface spec before implementation locks it in. NOT for choosing SDK/CLI/MCP/GUI surfaces for API-consuming developers (developer-surface-strategist), designing the concrete interaction flow within one already-assigned surface (agentic-coding-ux-designer), or the hot-bus/cool-bus transport mechanics themselves (swarm-invocation-designer).
Audit what PRs this session produced. Ask: "What work did I do this session that isn't in a PR yet, or isn't merged?" Forces the agent to account for all code changes before declaring done. Use at any point — especially at session end, after a manager wave, or when asked "what's left?"
After each execution wave completes, inspect the DAG's commitment landscape and premortem risk score. If any surviving nodes carry `commitment_level: TENTATIVE`, or if the premortem `recommendation` is `ACCEPT_WITH_MONITORING` or `ESCALATE_TO_HUMAN`, pause execution and run a structured parley: re-evaluate TENTATIVE nodes against the evidence produced by the just-completed wave, update risk severity where warranted, and either promote nodes to COMMITTED, demote them to EXPLORATORY, or prune them before launching the next wave. Parley is a scheduled operation triggered by wave completion — not an ad-hoc intervention — making wave boundaries the natural formation-break point where plans meet reality.
Build and extend pd-console — Port Daddy's GPU-native macOS operator console (GPUI 0.2.x, Zed's Rust UI). Covers the render-agnostic Block/Pane(Surface) contract, the two-thread reqwest↔smol refresh pipeline, Taffy flexbox layout, uniform_list virtual scroll, focus + keyboard nav, the OKLCH theme and ICS maritime flag badges, GPUI's missing text-input, and the real feature-gated cargo/CI gate. Use when adding panes, visual polish, or debugging GPUI rendering/layout/focus in core/pd-console. NOT for the TypeScript daemon, generic Rust toolchain/borrow-checker help (use rust-with-claude-code), or non-pd GPUI apps with a different theme/architecture.
| license | Apache-2.0 |
| name | intercultural-discourse |
| description | Cross-cultural communication frameworks for understanding discourse patterns across cultures |
| metadata | {"category":"Cognitive Science & Decision Making","tags":["intercultural","communication","discourse","cross-cultural","pragmatics"],"io-contract":{"kind":"deliverable","produces":[{"kind":"critique","description":"Multi-framework analysis of cross-cultural discourse identifying hidden breakdowns, power dynamics, and culturally-specific communication patterns that surface-level coding misses","format":"markdown"},{"kind":"refactor-plan","description":"Structured recommendations for reframing interaction analysis when initial single-framework results appear suspiciously clean or culturally misaligned","format":"markdown"},{"kind":"design-doc","description":"Decision framework documentation for selecting appropriate analytical approach (single vs. layered vs. emergent vs. foregrounded cultural analysis) based on context and power dynamics","format":"markdown"}]}} |
| allowed-tools | Read,Write,Edit,Glob,Grep |
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
references/asymmetry-status-and-the-pre-determined-interaction.md — Examines how status asymmetry shapes what gets said, suppressed, and validated in structured interactions. Read when analyzing power dynamics in hierarchical discourse.
references/coding-systems-and-the-limits-of-surface-analysis.md — Explains why coding systems capture surface patterns but miss illocutionary intent and hidden breakdowns. Read when surface-level coding produces suspiciously clean results.
references/communicative-breakdown-as-primary-data.md — Inverts standard analysis: treats breakdown as informatively rich, not noise. Read when identifying what failure points reveal about topic sensitivity.
references/contingency-and-formality-in-structured-exchanges.md — Maps spectrum from casual to formal interaction; extends with contingency concept. Read when determining how exchange structure constrains participant options.
references/cultural-context-as-active-analytical-tool.md — Shifts context from background to active analytical layer. Read when deciding whether to apply cultural frameworks.
references/cultural-criteria-and-avoiding-anglocentric-evaluation.md — Documents Anglocentric bias in Western discourse analysis frameworks. Read when evaluating silence, minimal response, or elaboration patterns.
references/emergent-research-and-data-revisitation.md — Establishes data revisitation as principled strategy, not planning failure. Read when considering whether to reanalyze existing transcripts with new frameworks.
references/hidden-breakdown-and-face-sensitive-communication.md — Explains why high power-distance contexts hide breakdowns from surface coding. Read when analyzing interactions where participants seem comfortable despite apparent misalignment.
references/layers-of-insight-as-analytical-methodology.md — Demonstrates multi-framework depth through worked example (IRF + moves/acts + cultural criteria). Read when applying layered framework analysis.
references/layers-of-insight-multi-tool-interpretation.md — Methodological stance for using multiple frameworks simultaneously without premature synthesis. Read when managing contradictions between analytical frameworks.
references/multi-purpose-data-and-the-ethics-of-inference.md — Addresses ethical tension when data collected for one purpose is reanalyzed for another. Read when revisiting interview data for discourse patterns beyond original consent scope.
references/primary-knower-inversion-and-role-contamination.md — Analyzes how research interviews invert teacher-student primary knower roles, affecting response quality. Read when assessing reliability of participant self-reports in asymmetric contexts.
references/repair-sequences-as-diagnostic-windows.md — Treats repair as diagnostic of interaction quality, not noise. Read when analyzing where and how breakdown occurs.
references/surface-coding-vs-illocutionary-intent.md — Documents systematic gap between surface features and actual intent in cross-cultural discourse. Read when interpreting positive responses that may mask false comprehension.
references/the-methodology-of-revisiting-data.md — Explains how new analytical tools make previously analyzed data yield different insights. Read when planning data revisitation with emergent frameworks.
references/the-researcher-as-instrument-and-source-of-bias.md — Examines researcher influence on interview data and decision-making bias. Read when assessing how analyst positionality shapes findings.
references/the-semi-structured-approach-to-complex-inquiry.md — Contrasts semi-structured flexibility with fully-structured reproducibility trade-offs. Read when deciding whether to follow rigid protocol or adapt to emerging 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: