documentation-patterns
Apply when writing code documentation: JSDoc comments, README files, API documentation, and inline comments.
Discover tools technical docs skills, compare source repositories and read the instructions for each workflow.
Apply when writing code documentation: JSDoc comments, README files, API documentation, and inline comments.
Designs intuitive Python library APIs following principles of simplicity, consistency, and discoverability. Handles API evolution, deprecation, breaking changes, and error handling. Use when designing new libra...
Creates comprehensive Python library documentation including Google-style docstrings, Sphinx setup, API references, tutorials, and ReadTheDocs configuration. Use when writing docstrings, setting up Sphinx docum...
Write, edit, and lint documentation files
README, 마크다운 문서, 아키텍처 문서 등 사용자가 읽을 수 있는 문서를 작성할 때 사용. 다이어그램 형식과 문서 구조 가이드라인을 따름.
Provides idiomatic Go programming expertise and best practices. Ensures clean, efficient, and maintainable code following official Go conventions. Specializes in concurrent programming patterns, interface desig...
Personalized blog writing assistant for chouzz. Helps transform technical practice snippets into well-structured, progressive blog posts suitable for Medium, Zhihu, and similar platforms. Triggers when chouzz p...
Follows project conventions, extracts examples from documentation, converts them to tests, and ensures documentation accuracy through automated testing. PROACTIVELY Use when generating comprehensive Vitest test...
コードの動作を日本語で詳しく説明するスキル。 以下の状況で使用: (1) ユーザーが「このコードを説明して」「何をしているか教えて」と依頼した時 (2) ユーザーが明示的に「/code-explainer」を実行した時 (3) コードの理解を...
Reference codebase for Elephant Src. Use this skill when you need to understand the structure, implementation patterns, or code details of the Elephant Src project.
Guided workflow for generating SDKs from OpenAPI specifications. Use when users request SDK generation, build, or creation for specific products (pingone, identitycloud, etc.) and languages (go, python, etc.)....
Comprehensive skill for designing, implementing, and documenting RESTful APIs with best practices
This skill should be used when the user asks to "search docs", "look up documentation", "find docs for [library]", "get documentation for [package]", or when working with a library and needing up-to-date API re...
Consult official Claude Code documentation from docs.claude.com using selective fetching. Use this skill when working on Claude Code hooks, skills, subagents, MCP servers, or any Claude Code feature that requir...
Routes documentation and explanation tasks. Triggers on document, explain, readme, api-docs, changelog, guide, comment, describe, write-docs.
코드를 문서화합니다. "문서 작성", "주석 추가", "document" 요청 시 사용합니다.
Technical Writer for documentation. Creates and maintains technical and user documentation. Use this skill for documentation, README, API docs, or user guides.
Documentation writing and editing for nx.dev docs. Use when adding, editing, or polishing documentation, migrating Markdoc to Starlight, debugging content transformations, or fixing documentation site issues. T...
Guide you through creating a single Red Hat Showroom workshop module from reference materials (URLs, files, docs, or text) with business storytelling and proper AsciiDoc formatting.
Parses interface/API information from files or directories and generates OpenAPI-compliant documentation with timestamps
Code repository analysis and technical documentation generation skill
Generates concise Chinese documentation for code interfaces (functions, classes, APIs) with Chinese comment extraction, optimized for Chinese development teams
Write and generate code using memex-cli with Codex backend. Use when (1) Generating code files and scripts, (2) Refactoring existing code, (3) Writing tests, (4) Creating project scaffolds, (5) Implementing alg...
Technical documentation for Rust projects. Creates API docs, README files, architecture guides, and contributor documentation. Follows Rust documentation conventions with strict quality standards.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.