skills.rest
transaurus
transaurusCOMMUNITY
Explore all skills by this author →
GitHub

app-frontend-system-migration

Migrate Backstage apps from the old frontend system to the new extension-based frontend system.

Updated Mar 27, 2026
Search Tags:#frontend#migration#plugins#legacy#extensions#hybrid#backstage
One-click install
npx skills add https://github.com/transaurus/staging-backstage-backstage --skill app-frontend-system-migration-transaurus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: app-frontend-system-migration
Source: https://github.com/transaurus/staging-backstage-backstage/tree/main/docs/.well-known/skills/app-frontend-system-migration
Command: npx skills add https://github.com/transaurus/staging-backstage-backstage --skill app-frontend-system-migration-transaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrate a Backstage app from the old frontend system to the new extension-based frontend system, enabling a staged, risk-controlled transition.

Core Features & Use Cases

  • Phase-by-phase hybrid migration bridging legacy app code to the new system while maintaining runtime compatibility.
  • Enable and coordinate feature discovery to automatically install discovered plugins and progressively replace the old app shell with the extension-driven architecture.
  • Stepwise migration of routes, sidebar/navigation, plugins, APIs, themes, and app-level concerns across Phase 1 (hybrid) and Phase 2 (full migration).

Quick Start

Use this skill to begin migrating a Backstage app from the old frontend system to the new extension-based frontend system.

Frequently Asked Questions about app-frontend-system-migration

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

FAQPage Schema
How do I migrate a Backstage app to the new frontend system?▼

Migrate a Backstage app by wrapping legacy options with conversion tooling, converting app roots to features, and enabling feature discovery to transition to the extension-based frontend system.

What is hybrid migration for Backstage frontend plugins?▼

Hybrid migration bridges legacy Backstage app code to the new extension-based frontend system while maintaining runtime compatibility across Phase 1 workflows.

How do I enable feature discovery when updating Backstage routes and sidebars?▼

Enable feature discovery to automatically install discovered plugins and progressively replace the old Backstage app shell with the extension-driven architecture.

Can I update Backstage themes and APIs without breaking legacy extensions?▼

Yes, you can stepwise migrate themes, APIs, routes, and sidebar concerns while coordinating legacy code removal to ensure compatibility until the full migration is complete.

What is the best way to remove legacy Backstage code after a frontend migration?▼

Coordinate removal of legacy code during Phase 2 full migration, ensuring all routes, plugins, APIs, and themes have been successfully transitioned to the new extension-based system.

Why does my Backstage app index.tsx need updating during frontend system migration?▼

Update index.tsx and tests to convert app roots to features, enabling the new extension-based frontend system to properly discover and load migrated plugins.

Related Skills

Explore More Software Engineering Skills→
olafkfreundolafkfreund

app-frontend-system-migration

Migrate Backstage apps to the new extension-based frontend system.

Community
Advanced
backstagebackstage
34.1k

app-frontend-system-migration

Migrate Backstage apps from the old frontend system to the extension-based frontend system.

Official
Advanced
olafkfreundolafkfreund

plugin-new-frontend-system-support

Migrate Backstage plugins to support legacy and new frontend systems with dual entry points.

Community
Intermediate
jacobduijzerjacobduijzer

app-frontend-system-migration

Migrate Backstage apps to the new extension-based frontend system.

Community
Advanced