End-of-session documentation updater. Updates DEVELOPMENT-PLAN.md checkboxes, adds PROGRESS.md session entries, updates GAME-DESIGN-DOCUMENT.md if design changed, syncs CLAUDE.md status, and keeps OS-specific versions (CLAUDE-Windows.md, mac-claude.md) in parity. Use when finishing a coding session or when the user says "update docs" or "end session".
Googleในใฟใคใซใฎใใถใคใณใใญใฅใกใณใ๏ผ่จญ่จๆธ๏ผไฝๆใฌใคใใใณใผใใฃใณใฐๅใซใฝใใใฆใงใขใฎๅฎ่ฃ ๆฆ็ฅใจ้่ฆใช่จญ่จๅคๆญใ่จ้ฒใใใใใฎ้ๅ ฌๅผๆๆธใไฝๆใใใ ไฝฟ็จใฟใคใใณใฐ: (1) ๆฐๆฉ่ฝใใทในใใ ใฎๅฎ่ฃ ๅใซ่จญ่จใๆๆๅใใใๆ (2) ้ฉๅใช่จญ่จใซใคใใฆไธ็ขบๅฎๆงใใใๆ (3) ใทใใขใจใณใธใใขใฎใฌใใฅใผใๆ็ใชๆ (4) ่จญ่จใๆๆงใพใใฏ่ญฐ่ซใฎไฝๅฐใใใๆ (5) ใปใญใฅใชใใฃใปใใฉใคใใทใผใฎๆค่จใๅฟ ่ฆใชๆ (6) ใฌใฌใทใผใทในใใ ใฎ้ซใฌใใซใใญใฅใกใณใใๅฟ ่ฆใชๆ ใใชใฌใผใใฌใผใบ: ใ่จญ่จๆธใใใใถใคใณใใญใฅใกใณใใใdesign docใใๅฎ่ฃ ๅใฎ่จญ่จใใใขใผใญใใฏใใฃๆๆธใ
Generates documentation using Sphinx and reStructuredText. Supports API docs, user guides, and architecture documentation. Use when creating project documentation, API references, or technical guides.
Generate comprehensive code documentation including docstrings, comments, and API documentation. Use when code lacks documentation, needs better explanations, or requires API docs. Focuses on clarity, completeness, and following language-specific documentation standards.
This skill should be used when the user asks about "gem development", "create a gem", "gemspec", "publish gem", "RubyGems", "bundler", "gem structure", "gem versioning", "semantic versioning", "gem testing", "gem documentation", or needs guidance on creating and publishing Ruby gems.
ไธบ Python ้กน็ฎไปๅบ็ๆ่ฏฆ็ป็ๆๆฏ่ฏดๆๆๆกฃใ่ช้กถๅไธไป็ป้กน็ฎๆๅปบ๏ผๆๆถ้ดๆต็จ่ฟฝ่ธชๆฐๆฎๆตๅจ๏ผ่ฏฆ่งฃๆฏไธชๆถ้ด็น็ๆไฝใ่พๅ ฅ่พๅบๅๅค็็ป่ใ็จไบ็จๆท้่ฆๆทฑๅ ฅ็่งฃไปฃ็ ๆต็จใๅๅงๅ่ฟ็จใๆฐๆฎๆตใๆไปปไฝ้่ฆ่ฏฆ็ปไปฃ็ ๅๆ็ๅบๆฏใ
Generate Level 1 (README.md) user documentation from design docs. Use when creating or updating package README files for npm/GitHub.
Format documentation with emojis, status bars, and versioning matrix. Use when creating or updating README files, documentation, specs, or any markdown files.
Keeps narrative framing in docs while keeping code comments structural and stable.
Automatically applies when writing function docstrings. Uses Google-style format with Args, Returns, Raises, Examples, and Security Note sections for proper documentation.
