{"owner":"rabbitmq","repo":"rabbitmq-tutorials","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Instructions for AI Agents\n\n## Overview\n\nThis repository contains runnable code for the [RabbitMQ tutorials](https://www.rabbitmq.com/tutorials)\nin many languages and client libraries. The accompanying prose lives on the website: this repo holds only executable examples.\n\nAll tutorials require a RabbitMQ node running on `localhost` with default settings and use\nthe default `localhost`-constrained seed user `guest` with well known credentials.\n\nTutorial code here and the prose at [`rabbitmq/rabbitmq-website`](https://github.com/rabbitmq/rabbitmq-website)\nshould be kept in sync: not necessarily in lockstep, but updated consistently within a few days of each other.\n\n\n## Repository Structure\n\nEach top-level directory (called a tutorial port) is a self-contained tutorial set for one language (client library),\nwith its own `README.md` covering setup and run instructions. Some directories use symlinks\nto reuse code.\n\nDirectories with a `-stream` suffix cover the [RabbitMQ Stream protocol](https://www.rabbitmq.com/docs/streams); the rest cover AMQP 0-9-1.\n\nIndividual directories (ports) can have their local `AGENTS.md` with language-specific instructions, e.g.\naround how to avoid standard input and output pitfalls when asked to run permutations of these tutorials\n(e.g. T1 publishers in Java and a T1 consumer that uses Swift 6 and Bunny.swift).\n\nAMQP 0-9-1 tutorials follow a standard numbering with consistent base filenames across languages:\n\n 1. Tutorial 1 (a.k.a. T1, \"Hello World\"): `send` / `receive`\n 2. Tutorial 2 (a.k.a. T2, \"Work Queues\"): `new_task` / `worker`\n 3. Tutorial 3 (T3, \"Publish/Subscribe\"): `emit_log` / `receive_logs`\n 4. Tutorial 4 (T4, \"Routing\"): `emit_log_direct` / `receive_logs_direct`\n 5. Tutorial 5 (T5, \"Topics\"): `emit_log_topic` / `receive_logs_topic`\n 6. Tutorial 6 (T6, \"RPC\"): `rpc_client` / `rpc_server`\n 7. Tutorial 7 (T7, \"Publisher Confirms\"): `publisher_confirms`\n\nStream tutorials cover `send` / `receive` and `offset_tracking_send` / `offset_tracking_receive`.\n\n\n## Adding or Modifying Tutorials\n\n * Read the language directory's README first\n * Follow the existing code style and naming conventions of the directory you are editing\n * Tutorials are learning material, not production code: keep them simple, readable, and self-contained\n * Keep dependencies minimal; use the idiomatic RabbitMQ client library for the language\n\n\n## Style\n\n * Only add comments where the logic isn't self-evident; keep them concise\n * Use proper English grammar and punctuation\n * Never add full stops to Markdown list items\n\n\n## Git\n\n * Never add yourself to the list of commit co-authors\n * Never mention yourself in commit messages in any way\n"},"files":{"AGENTS.md":"# Instructions for AI Agents\n\n## Overview\n\nThis repository contains runnable code for the [RabbitMQ tutorials](https://www.rabbitmq.com/tutorials)\nin many languages and client libraries. The accompanying prose lives on the website: this repo holds only executable examples.\n\nAll tutorials require a RabbitMQ node running on `localhost` with default settings and use\nthe default `localhost`-constrained seed user `guest` with well known credentials.\n\nTutorial code here and the prose at [`rabbitmq/rabbitmq-website`](https://github.com/rabbitmq/rabbitmq-website)\nshould be kept in sync: not necessarily in lockstep, but updated consistently within a few days of each other.\n\n\n## Repository Structure\n\nEach top-level directory (called a tutorial port) is a self-contained tutorial set for one language (client library),\nwith its own `README.md` covering setup and run instructions. Some directories use symlinks\nto reuse code.\n\nDirectories with a `-stream` suffix cover the [RabbitMQ Stream protocol](https://www.rabbitmq.com/docs/streams); the rest cover AMQP 0-9-1.\n\nIndividual directories (ports) can have their local `AGENTS.md` with language-specific instructions, e.g.\naround how to avoid standard input and output pitfalls when asked to run permutations of these tutorials\n(e.g. T1 publishers in Java and a T1 consumer that uses Swift 6 and Bunny.swift).\n\nAMQP 0-9-1 tutorials follow a standard numbering with consistent base filenames across languages:\n\n 1. Tutorial 1 (a.k.a. T1, \"Hello World\"): `send` / `receive`\n 2. Tutorial 2 (a.k.a. T2, \"Work Queues\"): `new_task` / `worker`\n 3. Tutorial 3 (T3, \"Publish/Subscribe\"): `emit_log` / `receive_logs`\n 4. Tutorial 4 (T4, \"Routing\"): `emit_log_direct` / `receive_logs_direct`\n 5. Tutorial 5 (T5, \"Topics\"): `emit_log_topic` / `receive_logs_topic`\n 6. Tutorial 6 (T6, \"RPC\"): `rpc_client` / `rpc_server`\n 7. Tutorial 7 (T7, \"Publisher Confirms\"): `publisher_confirms`\n\nStream tutorials cover `send` / `receive` and `offset_tracking_send` / `offset_tracking_receive`.\n\n\n## Adding or Modifying Tutorials\n\n * Read the language directory's README first\n * Follow the existing code style and naming conventions of the directory you are editing\n * Tutorials are learning material, not production code: keep them simple, readable, and self-contained\n * Keep dependencies minimal; use the idiomatic RabbitMQ client library for the language\n\n\n## Style\n\n * Only add comments where the logic isn't self-evident; keep them concise\n * Use proper English grammar and punctuation\n * Never add full stops to Markdown list items\n\n\n## Git\n\n * Never add yourself to the list of commit co-authors\n * Never mention yourself in commit messages in any way\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Instructions for AI Agents\n\n## Overview\n\nThis repository contains runnable code for the [RabbitMQ tutorials](https://www.rabbitmq.com/tutorials)\nin many languages and client libraries. The accompanying prose lives on the website: this repo holds only executable examples.\n\nAll tutorials require a RabbitMQ node running on `localhost` with default settings and use\nthe default `localhost`-constrained seed user `guest` with well known credentials.\n\nTutorial code here and the prose at [`rabbitmq/rabbitmq-website`](https://github.com/rabbitmq/rabbitmq-website)\nshould be kept in sync: not necessarily in lockstep, but updated consistently within a few days of each other.\n\n\n## Repository Structure\n\nEach top-level directory (called a tutorial port) is a self-contained tutorial set for one language (client library),\nwith its own `README.md` covering setup and run instructions. Some directories use symlinks\nto reuse code.\n\nDirectories with a `-stream` suffix cover the [RabbitMQ Stream protocol](https://www.rabbitmq.com/docs/streams); the rest cover AMQP 0-9-1.\n\nIndividual directories (ports) can have their local `AGENTS.md` with language-specific instructions, e.g.\naround how to avoid standard input and output pitfalls when asked to run permutations of these tutorials\n(e.g. T1 publishers in Java and a T1 consumer that uses Swift 6 and Bunny.swift).\n\nAMQP 0-9-1 tutorials follow a standard numbering with consistent base filenames across languages:\n\n 1. Tutorial 1 (a.k.a. T1, \"Hello World\"): `send` / `receive`\n 2. Tutorial 2 (a.k.a. T2, \"Work Queues\"): `new_task` / `worker`\n 3. Tutorial 3 (T3, \"Publish/Subscribe\"): `emit_log` / `receive_logs`\n 4. Tutorial 4 (T4, \"Routing\"): `emit_log_direct` / `receive_logs_direct`\n 5. Tutorial 5 (T5, \"Topics\"): `emit_log_topic` / `receive_logs_topic`\n 6. Tutorial 6 (T6, \"RPC\"): `rpc_client` / `rpc_server`\n 7. Tutorial 7 (T7, \"Publisher Confirms\"): `publisher_confirms`\n\nStream tutorials cover `send` / `receive` and `offset_tracking_send` / `offset_tracking_receive`.\n\n\n## Adding or Modifying Tutorials\n\n * Read the language directory's README first\n * Follow the existing code style and naming conventions of the directory you are editing\n * Tutorials are learning material, not production code: keep them simple, readable, and self-contained\n * Keep dependencies minimal; use the idiomatic RabbitMQ client library for the language\n\n\n## Style\n\n * Only add comments where the logic isn't self-evident; keep them concise\n * Use proper English grammar and punctuation\n * Never add full stops to Markdown list items\n\n\n## Git\n\n * Never add yourself to the list of commit co-authors\n * Never mention yourself in commit messages in any way\n","category":"root","tokens":672}]}