
Pennant Development
- 186 installs
- 3.6k repo stars
- Updated August 4, 2026
- laravel/boost
Implement Laravel Pennant feature flags for gradual rollouts, per-user or tenant gating, and safe toggling of experimental application capabilities.
About
Guides Laravel Pennant feature-flag implementation including scope drivers, stored definitions, middleware checks, and gradual rollout patterns for SaaS and multi-tenant Laravel applications.
- Feature definitions
- Scope drivers
- Gradual rollout
- Middleware gating
- Per-tenant toggles
Pennant Development by the numbers
- 186 all-time installs (skills.sh)
- +6 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #38 of 65 PHP & Laravel skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/laravel/boost --skill pennant-developmentAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 186 |
|---|---|
| repo stars | ★ 3.6k |
| Last updated | August 4, 2026 |
| Repository | laravel/boost ↗ |
What it does
Implement Laravel Pennant feature flags for gradual rollouts, per-user or tenant gating, and safe toggling of experimental application capabilities.
Files
Pennant Features
Documentation
Use search-docs for detailed Pennant patterns and documentation.
Basic Usage
Defining Features
<!-- Defining Features -->
use Laravel\Pennant\Feature;
Feature::define('new-dashboard', function (User $user) {
return $user->isAdmin();
});Checking Features
<!-- Checking Features -->
if (Feature::active('new-dashboard')) {
// Feature is active
}
// With scope
if (Feature::for($user)->active('new-dashboard')) {
// Feature is active for this user
}Blade Directive
<!-- Blade Directive -->
@feature('new-dashboard')
<x-new-dashboard />
@else
<x-old-dashboard />
@endfeatureActivating / Deactivating
<!-- Activating Features -->
Feature::activate('new-dashboard');
Feature::for($user)->activate('new-dashboard');Verification
1. Check feature flag is defined 2. Test with different scopes/users
Common Pitfalls
- Forgetting to scope features for specific users/entities
- Not following existing naming conventions