Trim Build iOS plugin prompts#262
Open
dimillian-oai wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Build iOS Apps was tripping prompt-length warnings in Codex. Its manifest starter prompt was also a string while the current plugin surface expects starter prompts as an array capped at three entries and 128 characters per entry.
The skill descriptions were still large enough for
plugin-evalto fail the plugin trigger-cost budget after the starter prompt fix, so this PR keeps the trigger metadata compact without moving any skill behavior out of the skill bodies.Impact
The plugin keeps the same skill inventory and workflows, but its discovery text is smaller and the starter prompt is a short Simulator-oriented prompt.
plugin-eval report progression
The same local report command was used throughout:
cd plugins/plugin-eval node ./scripts/plugin-eval.js analyze ../build-ios-apps --format markdownBefore the manifest prompt was normalized,
plugin-evalcould not emit a scored report because the string-shapeddefaultPrompthit:Use whentrigger wordingThe final report clears the failing trigger-cost check. Remaining warnings are static budget warnings for trigger/invoke/deferred text plus existing Python helper complexity and missing Python tests.
Validation
node ./scripts/plugin-eval.js analyze ../build-ios-apps --format markdowngit diff --check