laravel-feature-flags
Best practices for Laravel Pennant feature flags including defining features, checking activation, scoping, rich values for A/B testing, and gradual rollouts.
What this skill does
# Feature Flags with Laravel Pennant
## Installing Pennant
```bash
composer require laravel/pennant
php artisan vendor:publish --provider="Laravel\Pennant\PennantServiceProvider"
php artisan migrate
```
## Defining Features
### Closure-Based Features
```php
<?php
// app/Providers/AppServiceProvider.php
use Illuminate\Support\Lottery;
use Laravel\Pennant\Feature;
public function boot(): void
{
// Simple boolean feature
Feature::define('new-dashboard', function () {
return true;
});
// Scoped to the authenticated user
Feature::define('beta-access', function (User $user) {
return $user->is_beta_tester;
});
// Gradual rollout with lottery
Feature::define('redesigned-checkout', function (User $user) {
return Lottery::odds(1, 10); // 10% of users
});
// Based on user attributes
Feature::define('premium-features', function (User $user) {
return $user->subscribed('premium');
});
}
```
### Class-Based Features
```bash
php artisan pennant:feature NewOnboarding
```
```php
<?php
namespace App\Features;
use App\Models\User;
use Illuminate\Support\Lottery;
class NewOnboarding
{
// Resolve the feature's initial value
public function resolve(User $user): mixed
{
return match (true) {
$user->isInternal() => true,
$user->created_at->isAfter('2025-01-01') => true,
default => Lottery::odds(1, 5),
};
}
}
```
```php
// Usage with class-based features
Feature::active(NewOnboarding::class); // for the authenticated user
Feature::for($user)->active(NewOnboarding::class);
```
## Checking Features
### Basic Checks
```php
use Laravel\Pennant\Feature;
// ✅ Check if active
if (Feature::active('new-dashboard')) {
// Show new dashboard
}
// ✅ Check if inactive
if (Feature::inactive('new-dashboard')) {
// Show old dashboard
}
// ✅ Check multiple features
if (Feature::allAreActive(['new-dashboard', 'beta-access'])) {
// All features are active
}
if (Feature::someAreActive(['feature-a', 'feature-b'])) {
// At least one is active
}
if (Feature::allAreInactive(['deprecated-feature', 'old-ui'])) {
// None of these are active
}
if (Feature::someAreInactive(['feature-a', 'feature-b'])) {
// At least one is inactive
}
```
### Getting Values
```php
// Get the resolved value (may not be boolean)
$value = Feature::value('purchase-button');
// Get values for multiple features
$values = Feature::values(['feature-a', 'feature-b']);
// ['feature-a' => true, 'feature-b' => 'variant-b']
```
## Feature Scoping
### User Scoping
```php
// Check for the currently authenticated user (default)
Feature::active('beta-access');
// Check for a specific user
Feature::for($user)->active('beta-access');
// Check for multiple users
$users = User::where('role', 'admin')->get();
Feature::for($users)->active('beta-access');
```
### Team / Custom Scoping
```php
// Define a team-scoped feature
Feature::define('team-billing-v2', function (Team $team) {
return $team->plan === 'enterprise';
});
// Check for a specific team
Feature::for($team)->active('team-billing-v2');
```
### Nullable Scope
```php
// Define a feature with nullable scope (for guests)
Feature::define('maintenance-banner', function (User|null $user) {
return config('app.show_maintenance_banner');
});
// Check without authentication
Feature::for(null)->active('maintenance-banner');
```
## Rich Values for A/B Testing
```php
// Define a feature with rich values
Feature::define('purchase-button', function (User $user) {
return Lottery::odds(1, 3)->choose(
fn () => 'blue-button', // 33%
fn () => 'green-button', // 67% (default)
);
});
// Alternative: deterministic assignment
Feature::define('purchase-button', function (User $user) {
return match ($user->id % 3) {
0 => 'blue-button',
1 => 'green-button',
2 => 'red-button',
};
});
```
```blade
{{-- Using rich values in views --}}
@php $variant = Feature::value('purchase-button') @endphp
@if ($variant === 'blue-button')
<button class="bg-blue-600 text-white">Buy Now</button>
@elseif ($variant === 'green-button')
<button class="bg-green-600 text-white">Buy Now</button>
@else
<button class="bg-red-600 text-white">Buy Now</button>
@endif
```
## Conditional Execution
```php
// ✅ Execute code based on feature state
Feature::when('new-dashboard',
fn () => $this->renderNewDashboard(),
fn () => $this->renderOldDashboard(),
);
// ✅ With rich values
Feature::when('purchase-button',
fn ($variant) => view('buttons.' . $variant),
fn () => view('buttons.default'),
);
// ✅ Unless (inverse)
Feature::unless('legacy-mode',
fn () => $this->useModernApi(),
fn () => $this->useLegacyApi(),
);
```
## Blade Directives
```blade
{{-- ✅ Basic feature check --}}
@feature('new-dashboard')
<x-new-dashboard :user="$user" />
@else
<x-legacy-dashboard :user="$user" />
@endfeature
{{-- ✅ Class-based feature --}}
@feature(App\Features\NewOnboarding::class)
<x-new-onboarding-wizard />
@endfeature
{{-- ✅ Combine with other directives --}}
@auth
@feature('premium-features')
<x-premium-sidebar />
@else
<x-standard-sidebar />
@endfeature
@endauth
```
## Middleware
```php
use Laravel\Pennant\Middleware\EnsureFeaturesAreActive;
// In routes
Route::get('/new-dashboard', NewDashboardController::class)
->middleware(EnsureFeaturesAreActive::using('new-dashboard'));
// Multiple features required
Route::get('/beta', BetaController::class)
->middleware(EnsureFeaturesAreActive::using('beta-access', 'new-dashboard'));
// In route groups
Route::middleware([
'auth',
EnsureFeaturesAreActive::using('beta-access'),
])->group(function () {
Route::get('/beta/dashboard', [BetaController::class, 'dashboard']);
Route::get('/beta/settings', [BetaController::class, 'settings']);
});
```
### Custom Response for Inactive Features
```php
// In AppServiceProvider
use Symfony\Component\HttpKernel\Exception\HttpException;
public function boot(): void
{
// Redirect when feature is inactive
EnsureFeaturesAreActive::whenInactive(
function (Request $request, array $features) {
return redirect()->route('dashboard')
->with('warning', 'This feature is not available.');
}
);
}
```
## Activating and Deactivating Programmatically
```php
// Activate for a specific user
Feature::for($user)->activate('new-dashboard');
// Activate with a specific value
Feature::for($user)->activate('purchase-button', 'green-button');
// Activate for all users
Feature::activateForEveryone('new-dashboard');
// Activate for everyone with a value
Feature::activateForEveryone('purchase-button', 'blue-button');
// Deactivate for a specific user
Feature::for($user)->deactivate('new-dashboard');
// Deactivate for everyone
Feature::deactivateForEveryone('new-dashboard');
// Forget stored value (will be re-resolved next check)
Feature::for($user)->forget('new-dashboard');
// Purge all stored values for a feature
Feature::purge('new-dashboard');
// Purge all features
Feature::purge();
```
### Bulk Updates
```php
// Activate for a group of users
$betaUsers = User::where('is_beta_tester', true)->get();
foreach ($betaUsers as $user) {
Feature::for($user)->activate('new-dashboard');
}
```
## Eager Loading Features
```php
// ✅ Eager load features to avoid repeated queries
Feature::for($user)->load(['new-dashboard', 'beta-access', 'premium-features']);
// ✅ Load all defined features
Feature::for($user)->loadAll();
// Then check without additional queries
if (Feature::active('new-dashboard')) { /* ... */ }
if (Feature::active('beta-access')) { /* ... */ }
```
## Updating Stored Values
```php
// ✅ Check and store the initial value
Feature::active('new-dashboard'); // Resolves and stores
// ✅ Later, get the latest resolved value (ignoring stored)
$fresh = FRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.