developing-ansible-molecule skill

Rule of Thumb

• Default to the current ansible-native configuration. Do not emit new driver:, platforms:, or provisioner: blocks; those are legacy constructs.
• Treat the test instance as an ordinary Ansible managed node, not an Ansible development environment. Keep Ansible, Molecule, collections, and test orchestration on the control side; install only the runtime prerequisites and system facilities the managed node and role under test actually require. On Linux, Python is normally required on the managed node, but Ansible is not.
• If the repository already has scenarios, follow their existing style and change only what the task requires. Do not migrate a working legacy scenario unless the user asks for migration.
• Molecule evolves quickly; confirm the installed version with molecule --version before assuming a flag, schema key, or scenario layout exists, and verify version-sensitive details against the official docs at https://docs.ansible.com/projects/molecule/.