ReddRadar
Topic: vibe-coding
3,535 skills in this topic.
-
phx:investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
oliver-kriska/claude-elixir-phoenix 252
-
phx:intro
Walk through the Elixir/Phoenix plugin commands, workflow, and features in 6 interactive sections. Use when a new user wants to learn what the plugin offers or needs a refresher on available commands.
oliver-kriska/claude-elixir-phoenix 252
-
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
-
bernstein-agents
Manage Bernstein agents — list active agents, inspect their output, kill stalled agents, or stream live logs. Use when the user asks about agents, wants to see what an agent is doing, or needs to kill one.
chernistry/bernstein 104
-
bernstein-alerts
Show active alerts from Bernstein — failed tasks, stalled agents, budget warnings, blocked tasks needing human intervention. Use when the user asks about problems, errors, warnings, or what needs attention.
chernistry/bernstein 104
-
bernstein-approve
Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.
chernistry/bernstein 104
-
bernstein-cost
Show detailed cost breakdown and budget status for the Bernstein orchestrator. Use when the user asks about spending, budget, cost per model, cost per agent, or wants a cost projection.
chernistry/bernstein 104
-
bernstein-create-task
Create a new task in the Bernstein orchestrator. Use when the user wants to add a task, delegate work to an agent, file a bug fix, or queue up work for the orchestrator to handle.
chernistry/bernstein 104
-
bernstein-plan
Create and manage multi-step execution plans in Bernstein. Plans decompose complex goals into stages with dependencies. Use when the user wants to plan a complex feature, break down a large task, or review an execution plan before agents start working.
chernistry/bernstein 104
-
bernstein-quality
Show quality metrics for Bernstein runs — success rates per model, lint/test pass rates, completion time distributions. Use when the user asks about quality, reliability, which model performs best, or pass rates.
chernistry/bernstein 104
-
bernstein-status
Show Bernstein orchestrator status — active agents, task progress, costs, and alerts. Use when the user asks about orchestrator status, what agents are doing, task progress, how much has been spent, or what's happening with the build.
chernistry/bernstein 104
-
docs-review
Review all project documentation against the current codebase and fix inaccuracies. Only modifies documentation files.
njbrake/agent-of-empires 1,561
-
aoe
Manage AI coding agent sessions via Agent of Empires (aoe)
njbrake/agent-of-empires 1,561
-
deep-research
Use this skill instead of WebSearch for ANY question requiring web research. Trigger on queries like "what is X", "explain X", "compare X and Y", "research X", or before content generation tasks. Provides systematic multi-angle research methodology instead of single superficial searches. Use this proactively when the user's question needs online information.
deciding/handclaw 221
-
project_workflow
Create or update project workflow documentation in AGENTS.md (for opencode/codex) or CLAUDE.md (for claude). Use when: user asks to create/update a workflow, document build/test/debug steps, or update project documentation. The skill will check memory and repo to extract relevant commands, then write sections to the appropriate file. NOT for: one-off commands, reading existing docs only, or when the workflow sections are already complete.
deciding/handclaw 221
-
super-dev
Super Dev pipeline governance for research-first, commercial-grade AI coding delivery
shangyankeji/super-dev 213
-
super-dev-core
Super Dev pipeline governance for research-first, commercial-grade AI coding delivery
shangyankeji/super-dev 213