// Plugin-first doctrine and runtime engine for developer tools, plugin shells, agentic systems, memory and continuity, shell and terminal workflows, build and deploy posture, deterministic data processing, cross-platform strategy, and bridge-shaped language specialists. 适用于开发工具、插件壳层、记忆连续性、终端工作流、构建部署、数据处理与跨平台治理场景。
[HINT] SKILL.md 및 모든 관련 파일을 포함한 전체 스킬 디렉토리를 다운로드합니다
| name | developer-tool |
| version | 4.1 |
| description | Plugin-first doctrine and runtime engine for developer tools, plugin shells, agentic systems, memory and continuity, shell and terminal workflows, build and deploy posture, deterministic data processing, cross-platform strategy, and bridge-shaped language specialists. 适用于开发工具、插件壳层、记忆连续性、终端工作流、构建部署、数据处理与跨平台治理场景。 |
| metadata | {"absorbs":["auto-build","building-clis","code-logic","code-quality","code-reviewer","codebase-documenter","codemapper","dev-specialismsinit-local-tooling","diagram-generator","draw-io","excalidraw","github-actions-templates","graphviz-dot-generator","init-project","parallel-debugging","plantuml-diagram-generator","project-setup","verification-before-completion","penetration-tester","accessibility-tester","error-detector","error-coordinator","performance-testing","performance-engineer","codebase-exploration","database-administrator","cpp-pro","kotlin-specialist","flutter-expert","php-pro","powershell-module-architect","powershell-ui-architect","mobile-developer","algorithmic-art","deployment-engineer","platform-engineer","network-engineer","event-driven-architect","build-engineer","legacy-modernizer","dependency-manager","git-workflow-manager","csv-data-wrangler","data-researcher","pdf-skill","docx-skill","documentation-engineer","librarian","mcp-developer","multi-agent-coordinator","cli-developer"]} |
A large engine stays usable only when doctrine, governance, staging, and runtime stop pretending to be the same layer. 只有当 doctrine、governance、staging 与 runtime 不再伪装成同一层时，大型引擎才真正可用。
This is the canonical runtime shell and doctrine control center for developer-tool.
It is no longer just a first-wave plugin-shell introduction. It now serves as the top-level runtime and doctrine gateway for a matured multi-subsystem engine that contains:
Use this engine when the task involves:
developer-toolREADME.mdINVENTORY.mdABSORPTION_MATRIX.mdTRIGGER_SCOPE.mdreferences/INDEX.mdreferences/source-reservoir-map.mdai-agent-memory/README.mdagentic-system-basis/README.mdtool-ecosystem/README.mdshell-and-terminal/README.mdbuild-and-deploy/README.mddata-processing/README.mdcross-platform-development/README.mdlanguage-specialists/README.mdskills/ai-agent-memory/SKILL.mdskills/agentic-system-basis/SKILL.mdskills/tool-ecosystem/SKILL.mdskills/shell-and-terminal/SKILL.mdskills/build-and-deploy/SKILL.mdskills/data-processing/SKILL.mdskills/cross-platform-development/SKILL.mdskills/language-specialists/SKILL.mdcommands/prime/tool-runtime.mdcommands/prime/agentic-system-surface.mdcommands/prime/memory-surface.mdcommands/prime/tool-ecosystem-surface.mdcommands/prime/shell-and-terminal-surface.mdcommands/prime/build-and-deploy-surface.mdcommands/prime/data-processing-surface.mdcommands/prime/cross-platform-surface.mdcommands/prime/language-specialists-surface.mdcommands/route/choose-tool-surface.mdcommands/audit/plugin-structure.mdagents/memory-diagnostician.mdagents/agentic-system-diagnostician.mdagents/tool-ecosystem-diagnostician.mdagents/shell-terminal-diagnostician.mdagents/build-deploy-diagnostician.mdagents/data-processing-diagnostician.mdagents/cross-platform-diagnostician.mdagents/language-specialists-diagnostician.mdagents/plugin-auditor.mdagents/tooling-integrator.mdagents/shell-safety-reviewer.mdreferences/agentic-system-basis/INDEX.mdreferences/agentic-system-basis/activation-model.mdreferences/agentic-system-basis/runtime-activation-patterns.mdreferences/agentic-system-basis/bootstrap-capability-detection.mdreferences/agentic-system-basis/ensemble-team-governance.mdreferences/agentic-system-basis/factory-pipeline-autonomy-and-gate-model.mdreferences/ai-agent-memory/INDEX.mdreferences/memory-systems-overview.mdreferences/ai-agent-memory/memory-systems.mdreferences/ai-agent-memory/continuity-control-plane.mdreferences/ai-agent-memory/search-before-act-enforcement.mdreferences/tool-ecosystem/INDEX.mdreferences/plugin-runtime-overview.mdreferences/tool-ecosystem/core-shell-patterns.mdreferences/tool-ecosystem/component-model.mdreferences/tool-ecosystem/validation-audit-patterns.mdreferences/shell-and-terminal/INDEX.mdreferences/shell-and-terminal/shell-terminal.mdreferences/shell-and-terminal/runtime-shell-governance.mdreferences/shell-and-terminal/portable-session-workflows.mdreferences/build-and-deploy/INDEX.mdreferences/build-and-deploy/build-deploy.mdreferences/build-and-deploy/release-governance.mdreferences/build-and-deploy/deployment-orchestration-patterns.mdreferences/build-and-deploy/supply-chain-governance.mdreferences/data-processing/INDEX.mdreferences/data-processing/data-processing.mdreferences/data-agent-workflows.mdreferences/cross-platform-development/INDEX.mdreferences/cross-platform-development/cross-platform.mdreferences/language-specialists/INDEX.mdreferences/language-specialists/language-specialists.mdThis backbone is the primary developer-tool doctrine surface. If the shell cannot route into these pages cleanly, it is not doing its job.
Use this quick mapping when deciding what to load first:
| Pressure | First Owner |
|---|---|
| Recall, continuity, history lanes, working-state, trigger ownership | ai-agent-memory/README.md |
| Activation, bootstrap, orchestration, ensemble, autonomy | agentic-system-basis/README.md |
| Plugin shell law, component selection, commands, hooks, MCP, validation | tool-ecosystem/README.md |
| Shell scripting, terminal posture, portable sessions, shell safety | shell-and-terminal/README.md |
| CI/CD, release, deployment, supply-chain trust | build-and-deploy/README.md |
| Extraction, normalization, transformation, structured outputs | data-processing/README.md |
| Portability targets, support tiers, shared-core vs platform shell | cross-platform-development/README.md |
| Bridge-shaped specialist language guidance | language-specialists/README.md |
If two subsystems appear relevant, choose the one that owns the earliest or most expensive boundary mistake.
When the task is developer-tool heavy:
This engine exists to make tooling and runtime reasoning structured, layered, and resistant to donor sprawl.
Bridge skills classify the task and route into the correct subsystem doctrine. They should not duplicate the whole doctrine tree.
Commands own explicit prime, route, and audit workflows. They should not become giant tutorial documents in disguise.
Agents own bounded diagnosis, audit, and integration reasoning. They should not replace the doctrine center or become generalist dumping grounds.
Hooks remain conservative lifecycle assistance:
Rules freeze mature shell law for:
They should harden stable law, not immature judgment.
| Layer | Owner | Role |
|---|---|---|
| Canonical doctrine | developer-tool/references/ and canonical subtree docs | stable knowledge center |
| Root control plane | root docs and subsystem governance docs | routing, classification, promotion, runtime and staging boundary control |
| Staging layers | selected subtree staging zones | adapted complexity not yet flattened into canonical doctrine |
| Runtime shell | plugin shell surfaces under developer-tool and related plugins | activation, routing, lifecycle, bounded operational workflows |
| Donor reservoirs | preserved donor families or archived sources | upstream pattern supply, not direct runtime UX |
The shell should make the right doctrine easier to reach than the wrong source.
developer-tool often borders other heavy engines.
Default ownership law:
developer-tool owns shell/runtime/tooling architecture, memory control planes, build/deploy posture, and cross-domain control surfacesrust-coding-engine owns Rust-side structural and systems-language truthtypescript-coding-engine owns TypeScript-side type, runtime-validation, and TS-interoperability truthdev-designer-utility owns visual/design-system and artifact-generation truth when the issue is design-led rather than tooling-ledThe doctrine is:
developer-tool focused on runtime shell, governance, orchestration, and multi-domain control-plane truthdeveloper-tool is now a matured multi-subsystem heavy engine in canonical deep fusion.
What is already true:
What remains true:
This shell intentionally stays conservative:
The shell is the operational layer. Doctrine and governance remain the main sources of truth.
The reusable lesson is not:
“developer-tool is a plugin with lots of absorbed tooling content.”
The reusable lesson is:
“the
developer-toolshell is a doctrine-first control center for multi-domain tooling work: it routes by real control-plane, runtime, memory, delivery, data, and platform pressure; keeps runtime surfaces bounded; preserves subsystem doctrine as the primary knowledge center; and prevents staging or donor abundance from silently becoming shell truth.”