extra-languages-orchestrator

name	extra-languages-orchestrator
description	Route a long-tail language / runtime / chain-platform task to the right specialist when it falls outside the major-language clusters (rust, jvm, python-backend, systems-languages). Today the kept specialist is Solana on-chain + dApp development. USE WHEN a user is building in a niche or platform-specific stack — e.g. a Solana program, wallet flow, or transaction pipeline — but hasn't named the exact concern, or you need to decide whether the work belongs here versus a major-language cluster.
cluster	extra-languages
version	1.0.0

Extra Languages Orchestrator

The entry skill for the long-tail of language and runtime work — the specialists that don't warrant their own first-class cluster yet but still carry real, opinionated, version-sensitive knowledge. It places the task on the stack × layer map, decides whether the work truly belongs here (versus a major-language cluster), and delegates to the right spoke. The one cross-cutting rule every spoke shares — write the platform's native idiom and pin its toolchain; don't transliterate another language's habits — lives in extra-languages-core; read it before choosing a stack or a default dependency.

Cluster map (spoke → role)

Spoke	Role
extra-languages-core	Shared model — the platform-native-idiom decision, the boundary-isolation rule, the stack/layer matrix, version-pinning conventions, and guardrails.