reverts guidelines chcanges

Author: nunomaduro

.ai/inertia-react/2/forms.blade.php

@@ -1,8 +1,7 @@
-## Inertia + React Forms
-
 @php
 /** @var \Laravel\Boost\Install\GuidelineAssist $assist */
 @endphp
+## Inertia + React Forms
 
 @if($assist->inertia()->hasFormComponent())
 @boostsnippet("`<Form>` Component Example", "react")

.ai/inertia-svelte/2/forms.blade.php

@@ -1,8 +1,7 @@
-## Inertia + Svelte Forms
-
 @php
     /** @var \Laravel\Boost\Install\GuidelineAssist $assist */
 @endphp
+## Inertia + Svelte Forms
 
 - There are critical differences between Svelte 4 and 5, use the `search-docs` tool for up-to-date guidance.
 

.ai/laravel/core.blade.php

@@ -1,4 +1,4 @@
-## Laravel
+## Do Things the Laravel Way
 
 - Use `php artisan make:` commands to create new files (i.e. migrations, controllers, models, etc.). You can list available Artisan commands using the `list-artisan-commands` tool.
 - If you're creating a generic PHP class, use `artisan make:class`.

.ai/livewire/core.blade.php

@@ -1,4 +1,4 @@
-## Livewire
+## Livewire Core
 - Use the `search-docs` tool to find exact version specific documentation for how to write Livewire & Livewire tests.
 - Use the `php artisan make:livewire [Posts\\CreatePost]` artisan command to create new components
 - State should live on the server, with the UI reflecting it.

.ai/phpunit/core.blade.php

@@ -1,4 +1,4 @@
-## PHPUnit
+## PHPUnit Core
 
 - This application uses PHPUnit for testing. All tests must be written as PHPUnit classes. Use `php artisan make:test --phpunit <name>` to create a new test.
 - If you see a test using "Pest", convert it to PHPUnit.

.ai/pint/core.blade.php

@@ -1,4 +1,4 @@
-## Laravel Pint
+## Laravel Pint Code Formatter
 
 - You must run `vendor/bin/pint --dirty` before finalizing changes to ensure your code matches the project's expected style.
 - Do not run `vendor/bin/pint --test`, simply run `vendor/bin/pint` to fix any formatting issues.

.ai/tailwindcss/core.blade.php

@@ -1,4 +1,4 @@
-## Tailwind
+## Tailwind Core
 
 - Use Tailwind CSS classes to style HTML, check and use existing tailwind conventions within the project before writing your own.
 - Offer to extract repeated patterns into components that match the project's conventions (i.e. Blade, JSX, Vue, etc..)