When building systems with both user interfaces and internal logic, explicitly separating display names from system identifiers prevents cascading changes when marketing decides to rename a feature.

The pattern: use stable identifiers (type, id, slug) for code/database/filenames, and store display names (name, label) separately in configuration:

// config/features.php
return [
    'available_reports' => [
        [
            'type' => 'sales_report',               // Stable system identifier
            'name' => 'Quarterly Sales Analysis',   // User-facing display name
            'permission' => 'view_sales_reports',
        ],
        [
            'type' => 'inventory_report',
            'name' => 'Stock Level Summary',
            'permission' => 'view_inventory',
        ],
    ],
];

In your controllers:

class ReportController
{
    public function index()
    {
        $reports = collect(config('features.available_reports'))
            ->filter(fn ($report) => auth()->user()->can($report['permission'] ?? ''))
            ->map(fn ($report) => [
                'id' => $report['type'],      // Internal ID for API/routes
                'label' => $report['name'],   // Display name for UI
            ]);
            
        return view('reports.index', compact('reports'));
    }
    
    public function generate(string $reportType)
    {
        // Use 'type' for routing, job dispatch, filename generation
        $job = match ($reportType) {
            'sales_report' => new GenerateSalesReport(),
            'inventory_report' => new GenerateInventoryReport(),
            default => throw new InvalidArgumentException(),
        };
        
        dispatch($job);
    }
}

Job classes use the stable identifier:

class GenerateSalesReport implements ShouldQueue
{
    public function handle()
    {
        $filename = 'sales_report_' . now()->format('Y-m-d') . '.pdf';
        
        Storage::put("exports/{$filename}", $this->generatePdf());
        
        // Filename: 'sales_report_2024-03-05.pdf' — never changes
    }
}

Why this matters:

• Marketing freedom: “Quarterly Sales Analysis” can become “Revenue Insights Dashboard” without touching code
• Stability: Database queries, API endpoints, and filenames don’t break when display names change
• A/B testing: Easily test different labels for the same feature
• Internationalization: Display names can be translated while system identifiers stay English

What NOT to do:

// ❌ DON'T couple display names to class constants
class GenerateSalesReport
{
    public const DISPLAY_NAME = 'Quarterly Sales Analysis';
    
    public function getFilename()
    {
        return self::DISPLAY_NAME . '_' . now()->format('Y-m-d') . '.pdf';
        // Filename: 'Quarterly Sales Analysis_2024-03-05.pdf' — spaces, changes when label changes
    }
}

// ❌ DON'T hardcode display names in multiple places
// Controller
$reportName = 'Quarterly Sales Analysis';

// Blade view
Quarterly Sales Analysis

// Email notification
Mail::send(..., ['report' => 'Quarterly Sales Analysis']);

// Now you have 3+ places to update when marketing changes the name

The right approach:

• Store display names in config/*.php or database tables where non-developers can update them
• Use system identifiers everywhere in code (sales_report, not "Quarterly Sales Analysis")
• Fetch display names at runtime from the centralized source

Your codebase becomes more flexible, and non-technical stakeholders can update user-facing labels without opening a pull request.

When generating filenames from dynamic input—user-provided names, database values, or API responses—a three-step Laravel string helper chain ensures clean, filesystem-safe output.

The pattern combines Str::lower(), Str::slug(), and Str::title() to handle edge cases you might not think of:

use Illuminate\Support\Str;

class FileGenerator
{
    public static function sanitizeFilename(string $name): string
    {
        return Str::title(Str::slug(Str::lower($name), '_'));
    }
}

// Examples
FileGenerator::sanitizeFilename('Q4 Sales Report');
// Returns: 'Q4_Sales_Report'

FileGenerator::sanitizeFilename('User Analytics (2024)');
// Returns: 'User_Analytics_2024'

FileGenerator::sanitizeFilename('Employee List - HR Dept.');
// Returns: 'Employee_List_Hr_Dept'

FileGenerator::sanitizeFilename('Données françaises');
// Returns: 'Donnees_Francaises'

Why this three-step chain works:

1. Str::lower() normalizes case to avoid filesystem issues on case-sensitive systems (Linux servers are case-sensitive, Windows/Mac are not)
2. Str::slug() converts to URL-safe format, replacing spaces and special characters with your chosen separator (underscore here)
3. Str::title() capitalizes words for readable filenames without breaking filesystem compatibility

Real-world usage with timestamps:

class ReportExporter
{
    public function export(string $reportName, array $data): string
    {
        $filename = FileGenerator::sanitizeFilename($reportName) 
                    . '_' . now()->format('Y-m-d_His') 
                    . '.csv';
        
        Storage::put("exports/{$filename}", $this->toCsv($data));
        
        return $filename;
    }
}

// Output: 'Monthly_Revenue_2024-03-05_093045.csv'

Why not just use Str::slug() alone?

Plain Str::slug() would give you 'q4-sales-report' (all lowercase). The Str::title() step makes filenames more readable when users download them. Compare:

• Without title case: employee_performance_report.csv
• With title case: Employee_Performance_Report.csv

The second is clearer at a glance in file explorers.

Alternative separators:

You can use hyphens instead of underscores by changing the second parameter to Str::slug():

return Str::title(Str::slug(Str::lower($name), '-'));

This is common for web-facing URLs. Underscores are traditional for downloaded files, but both work fine for filesystems.

If you’re building multiple Laravel AI agents, you’ll notice a lot of repetitive setup code in every agent class:

// ❌ Every agent repeats the same middleware setup
class CustomerSupport implements Agent, HasMiddleware
{
    use Promptable;

    public function middleware(): array
    {
        return [
            RateLimitMiddleware::class,
            LoggingMiddleware::class,
            RetryMiddleware::class,
        ];
    }
}

class ReportGenerator implements Agent, HasMiddleware
{
    use Promptable;

    public function middleware(): array
    {
        return [
            RateLimitMiddleware::class,
            LoggingMiddleware::class,
            RetryMiddleware::class,
        ];
    }
}

DRY it up with a base agent:

// app/Ai/Agents/BaseAgent.php
abstract class BaseAgent implements Agent, HasMiddleware
{
    use Promptable;

    public function middleware(): array
    {
        return [
            RateLimitMiddleware::class,
            LoggingMiddleware::class,
            RetryMiddleware::class,
        ];
    }
}

Now every agent just extends BaseAgent:

// ✅ Clean and minimal
class CustomerSupport extends BaseAgent
{
    // Just your agent-specific logic
}

class ReportGenerator extends BaseAgent
{
    // Just your agent-specific logic
}

Benefits:

• Add/remove middleware in one place – affects all agents instantly
• Onboarding a new agent? One line: extends BaseAgent
• Override middleware for specific agents if needed (just override the middleware() method)

Example override for special cases:

// Most agents use BaseAgent defaults
class BulkProcessor extends BaseAgent
{
    // Different rate limit for bulk operations
    public function middleware(): array
    {
        return [
            BulkRateLimitMiddleware::class,
            ...parent::middleware(),
        ];
    }
}

Pattern applies beyond agents: Same concept works for controllers (BaseController), jobs (BaseJob), or any class hierarchy where you have shared setup.

If you’re integrating with a service that has dynamic pricing (shipping carriers, payment processors, cloud APIs), you might hardcode the rates in your config:

// config/shipping.php
return [
    'rates' => [
        'express' => ['base' => 5.99, 'per_kg' => 0.89],
        'standard' => ['base' => 2.99, 'per_kg' => 0.45],
    ],
];

The problem: Rates change frequently. You’re constantly updating config files, redeploying, and risking stale prices shown to customers.

Better approach: Fetch pricing dynamically from the provider’s API and cache it:

// app/Services/ShippingPricingService.php
class ShippingPricingService
{
    public function getRates(): array
    {
        return Cache::remember('shipping_rates', now()->addHour(), function () {
            $response = Http::withToken(config('shipping.api_key'))
                ->get('https://api.shippingprovider.example/v1/rates');

            return $response->json('rates');
        });
    }

    public function calculateCost(string $method, float $weight): float
    {
        $rates = $this->getRates();
        $rate = $rates[$method];

        return $rate['base'] + ($weight * $rate['per_kg']);
    }
}

Now your cost calculations always use current pricing, without manual config updates:

// Before: Hardcoded config (stale pricing risk)
$cost = config("shipping.rates.express.base") 
    + ($weight * config("shipping.rates.express.per_kg"));

// After: Dynamic pricing (always current)
$cost = app(ShippingPricingService::class)->calculateCost('express', $weight);

Cache strategy: 1-hour TTL is usually fine for pricing data – it doesn’t change minute-to-minute. If the provider updates rates, your app picks them up within an hour. No deploys needed.

Bonus: Some providers let you pass per-request pricing overrides. If your tracking package supports runtime config, you can pass the fetched rates directly:

// Hypothetical cost tracker with runtime pricing override
CostTracker::calculate(
    method: 'express',
    weight: $weight,
    pricingOverride: $this->shippingPricing->getRates()['express']
);

When NOT to do this: If the API is slow or unreliable, fetch pricing asynchronously via a scheduled job and store it in your database. Then your app reads from the DB instead of hitting the API every hour.

If you’re using Laravel AI SDK and need to log or track every AI agent call (costs, tokens, timing), you might be tempted to manually call your tracking service after every prompt():

// ❌ Repetitive - you'll forget this somewhere
$response = $agent->prompt($message);
UsageLogger::record($response);

Instead, use the HasMiddleware interface to automatically intercept all agent responses. Create a middleware that runs after every agent call:

// app/Ai/Middleware/LogUsage.php
namespace App\Ai\Middleware;

use Closure;
use Laravel\Ai\Prompts\AgentPrompt;

class LogUsage
{
    public function handle(AgentPrompt $prompt, Closure $next): mixed
    {
        $response = $next($prompt);

        // Automatic logging for ALL agents
        UsageLogger::record(
            response: $response,
            model: $response->meta->model,
            tag: class_basename($prompt->agent::class)
        );

        return $response;
    }
}

Then create a BaseAgent class that all your agents extend:

// app/Ai/Agents/BaseAgent.php
abstract class BaseAgent implements Agent, HasMiddleware
{
    use Promptable;

    public function middleware(): array
    {
        return [
            \App\Ai\Middleware\LogUsage::class,
        ];
    }
}

Now every agent that extends BaseAgent gets automatic logging:

// app/Ai/Agents/ReportGenerator.php
class ReportGenerator extends BaseAgent
{
    // Zero extra code - logging happens automatically
}

Why this matters: You have 20 agents and want to add cost tracking. Without middleware, you’re manually adding UsageLogger::record() after 20+ prompt() calls. With middleware, it’s one line in BaseAgent.

Bonus: Need authentication, rate limiting, or retries? Add more middleware to the BaseAgent::middleware() array. All agents inherit the behavior.