Merge pull request #117 from CodeWithDennis/chore/setup-script-and-boost-refresh

chore: add composer setup script and refresh dependencies

Author: CodeWithDennis

.cursor/skills/debug-using-debugbar/SKILL.md

@@ -0,0 +1,102 @@
+---
+name: debug-using-debugbar
+description: >
+  Use this skill to optimize requests or debug Laravel application issues — slow pages, N+1 queries, exceptions,
+  failed requests, or unexpected behavior — by inspecting data captured by Laravel Debugbar via
+  Artisan CLI commands. Use when the user asks to investigate a bug, diagnose a slow request,
+  find duplicate queries, check what happened on a previous request, or optimize database
+  performance, even if they don't explicitly mention "debugbar" or "profiling."
+compatibility: Requires Laravel with fruitcake/laravel-debugbar installed and debug mode enabled.
+---
+
+## Debugging and optimizing workflow
+
+1. Find the relevant request:
+   ```bash
+   php artisan debugbar:find --issues --max=50
+   ```
+2. Inspect the request summary to identify which collectors have data:
+   ```bash
+   php artisan debugbar:get {id}
+   ```
+3. Drill into the relevant collector based on the issue type:
+   ```bash
+   php artisan debugbar:get {id} --collector=exceptions
+   ```
+4. For query issues, use dedicated query analysis:
+   ```bash
+   php artisan debugbar:queries {id}
+   ```
+5. Trace the problem to source code using backtraces, then fix and re-test.
+
+## Finding requests
+
+```bash
+
+# List recent requests (shows summary with status, duration, memory, query count)
+
+php artisan debugbar:find
+
+# Filter by URI pattern (fnmatch) and/or HTTP method
+
+php artisan debugbar:find --uri="/api/*" --method=POST
+
+# Only show requests with issues (exceptions, slow queries, duplicates, errors)
+
+php artisan debugbar:find --issues --max=50
+
+# Customize issue thresholds (defaults: --min-queries=50, --min-duration=1000, --min-duplicates=2)
+
+php artisan debugbar:find --issues --min-queries=10 --min-duration=500
+
+# Threshold options also work standalone, filtering on just that criteria
+
+php artisan debugbar:find --min-queries=20
+```
+
+`--issues` flags: exceptions, non-2xx status, high query count, slow queries, duplicate query groups, slow request duration, and failed queries. Issue filtering applies on top of the fetched result set — increase `--max` to scan further back.
+
+## Inspecting a request
+
+```bash
+
+# Summary of all collectors (available collectors depend on config)
+
+php artisan debugbar:get latest
+php artisan debugbar:get {id}
+
+# Full data for a specific collector
+
+php artisan debugbar:get {id} --collector=exceptions
+```
+
+Pick the collector by issue type:
+- **Error/500** → `exceptions` · **Slow page** → `queries`, `time` · **Auth** → `auth`, `gate` · **Cache** → `cache`
+
+## Analyzing queries
+
+```bash
+
+# Overview with duplicate detection and slow query flags
+
+php artisan debugbar:queries {id}
+
+# Backtrace and params for a specific statement
+
+php artisan debugbar:queries {id} --statement=N
+
+# EXPLAIN plan or re-execute a SELECT
+
+php artisan debugbar:queries {id} --statement=N --explain
+php artisan debugbar:queries {id} --statement=N --result
+```
+
+Duplicate queries are a strong N+1 signal. Use `--statement=N` to get the backtrace and find the origin.
+
+## Gotchas
+
+- Always start with `debugbar:find --issues` rather than `debugbar:find` — the issue flags surface the most actionable requests immediately.
+- The `{id}` is the request ID from the `debugbar:find` output, or use `latest` to inspect the most recent request.
+- Collector availability depends on the app's debugbar config — the summary from `debugbar:get` shows which collectors have data.
+- `--explain` and `--result` only work on SELECT queries. They re-execute against the current database, so results may differ from the original request.
+- `debugbar:clear` removes all stored data — use it to reset between debugging sessions, not mid-investigation.

.cursor/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

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

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

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

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

.cursor/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.

.cursor/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']],
-```
+```

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

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

.cursor/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'));
-```
+```

.cursor/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
-```
+```

.cursor/skills/laravel-best-practices/rules/eloquent.md

@@ -145,4 +145,4 @@ Order::where('status', 'pending')->get();
 
 Prefer Eloquent queries and relationships over `DB::table()` whenever possible — they already reference the model's table. When `DB::table()` or raw joins are unavoidable, always use `(new Model)->getTable()` to keep the reference traceable.
 
-**Exception — migrations:** In migrations, hardcoded table names via `DB::table('settings')` are acceptable and preferred. Models change over time but migrations are frozen snapshots — referencing a model that is later renamed or deleted would break the migration.
+**Exception — migrations:** In migrations, hardcoded table names via `DB::table('settings')` are acceptable and preferred. Models change over time but migrations are frozen snapshots — referencing a model that is later renamed or deleted would break the migration.