What problem does it solve? Large plugin and tooling workspaces collapse into chaos when doctrine, governance, staging, and runtime layers blur together. This Skill provides a doctrine-first control center that routes developer-tooling tasks—memory continuity, agentic systems, shell workflows, build/deploy, data processing, cross-platform strategy—into the correct canonical lane instead of donor sprawl. ## Core Features & Use Cases - Subsystem Routing: A pressure router maps tasks to eight matured subsystems (ai-agent-memory, agentic-system-basis, tool-ecosystem, shell-and-terminal, build-and-deploy, data-processing, cross-platform-development, language-specialists) with explicit trigger ownership. - Layered Governance: Root control docs (INVENTORY, TRIGGER_SCOPE, ABSORPTION_MATRIX) freeze promotion rules so donor material becomes doctrine only through auditable staging, never direct runtime dependency. - Bounded Runtime Surfaces: Bridge skills, prime/route/audit commands, diagnostician agents, and conservative lifecycle hooks operationalize doctrine without replacing it. - Use Case: When asked how to structure a Claude Code plugin with memory continuity, the engine routes first to ai-agent-memory doctrine, escalates to governed staging only if needed, and invokes the violet-memory-lab runtime shell solely for push-based operational continuity. ## Quick Start Ask the assistant to classify your tooling, memory, shell, build, or cross-platform question and route it to the correct developer-tool subsystem doctrine before taking action.
