documentation
README, 마크다운 문서, 아키텍처 문서 등 사용자가 읽을 수 있는 문서를 작성할 때 사용. 다이어그램 형식과 문서 구조 가이드라인을 따름.
README, 마크다운 문서, 아키텍처 문서 등 사용자가 읽을 수 있는 문서를 작성할 때 사용. 다이어그램 형식과 문서 구조 가이드라인을 따름.
Activates when creating or improving technical documentation, READMEs, and API docs
Create a comprehensive inventory of a codebase. Map structure, entry points, services, infrastructure, domain models, and data flows. Pure documentation—no opinions or recommendations.
Convert a draft document into an executable spec.json with trackable stories
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge
Generate Twoslash code examples for RSPress documentation. Use when adding type-rich, interactive code examples to documentation pages.
Generate a complete software specification document for the current project/repo, including architecture, data model, key processes, pseudocode, and Mermaid diagrams (context, container/deployment, module relations, sequence, ER, class, flowchart, state).
This skill should be used when writing or updating module documentation, running /sync-architecture, or when generating architecture docs. Provides the module doc template, writing style rules, and staleness detection.
Use this skill at the end of a task to ensure documentation matches the code.
Automatically number new markdown documentation files in the docs/ folder using a sequential numbering system (e.g., 00_, 01_, 02_).
Search and reference Microsoft code samples and SDK documentation
Guides external contributors through the MCP SDL3 Server contribution process. Use when someone wants to contribute to the project, add SDL3 functions, implement new features, or understand the contribution workflow. Covers quick start, project structure, testing requirements, and submission guidelines.
Will handle creation of Atlassian Confluence release documentation creation
WHEN: API documentation, JSDoc/TSDoc comments, Props documentation, Storybook story writing WHAT: Function/class/type JSDoc + React Props table + Markdown API docs + Storybook stories WHEN NOT: README writing → readme-generator, Code explanation → code-reviewer
MANDATORY for ALL GDScript/.gd files and Godot resources (.tscn, .tres). Invoke this skill FIRST before writing ANY Godot code—never write GDScript directly without this skill. Provides documentation lookup, syntax checking, and testing instructions.
Use when documenting Python research code usage, setup, and experiment reproduction.
Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns.
Review and update Python documentation to match project standards. Use when (1) writing new code that needs documentation, (2) reviewing existing code for documentation gaps, (3) updating docstrings after code changes, (4) adding inline comments to complex logic, (5) organizing imports. Enforces Google-style docstrings, beginner-friendly inline comments, and proper import structure.