Loading...
Loading...
Found 547 Skills
Search flights, track prices, explore destinations, and find the best travel deals using Google Flights
This skill should be used when the user asks to "generate an AGENTS.md", "create a CLAUDE.md", "write agent instructions", "set up AGENTS.md", "make an AGENTS.md for this repo", "configure agent behavior", or mentions generating, writing, or improving an AGENTS.md or CLAUDE.md file for a project.
Maps codebase structure, queries symbols, traces call paths, and analyzes dependencies. Use when exploring unfamiliar code, finding function callers/callees, detecting circular imports, or generating project overviews.
一个全面、结构化的特性开发工作流程，包含代码库探索、架构设计、质量审查和实现等专门阶段。在构建需要以下条件的新特性时使用：（1）在做出更改之前了解现有代码库，（2）通过系统性的提问澄清模糊的需求，（3）在实现之前设计周到的架构，（4）通过多维度的代码审查确保质量。非常适合涉及多个文件、需要架构决策、包含复杂集成或需求有些不明确的功能特性。
Use when exploring unfamiliar codebases, before searching for code, or after editing files. Builds a structural AST index (classes, functions, imports, call graph) from 12 languages via tree-sitter. Trigger: /graphify
Use when the user asks to write SQL queries, optimize database performance, generate migrations, explore database schemas, or work with ORMs like Prisma, Drizzle, TypeORM, or SQLAlchemy.
Navigate unfamiliar code using GitNexus knowledge graph
Systematically explore and evaluate a library, tool, or GitHub repo in an isolated scratch environment. Use this skill whenever the user asks to "try", "evaluate", "explore", or "kick the tires" on a library/repo/tool, especially when they provide a GitHub URL, npm/pip package name, or repo shorthand like "owner/repo". Use it when they want real primitives, failure modes, and composability beyond quickstarts before deciding on integration. Produces runnable scratch/ scripts demonstrating key primitives, a composition script, and a Tutorial.md with honest findings. This is NOT for full integration into an existing codebase.
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, designing systems, or making architectural decisions. Enters plan mode, reads all available docs, explores the codebase deeply, then interviews the user relentlessly with ultrathink-level reasoning on every decision until a shared understanding is reached. Produces a validated design spec before any implementation begins. Triggers on feature requests, design discussions, refactors, new projects, component creation, system changes, and any task requiring design decisions.
Turn an idea or objective into a goal package for /goal. Interviews the user, builds a reviewed fact sheet via Plannotator, then explores the codebase to produce an execution plan.
Generates comprehensive documentation explaining how a codebase works, including architecture, key components, data flow, and development guidelines. Use when user wants to understand unfamiliar code, create onboarding docs, document architecture, or explain how the system works.
Context-gathering for finding files to read. Maps codebase structure, returns overview + prioritized file list with line ranges. Thoroughness: quick for lookups, medium for bugs/features, thorough for multi-area, very-thorough for architecture audits. Triggers: explore, find files, where is, how does X work.