dubbo-admin-domain
Routes dubbo-admin architecture questions to the right domain skill. Use for cross-module questions, end-to-end flows, subsystem boundaries, or deciding whether runtime, discovery, engine, events, store, Console API, or frontend guidance applies. Prefer a narrower dubbo-admin-* skill when the request clearly targets one subsystem.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 4.1k
- Forks
- 2.2k
01 前言 Front Matter
- name
- dubbo-admin-domain
- description
- Routes dubbo-admin architecture questions to the right domain skill. Use for cross-module questions, end-to-end flows, subsystem boundaries, or deciding whether runtime, discovery, engine, events, store, Console API, or frontend guidance applies. Prefer a narrower dubbo-admin-* skill when the request clearly targets one subsystem.
02 资源文件 14
- 参考文档evals/evals.json1.2 KB
- 参考文档references/anti-patterns.md9.6 KB
- 参考文档references/architecture-map.md4.4 KB
- 参考文档references/channel-economics-toolkit.md14.9 KB
- 参考文档references/core-frameworks.md11.1 KB
- 参考文档references/diagnostic-system.md4.4 KB
- 参考文档references/international-compliance-guide.md9.3 KB
- 参考文档references/landed-cost-calculator.md8.8 KB
- 参考文档references/marketplace-entry-playbook.md12.7 KB
- 参考文档references/new-digital-channels-guide.md12.6 KB
- 参考文档references/pop-up-execution-playbook.md9.6 KB
- 参考文档references/tariff-arbitrage-strategies.md9.0 KB
- 参考文档references/wholesale-pricing-calculator.md9.7 KB
- 参考文档references/work-modes-and-templates.md11.4 KB
03 SKILL.md 正文
dubbo-admin Domain Guide
Purpose
Use this skill to choose the right dubbo-admin domain workflow and avoid mixing registry discovery, runtime engine, EventBus, store, API, and frontend responsibilities.
When to use
Use for cross-module architecture, end-to-end data flow, skill selection, or issue triage that spans multiple subsystems.
Do not use when a request clearly targets one subsystem; load the narrower skill directly.
Inputs
Required:
- User goal, issue, file path, or subsystem name.
Optional:
- Stack trace, API path, frontend route, resource kind, or event type.
If missing, inspect top-level paths and identify the first concrete subsystem before loading a narrower skill.
Workflow
- Classify the request by primary subsystem.
- Select one narrow skill when possible.
- If the request spans multiple domains, order them by data flow: runtime/discovery or engine, events, store, manager, Console API, frontend.
- Read
references/architecture-map.mdwhen the boundary is unclear. - Avoid loading unrelated domain skills.
Output format
Return selected skill or skills, why they apply, which paths to inspect first, and any boundary assumptions.
Validation
- Confirm selected skill owns the code path being changed.
- Confirm cross-domain changes name both producer and consumer of data.
- If two skills overlap, state which one controls the contract.
Edge cases
- Registry discovery and runtime engine both use informers but source different data.
- EventBus dispatch is shared infrastructure; use
dubbo-admin-eventswhen dispatch behavior changes. - Store indexes are shared; use
dubbo-admin-storewhen query behavior changes.
References
- Read
references/architecture-map.mdfor subsystem ownership and end-to-end flow.
04 同仓库更多 Skills
dubbo-admin-store
Implements and reviews dubbo-admin resource storage and indexing changes. Use when the user asks about ResourceStore APIs, store routing, memory store behavior, index registration, IndexCondition, ListByIndexes, PageListByIndexes, ByMeshIndex, radix-tree prefix lookup, or pkg/core/store/, pkg/core/store/index/, and pkg/store/. Do not use for frontend, Console API, discovery, or engine tasks unless they require store or index changes.
dubbo-admin-runtime
Implements and reviews dubbo-admin runtime component changes. Use when the user asks about component abstraction, component composition, runtime bootstrap, dependency ordering, registration, lifecycle, startup, shutdown, runtime builder behavior, or pkg/core/runtime/ and pkg/core/bootstrap/. Do not use for discovery, engine, store, Console API, or frontend tasks unless component lifecycle or dependencies are affected.
dubbo-admin-frontend
Implements and reviews dubbo-admin Vue 3 frontend changes. Use when the user asks about ui-vue3, Vue views or components, frontend routing, route metadata, API clients, Pinia stores, SearchDomain, i18n, layout tabs, traffic rule form design, frontend tests, or Vite, ESLint, and Prettier configuration. Do not use for Go backend internals unless coordinating an API contract with the frontend.
dubbo-admin-events
Implements and reviews dubbo-admin EventBus dispatching. Use when the user asks about Event, Emitter, Subscriber, SubscriptionManager, EventBus component registration, Subscribe or Unsubscribe behavior, Send dispatch rules, subscriber ProcessEvent flow, resource-kind based routing, or event error handling under pkg/core/events/. Do not use for a domain subscriber unless the task changes the event bus contract or dispatch semantics.
dubbo-admin-engine
Implements and reviews dubbo-admin resource engine changes. Use when the user asks about runtime infrastructure discovery, engine factories, Kubernetes or mock engine ListWatchers, RuntimeInstance informers, RuntimeInstanceEventSubscriber, engine leader election, or merging RuntimeInstance data into Instance resources under pkg/core/engine/ and pkg/engine/. Do not use for registry discovery unless the task concerns engine-sourced RuntimeInstance resources.
dubbo-admin-discovery
Implements and reviews dubbo-admin registry discovery changes. Use when the user asks about Zookeeper or Nacos discovery, ListAndWatch, informers, discovery factories, discovery subscribers, ServiceProviderMetadata or ServiceConsumerMetadata processing, or Application, Service, RPCInstance, and Instance derivation under pkg/core/discovery/ and pkg/core/controller/. Do not use for engine-sourced RuntimeInstance behavior.