boost

Author: kawax

.github/instructions/laravel-boost.instructions.md

@@ -24,12 +24,7 @@ This application is a Laravel application and its main Laravel ecosystems packag
 
 ## Skills Activation
 
-This project has domain-specific skills available. You MUST activate the relevant skill whenever you work in that domain—don't wait until you're stuck.
-
-- `laravel-best-practices` — Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.
-- `fluxui-development` — Use this skill for Flux UI development in Livewire applications only. Trigger when working with <flux:*> components, building or customizing Livewire component UIs, creating forms, modals, tables, or other interactive elements. Covers: flux: components (buttons, inputs, modals, forms, tables, date-pickers, kanban, badges, tooltips, etc.), component composition, Tailwind CSS styling, Heroicons/Lucide icon integration, validation patterns, responsive design, and theming. Do not use for non-Livewire frameworks or non-component styling.
-- `livewire-development` — Use for any task or question involving Livewire. Activate if user mentions Livewire, wire: directives, or Livewire-specific concepts like wire:model, wire:click, wire:sort, or islands, invoke this skill. Covers building new components, debugging reactivity issues, real-time form validation, drag-and-drop, loading states, migrating from Livewire 3 to 4, converting component formats (SFC/MFC/class-based), and performance optimization. Do not use for non-Livewire reactive UI (React, Vue, Alpine-only, Inertia.js) or standard Laravel forms without Livewire.
-- `tailwindcss-development` — Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.
+This project has domain-specific skills available in `**/skills/**`. You MUST activate the relevant skill whenever you work in that domain—don't wait until you're stuck.
 
 ## Conventions
 
@@ -89,7 +84,6 @@ This project has domain-specific skills available. You MUST activate the relevan
 - Run Artisan commands directly via the command line (e.g., `php artisan route:list`). Use `php artisan list` to discover available commands and `php artisan [command] --help` to check parameters.
 - Inspect routes with `php artisan route:list`. Filter with: `--method=GET`, `--name=users`, `--path=api`, `--except-vendor`, `--only-vendor`.
 - Read configuration values using dot notation: `php artisan config:show app.name`, `php artisan config:show database.default`. Or read config files directly from the `config/` directory.
-- To check environment variables, read the `.env` file directly.
 
 ## Tinker
 
@@ -108,6 +102,12 @@ This project has domain-specific skills available. You MUST activate the relevan
 - Prefer PHPDoc blocks over inline comments. Only add inline comments for exceptionally complex logic.
 - Use array shape type definitions in PHPDoc blocks.
 
+=== deployments rules ===
+
+# Deployment
+
+- Laravel can be deployed using [Laravel Cloud](https://cloud.laravel.com/), which is the fastest way to deploy and scale production Laravel applications.
+
 === tests rules ===
 
 # Test Enforcement
@@ -145,10 +145,6 @@ This project has domain-specific skills available. You MUST activate the relevan
 
 - If you receive an "Illuminate\Foundation\ViteException: Unable to locate file in Vite manifest" error, you can run `npm run build` or ask the user to run `npm run dev` or `composer run dev`.
 
-## Deployment
-
-- Laravel can be deployed using [Laravel Cloud](https://cloud.laravel.com/), which is the fastest way to deploy and scale production Laravel applications.
-
 === livewire/core rules ===
 
 # Livewire

.github/skills/fluxui-development/SKILL.md

@@ -27,7 +27,7 @@ Use Flux UI components when available. Fall back to standard Blade components wh
 
 ## Available Components (Free Edition)
 
-Available: avatar, badge, brand, breadcrumbs, button, callout, checkbox, dropdown, field, heading, icon, input, modal, navbar, otp-input, profile, radio, select, separator, skeleton, switch, text, textarea, tooltip
+Available: avatar, badge, brand, breadcrumbs, button, callout, card, checkbox, dropdown, field, heading, icon, input, modal, navbar, otp-input, pagination, profile, progress, radio, select, separator, skeleton, switch, table, text, textarea, toast, tooltip
 
 ## Icons
 
@@ -78,4 +78,4 @@ php artisan flux:icon crown grip-vertical github
 - Trying to use Pro-only components in the free edition
 - Not checking if a Flux component exists before creating custom implementations
 - Forgetting to use the `search-docs` tool for component-specific documentation
-- Not following existing project patterns for Flux usage
+- Not following existing project patterns for Flux usage

.github/skills/laravel-best-practices/SKILL.md

@@ -187,4 +187,4 @@ Always use a sub-agent to read rule files and explore this skill's content.
 
 1. Identify the file type and select relevant sections (e.g., migration → §16, controller → §1, §3, §5, §6, §10)
 2. Check sibling files for existing patterns — follow those first per Consistency First
-3. Verify API syntax with `search-docs` for the installed Laravel version
+3. Verify API syntax with `search-docs` for the installed Laravel version

.github/skills/laravel-best-practices/rules/advanced-queries.md

@@ -103,4 +103,4 @@ public function scopeOrderByLastLogin($query): void
         ->take(1)
     );
 }
-```
+```

.github/skills/laravel-best-practices/rules/architecture.md

@@ -199,4 +199,4 @@ class Customer extends Model
         return $this->belongsToMany(Role::class);
     }
 }
-```
+```

.github/skills/laravel-best-practices/rules/blade-views.md

@@ -33,4 +33,4 @@ return view('dashboard', compact('users'))
 
 ## Use `@aware` for Deeply Nested Component Props
 
-Avoids re-passing parent props through every level of nested components.
+Avoids re-passing parent props through every level of nested components.

.github/skills/laravel-best-practices/rules/caching.md

@@ -67,4 +67,4 @@ If Redis goes down, the app falls back to a secondary store automatically.
 
 ```php
 'failover' => ['driver' => 'failover', 'stores' => ['redis', 'database']],
-```
+```

.github/skills/laravel-best-practices/rules/collections.md

@@ -41,4 +41,4 @@ More declarative than overriding `newCollection()`.
 ```php
 #[CollectedBy(UserCollection::class)]
 class User extends Model {}
-```
+```

.github/skills/laravel-best-practices/rules/config.md

@@ -70,4 +70,4 @@ If the application already uses language files for localization, use `__()` for
 ```php
 // Only when lang files already exist in the project
 return back()->with('message', __('app.article_added'));
-```
+```

.github/skills/laravel-best-practices/rules/db-performance.md

@@ -189,4 +189,4 @@ return view('users.index', compact('users'));
 @foreach ($users as $user)
     {{ $user->profile->name }}
 @endforeach
-```
+```