Documentation must stand alone without relying on conversation context
that readers cannot access. This captures working practices for writing
docs that carry their own meaning through explicit links and detail.

Source: https://wycats.substack.com/p/llm-documents-shouldnt-refer-to-the

Assisted-by: Claude Sonnet 4 via Claude Code

diff --git a/ai/AI.md b/ai/AI.md
index a44e57de..3f8074c1 100644
--- a/ai/AI.md
+++ b/ai/AI.md
@@ -50,6 +50,20 @@ claim. That was incorrect and should have been labeled.
 
 For detailed writing assistance, invoke the `writing` skill.
 
+## Documentation Grounding
+
+Write documentation as standalone artifacts. Readers cannot access this
+conversation, so the prose must carry its own meaning.
+
+When editing documentation:
+- Link to repository context when needed
+- Write out details that cannot be linked
+- Avoid references to unavailable conversations or artifacts
+- Use domain knowledge that practitioners share, not chat-specific context
+- Skip template patterns (rule-of-three structures, bolded-list conventions)
+  unless they serve the document's purpose
+- Let new ideas establish their own internal connections
+
 ## Version Control
 
 CRITICAL: Check for .jj directory before ANY version control operation.