T3-style prompts are wordy in a very specific way. You are not just asking for code. You are asking for code in the shape of a stack.
Next.js, Prisma, tRPC, Zod, Tailwind, auth, validation, edge cases, existing components, and whatever conventions the app already has. That is a lot of setup to type every time.
T3 work is usually stack-shaped, not generic
Voice helps when the task starts as explanation.
That usually means:
- a Prisma bug you can describe faster than you can transcribe
- a tRPC mutation that works in one path and fails in another
- a Zod validation problem where the real issue is flow, not syntax
- a page scaffold where the state and data flow matter more than the markup
The important part is not just the framework names. It is the shape of the bug or the shape of the change.
A T3 prompt that is worth saying out loud
Example:
The signup flow creates the user row, but the organization record sometimes fails and leaves the app in a half-created state. Keep the current API shape, move the write into one transaction, validate the payload earlier, and add tests for duplicate email plus missing organization name.
That is easier to dictate than to type from scratch because the real value is the explanation.
What to type instead of dictate
The cleanest T3 workflow is to speak the bug, the expected outcome, and the constraints as if you were briefing another engineer who already knows the stack.
Then type the parts that are painful to repair if they land wrong:
- exact model names
- file paths
- imports
- schema details
- snippets
That split matters more in T3 projects than in generic code generation because the stack is already dense with terms that sound similar and fail differently.
Where voice helps most in this stack
The highest-value use is usually before code exists.
Voice is good when you are trying to explain:
- how the data should move
- what the page should do
- what the edge case is
- what must stay compatible
Once that paragraph exists, the rest of the toolchain can do its job.
When not to use voice
If the problem is mostly imports, paths, and schema names, type it.
If the task is a tiny edit in one file, type it.
If the change will succeed or fail based on one exact symbol, type it.
Voice prompting T3 Code on Mac works when the brief is the hard part. The keyboard is still better for the sharp edges.