What problem does it solve?
Many Rails projects mix raw HTML and manual UI wiring with Bali ViewComponents, leading to inconsistent UI, duplicated patterns, and fragile Stimulus wiring; this Skill identifies those issues and recommends verified component replacements to improve maintainability and correctness.
Core Features & Use Cases
- Anti-pattern detection: Finds incorrect Bali API usage such as deprecated parameters, wrong slot calls, and form builders missing Bali::FormBuilder.
- Raw HTML replacement identification: Locates high-impact structural candidates (tables, page layouts, cards, modals) and repeated UI patterns that should use Bali components.
- Verified suggestions & reporting: Produces prioritized findings with file locations, current code excerpts, and replacement suggestions that must be verified against the bali-components reference.
- Use Case: Run a project-wide audit to convert manual tables and admin layouts into Bali::DataTable and Bali::AppLayout components and fix form builders across the codebase.
Quick Start
Run an audit of app/views/ to list HIGH priority Bali component replacements with code examples and verified API references.