RHDH Plugin Authoring

Own plugin source code: creating a new Backstage dynamic plugin for RHDH and implementing features inside an existing one. Backend and frontend are branches of the same job — the same conventions, the same build gates, the same repo — so choose the branch from the request rather than asking for a skill.

Start here

1. Read the target repository's AGENTS.md or CLAUDE.md and any linked specification or issue. Repository rules beat anything written here.
2. Run python scripts/detect-rhdh-context.py --path <plugin-or-workspace> in an existing checkout. Record role, frontend system, plugin ID, dynamic status, MUI version, and package manager.
3. Establish the target RHDH and Backstage versions. Prefer an explicit user or repository value; otherwise invoke /rhdh-context for repository, tool, and version facts. If it is unavailable, ask the user instead of guessing.
4. Inspect branch and status before modifying files, and protect uncommitted work.