How do I install the Pennant Development skill?

Run npx skillmds@latest add tomevault-io/pennant-development in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pennant Development safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pennant Development?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pennant Development free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Pennant Development?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pennant Development by tomevault-io

Name: Pennant Development
Author: tomevault-io

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.

tomevault-io Updated Sep 17, 2026

File contents

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 / Deactivating

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

Verification

Check feature flag is defined
Test with different scopes/users

Common Pitfalls

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

Source: laravel/pennant — distributed by TomeVault.

---name: pennant-developmentdescription: 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.license: MIT---# Pennant Features## DocumentationUse `search-docs` for detailed Pennant patterns and documentation.## Basic Usage### Defining Features```phpuse Laravel\Pennant\Feature;Feature::define('new-dashboard', function (User $user) { return $user->isAdmin();});```### Checking Features```phpif (Feature::active('new-dashboard')) { // Feature is active}// With scopeif (Feature::for($user)->active('new-dashboard')) { // Feature is active for this user}```### Blade Directive```blade@feature('new-dashboard') <x-new-dashboard />@else <x-old-dashboard />@endfeature```### Activating / Deactivating```phpFeature::activate('new-dashboard');Feature::for($user)->activate('new-dashboard');```## Verification1. Check feature flag is defined2. Test with different scopes/users## Common Pitfalls- Forgetting to scope features for specific users/entities- Not following existing naming conventions---> Source: [laravel/pennant](https://github.com/laravel/pennant) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions