secondary-router: Скилл для маршрутизации доменов в Godot

--- name: secondary-router description: Tier 2 domain router for Godot workflows. Select domain-level skill clusters after Tier 1 foundation selection. tier: secondary godot_version: 4.6+ doc_anchors: - godot-docs/tutorials/best_practices/index.rst - godot-docs/getting_started/introduction/key_concepts_overview.rst tags: - routing - domains depends_on: - godot-skills/godot-foundations/foundation-router/SKILL.md --- # Secondary Router ## Use When - Tier 1 foundation skills are selected and you need domain-level execution focus. ## Outcomes - Domain scope is narrowed to the minimum relevant Tier 2 clusters. - Tier leakage is reduced before system-level (Tier 3) selection. - Routing decisions remain consistent across similar requests. ## Required Rules - Enter this router only after Tier 1 has been selected. - Select the smallest set of domains that covers the task. - Do not encode system/API specifics in domain selection notes. - Escalate to Tertiary only when a concrete Godot system must be chosen. ## Workflow 1. Translate task into one or more domain concerns. 2. Select matching domain skills and reject non-essential domains. 3. Document why each domain is required for current scope. 4. Identify likely Tier 3 contracts per selected domain. 5. Hand off to `tertiary-router` or a specific Tier 3 contract. ## Validation - Selected domains explain all task requirements without including unrelated clusters. - Re-running routing on the same task yields same domain set. - Tier 3 selection links cleanly back to chosen Tier 2 domains. ## Failure Modes - Domain over-selection creates unnecessary complexity and context switching. - Domain under-selection misses key constraints (for example networking + UI coupling). - Embedding API-level detail in Tier 2 causes abstraction leakage. ## Local Doc Anchors - `godot-docs/tutorials/best_practices/index.rst` - `godot-docs/getting_started/introduction/key_concepts_overview.rst`