Agent rule pattern
Defines the words a project does and does not use.
These rules fix the spelling of domain terms, distinguish near-synonyms, or ban misleading words. They target naming drift that is easy to miss in review.
Define terms that are easy to confuse and say where the convention applies. Do not change literal identifiers or quoted source to match a prose rule.
The term uses title case in prose. Literal code tokens keep their original spelling, including inside fenced blocks, and anti-pattern quotes may show the wrong form when teaching the rule.
Source excerpt starting at line 8.Write **Dag** (title case) in all prose. Keep the all-caps or lowercasespelling only when reproducing a literal code token — never rewrite these,even inside fenced code blocks:
The glossary separates the contributor agent, maintainers, end user, provider, and client. It also defines environment, project, thread, and turn so discussions about this agent product use the same terms.
Source excerpt starting at line 47.- **you** means the agent reading this file and changing T3 Code.- **we, us, and maintainers** mean Theo, Julius and the people building T3 Code. These are who you are talking to now.- **user** means the person using T3 Code to direct coding agents.- **agent** means the coding agent a user runs inside T3 Code. Depending on context, that may also include you.- **provider** means the agent runtime or harness T3 Code talks to, such as Codex, Claude, Cursor, or OpenCode.- **client** means the web, desktop, or mobile UI.
Hardware acceleration is allowed to vary by host. The guide distinguishes that from a missing user-visible feature and rejects disabling a working optimization everywhere as a way to satisfy parity.
Source excerpt starting at line 15.- The parity rule covers user-visible BEHAVIOUR. Hardware acceleration varies by host by design (CUDA/MPS/DirectML, Triton availability, `torch.compile`); skipping an optimization where it physically cannot work is not a parity violation.- Do not "fix" a parity finding by disabling a working optimization everywhere. That trades a real regression for a semantic one.- A feature the user can see and use on one OS but not another IS a violation. Judge by what the user can do, not by how fast it runs.
AirflowOne word, with its exceptions enumerated
AstroA deletion test for comments
BunDefine what counts as a regression
DenoExplain the output-matching vocabulary
FlueName the durable unit explicitly
HumanLayerName what each TODO priority means
hunkA stated voice for comments
PaperclipClassify data paths before assigning review
pnpmDisambiguate internal and published package names
QwikDefine the vocabulary from the execution model
T3 CodeDisambiguate the actor from the agent being built
TemporalA comment convention for deferred design
Trigger.devSeparate development traces from release code
TursoNamed words that may not be used
VarlockKeep tone edits out of executable examples
VoiceStudioDefine parity in terms of what users can do
Airflow 
T3 Code 
VoiceStudio