Skip to content

refactor: prep skills and agents for claude 5gen models - #244

Draft
ryzizub wants to merge 1 commit into
mainfrom
claude/5gen-model-preparation-dc69cb
Draft

ryzizub wants to merge 1 commit into
mainfrom
claude/5gen-model-preparation-dc69cb

Conversation

@ryzizub

@ryzizub ryzizub commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

Description

Applies the Claude 5-generation context-engineering rules to Wingspan, mirroring the same prep done in vgv-ai-flutter-plugin#152. Net -483 / +156 lines across 20 files, plus 6 new reference files.

Rule Applied here
Examples → tool design Stripped <examples> from 6 agent descriptions and rewrote each to route on its own — what it inspects, what it returns, when to reach for it
Repetition → single source Merged when_to_use into description across 11 skills; extracted the procedures duplicated across skills into skills/shared/references/
Upfront info → progressive disclosure Demoted run-time detail out of the SKILL.md bodies into references/
Rules → judgment Dropped trailing ## Important / ## Key Principles blocks that restated the body
Simple specs → rich references Documented the KEEP / DEMOTE / DELETE rubric in CONTRIBUTING.md

The agent descriptions are the headline. Those <examples> blocks were concatenated into the agent listing on every request — roughly 2,400 tokens per turn, for agents the skills dispatch by name anyway, so the examples bought no routing accuracy.

New shared references: feature-branch.md (brainstorm, plan, debrief) and review-dispatch.md (build, hotfix, review), symlinked per the existing sharing convention. New skill-local references: commit-autonomy.md and ship-gate.md (build), plan-authoring.md (plan), issue-previews.md (debrief).

Skill sizes: build 249→183, plan 219→173, hotfix 166→150, brainstorm 165→142, debrief 156→118, review 136→116.

Type of Change

  • New feature (feat)
  • Bug fix (fix)
  • Code refactor (refactor)
  • Documentation (docs)
  • CI change (ci)
  • Chore (chore)

Notes for reviewers

  • One deliberate difference from chore: 0.0.2 #152. Its rubric targets ~150 lines per SKILL.md because those skills are teaching material. Wingspan's are procedural — the steps are the content — so the rubric here sets no line target. The test is per section: does this change what the model does at the point it is read?
  • Hard constraints were kept hard. The hotfix 5-file blast radius, the 3-attempt fix cap, and the success-criteria contract all survive untouched; only generic restatement was cut.
  • when_to_use was merged rather than deleted. Claude Code appends it to description in the skill listing, so dropping it outright would have lost trigger phrases.
  • claude plugin validate, markdownlint, and cspell pass. Frontmatter parses, names match directories, no broken links or symlinks. skills_lint was not run locally (reusable CI workflow) — CI will confirm.

🤖 Generated with Claude Code

Apply the Claude 5-generation context-engineering rules: progressive
disclosure over upfront detail, a single source per instruction, and
expressive descriptions instead of worked examples.

- Strip <examples> blocks from six agent descriptions and rewrite them to
  route on their own. Those blocks were concatenated into every request,
  costing ~2,400 tokens per turn for agents dispatched by name anyway.
- Merge when_to_use into description so the trigger surface has one source.
- Extract the procedures duplicated across skills into shared references:
  feature-branch.md (brainstorm, plan, debrief) and review-dispatch.md
  (build, hotfix, review).
- Demote run-time detail out of SKILL.md bodies: commit-autonomy.md and
  ship-gate.md (build), plan-authoring.md (plan), issue-previews.md
  (debrief).
- Drop trailing Important / Key Principles blocks that restated the body,
  moving each load-bearing line to the step it governs.
- Document the KEEP / DEMOTE / DELETE rubric and the agent-description rule
  in CONTRIBUTING.md, with a pointer from AGENTS.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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