Loading...
Loading...
Found 30 Skills
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.
Rewrite AI-generated developer text to sound human — fix inflated language, filler, tautological docs, and robotic tone. Use after review-ai-writing identifies issues.
General Correctness rules, Rust patterns, comments, avoiding over-engineering. When writing code always take these into account
HTML structure, data attributes, and commenting guidelines for Shopify themes. Use when structuring HTML markup and adding comments to Shopify theme code.
Documentation generation workflow covering API docs, architecture docs, README files, code comments, and technical writing.
표준 한국어 규칙에 기반한 문법, 맞춤법, 띄어쓰기, 구두점 검사기. 맞춤법 오류(되/돼, -ㄴ지/-는지), 띄어쓰기 오류(의존명사, 보조용언), 문법 오류(조사 사용, 시제), 구두점 문제를 감지하고 교정합니다. 다음 상황에 사용하세요. (1) 한국어 문서 작성 후 검토 (2) 작성 중 실시간 교정 (3) 코드의 한국어 주석이나 문서 검사 (4) 설명과 함께 한국어 문법 학습 (5) 공식 문서 품질 보장
Adds Doxygen-compatible documentation comments to C++ header files. Use this skill exclusively for adding or improving API documentation in existing header files (*.hpp, *.h). Do NOT create new resource files such as Doxyfile, scripts, or README files.
[Docs] Autonomous subagent variant of documentation. Use when creating or updating technical documentation, API documentation, or inline code documentation.
Translate code comments, documentation, and UI strings between multiple languages. Use when internationalizing applications or translating technical documentation.
Audit and improve JavaScript/TypeScript documentation including JSDoc comments (@param, @returns, @template, @example), comment markers (TODO, FIXME, HACK), and code comment quality. Use when asked to 'add JSDoc', 'document this function', 'audit documentation', 'fix comments', 'add TODO/FIXME markers', or 'improve code documentation'.
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.
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.