Short notes on things picked up along the way.
43 posts
The obvious way to wire "/skill" is to splice the skill's text into the prompt. That silently throws away progressive disclosure. The better move is to make the slash command a directive to the model.
A dynamic form whose fields arrive async is the case that bites. Recreating form() when the fields change throws at runtime — the fix is one stable form, a reactive model, and per-item rules via applyEach.
An agent's built-in skills are frozen at deploy. A SKILL.md folder a user uploads — mounted as a second skills root and synced by content hash — teaches the agent a workflow that's live on the next message, no deploy.
We're migrating a large app off Reactive Forms. Signal Forms collapse the parallel form-state + valueChanges dance into one thing — the model signal you already own, with validity and errors as signals you read directly.
A programmatically generated .xlsx has formula strings but no computed values. To know the formulas even work, drive headless LibreOffice to recompute — with one non-obvious flag.