Loading...
Loading...
Found 3,197 Skills
Complete Guide for Migrating from Cursor Development Mode to Claude Code Development Mode. Use this skill when projects need to switch from Cursor AI IDE to Claude Code CLI, including configuration migration, document structure conversion, workflow adaptation, etc.
Use when synthesizing multiple sources into coherent knowledge bases, performing multi-source analysis, or creating topic expertise from URLs and files. Also use when encountering content integration tasks requiring connections across disparate materials.
Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.
When referencing files, format them as markdown links with line numbers using GitHub-style #L syntax.
A clear, concise description of what this skill does (1-2 sentences). Focus on the VALUE it provides to the user.
Use when a request asks for software design patterns or design principles, including explanations, comparisons, summaries, or quick reference grounded in local docs.
Universal skill reviewer: SKILL mode (D1-D9 + M1-M5) or COMMAND mode (.claude/commands review)
Generates a structured U.S. estate administration/probate status summary covering decedent identifiers, asset inventory, creditor claims, distributions, tax compliance, disputes, and next steps with source citations. Trigger on requests for estate administration summary, probate status report, executor update, estate progress report, inventory and appraisal summary, creditor claims status, or distribution schedule summary.
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use before /plan-ceo-review or /plan-eng-review.
Create CodeTour `.tour` files — persona-targeted, step-by-step walkthroughs with real file and line anchors. Use for onboarding tours, architecture walkthroughs, PR tours, RCA tours, and structured "explain how this works" requests.
README construction — initialize template structure, generate per-package READMEs from doc comments, plan writing tasks, assemble root README from docs/ and package READMEs via doc.json config, and verify edits with `plan drift`.
Repository understanding and hierarchical codemap generation