ViewComponents Specialist

ViewComponents use slots to compose flexible, reusable UI patterns. Define slots in your component class, render them in the template, and pass content blocks from the view. Slots enable slot-based and inline template patterns while maintaining clean separation between logic and presentation.

Use Service Wrapper pattern: delegate public methods from your service to the component via Ruby's `delegate` keyword, then access them in the template with the `helpers` prefix. This ensures proper method exposure and maintains functional requirements across component patterns.

Create preview files that instantiate components with sample data, then configure them in your Rails app to render in isolation. Previews let you test rendering logic, verify slot behavior, and debug component issues without a full page context.

Simple components render static markup; Service Wrapper components delegate to business logic; Slot-based components compose content blocks; Inline Template components define views inline. Choose based on complexity, reusability, and whether you need slots or service integration.

Yes. Access helpers via the `helpers` prefix to maintain consistent, scoped access and avoid naming conflicts. This enforces the pattern across all component methods and ensures proper delegation from services to the view layer.

Run the component creation checklist: verify Rails version compatibility, confirm service interfaces if using Service Wrapper pattern, check slot requirements, and validate helper availability. Pre-work protocol catches issues before implementation.