Loading...
Loading...
Found 3,123 Skills
Research an Elixir/Phoenix topic on the web. Searches ElixirForum, HexDocs, blogs, and GitHub. Uses efficient markdown conversion.
2. Create Feature Design Document
Document a recently solved problem to compound your team's knowledge
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when you have a spec or requirements for a multi-step task, before touching code
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Use this skill whenever the user mentions changelogs, release notes, version updates, "what changed", product updates, app store descriptions, or needs to summarize recent development work for non-technical audiences.
Task Breakdown - generates an implementation plan with tracked tasks based on requirements and design documents. Use when breaking down a design into actionable work items.
Spec Status - displays pipeline progress dashboard for a single specification showing document statuses, blockers, and next action.
Generate or update project memory for AI agents — default to AGENTS.md, support agent-specific targets such as CLAUDE.md, and keep sibling memory files synchronized while capturing stable architecture, conventions, and operational knowledge
Audits the bundled `clerk-cli` skill against the Clerk CLI source tree and proposes or applies updates. Use when the user says "audit the clerk-cli skill", "update the clerk-cli skill", "check clerk-cli against the CLI source", "resync clerk-cli skill", "run audit-clerk-skill", or after Clerk CLI commands, flags, or agent-mode behavior change.
Facilitates the learning step of a proven customer-interview method — the recording half: turning raw material from ONE customer conversation (transcript, notes, memory dump) into a brief per-person debrief file, mapped against the numbered interview-question list (Q1, Q2, … with H-number tags). One concise answer per question actually asked, key phrases kept verbatim, unasked questions honestly skipped, a one-line commentary only where in-the-moment context helps later analysis, and an addenda section for everything heard that fit no question. Load when the user has just done a customer interview and says 'here's the transcript,' 'process my call notes,' 'file this conversation against my questions,' or 'add this interview to the record.' Do NOT load for writing goals, hypotheses, or interview questions (earlier steps), for synthesizing patterns across multiple interviews and updating hypotheses (the next step), or for summarizing meetings or transcripts unrelated to customer interviews.