Loading...
Loading...
Found 88 Skills
This skill should be used when agents need to search codebases for text patterns or structural code patterns. Provides fast search using ripgrep for text and ast-grep for syntax-aware code search.
Use this skill when you need to keep a repository's README.md file updated with project metadata, installation instructions, usage examples, and more. It automates synchronization by analyzing codebase patterns and dependencies.
Use this skill whenever the user asks to analyze, understand, or survey an entire project, codebase, or any collection of files. Trigger phrases include "analyze a large file", "process multiple files", "comprehend this problem", "take a look at these files", "familiarize yourself with this project", or any similar request, however phrased. Also activate when the task involves processing context that exceeds what can be reasoned about in a single pass, when encountering any input larger than ~50KB that requires detailed analysis, or when the user mentions "context comprehension" or "recursive comprehension". This skill TAKES PRIORITY over your default explore subagents for any project-wide or codebase-wide analysis task.
Structured development workflow that separates research, planning, and implementation into distinct phases with persistent markdown artifacts. Use when starting any non-trivial feature, refactor, bug investigation, or codebase change. Trigger on: "deep work", "research and plan", "plan before coding", "write a plan", "research this codebase", "don't code yet", "understand then implement", or when the user wants a disciplined approach to a complex task. Also use when the user says "research", "plan", "annotate", "implement the plan", or references research.md/plan.md artifacts.
This skill should be used when user asks to "generate UML", "create sequence diagram", "生成时序图", "生成类图", "generate PlantUML", or discusses generating UML diagrams for new interfaces or API design.
Access AI-generated documentation and insights for GitHub repositories via DeepWiki. This skill should be used when exploring unfamiliar codebases, understanding repository architecture, finding implementation patterns, or asking questions about how a GitHub project works. Supports any public GitHub repository.
Find similar or analogous code patterns elsewhere in a codebase. Use when answering "Do we do something similar elsewhere?" or "What existing patterns match this?" Returns factual findings about similar code - locations, similarity type, and confidence.
Hypothesis-driven deep research swarm. Spawns specialist sub-agents to investigate a task across codebase patterns, web sources, MCP tools, installed skills, and project dependencies — with evidence grading and adversarial challenge. Activates on: research, investigate, discover, deep research, how should I, what's the best way, explore options, analyze approaches, scout, prior art, feasibility.
Update existing app design document based on codebase changes and project evolution
Transform codebases into authentic, interview-defensible resume project experience. Use when analyzing a codebase for: (1) Extracting resume-ready project descriptions, (2) Preparing for technical interview questions about past projects, (3) Understanding the engineering depth and value of a codebase, (4) Identifying defensible technical achievements. Prioritizes correctness and interview credibility over exaggeration.
This skill should be used when the user wants to identify the single highest-impact improvement to make to their project. Triggers on requests like "what should I build next", "innovate", "best improvement", "next big thing", or when seeking the most compelling addition to a codebase.
Use when you need to plan technical solutions that are scalable, secure, and maintainable.