Documentation

Update documentation files based on recent changes while enforcing project writing guidelines.

Generates protobuf API definitions for go-kratos microservices with HTTP annotations, validation rules, and OpenAPI documentation. Use when defining service contracts and APIs.

Use when writing BigQuery queries, optimizing query performance, analyzing execution plans, or avoiding common SQL gotchas. Covers parameterized queries, UDFs, scripting, window functions (QUALIFY, ROW_NUMBER, RANK, LEAD/LAG), JSON functions, ARRAY/STRUCT operations, BigQuery-specific features (EXCEPT, REPLACE, SAFE_*), CTE re-execution issues, NOT IN with NULLs, DML performance, Standard vs Legacy SQL, and performance best practices.

Generate structured research reports with findings, comparisons, recommendations, and citations. Use when documenting investigation results or creating technical comparisons.This skill provides comprehensive research report templates:- Investigation findings with proper structure- Technology comparison tables- Best practices summaries- Citation and reference management- Executive summariesTriggers: "create report", "summarize findings", "compare technologies", "research report", "調査レポート", "技術比較", "ベストプラクティス"

Systematic methodology for debugging bugs, test failures, and unexpected behavior.Use when encountering any technical issue before proposing fixes. Covers root causeinvestigation, pattern analysis, hypothesis testing, and fix implementation.Use ESPECIALLY when under time pressure, "just one quick fix" seems obvious, oryou've already tried multiple fixes. NOT for exploratory code reading.

Comprehensive pre-production repository audit for preparing repos for public release. Use when the user wants to perform a "final sweep", "production check", "pre-release audit", or prepare a repository to be made public. Audits metadata files across all project types (Fabric mods, Node/npm, Go, Python, etc.) for correct username/organization, checks README links, and identifies leftover development artifacts like planning docs, test scripts, and temporary files. Interactive cleanup with user confirmation.

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

Discovers and lists recently modified or created files in Google Drive with professional metadata and summaries. Returns a structured table including file names, types (Docs, Sheets, PDFs, etc.), modification timestamps, 30-word summaries, owners, and direct Drive links. Defaults to the last 24 hours but accepts custom timeframes (e.g., "last 3 hours" or "last week"). Sorts by most recent activity and highlights key changes like new folders, shared file updates, and SNMG18 Meeting Minutes modifications. Use for tracking file changes, finding recent work, or monitoring Drive activity.

Plan and execute complex features using markdown checklists. Use when the user asks to "plan a feature", "create a checklist", or "break down a task".

Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. All plans MUST be validated using the included validation script. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.

Automated generation of promotional assets for podcast episodes from transcripts. Use when the user provides a podcast episode transcript (markdown file) and needs: (1) a one-paragraph episode summary, (2) AI-generated featured image, (3) compelling quotes for social media, (4) short promotional video. Orchestrates transcript analysis, AI image generation via Replicate MCP, and video creation for complete episode marketing asset package.

Generate type-safe API clients from OpenAPI/Swagger specifications or API documentation. Use when users need to create TypeScript or Python API clients with Zod/Pydantic validation, retry logic, error handling, and proper typing. Supports REST APIs, generates from OpenAPI specs or manual endpoint definitions.

Maintains SnowTower project documentation, README, and Claude configuration. Use when updating documentation, auditing .claude folder contents, syncing README with actual project state, or reviewing agent/pattern definitions. Triggers on mentions of documentation, README, maintenance, or .claude folder updates.

Write secure, performant database queries using parameterization, proper indexing, and optimization techniques. When creating or modifying database query logic, data access layers, or repository files. When working on files that interact with databases using SQL, ORMs, or query builders. When implementing SELECT queries, joins, transactions, or data fetching logic. When optimizing queries to prevent N+1 problems, using eager loading, or implementing query caching. When writing parameterized queries to prevent SQL injection vulnerabilities.

Best Rust documentation practices. Use when writing docstrings, documenting functions/types/traits/modules, creating error sections, using intra-doc links, or following rustdoc conventions.

Processes research branches from Claude Code Web sessions - merges content, moves docs to docs/research/, and creates GitHub issues. Use when /popkit:next detects research branches or when manually processing research from mobile sessions. Do NOT use for regular feature branches - only for branches matching claude/research-* or containing research documentation.

Style guidelines for justfile recipe documentation. Use when writing or editing justfiles to ensure consistent and concise documentation.

Guidelines for creating custom rules, custom skills, and custom subagents for Claude.

Create and manage NAF v4 (NATO Architecture Framework) / ADMBw Requirements Viewpoints (R2-R6) in Sparx Enterprise Architect. Use when the user wants to create R2 (Requirement Catalogue), R3 (Requirement Dependencies), R4 (Requirement Conformance), R5 (Requirement Derivation), or R6 (Requirement Realization) diagrams, add requirements elements, create associations between requirements, or work with NAF requirements modeling. Also triggers on natural language like "functional requirement", "requirement category", "derived from", "conforms to standard", etc.

Forensic, high-fidelity context handover for seamless continuation in a new chat. Produces a single Markdown transfer artifact plus reusable templates, preserving decisions, requirements, non-negotiables, and open loops without truncation by judgment. Not for code continuation unless explicitly stated.