Design Blade Component

When To Use

Use this skill when a Blade view is getting repetitive, too large, or hard to reuse across the app.

Inputs Needed

• UI purpose, repeated markup, slots, props, localization needs, accessibility concerns, and tests.

Workflow

1. Inspect existing Blade components and partials.
2. Decide whether the UI belongs in a class-based component, anonymous component, or partial.
3. Prefer the smallest reusable unit that removes duplication.
4. Keep component APIs small and obvious.
5. Localize labels and messages.
6. Keep presentation logic out of the template whenever possible.
7. Add tests when the component drives behavior or important UI states.