PrimeVue Plugin

The PrimeVue Plugin adds PrimeVue skills and the PrimeVue MCP server to Claude Code, Codex, GitHub Copilot, Cursor, or Gemini CLI. Plugins installed through GitHub Copilot CLI are also available in VS Code. Install the plugin when you want the assistant to follow PrimeVue-specific workflows as well as read the current component documentation.

The plugin is published from the primefaces/primeui-plugins repository. Use @primeui/cli for the same installation flow across supported assistants, or follow the manual setup for your client.

Installing the PrimeVue Plugin adds:

• Seven skills for PrimeVue implementation, setup, theming, accessibility, migration, and troubleshooting.
• The PrimeVue MCP server, configured with @primevue/mcp.
• The manifest required by the selected assistant.

PrimeNG and PrimeReact are separate plugins. Installing this plugin does not change your application or install PrimeVue dependencies in the project.

Each skill covers one type of PrimeVue work. The skills use @primevue/mcp when they need component APIs, examples, setup guides, or usage validation.

Skill names use the primevue- prefix because assistants may keep skills from several plugins in one shared namespace.

You do not need to select a skill manually. Describe the PrimeVue task and the router chooses the relevant workflow.

• The router checks that the project uses Vue and PrimeVue.
• The selected skill reads only the component or guide information needed for the task.
• When component metadata is available, the skill validates the final PrimeVue usage.
• If the documentation does not confirm a setup or API, the skill reports the limitation instead of guessing.

After implementation, run the checks required by your project, including type checking, tests, browser behavior, accessibility, and visual review where applicable.

Set --tool to the assistant you use. Keep --library primevue when you run the command outside a project or from a project that uses more than one PrimeUI library.

Use the same CLI to check the installation, update the plugin, or remove it. Each command applies only to PrimeVue in the selected assistant.

Run doctor when the plugin or MCP server is not working as expected. It checks the installation, starts the MCP server, confirms the available tools, and tests documentation retrieval and component validation. Checks that an assistant does not expose are reported as unsupported.

Claude Code, Codex, and GitHub Copilot can install the plugin directly from the public marketplace. For manual Cursor or Gemini CLI setup, clone the repository to a location you intend to keep because those clients use the selected plugins/primevue directory after installation.

Add the PrimeUI marketplace, then install only the PrimeVue plugin.

Add the PrimeUI marketplace, inspect its catalog, then install only the PrimeVue plugin. Use the interactive plugin browser to manage enablement.

Install the PrimeVue Plugin through GitHub Copilot CLI. VS Code automatically discovers plugins installed by Copilot CLI, so it does not need a separate plugin configuration.

For local setup, link the PrimeVue plugin directory into Cursor's local-plugin directory. Restart Cursor or run Developer: Reload Window after creating the link.

Validate the PrimeVue extension directory, then install it from the persistent checkout. Do not install from the repository root because it contains plugins for all three PrimeUI libraries.