Loading...
Loading...
Found 3,123 Skills
Use after implementing features - 7-criteria code review with MANDATORY artifact posting to GitHub issue; blocks PR creation until complete
Document codebase as-is with thoughts directory for historical context
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.
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)
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.
Add an implementation requirement to the ***implementation reqs*** section of a ***plain spec file. Use when the user wants to add non-functional requirements like technology choices, architectural constraints, coding standards, data formats, error handling strategies, or any HOW-to-build guidance to a .plain file.
Guide counterparty credit risk measurement and management for OTC and securities trading. Use when measuring current or potential future exposure to a counterparty, setting or reviewing counterparty credit limits, evaluating ISDA Master Agreement netting benefits, designing collateral management or CSA terms, assessing central clearing mandates under Dodd-Frank or EMIR, monitoring counterparty creditworthiness via CDS spreads or ratings, managing Herstatt or settlement risk in FX, quantifying wrong-way risk, or building real-time exposure dashboards. Also use for counterparty default scenarios, credit deterioration events, EAD and SA-CCR calculations, and CVA capital charges.