bvandeusen/FabledScribe
1
0
Fork 0
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases 53 Wiki Activity

Snippets gain notes; when_to_use is the situation it is ranked on (#4378) #184

Merged
bvandeusen merged 1 commits from dev into main 2026-09-23 18:00:36 -04:00
Conversation 0 Commits 1 Files Changed 9
+313 -21
1 Commits
Author SHA1 Message Date
bvandeusenandClaude Opus 5.5 4ae18a9dd9 feat(snippets): a snippet has notes; when_to_use is the situation it is ranked on (#4378)
CI & Build / Plugin hooks (push) Successful in 12s
Details
CI & Build / Python tests (push) Successful in 1m37s
Details
CI & Build / Python lint (push) Successful in 3s
Details
CI & Build / integration (push) Successful in 50s
Details
CI & Build / TypeScript typecheck (push) Successful in 53s
Details
CI & Build / Build & push image (push) Successful in 34s
Details 
A snippet had no field for prose, so what a session learned about one went
into when_to_use — the trigger joined onto every chunk it is embedded as. A
sweep found write-ups of up to 3 KB there, headings and all.

- notes: stored after the code under `## Notes`, parsed back from the body,
  carried by every path that rebuilds it (update, merge, un-merge). A
  snippet with no notes composes the body it always did.
- create/update_snippet (MCP) take notes and return trigger_advice when
  when_to_use is long, headed or multi-paragraph. Advice, not a refusal.
- Tool docs, the reusing-code skill and the editor hint describe the trigger
  as the situation and point the explanation at notes.
- Editor gains a Notes field; the detail view renders it as markdown.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-09-23 17:27:22 -04:00