/ask is the writing on this site, made askable. Type a question about the mental side of tennis and you get an answer drawn from what I have written, in my voice, with the source post linked. People are already asking real things, and some of the answers are working better than I expected. Which raises a fair question: where does /ask end, and coaching begin?
A player types into /ask: Why do I play worse against pushers?
The answer that comes back is good. It names the mechanism. The pusher removes automatic attentional anchors, so concentration has to be more deliberate. Sustained attention has to be active rather than pulled along by the rhythm of the rally. The slow grinding exchange generates internal discomfort, boredom, irritation, impatience, and when equanimity with that discomfort fails, the player starts playing their internal state instead of the situation. The shot selection gets driven by wanting the rally to end. The training is twofold: equanimity with the unpleasantness, concentration on the specific attentional task the situation requires.
That answer is conceptually correct. It applies to most players who struggle against pushers. If you read it carefully and recognize yourself in it, it can change how you train.
Now consider a different version of the same question. A player asks me on court, after losing in three to a pusher: Why did I play worse today?
The answer that comes back from /ask, even if I gave it that exact question, would be the general mechanism. The same one. Pushers, internal discomfort, attentional drift, the standard prescription.
The answer I would give, watching that player, would be different. Because I would have seen that the unpleasantness today was not boredom or irritation. It was the memory of losing to the same player last year. I would have seen that they over-hit on the third ball of every long rally, not the first or the second. I would have seen them check the score after every point in the second set, which they do not do in matches they are winning. The standard prescription about equanimity with discomfort applies, but the discomfort that actually drove today's loss has a specific shape, a specific trigger, and a specific entry point for training that is not the same as the corpus answer.
This is the line /ask was built around. Not the line between simple and complex questions. Not the line between definitions and diagnostics. The line between answers that exist in language and answers that exist only in the moment of seeing.
What /ask handles well.
Definitions and distinctions. What is sensory clarity? How is it different from concentration? What does equanimity actually mean in tennis terms?
Mechanism questions. Why do players choke? Why does "stay present" not work as an instruction? What is the difference between trying to relax and learning to allow what is there?
Pattern questions. Why do players play worse against pushers? Why do they rush forehands from neutral position? Why does nervousness escalate during a tiebreak? The corpus describes these patterns in detail, and /ask retrieves them well.
Framework questions. What are the three skills, and what does Interest have to do with all three? What is Motor imagination, and how does it train movement without movement? How is Sustained attention different from Selective attention? Why is Outer somatic different from Inner somatic, when only the player can tell which is which? Where does Foreground equanimity end and Background equanimity begin?
Cross-referencing. I have read the pre-match nerves post and the choking post. How do they fit together?
Any of these questions, typed into /ask, gets an answer drawn from a specific post on this site, with the post linked at the bottom. The corpus is visible. You can read further when you want depth.
What /ask cannot do.
It cannot see you. It cannot watch how the pattern actually shows up in your matches. It cannot notice what you have not said. It cannot tell whether the standard answer applies to you or whether the standard answer is missing the specific shape of your version of the pattern.
Real coaching often lives in the detail, and the detail is easily missed in the moment. The half-second hesitation before the second serve. The shoulders dropping after a missed return. The specific score at which the rhythm changes. The way the eyes drift to the opponent's body just before the toss instead of staying with the contact point. These are visible from outside and almost invisible from inside. They are happening while the player is playing, which means the player cannot also be watching them. /ask can describe what is generally true about most players, which is genuinely useful. The actual training entry point for any given player is usually somewhere in the detail they did not know to ask about.
It cannot follow you across a week, a season, a coaching cycle. It does not know that you played differently last month, that you have a recurring shoulder issue, that you grew up with a coach who shouted, that your serve breaks down specifically in the second set of three-set matches.
It cannot catch what you are not asking about. The question you bring to /ask is the question you already know to ask. A coach watching you sees the questions you do not know to ask yet, the patterns that are visible from outside but invisible from inside.
It does not give in-match guidance. It does not adjust the prescription based on what is actually happening in your tennis this week. It does not respond to the player you are this morning rather than the average player the corpus describes.
Two different kinds of jobs.
It is tempting to read /ask as a stripped-down coach. It is not.
/ask is the writing, made askable. It is for the player who wants to understand the mechanism, who wants the definition, who wants to know what the framework says about a specific situation. For that, it is genuinely useful, and often better than you would expect.
For the player who wants someone to see them play and train these skills into their own tennis, that is what coaching is for.
Have a follow-up question? Ask the assistant →
