oliver-kriska/claude-elixir-phoenix / targets/codex/skills/phx-intro
phx-intro
VerifiedWalk through the Elixir/Phoenix plugin commands, workflow; Use when a new user wants to learn what the plugin offers…
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.1 KB |
| references/tutorial-content.md | markdown | 18.0 KB |
SKILL.md
View on GitHub---
name: phx-intro
description: Walk through the Elixir/Phoenix plugin commands, workflow; Use when a
new user wants to learn what the plugin offers…
---
# 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
1. Read `references/tutorial-content.md` for all section content
2. Parse `$ARGUMENTS` for `--section N` flag (1-6)
3. If `--section N` specified, jump directly to that section
4. Otherwise start from Section 1
### Section Presentation Loop
For each section:
1. Present the section content completely — every paragraph, table, and code block from the reference file
— as **visible response text emitted BEFORE the `AskUserQuestion` call**; content composed only in thinking is invisible to the user
2. 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
1. **ONE section at a time** — never dump all content at once
2. **User controls pace** — always offer to stop between sections
3. **Clean formatting** — use tables and code blocks, not walls of text
4. **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 `$elixir-phoenix:phx-plan` with your next feature to see the workflow in action.
Run `$elixir-phoenix: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
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |