44 skills · sorted by relevance
Build Vue 3 applications using JavaScript and JSDoc comments that describe data types. Create components and reusable logic, configure Vite, routing, and state management, and check annotations and behavior with ESLint and Vitest.
Generate API documentation from TypeScript and JavaScript source code. Extract JSDoc comments, fill gaps in public API descriptions, and produce OpenAPI 3.0 definitions, a standard format for describing HTTP endpoints.
Create and maintain code comments, API specifications, documentation sites, and user guides. Apply consistent formats, document parameters and errors, validate code examples, and report which parts of the code have been documented.
Maintain Cherry Studio documentation by checking it against source code, placing facts in appropriate files, and removing duplication. Review documentation affected by code changes and keep relevant English and Chinese counterparts aligned.
Apply the same operation across multiple files using parallel worker agents. The skill finds matching files, divides the work, and reports successes, failures, and skipped files, with a preview option before edits.
Add JSDoc comments to JavaScript or TypeScript functions that are missing documentation. Use when asked to document functions, add JSDoc, or improve code comments.
The English summary is being prepared. Showing the original description.
Documents TypeScript code with JSDoc comments, generates API documentation, and creates type-safe documentation. Use when users request "JSDoc", "code documentation", "API docs", "TypeDoc", or "inline documentation".
The English summary is being prepared. Showing the original description.
Turn source code into project documentation, from a README with installation steps and examples to API references, architecture diagrams, developer guides, and changelogs. Match the scope and comment format to the project's size and programming language.
Apply consistent deprecation notices to public Remotion APIs that remain available. Use TypeScript annotations and documentation formatting to mark APIs as no longer recommended, identify replacements, and review whether both representations follow the conventions.
Write and edit READMEs, guides, and other documentation using the code as evidence. Improve structure, wording, and terminology while checking related pages and links against the project's contribution process and documentation style guide.
Add or revise source-level JSDoc for Shift APIs. Use this skill before writing or editing documentation comments for exported classes, methods, constructors, domain data structures, render frames, reactive state, or any API where caller intent, side effects, lifetime, ownership, or nullability are easy to misunderstand.
The English summary is being prepared. Showing the original description.
Generate comprehensive documentation for undocumented or poorly documented codebases. Use when a user asks to document code, add JSDoc/docstrings, create README files, generate architecture docs, explain what a codebase does, produce onboarding guides, or document internal APIs. Works with any language.
The English summary is being prepared. Showing the original description.
Generate and update language-idiomatic doc comments for TypeScript (TSDoc/JSDoc) and Rust (Rustdoc). Use when asked to "add docs", "document this file", "generate docstrings", "add JSDoc", "add Rustdoc", "write TSDoc", or when working with TypeScript or Rust source files that need documentation comments. Supports file-level and selection-level operations. Deterministic and idempotent — safe to run repeatedly on the same code. Does NOT change behavior, rename symbols, or refactor code.
The English summary is being prepared. Showing the original description.
How to write JSDoc on @rhinestone/sdk public symbols, which is autogenerated into the published SDK Reference. Use when adding or editing doc comments on entry points, the account instance, actions, or utils in sdk/src.
The English summary is being prepared. Showing the original description.
Documentation conventions for generating high-quality AI agent skills from TypeScript source. Use when preparing a library for skill generation, auditing JSDoc quality, fixing audit warnings, writing @useWhen/@avoidWhen/@never tags, or asking about documentation conventions for skills. Use this even if the user just says 'audit my docs', 'improve my JSDoc', or 'make my skills better'.
The English summary is being prepared. Showing the original description.
コードコメントの正確性、完全性、長期的な保守性を分析する。JSDoc、コメント、README等のドキュメントが変更された場合に使用。
The English summary is being prepared. Showing the original description.
Automate doc generation with JSDoc/TSDoc, linters, and pre-commit hooks. Use when setting up markdownlint, configuring doc linting pipelines, integrating JSDoc/TSDoc, or building automated documentation workflows.
The English summary is being prepared. Showing the original description.
TypeDoc (TypeScript API ドキュメントジェネレーター) リファレンス。 typedoc.json、TSDoc タグ、CLI オプション、entryPoints、 テーマ (default / markdown)、プラグイン開発、 TSDoc / JSDoc コメントから HTML / Markdown ドキュメント生成。
The English summary is being prepared. Showing the original description.
コードにコメント・ドキュメンテーションコメントを追加・補強する。「コメント追加して」「コメント書いて」 「コメントを補強して」「JSDoc 付けて」「docstring 付けて」「ドキュメンテーションコメント付けて」で使用。 パッケージ・サービス視点での役割境界、呼び出し元・呼び出し先の前提と契約、他ファイル・他サービスからの 文脈を「その場で読める」形で残す。コード自体は変更しない（実装変更は implement-issue へ）。 詳細規約は code-comment-style、コミット作成は create-commit、CLAUDE.md 同期は update-docs を参照。
The English summary is being prepared. Showing the original description.
有馬記念分析システムのコメント引き算レビュー。不要コメント（コードの再掲・getter 名と同義の JSDoc）、コメント量の増えすぎ（多行ファイルヘッダ・長い @example・装飾過多・base 差分での純増）、陳腐化（コメントアウトされた旧コード・重み変更で古くなる数値コメント・理由なし TODO）、冗長・重複（同じ重み配分の説明が複数ファイルに散在）を検証する。コメントが『存在するか/1行で why を書くか』の足し算側は review-code 2.5 の責務で、本スキルはその過剰・不要を削る側を見る。Use when user says 'コメントレビュー', 'コメント量チェック', 'review comments', '不要コメント確認', or '過剰コメント'.
The English summary is being prepared. Showing the original description.
Review and refine source-code comments and documentation attached to functions or other declarations. The skill removes redundant explanations, checks outdated TODOs, and preserves concise, evidence-based reasons and constraints that maintainers cannot readily infer from the code.
Review Handsontable code changes for architecture, code quality, performance, accessibility, and test coverage. Findings include severity, confidence, and file locations, helping developers assess whether changes follow project rules and demonstrate the intended behavior.
Work on Handsontable core bugs, features, and TypeScript types using its architecture and implementation conventions. The skill directs tasks to specialist guides and outlines registration, compatibility, documentation, and testing checks for changes.
Build, debug, and refactor JavaScript applications for browsers and Node.js. Covers asynchronous tasks with async/await, module organization, performance checks, and test creation, with explicit error handling and modern ES2023+ syntax.