Where to go from here

Once a prompt or two has landed the way you expected, two pages go further in different directions. Prompt examples covers how different kinds of requests, direct, exploratory, outcome-based, tend to actually be phrased, with a large set of worked examples across common tasks.

Use cases covers the broader categories of work people reach for tCode to do day to day, orientation in unfamiliar code, turning an error into a fix, refactoring across files, and more, grouped by the kind of work rather than by any specific language or framework.

Neither page assumes you have memorized anything from this one; they are meant to be read whenever the specific question they answer actually comes up for you, not necessarily right after finishing your first session.

Beyond those two, Command reference is worth bookmarking rather than reading straight through, useful the moment you want to know exactly what a specific slash command does without re-deriving it from memory.

There is no expected timeline for moving from a first session to being comfortable with tCode day to day; some people settle in within one working session, others take a few days of normal use before it stops feeling like a new tool. Both are completely typical.