pennant-development
Use when working with Laravel Pennant the official Laravel feature flag package. Trigger whenever the query mentions Pennant by name or involves feature flags or feature toggles in a Laravel project. Tasks include defining feature flags checking whether features are active creating class based features in `app/Features` using Blade `@feature` directives scoping flags to users or teams building custom Pennant storage drivers protecting routes with feature flags testing feature flags with Pest or PHPUnit and implementing A B testing or gradual rollouts with feature flags. Do not trigger for generic Laravel configuration authorization policies authentication or non Pennant feature management systems.
77
89%
Does it follow best practices?
Impact
100%
1.00x1 of 3 eval scenarios. Add 2 more for a full score.
Passed
No findings from the security scan
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 />
@endfeatureActivating 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
- Repository
laravel/boost
- Revision
30e24b7
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.