JRebirth

Scaffold a complete JRebirth MVC feature (screen, editor, dashboard, panel). Use when a new self-contained UI unit needs Model, View, Controller, and optionally Commands, Services, and Waves.

Spot and fix JRebirth anti-patterns (runLater glue, raw threads, logic in controllers, state in views, global facade abuse). Use when reviewing or cleaning up JRebirth code that smells like plain JavaFX.

Create the JRebirth/JavaFX application entry point and shell configuration. Use when bootstrapping a new app, choosing the first model, or customizing the stage, scene, and preloaded resources.

Create a JRebirth Behavior for a tiny, genuinely shared cross-cutting helper. Use only when small reusable interaction logic appears in several places.

Create a multi command that runs a named, ordered sequence of smaller JRebirth commands. Use when one user action must trigger several existing commands in a known order.

Create a single JRebirth Command for one explicit, named action (save, refresh, load one thing, navigate). Use when a discrete action must be run and named clearly.

Create a JRebirth Controller that wires user gestures to model, commands, or services. Use when adding button, key, selection, or menu handlers.

Verify JavaFX CSS rules, selectors, pseudo-classes, and property names against the official reference. Use when the user asks to validate or fix JavaFX CSS or inline JavaFX styles.

Author and fix the JPMS module-info.java of any Java module that uses JRebirth: requires, exports, opens for reflection, the generated ModuleStarter provider, and ServiceLoader uses/provides. Use when creating a new JRebirth module, when JavaFX or JRebirth reflection fails at runtime (IllegalAccessException, "does not open"), or when a module is not picked up (ModuleStarter missing).

Decide which JRebirth role a piece of code belongs to before writing it. Use when starting any JRebirth work, when roles feel blurred, or when plain JavaFX habits (runLater, raw threads, state in views) start leaking in.

Create a Maven project or module that uses JRebirth AF, JavaFX, JPMS, generated ModuleStarter, and the standard Application/Model/View/Controller skeleton. Use when bootstrapping a new standalone app, sample, showcase, or repo submodule.

Create or extend a JRebirth Model (state, bindings, orchestration). Use when a feature needs properties, selection, validation state, or when it triggers commands and services.

Migrate legacy or messy JavaFX code into the JRebirth role split incrementally. Use before editing many files in an old JavaFX feature, or when a class mixes state, nodes, events, and actions.

Centralize shared JRebirth UI resources (images, fonts, styles, labels, sizes, colors) through resource enums and items. Use when adding assets or replacing magic constants and raw getResource strings.

Create a JRebirth Service for slow, external, backend, or integration work (REST, DB gateway, file import/export, heavy computation). Use to keep long work out of Model, View, and Controller.

Keep a JRebirth client clean while consuming Spring-side services or APIs. Use when wiring backend calls, mapping DTO and FXO, or deciding where network and entity code may live.

Update JRebirth Maven Site documentation when framework code changes. Use when adding or modifying API, commands, services, models, modules, annotations, or any public-facing JRebirth feature, or when asked to write or fix documentation pages.

Build a JRebirth View (scene graph, controls, bindings, view-local CSS). Use when composing nodes for a feature, or attaching a stylesheet to a view.

Define and use JRebirth Waves for decoupled messaging between components. Use for cross-feature notifications, app-wide refresh triggers, or decoupled orchestration, not for plain local method calls.