Loading...
Loading...
Found 2,234 Skills
Structured clarification and requirements gathering through focused dialogue. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed. Triggers on: 'ask me', 'ask questions about', 'clarify requirements', 'gather requirements', 'I need you to ask', or when the user explicitly wants a question-and-answer session before work begins.
Collaborative discovery and design framing for ambiguous or high-risk work. Use when requirements are unclear, multiple approaches are possible, or you need to turn an idea into a validated design brief before planning or coding.
Initialize or update project documentation. Use when setting up docs for a new project (`--init`) or syncing docs to current codebase and architecture changes (`--update`).
Form handling with Formisch, the type-safe form library for modern frameworks. Use when the user needs to create forms, handle form state, validate form inputs, or work with Formisch.
Schema validation with Valibot, the modular and type-safe schema library. Use when the user needs to validate data, create schemas, parse inputs, or work with Valibot in their project. Also use when migrating from Zod to Valibot.
Fetch, organize, and analyze LangSmith traces for debugging and evaluation. Use when you need to: query traces/runs by project, metadata, status, or time window; download traces to JSON; organize outcomes into passed/failed/error buckets; analyze token/message/tool-call patterns; compare passed vs failed behavior; or investigate benchmark and production failures.
Specification-driven development with structured phases: Initialize, Plan, Tasks, Implement+Validate. Creates structured feature specs with traceability to requirements. Use when: starting projects, planning features, implementing with verification, or tracking decisions across sessions. Also use when the user wants to break a feature into tasks, plan before coding, track implementation progress, set up a new project structure, or organize work into specs and plans. Triggers on "map codebase", "initialize", "initialize project", "create feature", "plan", "tasks", "implement", "validate", "archive", "break this into tasks", "plan this feature", "start a new project".
Use when reviewing Rust code for craft quality, when writing new Rust code that should follow professional patterns, or when the user asks to judge, audit, or improve Rust code against best practices. Covers type design, function signatures, trait architecture, error handling, visibility, macros, testing, and performance patterns.
This skill guides the agent in identifying and replacing AI model-specific cliches and formulaic expressions with more natural, human-like language, grounded in external search for better alternatives.
This skill should be used when the user asks to "break down tasks", "create a task list", "plan implementation", "decompose architecture", "create agent tasks", "plan MVP build", "break down feature", "create execution plan", or mentions task breakdown, agent development workflow, or implementation planning. Two-phase workflow for AI agent development with granular, testable tasks.
This skill should be used when the user asks to "remove AI slop", "clean up AI code", "remove AI patterns", "fix AI-generated code", "clean up PR", "remove unnecessary comments", "fix defensive checks", or mentions AI slop, AI code cleanup, or code quality issues from AI-assisted development. Identifies and removes unnecessary comments, defensive checks, type casts to any, and style inconsistencies.
This skill is intended for translating academic texts between Chinese and English. It is activated by keywords such as "翻译", "中译英", "英译中", "translate", "paper translation", "academic writing", or when academic documents (including 论文, 文献, 摘要, paper, abstract, manuscript) require translation that adheres to scholarly rigor and consistent terminology.