raykit-solid-lumino-bridgelisted
Install: claude install-skill raykit-apps/raykit
# Raykit Solid Lumino Bridge
Use Raykit's existing browser primitives before adding new abstractions. Reuse `BaseWidget`, `SolidWidget`, `SolidRenderer`, `WidgetFactory`, `WidgetService`, and `ApplicationBrowserContribution` instead of inventing a parallel bridge.
## Start Here
1. Inspect the target package and confirm that the work belongs in `src/browser`.
2. Read [repo-map.md](./references/repo-map.md) to anchor the implementation to existing code.
3. Choose one rendering path:
- Use `SolidWidget` for a full Lumino view or panel body.
- Use `SolidRenderer` for a specific host element that already exists.
4. Put shared state and cross-widget communication into an injectable service.
5. Register widget creation through `WidgetFactory` and open or attach the widget from an `ApplicationBrowserContribution`.
6. Validate with `pnpm lint:fix` and `pnpm check`.
## Choose The Bridge
Use [rendering-patterns.md](./references/rendering-patterns.md) when deciding between the two rendering primitives.
Default to `SolidWidget` when the Solid tree owns the widget body. `SolidWidget` already waits for Lumino attachment before rendering, which matches the current implementation in `packages/widgets/src/browser/solid-widget.ts`.
Use `SolidRenderer` when a Lumino widget or another browser object already owns the DOM node and you only need Solid to render inside a provided host. Treat it as a targeted rendering primitive. The repo currently defines this primitive, but it is not ye