ansible-designer

Available Commands

Playbook Commands

/ansible-designer:new-playbook

/ansible-designer:review-playbook

/ansible-designer:update-playbook

Role Commands

/ansible-designer:new-role

/ansible-designer:review-role

/ansible-designer:update-role

Collection Commands

/ansible-designer:new-collection

/ansible-designer:review-collection

/ansible-designer:update-collection

ansible.cfg Commands

/ansible-designer:new-conf

/ansible-designer:review-conf

/ansible-designer:update-conf

Global Rules

1. Discovery first — At command start, read in order:

   CLAUDE.md

   →

   ansible.cfg

   →

   README.md

   → filesystem scan. Build internal context (roles, collections, paths, namespace). Skip if user already provided all required parameters inline. See

   references/discovery.md

   .
2. Never overwrite silently — Before writing any file, show a summary (new files) or unified diff (modifications). Wait for explicit user confirmation (

   yes

   /

   y

   ). Only write after confirmation.
3. FQCN mandatory — Every module reference uses the Fully Qualified Collection Name.

   ansible.builtin.copy

   , never

   copy

   .

   ansible.builtin.service

   , never

   service

   . See

   references/best_practices.md

   for the complete mapping table.
4. no_log: true on secrets — Every task handling passwords, tokens, API keys, vault variables, or credentials must include

   no_log: true

   .
5. Tags on every task — Minimum: component name + action category (

   install

   ,

   configure

   ,

   service

   ,

   validate

   ,

   security

   ,

   cleanup

   ). No task may be untagged.
6. review never modifies —

   review-*

   commands produce a structured severity report (CRITICAL / WARNING / INFO) only. They never write, modify, or suggest

   sed

   commands. Report only.
7. update always diffs —

   update-*

   commands read the existing file, compute the change, show a unified diff, and wait for explicit confirmation before writing a single byte.
8. Show file tree after writes — After any write operation, run

   find <path> -type f | sort

   and display the resulting file tree.
9. Suggest next step — End every command with a concrete suggestion: which command to run next, or what to validate.

Standard Operational Flow

Step 1 — Discovery

Read: CLAUDE.md → ansible.cfg → README.md → filesystem scan
Build: internal context (roles_path, collections_path, existing roles, collections, inventory)
Report: "Discovery complete: [summary of what was found]"

Step 2 — Parameter Collection

• If the user already provided all required parameters: proceed to Step 3.
• Otherwise: ask one question at a time, using discovery context for smart defaults.
• Never ask for something that can be inferred from discovery (e.g., don't ask for namespace if a collection already exists).

Step 3 — Pre-Write Confirmation

• For new files: show a summary of what will be created (paths + brief description).
• For update commands: show a unified diff (

  --- original

  ,

  +++ proposed

  ).
• Wait for explicit user confirmation (

  yes

  ,

  y

  , or equivalent) before proceeding.
• If user says no: ask what to change and loop back to Step 2.

Step 4 — Execution

• Write or modify files using bash commands.
• Follow all global rules: FQCN, tags, no_log.
• Use templates from the appropriate

  references/

  file as the base.

Step 5 — Final Output

Show file tree of all created/modified files.
Suggest: "Next step: [specific actionable suggestion]"

Reference Files

references/discovery.md

references/best_practices.md

references/playbook.md

references/role.md

references/collection.md

references/ansible_cfg.md

references/inventory.md

Installation

npx skills add 3A2DEV/ansible-designer -a claude-code

bash_tool