tanaab-coding

To route coding tasks across multiple surfaces, activate tanaab-coding-core, select a single primary owning skill via the routing-matrix, and apply companion skills only when the task crosses surfaces like frontend or shell.

You need a routing matrix for orchestration when a coding task spans multiple surfaces such as testing, release, or documentation, requiring a decision to select one primary owner and ensure safe, auditable handoffs.

The best way to orchestrate coding, testing, and release requests is to identify a single primary owning skill using a routing matrix, ensuring correct surface routing and applying templates only when reusability is explicitly needed.

You should not apply companion skills and templates for every coding workflow; add companion skills only when a task crosses surfaces, and apply templates solely when scaffolding or reusability is explicitly required.

Unified routing works with executable surfaces and dist outputs by respecting user-facing artifacts during routing decisions, validating handoffs against bundled references to ensure safe and auditable task execution.

Designating a single primary owner for a multi-surface coding task ensures clear accountability, prevents conflicting logic across JavaScript or testing surfaces, and validates routing decisions against bundled references for safe handoffs.