
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.
- Installs
- 82
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/iserter/laravel-claude-agents --skill laravel-feature-flags- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads laravel-feature-flags automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Feature Flags with Laravel Pennant
Installing Pennant
composer require laravel/pennant
php artisan vendor:publish --provider="Laravel\Pennant\PennantServiceProvider"
php artisan migrate
Defining Features
Closure-Based Features
<?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
php artisan pennant:feature NewOnboarding
<?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),
};
}
}
// Usage with class-based features
Feature::active(NewOnboarding::class); // for the authenticated user
Feature::for($user)->active(NewOnboarding::class);
Checking Features
Basic Checks
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
// 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
// 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
// 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
// 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
// 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',
};
});
{{-- 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
// ✅ 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
{{-- ✅ 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
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
// 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
// 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
// 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
// ✅ 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
// ✅ Check and store the initial value
Feature::active('new-dashboard'); // Resolves and stores
// ✅ Later, get the latest resolved value (ignoring stored)
$fresh = Feature::for($user)->value('new-dashboard');
In-Memory Driver (for Testing or Stateless)
// config/pennant.php
'default' => env('PENNANT_STORE', 'database'),
'stores' => [
'array' => [
'driver' => 'array',
],
'database' => [
'driver' => 'database',
'connection' => null,
'table' => 'features',
],
],
Testing Feature Flags
use Laravel\Pennant\Feature;
public function test_new_dashboard_is_shown_when_feature_active(): void
{
// Activate the feature for the test
Feature::activate('new-dashboard');
$response = $this->actingAs($this->user)
->get('/dashboard');
$response->assertSee('New Dashboard');
}
public function test_old_dashboard_is_shown_when_feature_inactive(): void
{
// Deactivate the feature for the test
Feature::deactivate('new-dashboard');
$response = $this->actingAs($this->user)
->get('/dashboard');
$response->assertSee('Classic Dashboard');
}
public function test_rich_value_determines_button_variant(): void
{
Feature::for($this->user)->activate('purchase-button', 'green-button');
$response = $this->actingAs($this->user)
->get('/shop');
$response->assertSee('bg-green-600');
}
public function test_feature_middleware_blocks_inactive_features(): void
{
Feature::deactivate('beta-access');
$response = $this->actingAs($this->user)
->get('/beta/dashboard');
$response->assertStatus(400);
}
public function test_gradual_rollout_is_consistent(): void
{
// Features are stored after first resolution, so they stay consistent
$firstCheck = Feature::for($this->user)->active('redesigned-checkout');
$secondCheck = Feature::for($this->user)->active('redesigned-checkout');
$this->assertEquals($firstCheck, $secondCheck);
}
Using Array Driver in Tests
// phpunit.xml or .env.testing
// PENNANT_STORE=array
// Or in test setup
protected function setUp(): void
{
parent::setUp();
Feature::store('array');
}
Checklist
- Pennant installed and migrations run
- Features defined with clear, descriptive names
- Closure-based features used for simple flags
- Class-based features used for complex resolution logic
- Feature scoping matches business domain (user, team, etc.)
- Rich values used for A/B testing variants
-
@featureBlade directive used in templates -
EnsureFeaturesAreActivemiddleware guards feature-gated routes - Features eager loaded to prevent repeated queries
- Programmatic activation/deactivation used for admin controls
- Tests use
Feature::activate()/Feature::deactivate()for deterministic behavior - Array driver used in test environment for speed
- Old features purged after full rollout
FAQ
What does the laravel-feature-flags skill do?
Best practices for Laravel Pennant feature flags including defining features, checking activation, scoping, rich values for A/B testing, and gradual rollouts.
How do I install laravel-feature-flags?
Run npx skills add https://github.com/iserter/laravel-claude-agents --skill laravel-feature-flags in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/laravel-feature-flags/ (personal) or .claude/skills/laravel-feature-flags/ (project).
Which AI agents can use laravel-feature-flags?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is laravel-feature-flags safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains laravel-feature-flags?
It is published by iserter in iserter/laravel-claude-agents. It has 82 recorded installs.
More from iserter/laravel-claude-agents
eloquent-best-practices
iserter/laravel-claude-agents
Best practices for Laravel Eloquent ORM including query optimization, relationship management, and avoiding common pitfalls like N+1 queries.
laravel-tdd
iserter/laravel-claude-agents
Open the skill to read its SKILL.md instructions.
laravel-blade-component-patterns
iserter/laravel-claude-agents
Best practices for Laravel Blade components including class-based and anonymous components, slots, attribute bags, and reusable UI patterns.
api-resource-patterns
iserter/laravel-claude-agents
Open the skill to read its SKILL.md instructions.
laravel-systematic-debugging
iserter/laravel-claude-agents
Systematic debugging process for Laravel applications - ensures root cause investigation before attempting fixes. Use for any Laravel issue (test failures, bugs, unexpected behavior, performance problems).
laravel-validation-patterns
iserter/laravel-claude-agents
Best practices for Laravel validation including Form Requests, custom rules, conditional validation, and input sanitization.
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.