development-guidelines
プロジェクトの開発ガイドライン(docs/development-guidelines.md)を新規作成/更新する。既存の開発ガイドラインがある場合は最優先し、構造と方針を維持して更新する。内容は「コーディング規約(implementation.md)」と「開発プロセス(process.md)」の2本立てで、具体例と理由、測定可能な基準を含める。
プロジェクトの開発ガイドライン(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.
Complete implementation guide for the DocsSidebar v2 (React Complex Tree + Convex + Liveblocks + AI).
Instructions for checking the available guides in the ai4space repository and reading them.
Write or upgrade conventional Python docstrings for public modules, classes, functions, methods, and properties. Docstrings must be user-facing, mkdocstrings-friendly, include runnable examples, and must not repeat type hints.
How user-facing and internal documentation should be written and maintained.
Docs Internal Agent. 아키텍처 문서, 온보딩 가이드 작성을 담당합니다.
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
Write self-documenting code with minimal, evergreen comments that explain complex logic without documenting changes or temporary fixes. Use this skill when adding comments to any code file. When deciding whether code needs a comment or should be made more self-explanatory. When writing comments for complex algorithms or business logic. When tempted to add comments about recent changes, fixes, or TODOs. When reviewing existing comments for relevance and accuracy.
코드를 문서화합니다. "문서 작성", "주석 추가", "document" 요청 시 사용합니다.
Creates C3 architecture documentation from scratch using staged Socratic discovery. Use when the user asks to "adopt C3", "onboard me to architecture", "scaffold C3 docs", "init C3", "set up architecture docs", or starts C3 documentation for a new project. Implements 3-stage workflow: Inventory → Details → Finalize.
Produce a feature/component documentation that adheres to repo standards.
Эксперт по документации кода. Используй для JSDoc, docstrings, комментариев и автогенерации документации.