Loading...
Loading...
Found 145 Skills
FFmpeg-based 4-step video creation: Validate, Prepare, Encode, Verify. Use when user wants to combine a static image with audio to create an MP4 video, create a music video from cover art, or produce podcast/YouTube video from an image and audio file. Use for "image to video", "static video", "mp4 from image", "album art video", or "audio visualization". Do NOT use for video editing, live streaming, or generating images.
Go error handling patterns: wrapping with context, sentinel errors, custom error types, errors.Is/As chains, and HTTP error mapping. Use when implementing error returns, defining package-level errors, creating custom error types, wrapping errors with fmt.Errorf, or checking errors with errors.Is/As. Use for "error handling", "fmt.Errorf", "errors.Is", "errors.As", "sentinel error", "custom error", or "%w". Do NOT use for general Go development, debugging runtime panics, or logging strategy.
Manually teach Claude Code an error pattern and its solution, storing it in the learning database with high confidence. Use when user provides an explicit "error -> solution" pair, wants to pre-load fix knowledge, or corrects a previous bad fix. Use for "/learn", "teach pattern", "remember this fix". Do NOT use for automatic error learning (that is the error-learner hook), debugging live issues, or querying existing patterns.
Go-specific code review with 6-phase methodology: Context, Automated Checks, Quality Analysis, Specific Analysis, Line-by-Line, Documentation. Use when reviewing Go code, PRs, or auditing Go codebases for quality and best practices. Use for "review Go", "Go PR", "check Go code", "Go quality", "review .go". Do NOT use for writing new Go code, debugging Go bugs, or refactoring -- use golang-general-engineer, systematic-debugging, or systematic-refactoring for those tasks.
Validate-then-fix workflow for PR review comments: Fetch, Validate, Plan, Fix, Commit. Use when user wants to address PR feedback, fix review comments, or resolve reviewer requests. Use for "fix PR comments", "address review", "pr-fix", or "resolve feedback". Do NOT use for creating PRs, reviewing code without fixing, or general debugging unrelated to PR comments.
Statistical rule discovery through measurement of Go codebases: Count patterns, derive confidence-scored rules, produce Style Vector fingerprint. Use when analyzing codebase conventions, extracting implicit coding rules, profiling a repo before onboarding or PR automation. Use for "analyze codebase", "find coding patterns", "what conventions does this repo use", "extract rules", or "codebase DNA". Do NOT use for code review, bug fixes, refactoring, or performance optimization.
Identify and fix common testing mistakes across unit, integration, and E2E test suites. Use when tests are flaky, brittle, over-mocked, order-dependent, slow, poorly named, or providing false confidence. Use for "test smell", "fragile test", "flaky test", "over-mocking", "test anti-pattern", or "skipped tests". Do NOT use for writing new tests from scratch (use test-driven-development), refactoring architecture (use systematic-refactoring), or performance profiling without a specific test quality symptom.
Analyze and optimize blog post SEO: keywords, titles, meta descriptions, headers, and internal linking. Use when user says "check seo", "optimize for search", "improve search visibility", or when publishing a new post that needs search optimization. Do NOT use for writing new content, major content edits, or site-wide technical SEO (robots.txt, sitemaps).
Go testing patterns and methodology: table-driven tests, t.Run subtests, t.Helper helpers, mocking interfaces, benchmarks, race detection, and synctest. Use when writing new Go tests, modifying existing tests, adding coverage, fixing failing tests, writing benchmarks, or creating mocks. Triggered by "go test", "_test.go", "table-driven", "t.Run", "benchmark", "mock", "race detection", "test coverage". Do NOT use for non-Go testing (use test-driven-development instead), debugging test failures (use systematic-debugging), or general Go development without test focus (use golang-general-engineer directly).
Persistent markdown files as working memory for complex tasks: plan, track progress, store findings. Use when tasks have 3+ phases, require research, span many tool calls, or risk context drift. Use for "plan", "break down", "track progress", "multi-step", or complex tasks. Do NOT use for simple lookups, single-file edits, or questions answerable in one response.
Weighted decision scoring framework for architectural and technology choices. Frames decisions with 2-4 options, scores against weighted criteria, detects close calls, and records decisions in the active ADR or task plan. Use when: "should I use X or Y", "which approach", "compare options", "trade-offs between", "help me decide", "evaluate alternatives"
Manage editorial content pipeline through 6 stages: Ideas, Outlined, Drafted, Editing, Ready, Published. Use when user wants to view pipeline status, add ideas, move content between stages, schedule posts, or archive published content. Use for "content calendar", "pipeline status", "add idea", "schedule post", or "move to drafted". Do NOT use for creating Hugo content files, deploying posts, or modifying site configuration.