7 Commits
Author SHA1 Message Date
ayobamiseun cda4542ade fix(skills): close description-vocabulary gaps, raise rank-1 floor to 95
Eleven positive trigger prompts ranked their skill #2-#3 because the
descriptions lacked vocabulary users actually say (follow-up to #351):

- debugging-and-error-recovery: regression vocabulary (worked yesterday,
  what broke)
- documentation-and-adrs: 'document an architecture decision', design
  reasoning ('documentation' and 'document' don't stem together)
- doubt-driven-development: cross-examining assumptions, stress-testing
  a plan for hidden failure modes, high-stakes changes
- git-workflow-and-versioning: splitting a messy working tree into
  atomic commits
- incremental-implementation: thin/verifiable slices, next task from a
  plan, feature flags
- shipping-and-launch: what needs to be in place before shipping
- spec-driven-development: PRD, objectives and scope
- test-driven-development: red-green-refactor
- using-agent-skills: deciding which workflow applies to the work
- source-driven-development: verify against the official docs
  ('docs'/'documentation' don't stem together)

Trigger rank-1 rate: 86% -> 100% (76/76), no new collision warnings.
CI floor raised from 80 to 95 per the ratchet policy; README baseline
updated and the stale #351 tracking sentence rephrased as guidance.
2026-09-07 21:46:11 +01:00
superandy8288andClaude Opus 5 b61213f534 Add pull-request vocabulary to git-workflow-and-versioning description
The skill body already covers pull requests -- "ideally a separate PR" and
"Target ~100 lines per commit/PR" -- but the frontmatter description never
uses the words "pull request" or "PR". Prompts phrased that way therefore
do not route to this skill first.

Adds a trigger case for the gap, and the vocabulary that closes it.

Tier-2 routing, via scripts/run-evals.js:

  baseline                      86%  67/78
  with new case, no fix         85%  67/79   <- case does not rank first
  with new case and fix         86%  68/79   <- case ranks first

Exactly one case changed rank; no other skill regressed.
scripts/validate-skills.js passes: 24 skills, 0 errors, 0 warnings.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-22 19:26:16 -06:00
Arun Kumar Thiagarajan 1ffce563cf docs(git-workflow): add release & versioning (semver, tags, changelog)
git-workflow-and-versioning had versioning in its name but no versioning content.
Adds a Release & Versioning section: semver as a consumer contract, tag-as-source-
of-truth, and human-readable changelogs written with the change. Cross-links
api-and-interface-design, deprecation-and-migration, and shipping-and-launch.
2026-06-27 23:06:47 +05:30
Federico Bartoli fea75b1647 Align skill descriptions with Anthropic best practices
Update all SKILL.md descriptions to lead with what the skill does
(third person) followed by trigger conditions, per Anthropic's
skill authoring docs. All original trigger conditions preserved.
Update description max chars to match Anthropic spec (1024).
Retain workflow-summary warning in skill-anatomy.md to prevent
agents from following descriptions instead of reading full skills.
Add Table of Contents to reference files longer than 100 lines so
Claude can see the full scope of available information even when
previewing with partial reads.
2026-03-31 22:41:45 +02:00
Federico Bartoli 702a894889 Soften prescriptive language for Claude 4.6 compatibility
Anthropic's Claude 4 prompting best practices document warns that
newer models overtrigger on strong directive language (Never/Always/MUST)
that was necessary for older models. This replaces aggressive directives
with natural phrasing across skills and agents while preserving all
security-critical rules (OWASP, prompt injection, secrets) unchanged.

Also reframes trunk-based development as "Recommended" with a note
acknowledging alternative branching strategies like gitflow.
2026-03-31 19:29:59 +02:00
Addy Osmani 8739c15974 Refactor to better reflect Google SWE best practices 2026-03-28 14:06:57 -07:00
Addy OsmaniandClaude Opus 4.6 9434558fd4 add git-workflow-and-versioning and shipping-and-launch skills
Ship phase skills covering atomic commits, branch strategy,
pre-launch checklists, and staged rollout procedures.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-15 14:36:47 -08:00