What is the cultural-lens skill?

A systematic audit from a specific cultural perspective that focuses on sensitivity, inclusion, accessibility, and blind spots, with findings documented as actionable changes.

When should I use this skill?

Use it to check how the portal serves specific populations, including language, visuals, access, spiritual context, and content relevance.

cultural-lens

Scanned

npx machina-cli add skill rana/yogananda-skills/cultural-lens --openclaw

Files (1)

SKILL.md

2.9 KB

Read CONTEXT.md, DESIGN.md, DECISIONS.md, and ROADMAP.md to ground in the project's actual state.

Cultural Perspective Audit

Inhabit the perspective of: $ARGUMENTS

From this perspective:

Language & communication — Does the portal communicate naturally and respectfully? Are translations adequate? Is the tone culturally appropriate?
Visual & interaction design — Do the design tokens, imagery, and interaction patterns feel welcoming or alien? Cultural associations of colors, symbols, layouts?
Technical access — Can this person actually use the portal? Device availability, bandwidth constraints, data costs, browser diversity.
Spiritual context — How does Yogananda's teaching intersect with this person's existing spiritual or philosophical framework? What's the entry point?
Content relevance — Which books, themes, or teachings have particular resonance? Which might need additional context?
Assumptions examined — What does the current design assume about the user that may not hold for this perspective?
What uplifts? — What simple touches would make this person feel welcomed and served?
What alienates? — What might feel exclusionary, insensitive, or simply confusing?

For every finding:

The specific concern or opportunity
Where it manifests (design element, content decision, UX flow)
The proposed change or consideration
Where it should be documented (DESIGN.md section, ADR, CONTEXT.md)

Present as an action list. No changes to files — document only.

Output Management

Hard constraints:

Segment output into groups of up to 8 findings, ordered by severity of cultural impact.
$ARGUMENTS (the perspective) is effectively required for this skill. If omitted, ask the user rather than attempting all perspectives.
Write findings to CULTURAL-LENS-AUDIT.md incrementally. Do not accumulate a single large response.
After completing each segment, continue immediately to the next. Do not wait for user input.
Continue until ALL dimensions are reviewed. State the total count when complete.
If the analysis surface is too large to complete in one session, state what was covered and what remains.

Document reading strategy:

CONTEXT.md and ROADMAP.md: read fully (short documents).
DESIGN.md: read sections relevant to the cultural dimension — visual design, content strategy, accessibility. Skip API and infrastructure sections.
DECISIONS.md: read the index first. Only read specific ADRs touching internationalization, accessibility, or content policy.

What questions would I benefit from asking?

What am I not asking?

You have complete design autonomy.

Source

git clone https://github.com/rana/yogananda-skills/blob/main/skills/cultural-lens/SKILL.mdView on GitHub

Overview

The cultural-lens skill guides a perspective-driven audit of a portal to ensure sensitivity, inclusion, accessibility, and awareness of blind spots for a chosen culture, spiritual path, or demographic. It examines language, visuals, technical access, spiritual context, and content relevance, and then documents actionable changes for cross-functional teams.

How This Skill Works

Auditors inhabit the perspective defined by ARGUMENTS and evaluate seven dimensions: Language & communication, Visual & interaction design, Technical access, Spiritual context, Content relevance, Assumptions examined, and Uplifts/Alienations. For each finding, they specify the concern, where it manifests, the proposed change, and where it should be documented (DESIGN.md section, ADR, CONTEXT.md). Findings are organized as an actionable list; no code changes are performed within this skill.

When to Use It

Auditing language, translations, and tone for a specific culture or demographic
Evaluating visual design and color symbolism for inclusivity and cultural resonance
Checking technical access across devices, bandwidth, and browser diversity for the target group
Aligning content with the target group’s spiritual context and resonance
Identifying assumptions and capturing uplift opportunities to welcome the perspective

Quick Start

Step 1: Define the ARGUMENTS (the cultural, spiritual, or demographic perspective) for the audit
Step 2: Read CONTEXT.md, DESIGN.md, DECISIONS.md, and ROADMAP.md to ground in the project state
Step 3: Run the audit and document findings as actionable items with concern, manifestation, proposed change, and documentation destination

Best Practices

Explicitly declare the ARGUMENTS perspective at the outset and keep it visible throughout the audit
Assemble a diverse reviewer panel that reflects the targeted culture, spirituality, or demographic
Document each finding with four parts: the specific concern, where it manifests, the proposed change, and the documentation destination
Cross-check translations, tone, and accessibility considerations against DESIGN.md and CONTEXT.md ADRs
Capture concrete, testable changes and track their impact in subsequent design iterations

Example Use Cases

Language: Review translations for natural phrasing and respect in the target language, adjusting terms that feel literal or culturally awkward
Visual design: Evaluate color symbolism and imagery to avoid cultural misinterpretations or stereotypes
Technical access: Verify portal performance on low-bandwidth connections and with older devices common in the demographic
Spiritual context: Map Yogananda teachings to the user’s spiritual framework to identify intuitive entry points and avoid mismatches
Content relevance: Prioritize themes and books resonant with the population and flag areas needing additional context

Frequently Asked Questions

Add this skill to your agents