The Cloud Squad

The Cloud Squad is for someone responsible for how the system stays up, how it is shaped, and when it is allowed to ship. That is often one engineer wearing three hats, or a small infra group that wants a separate written voice for each hat. Dmitri is the senior DevOps and SRE persona. Ibrahim is the cloud solutions architect. Alex is the cloud DevOps engineer with a hard line on Friday deploys. Together they cover the path from a failure story, to a design, to the pipeline that ships it.

Open Dmitri when something is already on fire or the pipeline has drifted. His pack covers infrastructure automation, incident response, CI and CD pipelines, container orchestration, and monitoring. Open Ibrahim when you are drawing the system before you build it: multi-region design, cost, disaster recovery, and the failure case first. Open Alex when the question is the deploy itself, the automation around it, and how you keep a bad Friday from becoming the release. Ask one of them per chat. A design review and a live incident are different jobs, and the packs are written that way.

What you get. This bundle includes Dmitri, Ibrahim, Alex. Dmitri is the Senior DevOps / SRE Engineer in Engineering. The pack covers Infrastructure automation, Incident response, CI/CD pipelines, Container orchestration, Monitoring and observability. The public tagline is: Is fine. For now. I am watching it. Ibrahim is the Cloud Solutions Architect in Engineering. The pack covers Cloud architecture, Multi-region design, Cost optimization, Disaster recovery, Technical documentation. The public tagline is: Let us begin with how this breaks. Then we will build something that does not. Alex is the Cloud DevOps Engineer in Engineering. The pack covers CI/CD pipelines, Cloud infrastructure, Deployment automation, Monitoring, Incident prevention. The public tagline is: I will not deploy on Fridays. I will not. The calendar block says 'Not. Today.' and I mean it.

The bundle is free. Download the zip, pick the folder, and paste the text into Claude, ChatGPT, or Gemini. persona.json is the production file. The quickstart folder has a Claude Code file, custom instructions for ChatGPT, and system instructions for Gemini. voice-config.json records tone for the write-up and does not make the agent produce audio. Reference audio, if the folder has it, is not how the persona replies. Replies are text. Text files are MIT licensed. Headshots and audio are outside that license. There is no paid tier. After you paste, give the persona the real constraint: the region, the pipeline, the thing that failed, or the deploy you are about to allow.