What problem does it solve? Building JavaFX feature screens (registration forms, listings, detail views) often produces frozen UIs from database calls on the UI thread, fragile FXML that breaks the parser, hardcoded colors that break dark themes, and controllers bloated with business logic. This Skill enforces a disciplined workflow that avoids all of these failure modes. ## Core Features & Use Cases - Mockup-first workflow (RO-06): Presents a visual mockup for approval before writing any FXML or controller code, declaring assumptions instead of blocking on missing inputs. - FXML + thin controller generation: Produces a screen following the project's existing conventions, with empty/loading/error/success states covered, theme tokens instead of fixed hex colors, and Log4j 2 error handling. - Anti-freeze mechanism mirroring: Detects how the project handles database I/O (JavaFX Task with daemon threads vs. synchronous DAO calls for simple form writes, as in the SIGO reference) and mirrors that pattern instead of imposing one. - Use Case: Ask for a customer registration screen consuming a ClienteDAO; the Skill shows a mockup, reads existing screens and the DAO, then delivers FXML plus controller with compile and binding verification. ## Quick Start Use the javafx-screen-fxml skill to create the customer registration screen with FXML and controller consuming the existing ClienteDAO.
