C Style Guide captures reusable agent playbook guidance for agent design & orchestration. Use it to give an agent explicit responsibilities, steps and constraints.

The name should be general, descriptive of the service being integrated, easy to infer from the task description, and without version numbers. Use it to ground design choices in named patterns, trade-offs and examples.

Although these suggestions can be applied to any programming language, I will use JavaScript to illustrate them in practice. Use English language when naming your variables and functions.