Programowanie · Nauka i wyjaśnianie
phx-help
/phx-help
Rekomenduje odpowiedni przepływ pracy phx-* przy wyborze skilla z pluginu Elixir.
Dla kogo
- Autor
- oliver-kriska ↗
- Repozytorium
- claude-elixir-phoenix ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 22.10.2026
Ocena i bezpieczeństwo
100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Przestarzałość
Brak sygnałów. Repozytorium zmienione 22.10.2026, bez odwołań do wycofanych modeli i API.
Licencja
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Rekomenduje odpowiedni przepływ pracy phx-* przy wyborze skilla z pluginu Elixir.
Oryginalny opis (EN)
Recommend the right $elixir-phoenix:phx-* workflow. Use when choosing a plugin skill, not for Codex /help.
Jak działa
- Usage
- Arguments
- Execution Flow
- Iron Laws
- Integration
Sekcje z nagłówków SKILL.md, w oryginale · 99 linii, 635 słów
Podgląd SKILL.md
--- name: phx-help description: Recommend the right $elixir-phoenix:phx-* workflow. Use when choosing a plugin skill, not for Codex /help. --- # Plugin Help — Interactive Command Advisor Helps users find the right command, skill, or agent for their situation. ## Usage ``` $elixir-phoenix:phx-help # Analyze context, suggest commands $elixir-phoenix:phx-help how do I debug this? # Route to $elixir-phoenix:phx-investigate $elixir-phoenix:phx-help add a new feature # Route to $elixir-phoenix:phx-plan -> $elixir-phoenix:phx-work ``` ## Arguments - `$ARGUMENTS` — optional description of what the user wants to do - Empty = analyze current context (git status, existing plans, file patterns) ## Execution Flow ### Step 1: Gather Context If `$ARGUMENTS` is non-empty, use it as primary signal. Always gather ambient context (run in parallel): 1. Check for existing plans: use Glob on `.claude/plans/*/plan.md` — active work in progress? 2. Check git status: uncommitted changes? which files? 3. Check for solution docs: use Glob on `.claude/solutions/**/*.md` — prior knowledge? ### Step 2: Classify Intent Read `references/tool-catalog.md` for the full routing table. Map the user's situation to one of these categories: | Category | Signals | Primary Commands | |----------|---------|-----------------| | **Starting out** | No plans, new to plugin | `$elixir-phoenix:phx-intro` | | **Ideation** | "explore", "brainstorm", "not sure", "how to approach", "vague idea" | `$elixir-phoenix:phx-brainstorm` | | **New feature** | "add", "build", "implement", multi-file | `$elixir-phoenix:phx-plan` → `$elixir-phoenix:phx-work` | | **Quick change** | Single file, <50 lines, "fix typo" | `$elixir-phoenix:phx-quick` | | **Bug** | Error, stack trace, "broken", "failing" | `$elixir-phoenix:phx-investigate` | | **Review** | "check", "review", PR ready | `$elixir-phoenix:phx-review` | | **Performance** | "slow", "N+1", "memory" | `$elixir-phoenix:phx-perf`, `$elixir-phoenix:ecto-n1-check`, `$elixir-phoenix:lv-assigns` | | **Research** | "how to", "best practice", "evaluate lib" | `$elixir-phoenix:phx-research` | | **Resume work** | Existing plan with unchecked tasks | `$elixir-phoenix:phx-work --continue` | | **Post-fix** | "that worked", solved a hard bug | `$elixir-phoenix:phx-compound` | | **Full cycle** | Large feature, new domain area | `$elixir-phoenix:phx-full` | | **Project health** | "audit", "tech debt", "overall quality" | `$elixir-phoenix:phx-audit`, `$elixir-phoenix:phx-techdebt` | | **Dep update audit** | "audit deps", "supply chain", "post-`mix deps.update`", "review mix.lock PR" | `$elixir-phoenix:phx-deps-audit` | | **Manual dep vetting** | "vet this package", "approve dep", "trust ledger", "after $elixir-phoenix:phx-deps-audit findings" | `$elixir-phoenix:phx-deps-vet` | | **Deployment** | "deploy", "release", "production" | `$elixir-phoenix:phx-verify` then deploy skill | | **Permissions** | "too many prompts", "allow", "permission fatigue" | `$elixir-phoenix:phx-permissions` | | **Returning after time off** | "what did I miss", "back from vacation", "catch up", "what changed while I was out" | `/catchup` (companion plugin, separate install) | ### Step 3: Respond or Clarify **If high confidence** (clear match to one category): Present the recommendation with: - The command to run (with exact syntax) - One-line explanation of what it does - What artifacts it creates (if any) - Suggested next step after it completes **If medium confidence** (2-3 possible matches): Use `AskUserQuestion` with the top options, each with a one-line explanation. **If low confidence** (vague or no signal): Ask ONE focused clarifying question. Examples: - "Are you starting something new or continuing existing work?" - "Is this a bug fix or a new feature?" - "How many files do you expect to change?" Then recommend based on the answer. ### Step 4: Offer Follow-up After recommending, always add: - "Run `$elixir-phoenix:phx-help` anytime to get routing advice" - If they seem new: "Try `$elixir-phoenix:phx-intro` for a full plugin walkthrough" ## Iron Laws 1. **ONE recommendation** — don't dump the full catalog, pick the best match 2. **MAX ONE clarifying question** — don't interrogate, make your best guess 3. **Show exact syntax** — `$elixir-phoenix:phx-plan Add user notifications` not just "use the plan command" 4. **Context over keywords** — existing plans + git state matter more than word matching 5. **NEVER block** — if user already knows what they want, DO NOT redirect ## Integration - Complements `intent-detection` (auto-trigger) with explicit invocation - References same routing logic but adds interactive clarification - Can recommend `$elixir-phoenix:phx-intro` for onboarding
Pliki w paczce (2)
- SKILL.md 5 KB
- references/tool-catalog.md 10 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · oliver-kriska/claude-elixir-phoenix | 100 | MIT |
| oliver-kriska/claude-elixir-phoenix | 100 | MIT |
| oliver-kriska/claude-elixir-phoenix | 100 | MIT |
| oliver-kriska/claude-elixir-phoenix | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki a15d035a4285 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100phx-intro
Przedstawia komendy i przepływ pracy pluginu Elixir osobie, która dopiero zaczyna pracę z tym narzędziem. - 100phx-full
Prowadzi pełny cykl pracy nad funkcją Elixir i Phoenix z bramkami kontrolnymi, od pomysłu po gotowy kod. - 100gendiff
Używa API gendiff z elixirstream.dev do pokazania zmian między wersjami generatorów Elixir i Phoenix (phx.new, phx.gen.auth, Nerves, Scenic, Surface, Credo), by aktualizować na podstawie rzeczywistych diffów.