diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 0c38da22..951572dd 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -16,7 +16,7 @@ A clear and concise description of what the bug is.
 ```
 
 **Expected behavior**
-What you expected to happen when using `@pure`.
+What you expected to happen when using `@blaze`.
 
 **Actual behavior**
 What actually happened instead.
@@ -27,4 +27,4 @@ What actually happened instead.
 - Blaze version: [e.g. 1.0.0]
 
 **Additional context**
-Add any other context about the problem here (error messages, stack traces, etc.)
\ No newline at end of file
+Add any other context about the problem here (error messages, stack traces, etc.)
diff --git a/AGENTS.md b/AGENTS.md
index 7d1c4e57..63f475e9 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -6,36 +6,36 @@ This document provides guidance for AI assistants helping users work with Larave
 
 Laravel Blaze is a performance optimization package that pre-renders static portions of Blade components at compile-time, dramatically reducing runtime overhead. It works by:
 
-1. Identifying components marked with the `@pure` directive in their source
+1. Identifying components marked with the `@blaze` directive in their source
 2. Analyzing component source for runtime dependencies
 3. Pre-rendering eligible components during Blade compilation
 4. Falling back to normal rendering for unsafe components
 
 ## Core Concepts
 
-### The @pure Directive
+### The @blaze Directive
 
-The `@pure` directive tells Blaze that a component has no runtime dependencies and can be safely optimized. It must be placed at the top of a component file:
+The `@blaze` directive tells Blaze that a component has no runtime dependencies and can be safely optimized. It must be placed at the top of a component file:
 
 ```blade
-@pure
+@blaze
 
 @props(['title'])
 
 <h1 class="text-2xl font-bold">{{ $title }}</h1>
 ```
 
-The `@pure` directive supports optional parameters to control different optimization strategies:
+The `@blaze` directive supports optional parameters to control different optimization strategies:
 
 ```blade
 {{-- All optimizations enabled (default) --}}
-@pure
+@blaze
 
 {{-- Explicitly enable all optimizations --}}
-@pure(fold: true, memo: true, aware: true)
+@blaze(fold: true, memo: true, aware: true)
 
 {{-- Disable specific optimizations --}}
-@pure(fold: false, memo: true, aware: false)
+@blaze(fold: false, memo: true, aware: false)
 ```
 
 **Parameters:**
@@ -45,7 +45,7 @@ The `@pure` directive supports optional parameters to control different optimiza
 
 ### Code Folding Process
 
-When a `@pure` component is encountered, Blaze:
+When a `@blaze` component is encountered, Blaze:
 1. Replaces dynamic content being passed in via attributes or slots with placeholders
 2. Renders the component with placeholders
 3. Validates that placeholders are preserved
@@ -58,7 +58,7 @@ When a component can't be folded (due to dynamic content), Blaze automatically f
 
 ## Helping Users Analyze Components
 
-When a user asks about adding `@pure` to a component or wants you to analyze their components, follow this process:
+When a user asks about adding `@blaze` to a component or wants you to analyze their components, follow this process:
 
 ### 1. Read and Analyze the Component
 
@@ -67,9 +67,9 @@ First, examine the component source code for:
 - Dynamic content that changes per request
 - Dependencies on global state or context
 
-### 2. Safe Patterns for @pure
+### 2. Safe Patterns for @blaze
 
-Components are safe for `@pure` when they only:
+Components are safe for `@blaze` when they only:
 - Accept props and render them consistently
 - Perform simple data formatting (dates, strings, etc.)
 - Render slots without modification
@@ -77,27 +77,27 @@ Components are safe for `@pure` when they only:
 Examples:
 ```blade
 {{-- UI components --}}
-@pure
+@blaze
 <div class="card p-4 bg-white rounded shadow">{{ $slot }}</div>
 
 {{-- Prop-based styling --}}
-@pure
+@blaze
 @props(['variant' => 'primary'])
 <button class="btn btn-{{ $variant }}">{{ $slot }}</button>
 
 {{-- Simple formatting --}}
-@pure
+@blaze
 @props(['price'])
 <span class="font-mono">${{ number_format($price, 2) }}</span>
 
 {{-- Components using @aware --}}
-@pure
+@blaze
 @aware(['theme'])
 @props(['theme' => 'light'])
 <div class="theme-{{ $theme }}">{{ $slot }}</div>
 ```
 
-### 3. Unsafe Patterns (Never @pure)
+### 3. Unsafe Patterns (Never @blaze)
 
 **Authentication & Authorization:**
 - `@auth`, `@guest`, `@can`, `@cannot`
@@ -134,89 +134,89 @@ Examples:
 - Components that display pagination controls
 - Data tables with pagination
 
-**Nested Non-Pure Components:**
+**Nested Non-Foldable Components:**
 - Components that contain other components which use runtime data
-- Parent components can't be `@pure` if any child component is dynamic
-- Watch for `<x-*>` tags inside the component that might be non-pure
+- Parent components can't be `@blaze` if any child component is dynamic
+- Watch for `<x-*>` tags inside the component that might be non-foldable
 
 ### 4. Analysis Process
 
 When analyzing a component:
 
 1. **Scan for unsafe patterns** using the lists above
-2. **Check for child components** - look for any `<x-*>` tags and verify they are also pure
+2. **Check for child components** - look for any `<x-*>` tags and verify they are also foldable
 3. **Check for indirect dependencies** - props that might contain dynamic data (like paginator objects)
 4. **Consider context** - how the component is typically used
 5. **Test edge cases** - what happens with different prop values
 
 #### Special Case: Nested Components
 
-When a component directly renders other Blade components in its template (not via slots), verify those are also pure:
+When a component directly renders other Blade components in its template (not via slots), verify those are also foldable:
 
 ```blade
 {{-- Parent component --}}
-@pure <!-- ⚠️ Only safe if directly rendered child components are pure -->
+@blaze <!-- ⚠️ Only safe if directly rendered child components are foldable -->
 
 <div class="data-table">
-    <x-table-header /> <!-- Must be pure -->
+    <x-table-header /> <!-- Must be foldable -->
     {{ $slot }} <!-- ✅ Slot content is handled separately, can be dynamic -->
-    <x-table-footer /> <!-- Must be pure -->
-    <x-table-pagination /> <!-- ❌ If this uses paginator, parent can't be @pure -->
+    <x-table-footer /> <!-- Must be foldable -->
+    <x-table-pagination /> <!-- ❌ If this uses paginator, parent can't be @blaze -->
 </div>
 ```
 
 **Key distinction**:
-- Components **hardcoded in the template** must be pure for the parent to be @pure
+- Components **hardcoded in the template** must be foldable for the parent to be @blaze
 - Content **passed through slots** is handled separately and can be dynamic
 
 ### 5. Making Recommendations
 
 **For safe components:**
 ```
-This component is safe for @pure because it only renders static HTML and passed props. Add @pure at the top of the file.
+This component is safe for @blaze because it only renders static HTML and passed props. Add @blaze at the top of the file.
 ```
 
 **For unsafe components:**
 ```
-This component cannot use @pure because it contains [specific pattern]. The [pattern] changes at runtime and would be frozen at compile-time, causing incorrect behavior.
+This component cannot use @blaze because it contains [specific pattern]. The [pattern] changes at runtime and would be frozen at compile-time, causing incorrect behavior.
 ```
 
 **For borderline cases:**
 ```
-This component might be safe for @pure, but consider if [specific concern]. Test thoroughly after adding @pure to ensure it behaves correctly across different requests. If folding isn't possible, memoization will still provide performance benefits.
+This component might be safe for @blaze, but consider if [specific concern]. Test thoroughly after adding @blaze to ensure it behaves correctly across different requests. If folding isn't possible, memoization will still provide performance benefits.
 ```
 
 ## Common User Requests
 
-### "Can I add @pure to this component?"
+### "Can I add @blaze to this component?"
 
 1. Read the component file
 2. Analyze for unsafe patterns
 3. Provide a clear yes/no with explanation
 4. If no, suggest alternatives or modifications
 
-### "Add @pure to my components"
+### "Add @blaze to my components"
 
 1. Find all component files (`resources/views/components/**/*.blade.php`)
 2. Analyze each component individually
-3. Add `@pure` only to safe components (include a line break after `@pure` )
+3. Add `@blaze` only to safe components (include a line break after `@blaze` )
 4. Report which components were modified and which were skipped with reasons
 
 ### "Optimize my Blade components"
 
-1. Audit existing components for @pure eligibility
-2. Identify components that could be refactored to be pure
+1. Audit existing components for @blaze eligibility
+2. Identify components that could be refactored to be foldable
 3. Suggest architectural improvements for better optimization
 4. Provide before/after examples
 
 ## Implementation Guidelines
 
-### Adding @pure to Components
+### Adding @blaze to Components
 
-When adding `@pure` to a component:
+When adding `@blaze` to a component:
 
 1. **Always read the component first** to understand its structure
-2. **Add @pure as the very first line** of the component file
+2. **Add @blaze as the very first line** of the component file
 3. **Preserve existing formatting** and structure
 4. **Don't modify component logic** unless specifically requested
 
@@ -228,7 +228,7 @@ Example edit:
 <h1>{{ $title }}</h1>
 
 {{-- After --}}
-@pure
+@blaze
 
 @props(['title'])
 
@@ -241,21 +241,21 @@ When processing multiple components:
 
 1. **Process files individually** - don't batch edits
 2. **Report results clearly** - which succeeded, which failed, and why
-3. **Provide summary statistics** - "Added @pure to 15 of 23 components"
+3. **Provide summary statistics** - "Added @blaze to 15 of 23 components"
 4. **List problematic components** with specific reasons for skipping
 
 ### Error Handling
 
-If Blaze detects unsafe patterns in a `@pure` component, it will show compilation errors. When helping users:
+If Blaze detects unsafe patterns in a `@blaze` component, it will show compilation errors. When helping users:
 
 1. **Explain the error** in simple terms
 2. **Show the problematic code** and why it's unsafe
-3. **Suggest solutions** - remove @pure or refactor the component
+3. **Suggest solutions** - remove @blaze or refactor the component
 4. **Provide alternatives** if the optimization is important
 
 ## Testing Recommendations
 
-After adding `@pure` to components:
+After adding `@blaze` to components:
 
 1. **Test with different props** to ensure consistent rendering
 2. **Verify in different contexts** - authenticated vs guest users
diff --git a/README.md b/README.md
index f48c07d4..a7e686fe 100644
--- a/README.md
+++ b/README.md
@@ -5,7 +5,7 @@ Speed up your Laravel app by optimizing Blade component rendering performance.
 > ⚠️ **Early stages** - This is an early-stage experimental package. APIs may change, and edge cases have yet to be worked out. Please test thoroughly and report any issues!
 
 ```
-Rendering 25,000 pure button components:
+Rendering 25,000 foldable button components:
 
 Without Blaze  ████████████████████████████████████████  750ms
 With Blaze     ██                                         45ms
@@ -27,16 +27,16 @@ composer require livewire/blaze
 
 ## Usage
 
-To optimize a Blade component for performance, simply add the `@pure` directive at the top of your component file.
+To optimize a Blade component for performance, simply add the `@blaze` directive at the top of your component file.
 
-The `@pure` directive signals that your component is "pure" - meaning it has no side effects and always renders the same output for the same input (no auth checks, no database queries, no time-dependent content). Think of these as your basic UI building blocks like buttons, cards, and badges.
+The `@blaze` directive signals that your component is "foldable" - meaning it has no side effects and always renders the same output for the same input (no auth checks, no database queries, no time-dependent content). Think of these as your basic UI building blocks like buttons, cards, and badges.
 
-> **Using Flux?** All eligible Flux components are already marked with `@pure` - you don't need to do anything! Just install Blaze and enjoy the performance boost.
+> **Using Flux?** All eligible Flux components are already marked with `@blaze` - you don't need to do anything! Just install Blaze and enjoy the performance boost.
 
 ```blade
 {{-- resources/views/components/button.blade.php --}}
 
-@pure
+@blaze
 
 @props(['variant' => 'primary'])
 
@@ -45,17 +45,17 @@ The `@pure` directive signals that your component is "pure" - meaning it has no
 </button>
 ```
 
-The `@pure` directive supports optional parameters to control different optimization strategies:
+The `@blaze` directive supports optional parameters to control different optimization strategies:
 
 ```blade
 {{-- All optimizations enabled (default) --}}
-@pure
+@blaze
 
 {{-- Explicitly enable all optimizations --}}
-@pure(fold: true, memo: true, aware: true)
+@blaze(fold: true, memo: true, aware: true)
 
 {{-- Disable specific optimizations --}}
-@pure(fold: false, memo: true, aware: false)
+@blaze(fold: false, memo: true, aware: false)
 ```
 
 **Parameters:**
@@ -84,16 +84,16 @@ Blaze will automatically optimize it during compilation, pre-rendering the stati
 
 ## Table of contents
 
-- [When to use @pure](#when-to-use-pure)
+- [When to use @blaze](#when-to-use-blaze)
 - [Performance expectations](#performance-expectations)
 - [Debugging](#debugging)
 - [AI assistant integration](#ai-assistant-integration)
 
-## When to use @pure
+## When to use @blaze
 
-The `@pure` directive tells Blaze that a component has no runtime dependencies and can be safely optimized. Only add it to components that render the same way every time they're compiled.
+The `@blaze` directive tells Blaze that a component has no runtime dependencies and can be safely optimized. Only add it to components that render the same way every time they're compiled.
 
-### The @pure litmus test
+### The @blaze litmus test
 
 Ask yourself these questions about your component:
 
@@ -101,32 +101,32 @@ Ask yourself these questions about your component:
 2. **Does it work the same on every request?** (no request data, no CSRF tokens)
 3. **Does it work the same at any time?** (no timestamps, no "time ago" formatting)
 4. **Does it only use the props you pass in?** (no session data, no database queries)
-5. **Are all child components it renders also pure?** (no dynamic components hardcoded inside)
+5. **Are all child components it renders also foldable?** (no dynamic components hardcoded inside)
 
-**If you answered YES to all questions → Add `@pure`**
-**If you answered NO to any question → Don't add `@pure`**
+**If you answered YES to all questions → Add `@blaze`**
+**If you answered NO to any question → Don't add `@blaze`**
 
 ### Quick mental model
 
-Think of `@pure` components as **"design system" components** - they're the building blocks that:
+Think of `@blaze` components as **"design system" components** - they're the building blocks that:
 - Look the same for everyone
 - Only change based on props you explicitly pass
 - Could be shown in a component library without any application context
 
 Examples: buttons, cards, badges, icons, layout grids, typography components
 
-**Not pure** : anything that's "smart" or "connected" - forms (CSRF), navigation (active states), user avatars (auth), timestamps (time), paginated tables (request state).
+**Not foldable** : anything that's "smart" or "connected" - forms (CSRF), navigation (active states), user avatars (auth), timestamps (time), paginated tables (request state).
 
-**For developers familiar with functional programming**: Think of `@pure` components like pure functions - they always produce the same output for the same input, with no side effects or dependencies on external state.
+**For developers familiar with functional programming**: Think of `@blaze` components like pure functions - they always produce the same output for the same input, with no side effects or dependencies on external state.
 
-### ✅ Safe for @pure
+### ✅ Safe for @blaze
 
 These components are good candidates for optimization:
 
 ```blade
 {{-- Static UI components --}}
 
-@pure
+@blaze
 
 <div class="card p-4 rounded shadow">
     {{ $slot }}
@@ -136,7 +136,7 @@ These components are good candidates for optimization:
 ```blade
 {{-- Components that only depend on passed props --}}
 
-@pure
+@blaze
 
 @props(['size' => 'md', 'color' => 'blue'])
 
@@ -145,15 +145,15 @@ These components are good candidates for optimization:
 </button>
 ```
 
-### ❌ Never use @pure with
+### ❌ Never use @blaze with
 
-Avoid `@pure` for components that have runtime dependencies:
+Avoid `@blaze` for components that have runtime dependencies:
 
 ```blade
 {{-- CSRF tokens change per request --}}
 
 <form method="POST">
-    @csrf <!-- ❌ Don't use @pure -->
+    @csrf <!-- ❌ Don't use @blaze -->
     <button type="submit">Submit</button>
 </form>
 ```
@@ -161,7 +161,7 @@ Avoid `@pure` for components that have runtime dependencies:
 ```blade
 {{-- Authentication state changes at runtime --}}
 
-@auth <!-- ❌ Don't use @pure -->
+@auth <!-- ❌ Don't use @blaze -->
     <p>Welcome back!</p>
 @endauth
 ```
@@ -171,7 +171,7 @@ Avoid `@pure` for components that have runtime dependencies:
 
 @props(['href'])
 
-<a href="{{ $href }}" @class(['active' => request()->is($href)])> <!-- ❌ Don't use @pure -->
+<a href="{{ $href }}" @class(['active' => request()->is($href)])> <!-- ❌ Don't use @blaze -->
     {{ $slot }}
 </a>
 ```
@@ -179,7 +179,7 @@ Avoid `@pure` for components that have runtime dependencies:
 ```blade
 {{-- Error bags are request-specific --}}
 
-@if($errors->has('email')) <!-- ❌ Don't use @pure -->
+@if($errors->has('email')) <!-- ❌ Don't use @blaze -->
     <span class="error">{{ $errors->first('email') }}</span>
 @endif
 ```
@@ -187,13 +187,13 @@ Avoid `@pure` for components that have runtime dependencies:
 ```blade
 {{-- Session data changes at runtime --}}
 
-<div>Welcome, {{ session('username') }}</div> <!-- ❌ Don't use @pure -->
+<div>Welcome, {{ session('username') }}</div> <!-- ❌ Don't use @blaze -->
 ```
 
 ```blade
 {{-- Pagination components --}}
 
-@props(['paginator']) <!-- ❌ Don't use @pure -->
+@props(['paginator']) <!-- ❌ Don't use @blaze -->
 
 <div class="pagination">
     {{ $paginator->links() }}
@@ -201,9 +201,9 @@ Avoid `@pure` for components that have runtime dependencies:
 ```
 
 ```blade
-{{-- Components containing non-pure children --}}
+{{-- Components containing non-foldable children --}}
 
-@pure <!-- ❌ WRONG: This table contains pagination which is dynamic -->
+@blaze <!-- ❌ WRONG: This table contains pagination which is dynamic -->
 
 @props(['items'])
 
@@ -230,17 +230,17 @@ Be careful with these patterns that might seem safe but can cause issues:
 {{-- Environment-dependent values --}}
 <script src="{{ config('app.cdn_url') }}/app.js"></script> <!-- Might change -->
 
-{{-- Components that CONTAIN other non-pure components --}}
-@pure <!-- ❌ May break if child components are dynamic -->
+{{-- Components that CONTAIN other non-foldable components --}}
+@blaze <!-- ❌ May break if child components are dynamic -->
 
 <div class="wrapper">
-    <x-user-greeting /> <!-- If this uses auth(), the parent can't be @pure -->
+    <x-user-greeting /> <!-- If this uses auth(), the parent can't be @blaze -->
 </div>
 ```
 
 ### Why isn't Blaze optimizing my component?
 
-Even with `@pure`, Blaze only folds components when it can safely pre-render them at compile-time:
+Even with `@blaze`, Blaze only folds components when it can safely pre-render them at compile-time:
 
 ```blade
 {{-- ✅ CAN be folded - static date value --}}
@@ -252,7 +252,7 @@ Even with `@pure`, Blaze only folds components when it can safely pre-render the
 
 **Why?** Blaze needs actual values at compile-time to pre-render. When you pass dynamic variables (like `$user->created_at`), Blaze doesn't know their values during compilation, so it skips folding and renders normally at runtime. This happens automatically - your component still works, it just won't be optimized.
 
-**Note**: If your `@pure` component isn't being folded, check if you're passing dynamic variables to it. The component itself is fine - it's the dynamic data preventing optimization.
+**Note**: If your `@blaze` component isn't being folded, check if you're passing dynamic variables to it. The component itself is fine - it's the dynamic data preventing optimization.
 
 ### Runtime Memoization
 
@@ -261,7 +261,7 @@ When a component can't be folded due to dynamic content, Blaze automatically fal
 ```blade
 {{-- This component can't be folded but will be memoized --}}
 
-@pure
+@blaze
 
 @props(['user'])
 
@@ -274,14 +274,14 @@ When a component can't be folded due to dynamic content, Blaze automatically fal
 **Benefits of memoization:**
 - Caches identical component renders
 - Reduces CPU usage for repeated components
-- Works with any `@pure` component, even with dynamic props
+- Works with any `@blaze` component, even with dynamic props
 - Automatic fallback when folding isn't possible
 
 ### 💡 Pro Tips
 
 - **Start with simple components**: Begin with basic UI components like buttons, cards, and badges
 - **Check your dependencies**: If your component uses any Laravel helpers or global variables, think twice
-- **Test thoroughly**: After adding `@pure`, verify the component still works correctly across different requests
+- **Test thoroughly**: After adding `@blaze`, verify the component still works correctly across different requests
 - **Blaze is forgiving**: If a component can't be optimized, Blaze will automatically fall back to normal rendering
 
 
@@ -324,13 +324,13 @@ When debug mode is enabled:
 This repository includes an [`AGENTS.md`](AGENTS.md) file specifically designed for AI assistants (like GitHub Copilot, Cursor, or Claude). If you're using an AI tool to help with your Laravel project:
 
 1. **Point your AI assistant to the AGENTS.md file** when asking about Blaze optimization
-2. **The file contains detailed guidance** for analyzing components and determining `@pure` eligibility
+2. **The file contains detailed guidance** for analyzing components and determining `@blaze` eligibility
 3. **Use it for automated analysis** - AI assistants can help audit your entire component library
 
 Example prompts for AI assistants:
-- "Using the AGENTS.md file, analyze my components and tell me which can use @pure"
-- "Help me add @pure to all eligible components following the AGENTS.md guidelines"
-- "Check if this component is safe for @pure based on AGENTS.md"
+- "Using the AGENTS.md file, analyze my components and tell me which can use @blaze"
+- "Help me add @blaze to all eligible components following the AGENTS.md guidelines"
+- "Check if this component is safe for @blaze based on AGENTS.md"
 
 ## License
 
diff --git a/SPEC.md b/SPEC.md
index a0718802..64c5ab50 100644
--- a/SPEC.md
+++ b/SPEC.md
@@ -579,10 +579,10 @@ Option B provides clear developer intent and prevents mysterious failures. Devel
 
 #### Proposed syntax
 
-The most straightforward approach is a `@pure` directive placed at the top of component files:
+The most straightforward approach is a `@blaze` directive placed at the top of component files:
 
 ```php
-@pure
+@blaze
 
 @props(['title'])
 
@@ -596,7 +596,7 @@ This clearly signals that the component has no runtime dependencies and is safe
 - Global configuration could enable automatic detection for those who prefer it
 - Directory-based opt-in could reduce per-component boilerplate
 
-However, `@pure` is the clearest option—it's self-documenting and doesn't create dependencies on specific tooling names. Since Blade may eventually become a deeper dependency of Laravel itself, tool-agnostic naming is preferable.
+However, `@blaze` is the clearest option—it's self-documenting and doesn't create dependencies on specific tooling names. Since Blade may eventually become a deeper dependency of Laravel itself, tool-agnostic naming is preferable.
 
 ### Error handling and debugging
 
@@ -604,7 +604,7 @@ Blaze uses a fail-safe approach: when folding encounters any issues, it falls ba
 
 #### The folding validation process
 
-When Blaze identifies a `@pure` component as foldable, it follows this validation process:
+When Blaze identifies a `@blaze` component as foldable, it follows this validation process:
 
 1. **Replace dynamic content with placeholders** - Dynamic attributes and slots are temporarily replaced with unique placeholder strings
 2. **Attempt rendering** - The component is rendered with placeholders in place
@@ -658,7 +658,7 @@ Folding will be skipped when:
 
 #### Disallowed folding
 
-Even when a component is marked with `@pure`, Blaze should perform static analysis to detect runtime dependencies that would make folding unsafe. When such patterns are found, Blaze should throw clear compilation errors rather than silently producing broken behavior.
+Even when a component is marked with `@blaze`, Blaze should perform static analysis to detect runtime dependencies that would make folding unsafe. When such patterns are found, Blaze should throw clear compilation errors rather than silently producing broken behavior.
 
 #### Detected unsafe patterns
 
@@ -666,7 +666,7 @@ During the pre-order traversal phase, Blaze scans component source code for thes
 
 **CSRF tokens:**
 ```php
-@pure  <!-- ❌ Error: CSRF tokens require runtime generation -->
+@blaze  <!-- ❌ Error: CSRF tokens require runtime generation -->
 
 <form method="POST">
     @csrf
@@ -676,14 +676,14 @@ During the pre-order traversal phase, Blaze scans component source code for thes
 
 **Session access:**
 ```php
-@pure  <!-- ❌ Error: Session data is runtime-dependent -->
+@blaze  <!-- ❌ Error: Session data is runtime-dependent -->
 
 <div>Welcome back, {{ session('username') }}</div>
 ```
 
 **Authentication checks:**
 ```php
-@pure  <!-- ❌ Error: Authentication state changes at runtime -->
+@blaze  <!-- ❌ Error: Authentication state changes at runtime -->
 
 @auth
     <p>You are logged in</p>
@@ -692,7 +692,7 @@ During the pre-order traversal phase, Blaze scans component source code for thes
 
 **Error bag access:**
 ```php
-@pure  <!-- ❌ Error: Validation errors are request-specific -->
+@blaze  <!-- ❌ Error: Validation errors are request-specific -->
 
 @if($errors->has('email'))
     <span class="error">{{ $errors->first('email') }}</span>
@@ -701,7 +701,7 @@ During the pre-order traversal phase, Blaze scans component source code for thes
 
 **Request data:**
 ```php
-@pure  <!-- ❌ Error: Request data varies per request -->
+@blaze  <!-- ❌ Error: Request data varies per request -->
 
 <input type="hidden" value="{{ request()->ip() }}">
 ```
@@ -711,12 +711,12 @@ During the pre-order traversal phase, Blaze scans component source code for thes
 When unsafe patterns are detected, Blaze should provide actionable error messages:
 
 ```
-Blaze Compilation Error: Component 'form-component' is marked @pure but contains runtime dependencies.
+Blaze Compilation Error: Component 'form-component' is marked @blaze but contains runtime dependencies.
 
 Found: @csrf directive on line 4
 Reason: CSRF tokens must be generated at runtime for security
 
-Solution: Remove @pure directive or extract CSRF handling to parent component
+Solution: Remove @blaze directive or extract CSRF handling to parent component
 
 Component: resources/views/components/form-component.blade.php:1
 ```
diff --git a/src/BlazeServiceProvider.php b/src/BlazeServiceProvider.php
index c78f9d9a..98b97761 100644
--- a/src/BlazeServiceProvider.php
+++ b/src/BlazeServiceProvider.php
@@ -2,9 +2,9 @@
 
 namespace Livewire\Blaze;
 
+use Livewire\Blaze\Directive\BlazeDirective;
 use Livewire\Blaze\Tokenizer\Tokenizer;
 use Illuminate\Support\ServiceProvider;
-use Illuminate\Support\Facades\Blade;
 use Livewire\Blaze\Memoizer\Memoizer;
 use Livewire\Blaze\Walker\Walker;
 use Livewire\Blaze\Parser\Parser;
@@ -15,7 +15,7 @@ class BlazeServiceProvider extends ServiceProvider
     public function register(): void
     {
         $this->registerBlazeManager();
-        $this->registerPureDirectiveFallback();
+        $this->registerBlazeDirectiveFallback();
         $this->registerBladeMacros();
         $this->interceptBladeCompilation();
         $this->interceptViewCacheInvalidation();
@@ -44,9 +44,9 @@ protected function registerBlazeManager(): void
         $this->app->bind('blaze', fn ($app) => $app->make(BlazeManager::class));
     }
 
-    protected function registerPureDirectiveFallback(): void
+    protected function registerBlazeDirectiveFallback(): void
     {
-        Blade::directive('pure', fn () => '');
+        BlazeDirective::registerFallback();
     }
 
     protected function registerBladeMacros(): void
@@ -94,4 +94,4 @@ public function boot(): void
     {
         // Bootstrap services
     }
-}
\ No newline at end of file
+}
diff --git a/src/Pure/Pure.php b/src/Directive/BlazeDirective.php
similarity index 75%
rename from src/Pure/Pure.php
rename to src/Directive/BlazeDirective.php
index 418ea57e..1478f15b 100644
--- a/src/Pure/Pure.php
+++ b/src/Directive/BlazeDirective.php
@@ -1,13 +1,20 @@
 <?php
 
-namespace Livewire\Blaze\Pure;
+namespace Livewire\Blaze\Directive;
 
-class Pure
+use Illuminate\Support\Facades\Blade;
+
+class BlazeDirective
 {
+    public static function registerFallback(): void
+    {
+        Blade::directive('blaze', fn () => '');
+    }
+
     public static function getParameters(string $source): ?array
     {
-        // If there is no @pure directive, return null
-        if (! preg_match('/^\s*(?:\/\*.*?\*\/\s*)*@pure(?:\s*\(([^)]+)\))?/s', $source, $matches)) {
+        // If there is no @blaze directive, return null
+        if (! preg_match('/^\s*(?:\/\*.*?\*\/\s*)*@blaze(?:\s*\(([^)]+)\))?/s', $source, $matches)) {
             return null;
         }
 
@@ -21,10 +28,10 @@ public static function getParameters(string $source): ?array
 
     /**
      * Parse directive parameters
-     * 
+     *
      * For example, the string:
      * "fold: false"
-     * 
+     *
      * will be parsed into the array:
      * [
      *     'fold' => false,
@@ -51,4 +58,4 @@ protected static function parseParameters(string $paramString): array
 
         return $params;
     }
-}
\ No newline at end of file
+}
diff --git a/src/Exceptions/InvalidPureUsageException.php b/src/Exceptions/InvalidBlazeFoldUsageException.php
similarity index 66%
rename from src/Exceptions/InvalidPureUsageException.php
rename to src/Exceptions/InvalidBlazeFoldUsageException.php
index 05dd93d4..82d1c412 100644
--- a/src/Exceptions/InvalidPureUsageException.php
+++ b/src/Exceptions/InvalidBlazeFoldUsageException.php
@@ -2,7 +2,7 @@
 
 namespace Livewire\Blaze\Exceptions;
 
-class InvalidPureUsageException extends \Exception
+class InvalidBlazeFoldUsageException extends \Exception
 {
     protected string $componentPath;
 
@@ -13,7 +13,7 @@ protected function __construct(string $componentPath, string $problematicPattern
         $this->componentPath = $componentPath;
         $this->problematicPattern = $problematicPattern;
 
-        $message = "Invalid @pure usage in component '{$componentPath}': {$reason}";
+        $message = "Invalid @blaze fold usage in component '{$componentPath}': {$reason}";
 
         parent::__construct($message);
     }
@@ -33,7 +33,7 @@ public static function forAware(string $componentPath): self
         return new self(
             $componentPath,
             '@aware',
-            'Components with @aware should not use @pure as they depend on parent component state'
+            'Components with @aware should not use @blaze fold as they depend on parent component state'
         );
     }
 
@@ -42,7 +42,7 @@ public static function forErrors(string $componentPath): self
         return new self(
             $componentPath,
             '\\$errors',
-            'Components accessing $errors should not use @pure as errors are request-specific'
+            'Components accessing $errors should not use @blaze fold as errors are request-specific'
         );
     }
 
@@ -51,7 +51,7 @@ public static function forSession(string $componentPath): self
         return new self(
             $componentPath,
             'session\\(',
-            'Components using session() should not use @pure as session data can change'
+            'Components using session() should not use @blaze fold as session data can change'
         );
     }
 
@@ -60,7 +60,7 @@ public static function forError(string $componentPath): self
         return new self(
             $componentPath,
             '@error\\(',
-            'Components with @error directives should not use @pure as errors are request-specific'
+            'Components with @error directives should not use @blaze fold as errors are request-specific'
         );
     }
 
@@ -69,7 +69,7 @@ public static function forCsrf(string $componentPath): self
         return new self(
             $componentPath,
             '@csrf',
-            'Components with @csrf should not use @pure as CSRF tokens are request-specific'
+            'Components with @csrf should not use @blaze fold as CSRF tokens are request-specific'
         );
     }
 
@@ -78,7 +78,7 @@ public static function forAuth(string $componentPath): self
         return new self(
             $componentPath,
             'auth\\(\\)',
-            'Components using auth() should not use @pure as authentication state can change'
+            'Components using auth() should not use @blaze fold as authentication state can change'
         );
     }
 
@@ -87,7 +87,7 @@ public static function forRequest(string $componentPath): self
         return new self(
             $componentPath,
             'request\\(\\)',
-            'Components using request() should not use @pure as request data varies'
+            'Components using request() should not use @blaze fold as request data varies'
         );
     }
 
@@ -96,7 +96,7 @@ public static function forOld(string $componentPath): self
         return new self(
             $componentPath,
             'old\\(',
-            'Components using old() should not use @pure as old input is request-specific'
+            'Components using old() should not use @blaze fold as old input is request-specific'
         );
     }
 
@@ -105,8 +105,8 @@ public static function forOnce(string $componentPath): self
         return new self(
             $componentPath,
             '@once',
-            'Components with @once should not use @pure as @once maintains runtime state'
+            'Components with @once should not use @blaze fold as @once maintains runtime state'
         );
     }
 
-}
\ No newline at end of file
+}
diff --git a/src/Folder/Folder.php b/src/Folder/Folder.php
index 0a34ac21..5bce2c8d 100644
--- a/src/Folder/Folder.php
+++ b/src/Folder/Folder.php
@@ -3,7 +3,7 @@
 namespace Livewire\Blaze\Folder;
 
 use Livewire\Blaze\Exceptions\LeftoverPlaceholdersException;
-use Livewire\Blaze\Exceptions\InvalidPureUsageException;
+use Livewire\Blaze\Exceptions\InvalidBlazeFoldUsageException;
 use Livewire\Blaze\Support\AttributeParser;
 use Livewire\Blaze\Events\ComponentFolded;
 use Livewire\Blaze\Nodes\ComponentNode;
@@ -11,7 +11,7 @@
 use Livewire\Blaze\Nodes\TextNode;
 use Livewire\Blaze\Nodes\SlotNode;
 use Livewire\Blaze\Nodes\Node;
-use Livewire\Blaze\Pure\Pure;
+use Livewire\Blaze\Directive\BlazeDirective;
 
 class Folder
 {
@@ -41,14 +41,14 @@ public function isFoldable(Node $node): bool
 
             $source = file_get_contents($componentPath);
 
-            $pureParameters = Pure::getParameters($source);
+            $directiveParameters = BlazeDirective::getParameters($source);
 
-            if (is_null($pureParameters)) {
+            if (is_null($directiveParameters)) {
                 return false;
             }
 
             // Default to true if fold parameter is not specified
-            return $pureParameters['fold'] ?? true;
+            return $directiveParameters['fold'] ?? true;
 
         } catch (\Exception $e) {
             return false;
@@ -74,18 +74,18 @@ public function fold(Node $node): Node
             if (file_exists($componentPath)) {
                 $source = file_get_contents($componentPath);
 
-                    $this->validatePureComponent($source, $componentPath);
+                    $this->validateFoldableComponent($source, $componentPath);
 
-                $pureParameters = Pure::getParameters($source);
+                $directiveParameters = BlazeDirective::getParameters($source);
 
                 // Default to true if aware parameter is not specified
-                if ($pureParameters['aware'] ?? true) {
+                if ($directiveParameters['aware'] ?? true) {
                     $awareAttributes = $this->getAwareDirectiveAttributes($source);
 
                     if (! empty($awareAttributes)) {
                         $component->mergeAwareAttributes($awareAttributes);
                     }
-                }                
+                }
             }
 
             [$processedNode, $slotPlaceholders, $restore, $attributeNameToPlaceholder, $attributeNameToOriginal, $rawAttributes] = $component->replaceDynamicPortionsWithPlaceholders(
@@ -122,7 +122,7 @@ public function fold(Node $node): Node
 
             return new TextNode($finalHtml);
 
-        } catch (InvalidPureUsageException $e) {
+        } catch (InvalidBlazeFoldUsageException $e) {
             throw $e;
         } catch (\Exception $e) {
             if (app('blaze')->isDebugging()) {
@@ -133,7 +133,7 @@ public function fold(Node $node): Node
         }
     }
 
-    protected function validatePureComponent(string $source, string $componentPath): void
+    protected function validateFoldableComponent(string $source, string $componentPath): void
     {
         $problematicPatterns = [
             '@once' => 'forOnce',
@@ -148,7 +148,7 @@ protected function validatePureComponent(string $source, string $componentPath):
 
         foreach ($problematicPatterns as $pattern => $factoryMethod) {
             if (preg_match('/' . $pattern . '/', $source)) {
-                throw InvalidPureUsageException::{$factoryMethod}($componentPath);
+                throw InvalidBlazeFoldUsageException::{$factoryMethod}($componentPath);
             }
         }
     }
diff --git a/src/Memoizer/Memoizer.php b/src/Memoizer/Memoizer.php
index c45e9cf1..1a921702 100644
--- a/src/Memoizer/Memoizer.php
+++ b/src/Memoizer/Memoizer.php
@@ -5,7 +5,7 @@
 use Livewire\Blaze\Nodes\ComponentNode;
 use Livewire\Blaze\Nodes\TextNode;
 use Livewire\Blaze\Nodes\Node;
-use Livewire\Blaze\Pure\Pure;
+use Livewire\Blaze\Directive\BlazeDirective;
 
 class Memoizer
 {
@@ -31,14 +31,14 @@ public function isMemoizable(Node $node): bool
 
             $source = file_get_contents($componentPath);
 
-            $pureParameters = Pure::getParameters($source);
+            $directiveParameters = BlazeDirective::getParameters($source);
 
-            if (is_null($pureParameters)) {
+            if (is_null($directiveParameters)) {
                 return false;
             }
 
             // Default to true if memo parameter is not specified
-            return $pureParameters['memo'] ?? true;
+            return $directiveParameters['memo'] ?? true;
 
         } catch (\Exception $e) {
             return false;
diff --git a/tests/BlazeTest.php b/tests/BlazeTest.php
index 6b1c5987..43826788 100644
--- a/tests/BlazeTest.php
+++ b/tests/BlazeTest.php
@@ -12,7 +12,7 @@
         View::addLocation(__DIR__ . '/fixtures/pages');
     });
 
-    it('renders pure components as optimized html through blade facade', function () {
+    it('renders foldable components as optimized html through blade facade', function () {
         // This is still outside-in - we're using Laravel's Blade facade, not calling Blaze directly
         $template = '
         <div class="page">
@@ -25,7 +25,7 @@
 
         $rendered = \Illuminate\Support\Facades\Blade::render($template);
 
-        // Pure components should be folded to optimized HTML
+        // Foldable components should be folded to optimized HTML
         expect($rendered)->toContain('<button type="button">Save Changes</button>');
         expect($rendered)->toContain('<div class="card">');
         expect($rendered)->toContain('<div class="alert">Success!</div>');
@@ -39,20 +39,20 @@
         expect($rendered)->toContain('<h1>Integration Test</h1>');
     });
 
-    it('leaves non-pure components unchanged through blade facade', function () {
-        $template = '<div><x-impure-button>Test Button</x-impure-button></div>';
+    it('leaves unfoldable components unchanged through blade facade', function () {
+        $template = '<div><x-unfoldable-button>Test Button</x-unfoldable-button></div>';
         $rendered = \Illuminate\Support\Facades\Blade::render($template);
 
-        // Non-pure component should render normally (not folded)
+        // Unfoldable component should render normally (not folded)
         expect($rendered)->toContain('<button type="button">Test Button</button>');
-        expect($rendered)->not->toContain('<x-impure-button>');
+        expect($rendered)->not->toContain('<x-unfoldable-button>');
 
         // Just verify it renders normally
     });
 
-    it('throws exception for components with invalid pure usage', function () {
-        expect(fn() => \Illuminate\Support\Facades\Blade::render('<x-invalid-pure.errors>Test</x-invalid-pure.errors>'))
-            ->toThrow(\Livewire\Blaze\Exceptions\InvalidPureUsageException::class);
+    it('throws exception for components with invalid foldable usage', function () {
+        expect(fn() => \Illuminate\Support\Facades\Blade::render('<x-invalid-foldable.errors>Test</x-invalid-foldable.errors>'))
+            ->toThrow(\Livewire\Blaze\Exceptions\InvalidBlazeFoldUsageException::class);
     });
 
     it('preserves slot content when folding components', function () {
diff --git a/tests/FoldTest.php b/tests/FoldTest.php
index d1b0d8ab..538c1703 100644
--- a/tests/FoldTest.php
+++ b/tests/FoldTest.php
@@ -72,8 +72,8 @@ function compile(string $input): string {
     });
 
     it('dynamic slot with unfoldable component', function () {
-        $input = '<x-button><x-impure-button>{{ $name }}</x-impure-button></x-button>';
-        $output = '<button type="button"><x-impure-button>{{ $name }}</x-impure-button></button>';
+        $input = '<x-button><x-unfoldable-button>{{ $name }}</x-unfoldable-button></x-button>';
+        $output = '<button type="button"><x-unfoldable-button>{{ $name }}</x-unfoldable-button></button>';
 
         expect(compile($input))->toBe($output);
     });
@@ -123,25 +123,25 @@ function compile(string $input): string {
         expect(compile($input))->toBe($output);
     });
 
-    it('component without @pure is not folded', function () {
-        $input = '<x-impure-button>Save</x-impure-button>';
-        $output = '<x-impure-button>Save</x-impure-button>';
+    it('component without @blaze is not folded', function () {
+        $input = '<x-unfoldable-button>Save</x-unfoldable-button>';
+        $output = '<x-unfoldable-button>Save</x-unfoldable-button>';
 
         expect(compile($input))->toBe($output);
     });
 
-    it('throws exception for invalid pure usage with $pattern', function (string $pattern, string $expectedPattern) {
+    it('throws exception for invalid foldable usage with $pattern', function (string $pattern, string $expectedPattern) {
         $folder = app('blaze')->folder();
-        $componentNode = new \Livewire\Blaze\Nodes\ComponentNode("invalid-pure.{$pattern}", 'x', '', [], false);
+        $componentNode = new \Livewire\Blaze\Nodes\ComponentNode("invalid-foldable.{$pattern}", 'x', '', [], false);
 
         expect(fn() => $folder->fold($componentNode))
-            ->toThrow(\Livewire\Blaze\Exceptions\InvalidPureUsageException::class);
+            ->toThrow(\Livewire\Blaze\Exceptions\InvalidBlazeFoldUsageException::class);
 
         try {
             $folder->fold($componentNode);
-        } catch (\Livewire\Blaze\Exceptions\InvalidPureUsageException $e) {
-            expect($e->getMessage())->toContain('Invalid @pure usage');
-            expect($e->getComponentPath())->toContain("invalid-pure/{$pattern}.blade.php");
+        } catch (\Livewire\Blaze\Exceptions\InvalidBlazeFoldUsageException $e) {
+            expect($e->getMessage())->toContain('Invalid @blaze fold usage');
+            expect($e->getComponentPath())->toContain("invalid-foldable/{$pattern}.blade.php");
             expect($e->getProblematicPattern())->toBe($expectedPattern);
         }
     })->with([
@@ -172,22 +172,22 @@ function compile(string $input): string {
     });
 
     it('supports folding aware components with single word attributes', function () {
-        $input = '<x-group variant="primary"><x-pure-item /></x-group>';
+        $input = '<x-group variant="primary"><x-foldable-item /></x-group>';
         $output = '<div class="group group-primary" data-test="foo"><div class="item item-primary"></div></div>';
 
         expect(compile($input))->toBe($output);
     });
 
     it('supports folding aware components with hyphenated attributes', function () {
-        $input = '<x-group variant="primary" second-variant="secondary"><x-pure-item /></x-group>';
+        $input = '<x-group variant="primary" second-variant="secondary"><x-foldable-item /></x-group>';
         $output = '<div class="group group-primary" data-test="foo" data-second-variant="secondary"><div class="item item-primary item-secondary"></div></div>';
 
         expect(compile($input))->toBe($output);
     });
 
     it('supports folding aware components with two wrapping components both with the same prop the closest one wins', function () {
-        $input = '<x-group variant="primary"><x-group variant="secondary"><x-pure-item /></x-group></x-group>';
-        // The pure-item should render the `secondary` variant because it is the closest one to the pure-item...
+        $input = '<x-group variant="primary"><x-group variant="secondary"><x-foldable-item /></x-group></x-group>';
+        // The foldable-item should render the `secondary` variant because it is the closest one to the foldable-item...
         $output = '<div class="group group-primary" data-test="foo"><div class="group group-secondary" data-test="foo"><div class="item item-secondary"></div></div></div>';
 
         expect(compile($input))->toBe($output);
@@ -256,7 +256,7 @@ function compile(string $input): string {
 
     it('cant fold dynamic props that get formatted', function () {
         $input = '<?php $date = "2025-07-11 13:22:41 UTC"; ?> <x-date :date="$date" />';
-        $output = '<?php $date = "2025-07-11 13:22:41 UTC"; ?> <?php $blaze_memoized_key = \Livewire\Blaze\Memoizer\Memo::key("date", [\'date\' => $date]); ?>\n<?php if (! \Livewire\Blaze\Memoizer\Memo::has($blaze_memoized_key)) : ?><?php ob_start(); ?><x-date :date="$date" /><?php \Livewire\Blaze\Memoizer\Memo::put($blaze_memoized_key, ob_get_clean()); ?><?php endif; ?><?php echo \Livewire\Blaze\Memoizer\Memo::get($blaze_memoized_key); ?>';
+        $output = '<?php $date = "2025-07-11 13:22:41 UTC"; ?> <?php $blaze_memoized_key = \Livewire\Blaze\Memoizer\Memo::key("date", [\'date\' => $date]); ?><?php if (! \Livewire\Blaze\Memoizer\Memo::has($blaze_memoized_key)) : ?><?php ob_start(); ?><x-date :date="$date" /><?php \Livewire\Blaze\Memoizer\Memo::put($blaze_memoized_key, ob_get_clean()); ?><?php endif; ?><?php echo \Livewire\Blaze\Memoizer\Memo::get($blaze_memoized_key); ?>';
 
         expect(compile($input))->toBe($output);
     });
diff --git a/tests/InfiniteRecursionTest.php b/tests/InfiniteRecursionTest.php
index b9b35f52..52b61d6c 100644
--- a/tests/InfiniteRecursionTest.php
+++ b/tests/InfiniteRecursionTest.php
@@ -20,7 +20,7 @@
         expect($rendered)->not->toContain('<x-button');
     });
 
-    it('should handle nested pure components without infinite recursion', function () {
+    it('should handle nested foldable components without infinite recursion', function () {
         $template = '<x-card><x-alert message="Nested alert!" /></x-card>';
 
         // This should complete without hanging or crashing
@@ -41,7 +41,7 @@
             <x-button type="submit" class="secondary">Button 2</x-button>
         </x-card>';
 
-        // This should complete without hanging or crashing  
+        // This should complete without hanging or crashing
         $rendered = \Illuminate\Support\Facades\Blade::render($template);
 
         expect($rendered)->toContain('<div class="card">');
@@ -85,8 +85,8 @@
     it('should handle components with variable attributes without infinite recursion', function () {
         // Test components with dynamic/variable attributes that might trigger edge cases
         $template = '
-        <x-button 
-            type="submit" 
+        <x-button
+            type="submit"
             class="btn-primary btn-large"
             data-action="save"
             aria-label="Save changes">
diff --git a/tests/MemoizeTest.php b/tests/MemoizeTest.php
index 7de54bde..e4ddca05 100644
--- a/tests/MemoizeTest.php
+++ b/tests/MemoizeTest.php
@@ -12,7 +12,7 @@
         Artisan::call('view:clear');
     });
 
-    it('can memoize an impure component', function () {
+    it('can memoize an unfoldable component', function () {
         $template = '<x-memoize />';
 
         $renderedA = app('blade.compiler')->render($template);
@@ -43,4 +43,4 @@
         expect($renderedA)->toContain('<div>');
         expect($renderedA)->not->toBe($renderedB);
     });
-});
\ No newline at end of file
+});
diff --git a/tests/fixtures/components/alert.blade.php b/tests/fixtures/components/alert.blade.php
index fdb54f57..284903cb 100644
--- a/tests/fixtures/components/alert.blade.php
+++ b/tests/fixtures/components/alert.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props(['message' => null])
 
diff --git a/tests/fixtures/components/avatar.blade.php b/tests/fixtures/components/avatar.blade.php
index 52d96b2b..e47aeedf 100644
--- a/tests/fixtures/components/avatar.blade.php
+++ b/tests/fixtures/components/avatar.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props([
     'iconVariant' => 'solid',
diff --git a/tests/fixtures/components/button.blade.php b/tests/fixtures/components/button.blade.php
index 7745a2b6..c6fe643e 100644
--- a/tests/fixtures/components/button.blade.php
+++ b/tests/fixtures/components/button.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props(['type' => 'button'])
 
diff --git a/tests/fixtures/components/card.blade.php b/tests/fixtures/components/card.blade.php
index 64a351f6..38daa5cd 100644
--- a/tests/fixtures/components/card.blade.php
+++ b/tests/fixtures/components/card.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props([])
 
diff --git a/tests/fixtures/components/date.blade.php b/tests/fixtures/components/date.blade.php
index 0932a0ce..32a9e7eb 100644
--- a/tests/fixtures/components/date.blade.php
+++ b/tests/fixtures/components/date.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props(['date'])
 
diff --git a/tests/fixtures/components/pure-item.blade.php b/tests/fixtures/components/foldable-item.blade.php
similarity index 95%
rename from tests/fixtures/components/pure-item.blade.php
rename to tests/fixtures/components/foldable-item.blade.php
index c8815e5c..b0c21153 100644
--- a/tests/fixtures/components/pure-item.blade.php
+++ b/tests/fixtures/components/foldable-item.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @aware(['variant', 'secondVariant' => null ])
 
diff --git a/tests/fixtures/components/form/fields/text.blade.php b/tests/fixtures/components/form/fields/text.blade.php
index d4ab65b0..58ae3988 100644
--- a/tests/fixtures/components/form/fields/text.blade.php
+++ b/tests/fixtures/components/form/fields/text.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props([])
 
diff --git a/tests/fixtures/components/form/index.blade.php b/tests/fixtures/components/form/index.blade.php
index 072a060e..4ad00762 100644
--- a/tests/fixtures/components/form/index.blade.php
+++ b/tests/fixtures/components/form/index.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props([])
 
diff --git a/tests/fixtures/components/form/input.blade.php b/tests/fixtures/components/form/input.blade.php
index d09419f9..aaf14c0f 100644
--- a/tests/fixtures/components/form/input.blade.php
+++ b/tests/fixtures/components/form/input.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props([])
 
diff --git a/tests/fixtures/components/group.blade.php b/tests/fixtures/components/group.blade.php
index 69748448..420fc931 100644
--- a/tests/fixtures/components/group.blade.php
+++ b/tests/fixtures/components/group.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props(['variant' => '', 'dataTest' => 'foo', 'secondVariant' => null])
 
diff --git a/tests/fixtures/components/invalid-pure/auth.blade.php b/tests/fixtures/components/invalid-foldable/auth.blade.php
similarity index 88%
rename from tests/fixtures/components/invalid-pure/auth.blade.php
rename to tests/fixtures/components/invalid-foldable/auth.blade.php
index 1bed37f3..7e1ef043 100644
--- a/tests/fixtures/components/invalid-pure/auth.blade.php
+++ b/tests/fixtures/components/invalid-foldable/auth.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 <div>
     Welcome, {{ auth()->user()->name }}
diff --git a/tests/fixtures/components/invalid-pure/aware.blade.php b/tests/fixtures/components/invalid-foldable/aware.blade.php
similarity index 93%
rename from tests/fixtures/components/invalid-pure/aware.blade.php
rename to tests/fixtures/components/invalid-foldable/aware.blade.php
index ea94b2ce..779f9a80 100644
--- a/tests/fixtures/components/invalid-pure/aware.blade.php
+++ b/tests/fixtures/components/invalid-foldable/aware.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @aware(['variant' => 'default'])
 
diff --git a/tests/fixtures/components/invalid-pure/csrf.blade.php b/tests/fixtures/components/invalid-foldable/csrf.blade.php
similarity index 88%
rename from tests/fixtures/components/invalid-pure/csrf.blade.php
rename to tests/fixtures/components/invalid-foldable/csrf.blade.php
index 7c7c6a5a..96adf89d 100644
--- a/tests/fixtures/components/invalid-pure/csrf.blade.php
+++ b/tests/fixtures/components/invalid-foldable/csrf.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 <form method="POST">
     @csrf
diff --git a/tests/fixtures/components/invalid-pure/error.blade.php b/tests/fixtures/components/invalid-foldable/error.blade.php
similarity index 94%
rename from tests/fixtures/components/invalid-pure/error.blade.php
rename to tests/fixtures/components/invalid-foldable/error.blade.php
index 2104184b..921e1e3c 100644
--- a/tests/fixtures/components/invalid-pure/error.blade.php
+++ b/tests/fixtures/components/invalid-foldable/error.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props(['name'])
 
diff --git a/tests/fixtures/components/invalid-pure/errors.blade.php b/tests/fixtures/components/invalid-foldable/errors.blade.php
similarity index 91%
rename from tests/fixtures/components/invalid-pure/errors.blade.php
rename to tests/fixtures/components/invalid-foldable/errors.blade.php
index 70252e29..16bd2d2e 100644
--- a/tests/fixtures/components/invalid-pure/errors.blade.php
+++ b/tests/fixtures/components/invalid-foldable/errors.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 <div class="{{ $errors->has('name') ? 'error' : '' }}">
     {{ $slot }}
diff --git a/tests/fixtures/components/invalid-pure/old.blade.php b/tests/fixtures/components/invalid-foldable/old.blade.php
similarity index 90%
rename from tests/fixtures/components/invalid-pure/old.blade.php
rename to tests/fixtures/components/invalid-foldable/old.blade.php
index 33f9be65..6380f2b0 100644
--- a/tests/fixtures/components/invalid-pure/old.blade.php
+++ b/tests/fixtures/components/invalid-foldable/old.blade.php
@@ -1,3 +1,3 @@
-@pure
+@blaze
 
 <input type="text" name="email" value="{{ old('email') }}" />
diff --git a/tests/fixtures/components/invalid-pure/once.blade.php b/tests/fixtures/components/invalid-foldable/once.blade.php
similarity index 96%
rename from tests/fixtures/components/invalid-pure/once.blade.php
rename to tests/fixtures/components/invalid-foldable/once.blade.php
index 967d94fc..0ee27556 100644
--- a/tests/fixtures/components/invalid-pure/once.blade.php
+++ b/tests/fixtures/components/invalid-foldable/once.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props(['title'])
 
diff --git a/tests/fixtures/components/invalid-pure/request.blade.php b/tests/fixtures/components/invalid-foldable/request.blade.php
similarity index 88%
rename from tests/fixtures/components/invalid-pure/request.blade.php
rename to tests/fixtures/components/invalid-foldable/request.blade.php
index 08c88572..1cb23303 100644
--- a/tests/fixtures/components/invalid-pure/request.blade.php
+++ b/tests/fixtures/components/invalid-foldable/request.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 <div>
     Current URL: {{ request()->url() }}
diff --git a/tests/fixtures/components/invalid-pure/session.blade.php b/tests/fixtures/components/invalid-foldable/session.blade.php
similarity index 89%
rename from tests/fixtures/components/invalid-pure/session.blade.php
rename to tests/fixtures/components/invalid-foldable/session.blade.php
index 58d7d1f4..b7ef58dc 100644
--- a/tests/fixtures/components/invalid-pure/session.blade.php
+++ b/tests/fixtures/components/invalid-foldable/session.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 <div class="message">
     {{ session('message') }}
diff --git a/tests/fixtures/components/memoize.blade.php b/tests/fixtures/components/memoize.blade.php
index 1c75096a..b7fb7ab8 100644
--- a/tests/fixtures/components/memoize.blade.php
+++ b/tests/fixtures/components/memoize.blade.php
@@ -1,3 +1,3 @@
-@pure(fold: false)
+@blaze(fold: false)
 
 <div>{{ str()->random() }}</div>
diff --git a/tests/fixtures/components/modal.blade.php b/tests/fixtures/components/modal.blade.php
index 53e08d43..4fd1a1cc 100644
--- a/tests/fixtures/components/modal.blade.php
+++ b/tests/fixtures/components/modal.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props([
     'header' => '',
diff --git a/tests/fixtures/components/panel/panel.blade.php b/tests/fixtures/components/panel/panel.blade.php
index 9b66a50a..3d7fc075 100644
--- a/tests/fixtures/components/panel/panel.blade.php
+++ b/tests/fixtures/components/panel/panel.blade.php
@@ -1,4 +1,4 @@
-@pure
+@blaze
 
 @props([])
 
diff --git a/tests/fixtures/components/impure-button.blade.php b/tests/fixtures/components/unfoldable-button.blade.php
similarity index 100%
rename from tests/fixtures/components/impure-button.blade.php
rename to tests/fixtures/components/unfoldable-button.blade.php
diff --git a/tests/fixtures/pages/integration-test.blade.php b/tests/fixtures/pages/integration-test.blade.php
index cfd17158..e83921a9 100644
--- a/tests/fixtures/pages/integration-test.blade.php
+++ b/tests/fixtures/pages/integration-test.blade.php
@@ -1,13 +1,13 @@
 <div class="page">
     <h1>Integration Test Page</h1>
-    
-    <!-- Pure component should get folded -->
+
+    <!-- Foldable component should get folded -->
     <x-button>Save Changes</x-button>
-    
-    <!-- Non-pure component should stay as component tag -->
-    <x-impure-button>Cancel</x-impure-button>
-    
-    <!-- Nested pure components should get folded -->
+
+    <!-- Non-foldable component should stay as component tag -->
+    <x-unfoldable-button>Cancel</x-unfoldable-button>
+
+    <!-- Nested foldable components should get folded -->
     <x-card>
         <x-alert message="Success!" />
     </x-card>
diff --git a/tests/fixtures/pages/invalid-foldable-test.blade.php b/tests/fixtures/pages/invalid-foldable-test.blade.php
new file mode 100644
index 00000000..b12aedc9
--- /dev/null
+++ b/tests/fixtures/pages/invalid-foldable-test.blade.php
@@ -0,0 +1,6 @@
+<div class="page">
+    <h1>Invalid Foldable Test</h1>
+
+    <!-- This should throw an exception because invalid-foldable has @blaze but uses $errors -->
+    <x-invalid-foldable>This should fail</x-invalid-foldable>
+</div>
diff --git a/tests/fixtures/pages/invalid-pure-test.blade.php b/tests/fixtures/pages/invalid-pure-test.blade.php
deleted file mode 100644
index 52723070..00000000
--- a/tests/fixtures/pages/invalid-pure-test.blade.php
+++ /dev/null
@@ -1,6 +0,0 @@
-<div class="page">
-    <h1>Invalid Pure Test</h1>
-    
-    <!-- This should throw an exception because invalid-pure has @pure but uses $errors -->
-    <x-invalid-pure>This should fail</x-invalid-pure>
-</div>
\ No newline at end of file