FabledScribe

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

public

refactor(ui): Phase 7 — strip chat/voice/journal/workspace/home surfaces

2026-05-27 15:14:00 -04:00

src

feat(snippets): a snippet has notes; when_to_use is the situation it is ranked on (#4378 )

2026-09-23 17:27:22 -04:00

.npmrc

Upgrade all major frontend dependencies

2026-03-09 21:30:55 -04:00

index.html

refactor: rename Fabled Assistant to Fabled Scribe