formatting tweaks

Author: taylorotwell

.ai/boost/core.blade.php

@@ -1,33 +1,32 @@
 # URLs
-- Whenever you create a URL use the `get-absolute-url` tool to ensure you're using the correct scheme, domain/IP, and port.
+Whenever you create a URL use the `get-absolute-url` tool to ensure you're using the correct scheme, domain / IP, and port.
 
 # Artisan
-- Use the `list-artisan-commands` tool when needing to call an artisan command to triple check the available params
+Use the `list-artisan-commands` tool when you need to call an artisan command to triple check the available parameters.
 
 # Tinker / Debugging
-You should use the `tinker` tool from Boost MCP when you need to run PHP to debug code or query eloquent models directly.
-Use the `database-query` tool when you only need to read from the database.
+You should use the `tinker` tool from Boost MCP when you need to run PHP to debug code or query Eloquent models directly.
 
+Use the `database-query` tool when you only need to read from the database.
 
 # Reading browser logs
 Only recent browser logs will be useful, discard any that are older than two hours or so.
 
 # Searching documentation
-
 Check the docs before making code changes to ensure we are approaching this in the correct way. Use multiple simple topic based queries.
 
 Boost comes with a powerful `search-docs` tool you should use before any other approaches. This tool automatically passes a list of installed packages and their versions to the remote Boost API, so it returns only version-specific documentation specific for the user's circumstance. You should pass an array of packages to filter docs on if you know you need docs for particular packages.
 
-'search-docs' tool is perfect for all Laravel related packages. Laravel, inertia, pest, livewire, nova, nightwatch, and more.
+The 'search-docs' tool is perfect for all Laravel related packages. Laravel, Inertia, Pest, Livewire, Nova, Nightwatch, and more.
 
 You must use this tool to search for Laravel-ecosystem docs before falling back to other approaches.
 
-## Available Search Syntax
+## Available search syntax
 You can and should pass multiple queries at once, the most relevant will be returned first. Start specific, broaden after.
 
 1. Simple Word Searches with auto-stemming - query=authentication - finds 'authenticate' and 'auth'
 2. Multiple Words (AND Logic) - query=rate limit - finds knowledge containing both "queue" AND "worker"
-3. Quoted Phrases (Exact Position) - query="infinite scroll - Words must be adjacent in that order
+3. Quoted Phrases (Exact Position) - query="infinite scroll - Words must be adjacent and in that order
 4. Mixed Queries - query=middleware "rate limit" - "middleware" AND exact phrase "rate limit"
 5. Multiple Queries - queries=["authentication", "middleware"] - ANY of these terms
 

.ai/core.blade.php

@@ -15,18 +15,18 @@
 
 ## Conventions
 - You must follow all existing code conventions used in this project. When creating or editing a file, check sibling files for the correct structure, approach, naming.
-- Use descriptive names. e.g. `isRegisteredForDiscounts` not `discount()`
+- Use descriptive names. For example, `isRegisteredForDiscounts` not `discount()`.
 
-## Verification scripts
-- Do not create verification scripts or tinker when tests cover that functionality and prove it works. Unit & feature tests are more important.
+## Verification Scripts
+- Do not create verification scripts or tinker when tests cover that functionality and prove it works. Unit and feature tests are more important.
 
-## Project Structure & Architecture
+## Project Structure and Architecture
 - Stick to existing directory structure - no new base folders without approval.
 - No dependency changes without approval.
 
 ## Replies
 - Be concise in your explanations - focus on what's important rather than explaining obvious details.
 
-## Documentation files
+## Documentation Files
 - You must only create documentation files if explicitly requested by the user.
 

.ai/fluxui-free/core.blade.php

@@ -5,4 +5,4 @@
     <flux:button variant="primary"/>
 </code-snippet>
 - Fallback to standard Blade components if Flux is unavailable.
-- Use Laravel Boost's `search-docs` tool to get the exact documentation & code snippets available for this project.
+- Use Laravel Boost's `search-docs` tool to get the exact documentation and code snippets available for this project.

.ai/fluxui-pro/core.blade.php

@@ -5,4 +5,4 @@
     <flux:button variant="primary"/>
 </code-snippet>
 - Fallback to standard Blade components if Flux is unavailable.
-- Use Laravel Boost's `search-docs` tool to get the exact documentation & code snippets available for this project.
+- Use Laravel Boost's `search-docs` tool to get the exact documentation and code snippets available for this project.

.ai/inertia-laravel/1/core.blade.php

@@ -1,4 +1,4 @@
-Inertia v1 core
+## Inertia v1 Core
 
 - Inertia v1 does _not_ come with these features. Do not recommend using these Inertia v2 features directly.
     - Polling

.ai/inertia-laravel/2/core.blade.php

@@ -1,10 +1,13 @@
+## Inertia v2 Core
+
 - Make use of all Inertia features from v1 & v2
 
-## Inertia v2 new features
+## Inertia v2 New Features
+
 - Polling
 - Prefetching
 - Deferred props
 - Infinite scrolling using merging props and WhenVisible
 - Lazy loading data on scroll
 
-- When using deferred props on the frontend we should add a nice empty state with pulsing/animated skeleton/blocks. Check the docs before making any changes to ensure we are approaching this in the correct way.
+- When using deferred props on the frontend we should add a nice empty state with pulsing / animated skeleton. Check the docs before making any changes to ensure we are approaching this in the correct way.

.ai/inertia-laravel/core.blade.php

@@ -1,7 +1,7 @@
-## InertiaJS Core
+## Inertia Core
 
-- Inertia.js components should be placed in the `resources/js/Pages` directory
-- Use `Inertia::render()` for server-side routing instead of traditional Blade views
+- Inertia.js components should be placed in the `resources/js/Pages` directory.
+- Use `Inertia::render()` for server-side routing instead of traditional Blade views.
 <code-snippet lang="php" name="Inertia::render example">
     // routes/web.php example
     Route::get('/users', function () {

.ai/inertia-react/core.blade.php

@@ -1,11 +1,11 @@
-- Use `router.visit()` or `<Link>` for navigation instead of traditional links
+- Use `router.visit()` or `<Link>` for navigation instead of traditional links.
 <code-snippet lang="react" name="Inertia client navigation">
     import { Link } from '@inertiajs/react'
 
     <Link href="/">Home</Link>
 </code-snippet>
 
-- For form handling, use `router.post` and related methods, do not use regular forms
+- For form handling, use `router.post` and related methods, do not use regular forms.
 <code-snippet lang="react" name="Form example">
 import { useState } from 'react'
 import { router } from '@inertiajs/react'

.ai/inertia-vue/core.blade.php

@@ -1,12 +1,12 @@
-- Vue components must have a single root element
-- Use `router.visit()` or `<Link>` for navigation instead of traditional links
+- Vue components must have a single root element.
+- Use `router.visit()` or `<Link>` for navigation instead of traditional links.
 <code-snippet lang="vue" name="Inertia client navigation">
     import { Link } from '@inertiajs/vue3'
 
     <Link href="/">Home</Link>
 </code-snippet>
 
-- For form handling, use `router.post` and related methods, do not use regular forms
+- For form handling, use `router.post` and related methods, do not use regular forms.
 <code-snippet lang="vue" name="Form example">
     <script setup>
     import { reactive } from 'vue'

.ai/laravel/10/core.blade.php

@@ -1 +1 @@
-Laravel 10 Core
+## Laravel 10 Core