Loading...
Loading...
Found 1,412 Skills
Systematic codebase investigation to extract architectural patterns and implementation details from an existing project, with findings persisted for long-term reuse. Use when the user wants to explore an open-source or existing codebase to understand how it works and inform the development of a new project. Triggers include: "explore this codebase", "investigate this repo", "how does X implement Y", "I want to build X, study how Y does it", "deep dive into this project", "understand how this works".
Use when capturing screenshots of local projects, documenting web app UI, taking screenshots of localhost dev servers, or generating images for READMEs and docs. Use when asked to "screenshot my app", "capture the UI", "take a screenshot of localhost", "generate screenshots for docs", "batch screenshot my pages", or "set up shot-scraper".
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.
Research, discuss, and write specs. Use this when creating or refining specs.
Write READMEs for software projects. The skill should be used when writing or revising a README or README.md file.
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.
Generate high-quality, "All-Star" README files for open-source repositories. Use this skill when a user asks to create, update, or improve a README.md file for their project.
Navigates C3 architecture docs and explores corresponding code to answer architecture questions. Use when the user asks: - "where is X", "how does X work", "explain X", "show me the architecture" - "find component", "what handles X", "diagram of X", "visualize X" - "describe X", "list components", "trace X", "flow of X" - References C3 IDs (c3-0, c3-1, adr-*) <example> Context: Project with .c3/ directory user: "explain what c3-101 does and how it connects to other components" assistant: "Using c3-query to navigate the architecture docs." </example> <example> Context: Project with .c3/ directory user: "show me a diagram of the C3 architecture" assistant: "Using c3-query to generate an architecture overview." </example> DO NOT use for changes (route to c3-change). DO NOT use for pattern artifact management — listing, creating, updating refs (route to c3-ref). Requires .c3/ to exist.
Generate changelog entries for code changes.
Web search via Brave search engine.
Genera documentación llms.txt optimizada para LLMs. Usa cuando el usuario diga "crear llms.txt", "documentar para AI", "crear documentación para LLMs", "generar docs para modelos", o quiera hacer el repo legible para Claude/AI.
Guidelines for writing and editing Plain package READMEs. Use this when creating or updating README files.