Loading...
Loading...
Found 29 Skills
Technical documentation expert for creating clear, comprehensive documentation. Use when user asks to write docs, create README, or document code.
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
표준 한국어 규칙에 기반한 문법, 맞춤법, 띄어쓰기, 구두점 검사기. 맞춤법 오류(되/돼, -ㄴ지/-는지), 띄어쓰기 오류(의존명사, 보조용언), 문법 오류(조사 사용, 시제), 구두점 문제를 감지하고 교정합니다. 다음 상황에 사용하세요. (1) 한국어 문서 작성 후 검토 (2) 작성 중 실시간 교정 (3) 코드의 한국어 주석이나 문서 검사 (4) 설명과 함께 한국어 문법 학습 (5) 공식 문서 품질 보장
Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.
HTML structure, data attributes, and commenting guidelines for Shopify themes. Use when structuring HTML markup and adding comments to Shopify theme code.
General Correctness rules, Rust patterns, comments, avoiding over-engineering. When writing code always take these into account
This skill should be used when writing documentation for codebases, including README files, architecture documentation, code comments, and API documentation. Use this skill when users request help documenting their code, creating getting-started guides, explaining project structure, or making codebases more accessible to new developers. The skill provides templates, best practices, and structured approaches for creating clear, beginner-friendly documentation.
[Docs] Autonomous subagent variant of documentation. Use when creating or updating technical documentation, API documentation, or inline code documentation.
Generates concise Chinese documentation for code interfaces (functions, classes, APIs) with Chinese comment extraction, optimized for Chinese development teams
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.
In-code documentation, folder READMEs, and code comments. Use when writing README.md files, JSDoc comments, or explaining code organization.
Auto-generate API documentation from code and comments. Use when API endpoints change, or user mentions API docs. Creates OpenAPI/Swagger specs from code. Triggers on API file changes, documentation requests, endpoint additions.