plugin-full-frontend-system-migration

Migrate Backstage plugins from the old frontend system to the new one.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/jacobduijzer/bimcollab-backstage-demo --skill plugin-full-frontend-system-migration-jacobduijzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-full-frontend-system-migration
Source: https://github.com/jacobduijzer/bimcollab-backstage-demo/tree/main/src/bimcollab/.agents/skills/plugin-full-frontend-system-migration
Command: npx skills add https://github.com/jacobduijzer/bimcollab-backstage-demo --skill plugin-full-frontend-system-migration-jacobduijzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @backstage/core-plugin-api, @backstage/frontend-plugin-api, and includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of migrating existing Backstage plugins to the new frontend system, ensuring backward compatibility is dropped and all functionalities are fully operational in the updated environment.

Core Features & Use Cases

  • Full Migration: Converts plugins from the old frontend system to the new one, removing all old system support.
  • Single App Usage: Ideal for internal plugins that only need to run in a single app.
  • Compatibility Removal: Removes backward compatibility, suitable for plugins ready to drop old system support.
  • Use Case: For example, a plugin developer can use this Skill to update a plugin that was previously running on the old frontend system to work exclusively with the new frontend system in Backstage.

Quick Start

Run the 'plugin-full-frontend-system-migration' skill to begin the migration process for your plugin.

Frequently Asked Questions about plugin-full-frontend-system-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Backstage plugins to the new frontend system?

To migrate Backstage plugins to the new frontend system, you run the migration script to convert existing plugins, dropping backward compatibility and ensuring all functionalities operate in the updated environment.

What does removing backward compatibility mean for Backstage plugin migration?

Removing backward compatibility means the migrated plugin drops all old frontend system support, relying exclusively on the new Backstage frontend system APIs for single-app usage or broader plugin distribution.

Can I use this migration approach for internal plugins running in a single app?

Yes, this migration approach is ideal for internal plugins that only need to run in a single Backstage app, allowing them to fully transition to the new frontend system without maintaining old system support.

Do I need knowledge of the new frontend system APIs to migrate Backstage plugins?

Yes, migrating Backstage plugins requires prior knowledge of the new frontend system and its APIs, specifically utilizing @backstage/core-plugin-api and @backstage/frontend-plugin-api to ensure successful compatibility removal and functionality.

What is the best way to update a Backstage plugin to work exclusively with the new frontend system?

The best way to update a Backstage plugin for the new frontend system is executing a full migration that converts the plugin code and removes all backward compatibility with the old system architecture.