Loading...
Loading...
Found 34 Skills
Guide for writing inline comments and JSDoc in the codebase. Use when generating code for bug fixes, new components, refactoring, or feature implementation.
MUST be used when user asks to document TypeScript or Vue code — add TSDoc/JSDoc blocks, docblocks, или «задокументировать» functions, classes, methods, interfaces, type aliases, enums, generics, Vue composables, defineProps/defineEmits/defineModel. Enforces strict TSDoc spec (tsdoc.org) and writes all descriptions in Russian. Triggers on phrases like «добавь tsdoc», «задокументируй», «напиши док», «add tsdoc», «document this», «generate jsdoc».
In-code documentation, folder READMEs, and code comments. Use when writing README.md files, JSDoc comments, or explaining code organization.
Write comprehensive code documentation including JSDoc, Python docstrings, inline comments, function documentation, and API comments. Use when documenting code, writing docstrings, or creating inline documentation.
This skill should be used when the user asks to "design ArkUI API", "add component property", "create Modifier method", "review ArkUI API", "deprecate API", "write JSDOC for ArkUI", or mentions OpenHarmony API design standards. Provides comprehensive guidance for ArkUI component API design following OpenHarmony coding guidelines, including static/dynamic interface synchronization, SDK compilation, and verification.
Use when creating or improving component documentation in Storybook. Helps generate comprehensive docs using MDX, autodocs, and JSDoc comments.
Generates API documentation from code including OpenAPI specs, JSDoc, and Python docstrings. Use when documenting APIs, REST endpoints, or library functions.
Generate API documentation from source code with JSDoc and OpenAPI support
Use when debugging TypeScript/JavaScript bugs by tracing call chains, understanding unfamiliar codebases quickly, making architectural decisions, or reviewing code quality. Extract function signatures and JSDoc without full file reads, trace call hierarchies up/down, detect code smells, and follow data flow. Triggers on debugging, understanding codebase, architectural analysis, signature extraction, call tracing.
Эксперт по документации кода. Используй для JSDoc, docstrings, комментариев и автогенерации документации.
Generate JSDoc/docstrings for functions
This skill should be used when the user wants to write, review, or refactor TypeScript code to follow industry best practices. Common triggers include "follow ts best practices", "review this typescript", "fix the typescript style", "make this idiomatic typescript", "apply typescript conventions", and "audit this ts file". Bakes in branded types, discriminated unions, ts-pattern for multi-branch logic, JSDoc on exports, kebab-case file naming, and *Params/*Options object-arg conventions. Skip when the user wants pure functional refactors (use ts-best-practices-functional) or is writing framework components (React/Vue/Svelte have different conventions).