rspress-sync
Sync site docs with API changes. Use when APIs have been updated and documentation needs to reflect the changes.
Sync site docs with API changes. Use when APIs have been updated and documentation needs to reflect the changes.
CUI JavaDoc documentation standards for Java classes, methods, and code examples
Review RSPress documentation for quality and Twoslash issues. Use when checking docs for completeness, accuracy, and code example quality.
Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution-design.md files in docs/specs/. Includes validation checklist, consistency verification, and overlap detection.
Create and maintain clear, useful documentation. Use when writing docs, README, API docs, guides, or ADRs.
Look up Microsoft API references, find working code samples, and verify SDK code is correct. Use when working with Azure SDKs, .NET libraries, or Microsoft APIs—to find the right method, check parameters, get working examples, or troubleshoot errors. Catches hallucinated methods, wrong signatures, and deprecated patterns by querying official docs.
技术文档生成技能。当用户需要编写 README、API 文档、项目文档、技术规范、使用指南或任何技术文档时使用此技能。
Describes the primary technologies, frameworks, libraries, and language conventions used in this codebase.
ライブラリやフレームワークのドキュメントが必要な場合に自動発動。Context7 MCPを使用して最新の公式ドキュメントを取得する。
Wraps up a coding session by creating documentation and committing artifacts. Use when the user says "wrap up", "close session", "let's finish", or similar end-of-session language.
Guide documentation updates when changing versions, adding content, or preparing releases
Update IBL5 documentation during pull requests and feature development. Use when updating docs, creating README files, or documenting completed work.
Guidelines for writing clear, comprehensive, and technically accurate documentation for Project SENTINEL. Use when creating READMEs, API docs, or internal engineering guides.
プロジェクトの開発ガイドライン(docs/development-guidelines.md)を新規作成/更新する。既存の開発ガイドラインがある場合は最優先し、構造と方針を維持して更新する。内容は「コーディング規約(implementation.md)」と「開発プロセス(process.md)」の2本立てで、具体例と理由、測定可能な基準を含める。
Write purposeful code comments that explain the "why" behind technical decisions, complex logic, and non-obvious implementations using JSDoc for components and APIs. Use this skill when documenting component props, explaining complex algorithms, noting performance optimizations, documenting workarounds, or adding API documentation. When working on component prop interfaces requiring JSDoc documentation, complex business logic or algorithms, performance optimization rationale, browser compatibility workarounds or hacks, API route documentation with request/response formats, configuration file explanations, Content Collection schema documentation, or regex patterns and what they match.
Technical specification writer. Use when creating detailed technical documentation, API specifications, or architecture documents.
Standards for API development, documentation, and maintenance using OpenAPI 3.0.
Use when adding support for a new Nango provider - configures provider in providers.yaml, creates documentation (main page, setup guide, connect guide), and updates docs.json following established patterns
Converts basic plans into Codex CLI execution-ready documents with embedded context, verification steps, and mandatory code review workflow. Use after creating a plan, or when preparing plans for Codex CLI execution where inline context is essential and execution is split into multiple files for automation.
세련된 README 파일, 변경 이력(changelog), 기여 가이드(contribution guide) 및 기술 문서를 작성하기 위한 전문가 수준의 Markdown 문서화 SKILL입니다. 사용 사례: (1) 배지와 섹션을 포함한 README 생성, (2) git 히스토리를 이용한 자동 변경 이력 생성, (3) 목차(table of contents) 생성, (4) 기여 가이드라인 작성, (5) 기술 문서 포맷팅, (6) 구문 강조(syntax highlighting)를 포함한 코드 문서화
Fixes documentation issues including missing JSDoc, module-level comments, and @returns tags. Use when functions lack documentation or JSDoc is incomplete.