Getting started

• Name the artifact when you already know it: Individual Guidance, Individual Outlook, or Individual Reflection.
• State the athlete, day, workout, and coaching objective as early as possible.
• Include the real coaching variable that matters most right now: pacing, fatigue, confidence, modification, recovery, or tone.
• Plain coaching language also works well. You do not need perfect prompt syntax to get a strong first draft.

• Open the conversation from the athlete profile when you need follow-up, clarification, or accountability.
• Use recent chat as part of Historical Context when prior messages should inform the next draft.
• Create directly from a conversation when that thread is the clearest source of the next coach artifact.

• Start here each day to see your athletes, open coach work, and your current invite code.
• Use the To-Dos preview to see what is open, in progress, and done this week.
• Use athlete cards to jump quickly into one athlete's profile.
• Use Create when the next draft is already obvious.

• Review goals, training level, sport focus, session length, injuries or limitations, and workout structure.
• Review this week's training days and the athlete's default workout days.
• Review metabolic baselines and strength markers when they matter for pacing, progress, or recommendations.
• Use athlete-specific rulesets for constraints or standards that should only apply to this one athlete.
• Open the conversation when you need direct follow-up or continuity from chat.
• Review published guidance across the athlete's week instead of guessing what has already gone out.

• Use To-Do, In Progress, and Done This Week to separate work states clearly.
• Create tasks for athlete follow-ups, programming cleanup, admin reminders, and loose ends.
• Use To-Dos for coach-owned work after the draft itself is written.

• Save drafts when you want to come back and edit before publishing.
• Set an intended day when the artifact belongs to a specific training date.
• Use Schedule Share when you want the artifact to publish later.
• Use Publish when the draft is ready to appear in the conversation and the athlete feed immediately.

• Set coach-wide weekly report guidance as the baseline prompt for every enabled athlete.
• Turn reports on athlete by athlete.
• Add athlete-specific weekly report guidance when one athlete needs a more tailored framing than the coach-wide default.

• Create sets around one methodology, program, or library.
• Upload source material and wait for it to become ready.
• Select only the sets that are relevant to the current draft so retrieval stays focused.

• Athletes can connect supported integrations such as OrangeTheory Fitness.
• Athletes control visibility of that data with their coaches.
• Only the data athletes choose to share should be treated as coach-visible context.

• Published guidance can provide continuity with what you already told the athlete.
• Recent text chat can provide continuity with mindset, follow-through, and current needs.
• Athlete-shared integration data from other services can provide additional training evidence and continuity when that context is available.
• Only integration data athletes choose to share should be treated as coach-visible context.

• Ask broad questions across your roster when you want a fast coach summary.
• Ask athlete-specific questions when you want help spotting patterns, follow-up topics, or gaps in continuity.
• Use Wolvy alongside Knowledge Sets when you want document-backed answers, not just chat-style suggestions.
• Treat Wolvy as a coach thinking partner, not as a replacement for final coach review.

First-week checklist

1. Complete Settings setup across Coaching, General Rulesets, Knowledge, Automated Reports, and Plan & Usage.

2. Invite one athlete with your code and confirm that athlete appears in Dashboard.

3. Open that athlete's profile and confirm goals, workout days, session length, limitations, baselines, and any athlete-specific rulesets.

4. Create one Individual Guidance draft and one future-looking artifact such as an Individual Outlook for that athlete.

5. Use Historical Context at least once so you understand how recent guidance, chat, and athlete-shared integration data can shape a draft.

6. Attach at least one Knowledge Set or one General Ruleset to a draft so you practice reusable AI context.

7. Save one draft, publish one artifact, and schedule one future share so you practice the full review flow.

8. Create at least one To-Do tied to that same athlete so follow-through work stays visible.

9. If weekly reports are part of your service, enable them for one athlete and add both general and athlete-specific weekly report guidance.

Best practices

• Put long-lived coaching principles into General Rulesets, not into one-off instructions.
• Put athlete-only constraints into athlete rulesets, not into general rulesets.
• Put source files, playbooks, and frameworks into Knowledge Sets, not into the instructions box.
• Use coach instructions for the immediate athlete moment, coaching decision, and desired tone.
• Use Historical Context when recent guidance, chat, or athlete-shared integration data should shape the next draft.
• Keep Coaching settings current because your bio, specialties, explanation style, and communication style all shape Wolverine's baseline behavior.
• Review every AI draft like a coach editor before it becomes athlete-facing guidance.
• Use To-Dos for coach work you still need to do and scheduled sharing for when athlete-facing guidance should go live.