Sponsored by

Find leads on Reddit on auto pilot

Agent skills
vibe-coding

Topic: vibe-coding

3,535 skills in this topic.

intent-detection Route ambiguous work requests to the correct /phx: workflow. Use when intent is unclear, mixed (bug + refactor), or user asks "how to approach this".
oliver-kriska/claude-elixir-phoenix 252
phx:init Initialize plugin in a project — install Iron Laws, auto-activation rules, and reference auto-loading into CLAUDE.md. Use when setting up or updating the plugin.
oliver-kriska/claude-elixir-phoenix 252
hexdocs-fetcher Fetch HexDocs for Elixir libraries with HTML-to-markdown conversion. Use when looking up docs on hexdocs.pm — modules, functions, guides, changelogs.
oliver-kriska/claude-elixir-phoenix 252
phx:help Recommend the right /phx: command for planning, review, debug, deploy, or test tasks. Use when "which command", "what should I use", or "how do I". NOT for /help.
oliver-kriska/claude-elixir-phoenix 252
phx:full Use for large features spanning multiple contexts, new domain modules, or when the user wants autonomous end-to-end implementation. Runs the full plan-implement-review-compound cycle with specialist agents and Iron Laws enforcement.
oliver-kriska/claude-elixir-phoenix 252
phx:examples Provide examples and walkthroughs for Phoenix, LiveView, Ecto, OTP patterns. Use when "how do I...", "show me an example", or "what does X look like".
oliver-kriska/claude-elixir-phoenix 252
elixir-idioms OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
oliver-kriska/claude-elixir-phoenix 252
ecto-patterns Ecto patterns — schemas, changesets, queries, migrations, Multi, associations, preloads, upserts. Use when editing Repo calls, Ecto.Query, or schema fields. Skip for Ash.
oliver-kriska/claude-elixir-phoenix 252
ecto-constraint-debug Debug Ecto constraint violations - trace triggers, check migrations, find duplicate data. Use when seeing unique_constraint, foreign_key_constraint, or check_constraint errors.
oliver-kriska/claude-elixir-phoenix 252
phx:document Write @moduledoc and @doc annotations into Elixir source files. Use ONLY when the user explicitly asks to generate documentation for modules, contexts, or schemas.
oliver-kriska/claude-elixir-phoenix 252
deploy Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
oliver-kriska/claude-elixir-phoenix 252
compound-docs Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
oliver-kriska/claude-elixir-phoenix 252
phx:compound Capture solved problems as searchable solution docs. Use after fixing bugs, when "that worked", or after successful /phx:review or /phx:investigate.
oliver-kriska/claude-elixir-phoenix 252
phx:challenge Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, or PR readiness.
oliver-kriska/claude-elixir-phoenix 252
phx:trace Trace Elixir call trees from entry points via mix xref. Use when debugging data flow, planning signature changes, or understanding how a bug reaches code.
oliver-kriska/claude-elixir-phoenix 252
phx:plan Plan multi-step Phoenix features with specialist agents. Use when building new domains, multi-file features, or creating plans from review findings. Use --existing to enhance a plan.
oliver-kriska/claude-elixir-phoenix 252
phx:pr-review Address PR review comments on Elixir/Phoenix code — fetch comments, draft responses, optionally fix code. Use when the user shares a PR URL or mentions reviewer feedback.
oliver-kriska/claude-elixir-phoenix 252
phx:brief Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.
oliver-kriska/claude-elixir-phoenix 252
phx:brainstorm Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
oliver-kriska/claude-elixir-phoenix 252
phx:boundaries Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
oliver-kriska/claude-elixir-phoenix 252
phx:audit Project health audit and health check — architecture, performance, security, tests, dependencies. Use quarterly, before releases, after refactors, or when asked about project health.
oliver-kriska/claude-elixir-phoenix 252
lv:assigns Audit LiveView socket assigns — memory estimates, missing temporary_assigns, unused assigns, unbounded lists needing streams. Use when investigating LiveView memory bloat.
oliver-kriska/claude-elixir-phoenix 252
lab:autoresearch Self-improving loop for plugin skills. Reads program.md, proposes one mutation per iteration, evaluates against deterministic scorer, keeps improvements via git, reverts failures. Targets weakest skill+dimension. Use with /loop for overnight runs.
oliver-kriska/claude-elixir-phoenix 252
skill-monitor Analyze skill effectiveness across sessions. Computes per-skill metrics (action rate, friction, outcomes), identifies degrading skills, and generates improvement recommendations. Requires session-scan data in metrics.jsonl.
oliver-kriska/claude-elixir-phoenix 252