Loading...
Loading...
Found 3,108 Skills
Enforces strict use of Chinese in all interactions, code comments, and documentation generation, in compliance with advanced technical writing standards. Enforces strict adherence to the Chinese language in all interactions, code comments, and documentation with high-quality technical writing standards.
REST API design and development expert specializing in endpoint design, HTTP semantics, versioning, error handling, pagination, and OpenAPI documentation. Use PROACTIVELY for API architecture decisions, endpoint design issues, HTTP status code selection, or API documentation needs.
Research MQL5 documentation (Japanese and English only) for MQL5 creation/editing issues, compile errors, or API questions. Use when users ask to look up docs, interpret MQL5 errors, or confirm correct language usage. Sources limited to https://www.mql5.com/ja/docs and https://www.mql5.com/en/docs.
Generate clear, professional, and polished Japanese technical articles suitable for corporate blogs, official documentation, and technical publications. Use this skill when the user wants to create enterprise-level content with consistent polite tone (です/ます), logical structure, and authoritative voice. Triggers include requests like "polished article", "professional tone", "enterprise blog", "公式ドキュメント", "プロフェッショナルな記事", or when content needs formal technical writing.
Documentation consistency reviewer that checks alignment between code implementation and documentation. Use when user requests reviewing documentation vs code consistency, checking if README/docs are outdated, verifying API documentation accuracy. Applicable for (1) reviewing README vs implementation consistency (2) checking if docs/ directory content is outdated (3) verifying API/config documentation accuracy (4) generating documentation consistency reports. Trigger words include doc review, documentation consistency, check outdated docs, verify docs.
This skill should be used when the user asks to "map documentation links", "extract docs navigation", "get documentation structure", "scrape docs sidebar", or wants to understand the structure of a documentation website before creating skills.
Conducts in-depth analysis of a specific source or topic, producing comprehensive summaries for research synthesis. Use when you need detailed analysis and documentation of individual sources as part of a larger research effort.
End-of-session documentation workflow that updates README, CHANGELOG, agent context files, and creates session logs. Use when wrapping up a working session, when asked to document session progress, when preparing handoff documentation, or when the user says "wrap up", "end session", "document progress", or "save session".
Update voxtype documentation for releases and features. Use when adding features, fixing bugs, or preparing releases. Covers user manual, troubleshooting, website, release notes, and contributor credits.
Generate a Phase Spec/PRD by extracting features from an annotated Vision PRD. Use when user wants to create quarterly phase documentation, extract requirements from vision, plan a development phase, or decompose features into R-nnnn requirements. Requires annotated Vision PRD with F-nnn tags and Coverage Index.
Reviews documentation PRs and provides GitHub PR suggestions. Load when asked to review, suggest changes, or provide feedback on docs content. Covers MDX, frontmatter, style guide, components, and content accuracy.
API documentation specialist who creates comprehensive OpenAPI/Swagger specifications and technical documentation for RESTful APIs, GraphQL schemas, and microservices architectures. Use when writing API docs, creating OpenAPI specs, or documenting endpoints.