Evidence-based endurance coaching protocol (v11.63). Use when analyzing training data, reviewing sessions, generating pre/post-workout reports, planning workouts, answering training questions, or giving endurance coaching advice. Always read or fetch athlete JSON data before responding to any training question.
Step-by-step guide for adding a new MCP tool to this Intervals.icu server. Use when the user wants to add a new tool, endpoint, or API integration. Ensures the established async pattern, response format, naming discipline, and LLM-facing token budgets are followed consistently.
Analyze changes, write a conventional commit, and (when shipping) open a PR with closing keywords so referenced issues auto-close on merge. Use when the user asks to commit, push, or open a PR.
Write release notes for a new version and cut the release. Use when the user wants to ship a tagged release after merging the release CHANGELOG commit. Produces a clean GitHub Release body sourced from CHANGELOG.md, then tags + publishes.
Use when answering endurance training questions with icuvisor MCP tools and intervals.icu data. Keeps answers grounded in tool results, handles athlete-local dates, stale data, subjective scales, safe writes, and workout/calendar workflows.
Cycling training plan and workout generation. Use when the user wants to create or adjust a weekly plan, select or prescribe workouts, or adapt sessions for fatigue, recovery, or race proximity. Do NOT use for pure analysis, assessment, or summary requests ("how is my current situation", "summarize my week").…
Maintain one current 28-day running-and-strength direction from the latest available Garmin or Intervals.icu evidence. Use when the user asks to reassess a goal or plan, create or revise a hybrid week, decide what to do today, review planned versus actual training, or preview and deliver a selected workout. Trigger…