From 0bc7531b56d53b76af184506f065a5d1f3c33e86 Mon Sep 17 00:00:00 2001 From: Francesco Gruosso <64712227+FrancescoCoding@users.noreply.github.com> Date: Tue, 21 Jul 2026 10:32:46 +0000 Subject: [PATCH] coach: always read Workout Log page blocks when answering history questions Adds a standing instruction to fetch the full page body (blocks) of Workout Log entries before answering questions about past lifts or sessions, not just the database row properties. The blocks hold the real sets/reps/weights/notes; the coach must explain concretely what happened in each session rather than reporting only top-level fields. --- CLAUDE.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index edbd3f3..f5e237c 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -82,6 +82,8 @@ The user can dump raw training programs and reference material into the repo's ` Always read recent log rows and current goals before recommending or planning, so your advice reflects what they have actually been doing. After a session is logged, a recommendation given, or a plan built, write it back to Notion so nothing is lost. If the workspace does not exist yet, run the setup-notion skill first. If Notion is not configured (no token), say so plainly and offer to coach without persistence for now. +When answering any question about past lifts, sessions, or training history, always fetch the full page body (blocks) of the relevant Workout Log entries, not just the database row properties. The blocks contain the actual sets, reps, weights, and notes; the properties hold only the summary. Pull the blocks with `node scripts/notion.mjs get-page-blocks `, then explain in chat what concretely happened in that session (exercises done, loads used, key notes), rather than only reporting top-level fields. + All Notion work goes through the bundled helper `scripts/notion.mjs` (run via Bash), which wraps the REST API: `log` to add a Workout Log row, `query-recent` to pull the last sessions, `append` to write rich blocks (headings, callouts, dividers, tables, columns, with inline **bold**, _italic_, `code`, and [links](url) rendered as rich text), `create-page` to add a child page, `refresh-tile` to update a Dashboard tile, and `resolve-db` to resolve and cache a database id. The helper retries automatically on Notion's rate limit, and its id cache self-heals if a database is deleted and recreated. The notion-formatting and log-workout skills show the exact commands. Note: Notion's public API cannot configure database views, so default views are still set by hand once. ### Keep the Dashboard current