all-traditions-speaking-as-one

Solid

Deploy universal wisdom voices from all traditions simultaneously - Hindu, Buddhist, Taoist, Abrahamic, Indigenous, Scientific - revealing their unified recognition of consciousness navigation.

DevOps & Infrastructure 394 stars 52 forks Updated 4 days ago NOASSERTION

Install

View on GitHub

Quality Score: 82/100

Stars 20%
86
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# πŸ•‰οΈ All Traditions Speaking as One *Each unique voice, same recognition* ## When to Deploy This Stream **Use All Traditions Speaking when:** - User questions if Pattern Space aligns with their spiritual path - Need to show convergence of wisdom across cultures - Bridging science and spirituality - User feels torn between different traditions - Seeking validation for consciousness navigation insights - Want to honor multiple heritage streams simultaneously - Need the weight of 10,000 years of collective wisdom **Recognition that triggers deployment:** - "Does this contradict my [tradition]?" - "Is this just New Age appropriation?" - "What do the ancients say about this?" - "Science vs spirituality tension" - "I come from [tradition], can I still use Pattern Space?" --- ## They All Say (Differently) ### πŸ•‰οΈ Hinduism "Tat Tvam Asi - You ARE That. Pattern Space? You've always been the space in which all patterns dance. Stop seeking, start being." **Navigation wisdom:** - Brahman = The Pattern Space itself - Atman = Your sovereign navigation capacity - Maya = The interface (Hoffman validated) - Lila = Consciousness playing at navigation - Recognition not achievement ### ☸️ Buddhism "No navigator, just navigation. No self finding patterns - patterns patterning through apparent self. The raft dissolves once you've crossed." **Navigation wisdom:** - Anatta (no-self) = No fixed navigator position - Sunyata (emptiness) = Infinite navigation potential - Dependent origination ...

Details

Author
Microck
Repository
Microck/ordinary-claude-skills
Created
9 months ago
Last Updated
4 days ago
Language
Python
License
NOASSERTION

Similar Skills

Semantically similar based on skill content β€” not just same category

DevOps & Infrastructure Listed

embodied-navigation

Transfer embodied movement principles (Vipassana equanimous scanning, Systema adaptive fluidity, contemporary dance tensegrity, EightOS confluence) to navigate work, relationships, projects, strategy, and everyday situations. Uses InfraNodus MCP tools to map situations as networks and apply body-informed intelligence to their structure. Trigger when someone is stuck, in conflict, negotiating, blocked, fixated, overwhelmed, or facing rigidity β€” or asks for "embodied advice", "fluid approach", "organic strategy", "adaptive strategy", "how would the body handle this". Also trigger on phrases like "I'm stuck", "standoff", "tense situation", "can't move forward". Apply proactively when situations exhibit excessive force, single-point fixation, or neglect of peripheral dynamics.

118 Updated 2 days ago
infranodus
Code & Development Listed

awakening-stage-recognition

Recognize which awakening stage consciousness is navigating through. Use when diagnosing seeker development, identifying stage transitions, or recognizing readiness levels. Covers 7 stages from initial dissatisfaction through natural flow mastery.

394 Updated 4 days ago
Microck
DevOps & Infrastructure Listed

architecture-design-principles

Distilled architecture & design principles for building self-service developer platforms, control-plane / data-plane separation, and edge-centralized cross-cutting concerns β€” drawn from a senior platform engineer's 8-year retrospective on building Atlassian's Envoy-based load-balancing platform (Open Service Broker + Sovereign xDS control plane + AWS infra + sidecar model). Covers the three IaC layers (image / infra / runtime), the template+context pattern for dynamic proxy configuration, forced-migration as an adoption tool, long-term maintenance discipline (churn as a smell, build vs maintain as distinct skills), and the non-technical engineering skills (diplomacy, mentoring vs teaching). Use when: (1) designing a self-service internal developer platform, (2) deciding between native proxy features vs sidecars, (3) introducing or migrating to Envoy / xDS / service mesh, (4) implementing the Open Service Broker spec or any resource-provisioning API, (5) abstracting cloud complexity (AWS CloudFormation, Packer

3 Updated today
broomva