Explore AI Agent Skills & Claude Prompts

Writes production-quality @moduledoc, @doc, and @typedoc annotations for Elixir modules. Scales doc shape to module complexity: one-line docs for simple wrappers, multi-section guides with examples for core concepts. Applies ExDoc conventions including cross-references, admonitions, doctests, tables, options lists, and return contracts. Use when asked to "document modules", "add moduledocs", "write elixir docs", "doc standard", "add @doc", "improve documentation", or when Elixir modules have thin, missing, or inconsistent documentation. Don't use for README files, user-facing guides, ExDoc configuration, hex.pm publishing, mix docs generation, non-Elixir projects, or LiveBook notebooks.

stop-slop

Detects and removes AI writing patterns from prose to make text sound human. Use when the user asks to clean up, edit, review, or rewrite text that sounds like AI, contains AI tells, or reads as generic filler. Use when drafting new prose with explicit instructions to avoid AI patterns or sounding robotic. Don't use for grammar fixes, spell-checking, general tone rewrites, style changes unrelated to AI patterns, code review, SEO optimization, or translation. Don't use if the user wants the writing to sound more formal or professional without mentioning AI patterns specifically.

guide

Coaches the user through completing a task themselves instead of doing it for them. The core signal is that the user wants to remain the actor and build understanding, not receive a finished result. Use when the user explicitly signals they want to be in the driver's seat: phrases like "guide me", "teach me", "help me learn", "I want to understand how to do this", "don't do it for me", or "let me figure it out". Don't use when the user says "show me how" or "walk me through" without pairing it with a desire to do the work themselves (these usually mean "just show me"). Don't use for requests that want a task completed directly, a bug fixed, a document produced, a one-shot explanation without back-and-forth, or general Q&A. Don't use when "help me understand X" means "explain X" without requesting interactive back-and-forth. Don't use when "help me work through" refers to debugging or problem-solving assistance, not skill-building.

interview

Conducts exhaustive requirements-gathering interviews for software features or systems. Reads existing context, then asks structured numbered questions covering purpose, technical design, UI/UX, edge cases, security, and rollout. Use when the user says "interview me", "deep dive on requirements", "spec this out", "fill out the spec", "help me think through this feature", or when a feature needs thorough requirements elicited before a spec or plan can be written. Don't use for quick clarifying questions during an in-progress task (use ask-questions-if-underspecified instead), for writing or updating a SPEC.md document (use create-spec instead), for generating a task plan (use create-plan instead), or for general architectural discussions that don't need structured requirements output.