Laravel Filament Solaris Laravel Package

Getting Started

• Install with the package’s documented constraint, e.g. composer require statikbe/laravel-filament-solaris:^0.4. Because this is a pre-1.0 package, pin at least the minor version and review release notes before upgrading.
• Publish the package config using the tag shown in the README, then inspect the published file first. The exact filename may be config/filament-solaris.php or similar; confirm from the publish command output.
• Register the Filament plugin in your panel provider if the package requires it, using the class name from the README. If no plugin registration is required, check the service provider bindings instead.
• Configure AI credentials and defaults in .env/config. As of 0.4.1, AiGenerator supports default AI provider, model, and timeout, so set these once rather than repeating them in every Filament action.

SOLARIS_AI_PROVIDER=openai
SOLARIS_AI_MODEL=your-model
SOLARIS_AI_TIMEOUT=30

• First use case: add a “Generate” action to a Filament form field, such as a Textarea or RichEditor, resolve AiGenerator, send the current field value as a prompt, and write the response back to form state.
• Where to look first:
  1. README quickstart and Filament examples.
  2. Published config for provider/model/timeout keys.
  3. The AiGenerator class to confirm the generate() signature and how 0.4.1 defaults are applied.
  4. The package service provider for bindings or extension points.

Implementation Patterns

• Centralize AI defaults in config and inject AiGenerator into Filament actions, jobs, and services. This avoids hardcoding provider/model/timeout in every action and makes 0.4.1’s defaults useful.
• Use per-call overrides only when needed. If the package exposes fluent methods or an options array, prefer:

$ai->withProvider('openai')
   ->withModel('your-model')
   ->withTimeout(20)
   ->generate($prompt);

Confirm the exact method names from the AiGenerator class; 0.4.1 may only add constructor/config defaults.

• A typical Filament form action:

use Filament\Forms\Components\Actions\Action;
use Filament\Forms\Set;
use Statikbe\FilamentSolaris\AiGenerator; // confirm namespace from README

Textarea::make('body')
    ->suffixAction(
        Action::make('generate')
            ->label('Generate')
            ->requiresConfirmation()
            ->action(function (Set $set, $state, AiGenerator $ai) {
                $set('body', $ai->generate("Rewrite this: {$state}"));
            })
    );

• For long prompts or slow providers, dispatch a queued job instead of calling the AI provider synchronously inside the Livewire request. Update the Filament form via a notification or Livewire event when the job completes.
• Create a reusable custom Filament action class or trait for repeated “generate into field” behavior. This keeps prompt construction, authorization, and error handling consistent across resources.
• In multi-panel or multi-tenant applications, resolve provider/model/timeout per panel or tenant rather than relying on one global default. Use a config override, scoped binding, or a small resolver service around AiGenerator.
• For tests, bind a fake AiGenerator implementation or fake the underlying HTTP calls. Assert the prompt passed in and the value written back to form state rather than calling a real AI provider.
• Protect generation actions with normal Filament authorization patterns, e.g. ->visible(fn () => auth()->user()->can('generate-content')).

Gotchas and Tips

• 0.4.1 is additive: it adds default AI provider, model, and timeout to AiGenerator. No breaking changes are indicated, but this is still a 0.4.x package. Pin ^0.4.1 and re-read release notes before minor upgrades.
• New defaults can hide missing configuration. If the default provider or model is invalid, failure may occur at generation time rather than boot time. Add a config check or smoke test in CI/staging.
• Timeout values must align across layers: the package’s AI timeout, Laravel HTTP client timeout, PHP max_execution_time, Livewire request timeout, and queue worker --timeout/retry_after. A package timeout longer than the queue worker timeout will cause confusing retries.
• After changing AI credentials or defaults in .env, run php artisan config:clear locally. In production, rebuild config cache with php artisan config:cache.
• Keep API keys in .env only. Do not commit provider credentials or generated config containing secrets.
• Synchronous generation inside a Filament action can block the UI and allow double submissions. Disable the action while processing or move the work to a queue.
• Log prompts and responses carefully. Redact PII and secrets, and avoid logging full customer content in production.
• To debug quickly, use php artisan tinker and call app(AiGenerator::class)->generate('test prompt') to isolate package/provider issues from Filament form issues.
• Extension points to check first: published config, container binding for AiGenerator, custom provider/model resolution, and Filament action closures. If the package does not expose a needed hook, wrap AiGenerator in your own service rather than modifying vendor code.
• Watch for provider-specific model names and token limits. The new default model may become stale as providers deprecate models; make it configurable per environment.