bali-components

Build Rails index pages using Bali::IndexPage with a Bali::DataTable component. You can wire New/Edit actions and pagination patterns directly into the page structure to ensure consistent UI and reduce buggy view code.

Rails form fields break when bypassing the form builder. You must require Bali::FormBuilder for all forms and avoid raw HTML fields. Enforcing this keyword-argument convention prevents inconsistencies and incorrect component slot wiring.

Interactive DaisyUI ViewComponents require JavaScript dependencies. You need slim-select for dropdowns, tippy.js for tooltips, and flatpickr for date pickers to ensure full interactive functionality within your Rails application.

You can audit existing Rails views for Bali component adoption. The Skill provides a component index and view-audit rules to check correct slot usage, form builder enforcement, and pagination patterns, preventing UI consistency regressions.

Structure modals and tooltips within a Bali::AppLayout by applying best-practice rules for correct component usage. Use explicit slot conventions and required JavaScript dependencies like tippy.js to build reliable admin dashboard pages.

The Bali form builder enforces keyword-argument conventions for all Rails view components. It requires Bali::FormBuilder for all forms and explicitly avoids raw HTML fields to maintain correct component API usage and prevent common mistakes.