frontend-plugin-development
Reference for building, wiring, running, and testing Backstage frontend plugins on the new frontend system. Use this skill when writing or changing a plugin built with `createFrontendPlugin`, adding entity page content, setting up a plugin's dev app or tests, wiring a plugin into an app, or debugging why a plugin, page, tab, API, or feature flag does not show up or fails at startup.
How do I install this agent skill?
npx skills add https://backstage.io --skill frontend-plugin-developmentIs this agent skill safe to install?
No partner audit is available yet. Read the source before installing.
What does this agent skill do?
Frontend Plugin Development
This skill collects the checks and traps that matter when working on a plugin built with createFrontendPlugin from @backstage/frontend-plugin-api. Most of these fail silently or only at runtime, so yarn tsc and yarn lint will not catch them.
It is a reference, not a procedure. Read only the reference that matches the task. The new-frontend-system-migration skill links here from its steps.
References
| Read | When |
|---|---|
| Plugin packaging | Creating or changing a plugin's entry point, package.json, exports, extension names, or feature flags |
| App integration | Installing a plugin in an app, removing legacy wiring for it, moving redirects, or enabling and disabling its extensions in app-config |
| Entity content | Adding or changing a tab on the catalog entity page with EntityContentBlueprint |
| Dev app | Setting up or fixing dev/index.tsx with @backstage/frontend-dev-utils, or providing APIs the plugin needs when it runs on its own |
| Testing | Adding a plugin smoke test, or providing APIs to components and hooks in tests |
| Troubleshooting | An error message or symptom at startup or runtime: missing plugin, missing page or tab, duplicate tab, API errors, ignored feature flags |
Contribute through extension inputs
A plugin should work once it is installed. Everything it adds is an extension, created with a blueprint, that attaches to an extension input of another extension: the app's, such as routes for PageBlueprint and APIs for ApiBlueprint, or another plugin's, such as the catalog entity page for EntityContentBlueprint. Adopters adjust these extensions through app-config or modules. If other plugins should be able to extend part of your plugin's UI, give that part an extension input and a blueprint that attaches to it.
When no extension input fits what the plugin adds, the fix is to add one, in the app or in the plugin that owns that part of the UI. Tell the user what is missing and where it belongs. Exporting a component for adopters to render in their app is a last resort, for when adding the input is out of scope, and the README should say it is temporary.
Check the dev app after a change
yarn tsc, lint, and unit tests do not catch most of the problems in these references. After changing a plugin, start its dev app (yarn start from the plugin directory) and check that:
- The page renders the plugin's content, not an error page or an error panel.
- The browser console has no
App startup encountered warnings:block.
See Troubleshooting for what each message means.
Further reading
- Building frontend plugins
- Testing frontend plugins
- Common extension blueprints
- Installing plugins
- Analytics events and their tests:
plugin-analytics-instrumentationskill
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/backstage.io/frontend-plugin-development">View frontend-plugin-development on skillZs</a>