test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
Essential command-line tools and system utilities.
Use when implementing any feature or bugfix, before writing implementation code
Help with chezmoi dotfile management, ansible playbooks, and syncing configs to the dotfiles repository. Use when modifying configuration files in ~/.config, ~/, ansible playbooks, or other managed locations. ALWAYS prompt the user about syncing to chezmoi after making config changes. Please use this anytime I mention configuration for my computer
任意のファイルパスが .claude/rules/ の paths 条件に該当するかを判定する。ファイル操作前の確認、paths 条件のテスト、rules 適用範囲の確認に使用。Determines if a file path matches any paths conditions in .claude/rules/. Use when checking if a file is covered by rules, testing path patterns, verifying rules coverage, or when the user asks about rule applicability.
Provides guidelines for verifying implementation requirements before creating, editing, or deleting files, and taking appropriate actions when requirements are not met.
Export a sanitized copy of your Claude Code skills to a public repo. Scans for sensitive content, applies sanitization, and verifies clean before export.
Create a new collector bot package with automatic implementation and validation. Use when user wants to create a new collector from scratch.
Detect Kiro specs with modified files in current branch. Use before PRs, spec-specific tests, or CI filtering.
Write files outside workspace sandbox (e.g., ~/.claude/skills). Use when creating/editing personal agent skills or other files that must exist outside the current workspace.
Performs implementation in the chain and records completion state and changed files in analysisContext. Use during implementation.
代码搬运师技能:优先搬运优秀开源项目,禁止重复造轮子。 Use when: 需要实现新功能、选择技术方案、评估是否自己实现。 Triggers: "实现", "开发", "创建", "构建", "写一个", "做一个"
Automatically selects and applies correct templates from /templates based on artifact type.
Idiomatic Go patterns and conventions from official Effective Go guide. Use when writing Go code to ensure proper naming, error handling, concurrency patterns, interface design, and Go-specific idioms. Triggers on Go file creation/editing, code review, or when user asks for idiomatic Go. If you cannot find any info visit to https://go.dev/doc/effective_go
Update LazyVim and all neovim plugins to their latest versions
Generates comprehensive pre-PR test checklist for dotfiles TUI. Use before merging feature branches to main, when running tests, creating test plans, or doing QA. Includes manual tests, automatic tests, security checks, performance tests, aesthetic review, and cross-repo compatibility with sshh and homebrew-tap.
Import entire Godot projects (.tscn scenes + .gd scripts) and convert to GameGen's format for DynamoDB. Detects programmatic position/size assignments and flags them.
Automatically update repository documentation whenever code changes (add/edit/refactor) occur. Use when modifying source code, public APIs/contracts, rendering/interaction/data/compute logic, diagnostics, or build/release/CI flows so docs stay consistent without asking.
Use this skill when the user wants to implement code with formal verification. This workflow discusses requirements, creates Idris2 specifications, reviews them, compiles for verification, then implements in the target language (Python, Rust, or TypeScript). Trigger when user mentions "formal spec", "idris2", or requests rigorous code implementation.
Build features when user wants to implement PRDs, write code for specs, or develop functionality. Works incrementally substory-by-substory with automatic testing and code review. Automatically loads PRD context to maintain consistency. Also writes standalone tests for any file.