Generate Ansible Playbooks from a Plain-English Description

Writing Ansible YAML from scratch means hunting through module docs and getting the indentation wrong — describe what you need and let Claude write it.

claude "Write an Ansible playbook that provisions a fresh Ubuntu 24.04 server: install nginx, create a deploy user with a specific SSH key, configure a firewall with ufw, and enable automatic security updates. Use best practices and idempotent tasks throughout."

Claude produces a well-structured playbook with properly namespaced variables, handlers for service restarts, and become: yes only where it's actually needed — not slapped on every task.

For multi-environment setups, ask Claude to split it into roles:

claude "Read the existing playbook at deploy/site.yml and refactor it into proper Ansible roles — webserver, database, and monitoring — with a group_vars directory structure for staging and production."

Claude handles the boilerplate you always forget: meta/main.yml, defaults/main.yml with sensible variable defaults, and handlers/main.yml wired up correctly.

You can also paste an existing bash setup script and ask Claude to convert it to idempotent Ansible tasks:

cat setup.sh | claude -p "Convert this bash script into idempotent Ansible tasks. Use the appropriate modules instead of raw shell commands wherever possible."

If you can describe your infrastructure in plain English, Claude can write the Ansible to build it.