skills

shadcn-vue for Vue/Nuxt with Reka UI components and Tailwind. Use for accessible UI, Auto Form, data tables, charts, dark mode, MCP server setup, or encountering component imports, Reka UI errors.

Decompose large Vue 3 components into focused SFCs and composables with explicit contracts, simple templates, and SSR-safe side effects.

Enforces an opinionated UI baseline to prevent AI-generated interface slop.

Keep cyclomatic complexity low; flatten control flow, extract helpers, and prefer table-driven/strategy patterns over large switches

Use API Resources with pagination and conditional fields; keep response shapes stable and cache-friendly

Portable storage configuration across S3/R2/MinIO with optional CDN—env toggles, path-style endpoints, and URL generation

Replace hardcoded values with constants, enums, and configuration for maintainability; use PHP 8.1+ enums and config files

Reduce controller bloat using Form Requests for auth/validation, small Actions/Services with DTOs, and resource/single-action controllers

Write focused controller tests using HTTP assertions; keep heavy logic in Actions/Services and unit test them

Create and register small, pure helper functions when they improve clarity; keep them organized and tested

Process large datasets efficiently using chunk(), chunkById(), lazy(), and cursor() to reduce memory consumption and improve performance

Create effective debugging prompts—include error messages, stack traces, expected vs actual behavior, logs, and attempted solutions

Remove unneeded Composer packages and assets to improve boot time, memory, and security surface

Store and serve files via Storage; set visibility, generate URLs, and handle streaming safely

Use interfaces and dependency injection to decouple code; bind implementations in the container

Build with i18n in mind from day one using Laravel translation helpers, JSON files, Blade integration, and locale management

Refine AI-generated code through specific feedback—point out errors, identify gaps, show desired changes, reference style guides

Safe database change patterns; when to modify vs add migrations; always pair models with migrations and factories; seeding guidance

Use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctness

Prevent N+1 queries by eager loading; enable lazy-loading protection in non-production; choose selective fields

Select only required columns to reduce memory and transfer costs; apply to base queries and relations

Enforce access via Policies and Gates; use authorize() and authorizeResource() to standardize controller protections

Use Laravel-specific vocabulary—Eloquent patterns, Form Requests, API resources, jobs/queues—to get idiomatic framework code

Unified quality gates for Laravel projects; Pint, static analysis (PHPStan/Psalm), Insights (optional), and JS linters; Sail and non-Sail pairs provided

Apply per-user and per-route limits with RateLimiter and throttle middleware; use backoffs and headers for clients

Keep routes clean and focused on mapping requests to controllers; avoid business logic, validation, or database operations in route files

Use the Strategy pattern to select behavior at runtime; bind multiple implementations to a shared interface

Schedule tasks with safety; use withoutOverlapping, onOneServer, and visibility settings for reliable cron execution

Stabilize workflows with Template Method or Strategy; extend by adding new classes instead of editing core logic

Wrap multi-write operations in transactions; use dispatchAfterCommit and idempotency patterns to ensure consistency