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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 4.1k
- Forks
- 2.2k
01 前言 Front Matter
- name
- dubbo-admin-frontend
- description
- 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.
02 资源文件 14
- 参考文档evals/evals.json1.2 KB
- 参考文档references/advanced-models.md5.1 KB
- 参考文档references/advanced-strategies.md9.3 KB
- 参考文档references/anti-patterns.md6.4 KB
- 参考文档references/awareness-mapping-guide.md10.7 KB
- 参考文档references/core-paradigms.md1.5 KB
- 参考文档references/diagnostic-system.md2.8 KB
- 参考文档references/frontend-structure.md4.3 KB
- 参考文档references/market-sizing-framework.md10.8 KB
- 参考文档references/scamper-innovation-model.md10.0 KB
- 参考文档references/spherical-scaling-system.md11.8 KB
- 参考文档references/traffic-rule-forms.md4.8 KB
- 参考文档references/voc-mining-playbook.md12.2 KB
- 参考文档references/work-modes-and-templates.md11.4 KB
03 SKILL.md 正文
dubbo-admin Frontend
Purpose
Use this skill to change or explain the Vue frontend while preserving routing, API, state, layout, i18n, and traffic-rule form patterns.
When to use
Use for ui-vue3/ changes, route definitions, views, components, API clients, Pinia stores, tabs, SearchDomain pages, traffic rule forms, and frontend validation.
Do not use for backend-only logic unless frontend API contracts are affected.
Inputs
Required:
- Frontend route, view, component, or user workflow.
- Intended UI behavior or API contract.
Optional:
- Backend endpoint or payload.
- Screenshot or user interaction path.
- Existing page to mirror.
If missing, start from ui-vue3/src/router/defaultRoutes.ts and identify the view.
Workflow
- Locate the route in
ui-vue3/src/router/defaultRoutes.ts. - Read the view under
ui-vue3/src/views/and nearby components or composables. - Check API calls in
ui-vue3/src/api/and request behavior insrc/base/http/request.ts. - Use shared components and layout patterns before adding new abstractions.
- Update Pinia state, i18n keys, and tests when user-visible behavior changes.
- Read
references/traffic-rule-forms.mdfor routing, dynamic config, or tag rule forms.
Output format
Return changed UI flow, route or component paths, API contract impact, validation commands, and any screenshot or browser-test gap.
Validation
- Run the smallest relevant command:
yarn lint,yarn type-check,yarn test:unit, oryarn build. - Confirm request payloads match backend models.
- Confirm new user-facing text has i18n keys.
- For traffic forms, confirm form and YAML paths round-trip the same data.
Edge cases
- Mesh is injected by the Axios request layer; avoid duplicate mesh handling unless required.
- Tabbed detail pages rely on route metadata and layout state.
- If backend response fields change, check both API client types and view usage.
References
- Read
references/frontend-structure.mdfor directory and route patterns. - Read
references/traffic-rule-forms.mdfor traffic form design and round-trip checks.
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-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-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.
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.