Skip to content

Remove redundant Pennant guidelines#645

Merged
pushpak1300 merged 4 commits intomainfrom
remove_redundunt_penant_guidelines
Mar 10, 2026
Merged

Remove redundant Pennant guidelines#645
pushpak1300 merged 4 commits intomainfrom
remove_redundunt_penant_guidelines

Conversation

@pushpak1300
Copy link
Member

When we first added skill support, skill triggering wasn't reliable enough, so we added a core.blade.php guideline that duplicated instructions already in the Pennant skill — things like "always use search-docs" and "activate pennant-development for Pennant tasks". This burned extra context tokens on every request.

We now have an eval system for testing and improving skill descriptions, so they trigger reliably. This means the redundant guideline file is no longer needed.

Approach

  • Remove the redundant core.blade.php guideline that duplicated the Pennant skill's own instructions
  • Refine the skill description to be more specific about Laravel Pennant scoping, validated through trigger evals

@pushpak1300 pushpak1300 marked this pull request as ready for review March 10, 2026 10:03
@pushpak1300
Copy link
Member Author

This is the result of the benchmarks.

Aspect Original Description Final Description
Format Activates when... / or when... Use when... Trigger whenever... Common tasks... Also trigger... Do not trigger...
Test Score 8/20 (40% pass rate) ~16/20 (80% pass rate)
Key Improvement Failed to trigger on legitimate Pennant queries Explicitly mentions Pennant by name + expanded common tasks
Length Shorter, concise Longer, more comprehensive
Trigger Keywords "feature flags", "feature toggles", "@feature directive" "Pennant" (by name) + all previous + class-based features, middleware, events, custom drivers, canary releases, dark launches
Negative Guidance None Explicitly excludes generic config, auth policies, authentication

@pushpak1300 pushpak1300 merged commit 14f625e into main Mar 10, 2026
22 checks passed
@pushpak1300 pushpak1300 deleted the remove_redundunt_penant_guidelines branch March 10, 2026 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant