Agent rule pattern
Changing values stay in one authoritative place.
Instead of copying version numbers, rule lists, or counts, the file points to the config, script, or array that owns them. Copied values drift.
Point to the file that owns a changing fact instead of copying the value. Add only enough context to find and understand it.
The file refuses to copy versions, rule lists, or counts that will go stale. Later sections follow through: the root package file owns scripts, and one validation command replaces a copied list of lint rules.
Source excerpt starting at line 4.monorepo. Prefer authoritative configuration and documentation over copyingdetails into this file: copied versions, rule lists, and counts become stale.
The command prefix section gives common examples, then points at the array in the router as authoritative, with the stated reason that a second copy drifts.
Source excerpt starting at line 57.Do not maintain a second exhaustive prefix list here. Consult
The guide names the file that pins the toolchain and the manager that installs it. This avoids maintaining a second list of current versions inside the instructions.
Source excerpt starting at line 22.- Tool versions (bun, pnpm, node, moon, gh) are pinned in `.prototools` and managed by [proto](https://moonrepo.dev/docs/proto); run `proto use` if a tool is missing or a pin changed. Never install toolchain versions globally; bump pins only in `.prototools`.
Agent BrowserKeep discovery stubs separate from working instructions
browser-usebrowser-use/browser-use
ClineSeparate authentication from startup health
cmuxGive all entry points one behavior owner
Deep AgentsKeep generated context below source evidence
DiffusersUse the same review rules locally and in CI
GitButlergitbutlerapp/gitbutler
Hermes AgentMake the test wrapper enforce isolation
HumanLayerRead package-local tool choices
KodyUse one authoritative local gate
LanceDBExpose what the documentation build does not discover
LogfireSeparate source-relative links from published routes
Next.jsExplain false negatives from ad hoc type checks
OmarchyOne list, not two
OpenAI Agents SDK for TypeScriptCompile the examples that readers see
OpenClawDefine a complete ownership cutover
PaperclipEnforce UI tokens with a named check
PierrePoint tool versions at their authority
PlaywrightPoint verification at the integrated check
pnpmDocument the platform prerequisite for shared instructions
Prisma ORMName the tracked source behind each tool-facing mirror
QwikKeep shared guidance in a generator input
RayRoute setup to existing contributor guides
SGLangDefine which source owns each kind of fact
StorybookThe file names itself as canonical
StrapiKeep skill sources independent of tool-specific paths
StreamlitSeparate development locks from public dependency contracts
Supabasesupabase/supabase
SvelteDelegate repository detail to the contributor guide
T3 CodeReserve documentation for reasoning the code does not carry
TanStack QueryApply one contributor contract to human and assisted work
Trigger.devExplain why shared dependency versions must match
uvUse one privileged workflow dispatcher
VarlockRead the local source of documentation
VoiceStudioGive mechanical rules to deterministic checks
Workers SDKA stated policy against copying
Workers SDK 
Omarchy 
Pierre