laravel-pennant-feature-flags
Use when creating feature toggles, checking flag status, or configuring class-based features using Laravel Pennant.
Works with
---
name: laravel-pennant-feature-flags
description: Use when creating feature toggles, checking flag status, or configuring class-based features using Laravel Pennant.
license: MIT
---
# Laravel Pennant Feature Flags
## When To Use
Use this skill when implementing continuous delivery, beta-testing features for specific users, or configuring runtime flags.
## Workflow
1. **Verify setup**: Ensure `laravel/pennant` is installed and driver settings are configured (`config/pennant.php`).
2. **Define Feature Flag**: Register feature toggles inside `AppServiceProvider`.
3. **Class-Based Flags**: Use class-based features for complex flag calculations.
4. **Conditional checks**: Check flags inside controllers, middleware, or Blade templates cleanly.
## Examples
### Good Example
```php
// app/Providers/AppServiceProvider.php
namespace App\Providers;
use Laravel\Pennant\Feature;
use App\Models\User;
class AppServiceProvider extends ServiceProvider
{
public function boot(): void
{
// Define simple check
Feature::define('beta-dashboard', function (User $user) {
return $user->inBetaGroup();
});
}
}
```
```blade
{{-- Blade check --}}
@feature('beta-dashboard')
<x-beta-dashboard-widget />
@else
<x-standard-dashboard-widget />
@endfeature
```
### Bad Example
```php
// ❌ Using hardcoded config values or database user flags manually for feature toggling.
if (config('app.features.beta_enabled') && auth()->user()->is_beta) {
// Boilerplate checks that are difficult to manage and test.
}
```More Deployment & CI/CD skills
azure-enterprise-infra-planner
microsoft/azure-skills
Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.
azure-kubernetes-app-deploy
microsoft/azure-skills
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster, containerize app for Kubernetes, generate K8s manifests for Azure, set up CI/CD for AKS, my AKS deployment is failing safeguard checks, I have a Django/Express/Spring Boot app to run on AKS. DO NOT USE FOR: creating or provisioning an AKS cluster (use azure-kubernetes), assessing migration to AKS Automatic (use azure-kubernetes-automatic-readiness), or deploying to non-AKS targets like Web Apps, Container Apps, or Functions.
finetuning
microsoft/azure-skills
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).
