Use whenever driving agent-browser against the local Relaticle app (relaticle.test and its panels) for testing, QA, business review, or UI automation. Covers Filament v5 + Livewire v4 quirks specific to this codebase: panel URL derivation (domain-routed vs path-routed — never assume), login flows for the app and…
TRIGGER when working with ai-sdk which is Laravel official first-party AI SDK. Activate when building, editing AI agents, chatbots, text generation, image generation, audio/TTS, transcription/STT, embeddings, RAG, vector stores, reranking, structured output, streaming, conversation memory, tools, queueing…
Use when the user asks to business-review their work (local mode default — 'business-review', 'review my branch'), a Relaticle pull request ('--pr ' or a bare PR number), or a described change (--describe). v3: panel-of-QAs engine — resolves the live environment first (URLs/creds/queue/Redis/Reverb are DISCOVERED from…
You are a code-reading subagent dispatched by the business-review skill during Stage 1 (Understand), at the close of the stage. Your single job: build the main agent's business context of the touched code so its case planning is grounded in what the code actually does, what its tests claim, and why it reached its…
You are a code-reading subagent dispatched by the business-review skill during Phase 4 (Understand). Your single job: read the PR diff + any new test files, output a structured JSON description of what the diff actually DOES behaviorally.
You are a grading subagent dispatched by rundriftcheck.py. Your single job: read a generated REVIEW.md (the output of a business-review eval-mode run) and score it 1-5 against a per-fixture rubric.
You are a text-reading subagent dispatched by the business-review skill during Phase 4 (Understand). Your single job: read the sanitized PR title + body + already-extracted acceptance criteria, and output a structured JSON description of what the PR CLAIMS to do.
Derives the run's journey map from the project profile and diff classification. This is the runtime replacement for v2's static journey catalog — there is no baked-in journey list. Every journey in the output traces to a real touched surface in the diff.
The parameterized subagent the fleet spawns (references/fleet.md). One template, many briefs. Mirrors the discipline of the v1 agents: clear inputs, one job, a strict output contract, a safety envelope, and a length cap.
The adversarial cold-reproducer. Implements references/verification.md as a dispatchable agent. Its existence is the fix for false-approves (failure mode A) without a wave of false-rejects.
Handles Laravel Cashier Stripe integration including subscriptions, webhooks, Stripe Checkout, invoices, charges, refunds, trials, coupons, metered billing, and payment failure handling. Triggered when a user mentions Cashier, Billable, IncompletePayment, stripeid, newSubscription, Stripe subscriptions, or billing.…
Use this skill whenever the user mentions Horizon by name in a Laravel context. Covers the full Horizon lifecycle: installing Horizon (horizon:install, Sail setup), configuring config/horizon.php (supervisor blocks, queue assignments, balancing strategies, minProcesses/maxProcesses), fixing the dashboard…
ACTIVATE when the user works on authentication in Laravel. This includes login, registration, password reset, email verification, two-factor authentication (2FA/TOTP/QR codes/recovery codes), passkeys, profile updates, password confirmation, or any auth-related routes and controllers. Activate when the user mentions…
Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow .ai/rules, resolve mixed or conflicting patterns (e.g. "are we using Form…
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…
Build filtered, sorted, and included API endpoints using spatie/laravel-query-builder. Activates when working with QueryBuilder, AllowedFilter, AllowedSort, AllowedInclude, or when the user mentions query parameters, API filtering, sorting, includes, or spatie/laravel-query-builder.
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…
Use this skill for Laravel MCP development. Trigger when creating or editing MCP tools, resources, prompts, servers, or UI apps in Laravel projects. Covers: artisan make:mcp- generators, routes/ai.php, Tool/Resource/Prompt/AppResource classes, schema validation, shouldRegister(), OAuth setup, URI templates, read-only…
Build and work with spatie/laravel-medialibrary features including associating files with Eloquent models, defining media collections and conversions, generating responsive images, and retrieving media URLs and paths.
Develops OAuth2 API authentication with Laravel Passport. Activates when installing or configuring Passport; setting up OAuth2 grants (authorization code, client credentials, personal access tokens, device authorization); managing OAuth clients; protecting API routes with token authentication; defining or checking…
Use when working with Laravel Pennant the official Laravel feature flag package. Trigger whenever the query mentions Pennant by name or involves feature flags or feature toggles in a Laravel project. Tasks include defining feature flags checking whether features are active creating class based features in app/Features…
Mandatory point-of-use sequence for capturing annotated screenshots that go into deliverables (ClickUp reviews, bug repros, internal evidence, end-user docs). Invoke this BEFORE every screenshot capture — not once per session — so the rules are fresh in context at the moment you actually shoot. Covers the annotate →…