name: laravel-blade description: Create Blade templates with components, slots, layouts, and directives. Use when building views, reusable components, or templating. versions: laravel: "12.x" php: "8.4" user-invocable: true references: references/components.md, references/slots-attributes.md, references/layouts.md, references/directives.md, references/security.md, references/vite.md, references/advanced-directives.md, references/custom-directives.md, references/advanced-components.md, references/forms-validation.md, references/fragments.md, references/templates/ClassComponent.php.md, references/templates/AnonymousComponent.blade.md, references/templates/LayoutComponent.blade.md, references/templates/FormComponent.blade.md, references/templates/CardWithSlots.blade.md, references/templates/DynamicComponent.blade.md, references/templates/AdvancedDirectives.blade.md, references/templates/CustomDirectives.php.md, references/templates/AdvancedComponents.blade.md, references/templates/Fragments.blade.md related-skills: laravel-livewire, laravel-i18n, fusecore

Laravel Blade

Agent Workflow (MANDATORY)

Before ANY implementation, launch in parallel:

1. fuse-ai-pilot:explore-codebase - Check existing views, components structure
2. fuse-ai-pilot:research-expert - Verify latest Blade docs via Context7
3. mcp__context7__query-docs - Query specific patterns (components, slots)

After implementation, run fuse-ai-pilot:sniper for validation.

Overview

Blade is Laravel's templating engine. It provides a clean syntax for PHP in views while compiling to pure PHP for performance.

Critical Rules

1. Always escape output - Use {{ }} not {!! !!} unless absolutely necessary
2. Use @props - Declare expected props explicitly
3. Merge attributes - Allow class/attribute overrides with $attributes->merge()
4. Prefer anonymous - Use class components only when logic is needed
5. Use named slots - For complex layouts with multiple content areas
6. CSRF in forms - Always include @csrf in forms

Decision Guide

Component Type Selection

Need dependency injection?
├── YES → Class-based component
└── NO → Anonymous component
    │
    Need complex props logic?
    ├── YES → Class-based component
    └── NO → Anonymous component

Layout Strategy

Simple page structure?
├── YES → Component layout (<x-layout>)
└── NO → Need fine-grained sections?
    ├── YES → @extends/@section
    └── NO → Component layout

Key Concepts

Reference Guide

Concepts (WHY & Architecture)

Templates (Complete Code)

Quick Reference

Anonymous Component

{{-- resources/views/components/alert.blade.php --}}
@props(['type' => 'info', 'message'])

<div {{ $attributes->merge(['class' => 'alert alert-'.$type]) }}>
    {{ $message }}
</div>

Class Component

// app/View/Components/Alert.php
class Alert extends Component
{
    public function __construct(
        public string $type = 'info',
        public string $message = ''
    ) {}

    public function render(): View
    {
        return view('components.alert');
    }
}

Named Slots

<x-card>
    <x-slot:header class="font-bold">
        Title
    </x-slot>

    Content goes here

    <x-slot:footer>
        Footer content
    </x-slot>
</x-card>

Attribute Merging

@props(['disabled' => false])

<button {{ $attributes->merge([
    'type' => 'submit',
    'class' => 'btn btn-primary'
])->class(['opacity-50' => $disabled]) }}
    @disabled($disabled)
>
    {{ $slot }}
</button>

Best Practices

DO

• Use @props to document expected props
• Use $attributes->merge() for flexibility
• Prefer anonymous components for simple UI
• Use named slots for complex layouts
• Keep components focused and reusable

DON'T

• Use {!! !!} without sanitization
• Forget @csrf in forms
• Put business logic in Blade templates
• Create deeply nested component hierarchies
• Hardcode classes (allow overrides)