Pennant Development

Handles Laravel Pennant feature flags from definition through deployment. You get helpers for defining flags with closures or class-based features in app/Features, checking them with Feature::active() or the @feature Blade directive, and scoping to specific users or teams. Covers the practical stuff like protecting routes, A/B testing, gradual rollouts, and building custom storage drivers. The verification steps are basic but the common pitfalls note about scoping is honest. If you're managing feature toggles in Laravel and want to use the official package instead of rolling your own conditionals, this gives you the patterns without having to dig through docs.

skills.sh installs: 265
GitHub stars: 3.7K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add laravel/boost --skill pennant-development --agent claude-code

Installs into .claude/skills of the current project.

Files

Pennant features

Documentation

Use search-docs for detailed Pennant patterns and documentation.

Basic usage

Defining features

use Laravel\Pennant\Feature;

Feature::define('new-dashboard', function (User $user) {
    return $user->isAdmin();
});

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

@feature('new-dashboard')
    <x-new-dashboard />
@else
    <x-old-dashboard />
@endfeature

Activating and deactivating

Feature::activate('new-dashboard');
Feature::for($user)->activate('new-dashboard');

Verification

Check that the feature flag is defined
Test with different scopes and users

Common pitfalls

Forgetting to scope features for specific users or other entities
Not following existing naming conventions

SKILL.md on GitHub

Details

Repository: github.com/laravel/boost
Categories: Backend & APIs, Testing & QA, Security, PHP & Laravel
First seen: Jun 3, 2026

More from laravel/boost

All 5