Run any Skill in Manus with one click

dubbo-admin-frontend

Stars4,047

Forks2,159

UpdatedMay 10, 2026 at 08:06

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

apache

apache/dubbo-admin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Web DevelopersComputer and Mathematical Occupations·SOC 15-1254

File Explorer

4 files

SKILL.md

readonly

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.

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 in src/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.md for 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, or yarn 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.md for directory and route patterns.
Read references/traffic-rule-forms.md for traffic form design and round-trip checks.

More from this repository

same repository

dubbo-admin-console-api

apache/dubbo-admin

Implements and reviews dubbo-admin Console API changes. Use when the user asks about HTTP endpoints, Gin routes, handlers, request or response models, console services, error handling, API pagination, or the handler to service to manager to store flow under pkg/console/. Do not use for frontend-only, discovery-only, or store-internals tasks unless they affect Console API behavior.

2026-05-104.0k

dubbo-admin-discovery

apache/dubbo-admin

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.

2026-05-104.0k

dubbo-admin-domain

apache/dubbo-admin

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.

2026-05-104.0k

dubbo-admin-engine

apache/dubbo-admin

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.

2026-05-104.0k

dubbo-admin-events

apache/dubbo-admin

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.

2026-05-104.0k

dubbo-admin-runtime

apache/dubbo-admin

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.

2026-05-104.0k

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.

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 in src/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.md for 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, or yarn 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.md for directory and route patterns.
Read references/traffic-rule-forms.md for traffic form design and round-trip checks.