Bali View Component Audit FAQs

Question 1

Does this skill suggest new components?

Accepted Answer

Yes, if it detects a UI pattern appearing three or more times that isn't currently a component, it will propose a new Bali component abstraction.

Question 2

Why should I use this alongside the bali-components skill?

Accepted Answer

The audit skill identifies where changes are needed, while the bali-components skill provides the exact API reference to ensure the replacement code uses the correct slots and parameters.

Question 3

Can it fix Rails form issues?

Accepted Answer

Yes, it specifically scans for forms missing the Bali::FormBuilder or manual Stimulus wiring that should be handled automatically by the component library.

Question 4

How does it prioritize audit findings?

Accepted Answer

It categorizes findings into High (structural or broken APIs), Medium (repeated UI patterns like lists and cards), and Low (cosmetic or specialized) priority levels.

Question 5

What is the primary purpose of the Bali View Audit skill?

Accepted Answer

It systematically reviews Rails views to find opportunities for replacing raw HTML with Bali ViewComponents and to fix incorrect component usage.

Bali View Component Audit

Key Features

Use Cases

Bali View Component Audit

Key Features

Use Cases