study-note
학습 중 떠오른 아이디어와 메모를 아카이브 파일에 시간순으로 기록합니다. `scripts/study-note-helper.sh`를 사용하여 현재 KATA 프로젝트의 docs/study/아카이브.md에 노트를 추가합니다.
Find the perfect capability for your agent.
학습 중 떠오른 아이디어와 메모를 아카이브 파일에 시간순으로 기록합니다. `scripts/study-note-helper.sh`를 사용하여 현재 KATA 프로젝트의 docs/study/아카이브.md에 노트를 추가합니다.
Get today's date for web searches and date-sensitive tasks. Auto-invoke before any WebSearch that includes a year (e.g., "React 2024", "Python 2025"), when searching for current documentation, latest releases, or recent information. Ensures searches use the correct current year instead of outdated dates.
Root cause fixing and avoiding workarounds. Use when encountering errors, bugs, or problems. Triggers on "bug", "error", "fix", "debug", "workaround", "wrapper", "hack", "broken", "not working", "failing", "issue", or when tempted to add complexity to avoid fixing the real problem.
Write Python docstrings following PEP 257 and popular formats (Google, NumPy, Sphinx). WHEN: Writing docstrings for Python functions/classes/modules, choosing docstring format, documenting parameters/returns/exceptions. WHEN NOT: JavaScript documentation (use js-docstring), TypeScript (use ts-docstring), PHP (use php-docstring), general code comments.
Use when documenting Python research code usage, setup, and experiment reproduction.
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.
Comprehensive code documentation standards and guidelines for maintaining up-to-date documentation across Python, HTML, CSS, and JavaScript codebases. Use when creating or modifying code to ensure proper documentation practices and maintainable code.
Expert Python development guidance for this codebase. Use when writing Python code, implementing features, or following project coding standards and patterns.
Analyze and explain Python code in detail. Provides comprehensive explanations of functions, classes, logic, and best practices. Use when user needs detailed explanations of Python code, documentation of existing codebases, or understanding of complex programming concepts and implementations.
TSDoc documentation standards for TypeScript following tsdoc.org conventions. WHEN: Writing TSDoc comments, documenting TypeScript functions/classes/interfaces/types, generating docs with TypeDoc, improving existing TS documentation. WHEN NOT: JavaScript code (use js-docstring), Python (use python-docstring), PHP (use php-docstring), runtime logic without documentation needs.
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 library APIs, reviewing existing APIs for improvements, or managing API versioning and deprecations.
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.
Comprehensive pytest testing skill for Python projects with specialized FastAPI support. Use when: (1) User wants to generate test files for existing code, (2) User asks about pytest patterns, best practices, fixtures, or test organization, (3) User is working with FastAPI testing (TestClient, async tests, dependency overrides, authentication), (4) User needs help writing tests, configuring pytest, or organizing test suites. Includes test generation script, FastAPI-specific patterns, fixture templates, and comprehensive pytest reference documentation.
Write meaningful code comments that explain WHY rather than WHAT, focusing on business logic, non-obvious solutions, workarounds, and complex algorithms while keeping code self-documenting. Use this skill when adding comments to explain rationale, documenting complex business logic, explaining workarounds or temporary solutions, describing performance optimizations, writing function documentation (JSDoc, docstrings, XML docs), or reviewing code for appropriate commenting. Apply when working on any code file that contains logic requiring explanation, public API functions, complex algorithms, security-critical code, or architectural decisions. This skill ensures comments explain rationale not implementation (WHY not WHAT), self-documenting code through clear naming (refactor unclear code instead of commenting), concise and evergreen comments (no who/when dated comments - Git tracks this), links to external resources for context, proper function documentation format (JSDoc for TS/JS, docstrings for Python, XML d
Pythonファイルの挙動を理解するために、挙動を変えずに解説コメントとdocstringを追加する。ユーザーが「XXX.pyについて、動作を理解したいから細かくコメント入れて」「挙動は変えずにコメントを足して」「このPythonファイルに解説を入れて」などと言ったときに使う。
JSDoc documentation standards for JavaScript following jsdoc.app conventions. WHEN: Writing JSDoc comments, documenting JavaScript functions/classes/modules, generating API docs with JSDoc, improving existing JS documentation. WHEN NOT: TypeScript code (use ts-docstring), Python (use python-docstring), PHP (use php-docstring), runtime logic without documentation needs.
Standardized procedure to generate developer API documentation for C++ libraries and Python modules.
Add detailed comments explaining WHY code works, its context, edge cases, and performance implications. Use when user mentions "add comments", "document", "explain code", "improve readability", or "maintainability". Supports C++, Python, Java, JavaScript, Go, Rust, SQL.
Write PHP DocBlocks following PSR-5 and PSR-19 PHPDoc standards. WHEN: Writing DocBlocks for PHP classes/methods/functions/properties, documenting @param/@return/@throws, type annotations in PHPDoc. WHEN NOT: Python docstrings (use python-docstring), JavaScript (use js-docstring), TypeScript (use ts-docstring).