Topic: vibe-coding
3,535 skills in this topic.
-
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
-
testing
Elixir testing patterns — ExUnit, Mox, factories, LiveView test helpers. Use when working on *_test.exs, test/support/, factory files, or fixing test failures.
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:verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
oliver-kriska/claude-elixir-phoenix 252
-
phx:techdebt
Analyze Elixir/Phoenix technical debt — duplicates, refactoring opportunities, credo issues. Use when asked about code quality, cleanup, or what to improve.
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: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
-
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.
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:review
Review code with parallel agents — tests, security, Ecto, LiveView, Oban. Use after implementation to catch bugs and anti-patterns before committing.
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-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-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
-
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-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-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-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
-
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
-
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
-
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
-
super-dev-core
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