Start with the repository that owns the product or documentation you want to change. Follow its setup, contribution rules, and required checks. A repository's own contribution guide takes precedence over this organization default.
When setting up Claude Code, Codex, or Devin for Terminal on a development
machine, register the shared browser rule
in their global instructions. Keep root AGENTS.md and a CLAUDE.md import
in new repositories so their rules also travel with the source. Put the
canonical browser block first in AGENTS.md; the
repository installer
updates this rule without replacing other repository instructions.
For documentation changes, use the Hraness documentation guidelines. Choose whether the reader needs guided learning, help with a task, exact reference, or explanation. Keep capabilities, examples, prerequisites, and effects accurate for the documented version. Review the changed reader path and the other surfaces that repeat its facts.
Use the README guidelines for repository front doors and writing style for public prose. Keep source records intact and exclude credentials, private data, and unsupported claims from public examples.
For optional product updates and development support, follow the shared invitation framework. Choose the appropriate website, CLI, agent or desktop surface, use the registered product identity, and keep signup and payment under the person's control.