sdk-cache-update-placement
Installation
SKILL.md
Rule
There is no single rule that "all follow-up cache writes belong on the structure" — pick the layer that keeps one obvious place for the invariant and avoids a stale cache. In priority order:
- API response + manager pipeline, first choice. If the server
response already contains the updated entity (or list), merge it
through the normal manager pipeline (
$editSingle/$createSingle/$fetchSingle/$add) on the top-level manager for that type. This is consistent for every holder of a cached reference automatically — nothing else to update by hand.