Intro

Plugin Introduction Tutorial

Interactive walkthrough of the Elixir/Phoenix plugin in 6 sections (~5 min).

Arguments

• $ARGUMENTS may contain --section N to jump to a specific section (1-6)
• No arguments = start from Section 1

Execution Flow

• Read ${CLAUDE_SKILL_DIR}/references/tutorial-content.md for all section content
• Parse $ARGUMENTS for --section N flag (1-6)
• If --section N specified, jump directly to that section
• Otherwise start from Section 1

Section Presentation Loop

For each section:

• Present the section content completely — do NOT abbreviate or summarize. Every paragraph, table, and code block in the reference file must appear in output

— as visible response text emitted BEFORE the AskUserQuestion call; content composed only in thinking is invisible to the user

• After presenting, use AskUserQuestion with options:
• If sections remain: "Next: [next section title]", "Skip to Cheat Sheet", "Stop here"
• If on final section (6): no question needed, end with closing message

Section Titles

| N | Title |

|---|-------|

| 1 | Welcome |

| 2 | Core Workflow Commands |

| 3 | Knowledge & Safety Net |

| 4 | Hooks & Behavioral Rules |

| 5 | Init, Review & Gaps |

| 6 | Cheat Sheet & Next Steps |

Iron Laws

• ONE section at a time — never dump all content at once
• User controls pace — always offer to stop between sections
• Clean formatting — use tables and code blocks, not walls of text
• NEVER skip the user's questions — tutorial is interactive, not a monologue; if the user asks a question mid-section, answer it before continuing

Closing Message

After Section 6 (or when user stops):

You're all set! Try `/phx:plan` with your next feature to see the workflow in action.
Run `/phx:intro --section N` anytime to revisit a specific section.

Notes

• This runs in main conversation context (not a subagent)
• Reference file is readable since skill runs in user's session
• Keep tone welcoming but concise — developers don't want fluff