dkmaker

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when you have a spec or requirements for a multi-step task, before touching code

Web search, developer research, and library docs. Use for ANY web search, looking up docs, debugging errors, researching patterns, bootstrapping projects, resolving dependencies, exploring GitHub code, finding code examples, or ANY question requiring current/post-cutoff knowledge. NEVER use built-in WebSearch tool — always use this skill instead.

Configure claude-speak TTS - set up API key, choose voices, test playback, fix PATH issues, and manage settings

Launch claude -p sessions in background with filtered output and structured results. Use when executing implementation plans via background headless sessions instead of subagents or manual parallel sessions.

Development toolkit for the my-claude-plugins marketplace. Use when working on plugin development, troubleshooting plugin issues, creating new plugins, or maintaining the my-claude-plugins repository.

Use when executing implementation plans with independent tasks in the current session

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Identify and articulate customer benefit in all forms of customer communication for IT service providers, managed service providers, SaaS companies, and any business that communicates technical work to non-technical customers. Use this skill when writing, reviewing, or improving any customer-facing text: emails, status updates, proposals, support replies, reports, newsletters, or presentations. The skill analyzes communication for missing benefit statements, then rewrites it so the customer clearly understands the value they receive — in terms they care about, not technical jargon. Activate even when the user doesn't explicitly mention "benefit" — any customer communication can be improved.

Use this skill when building or maintaining a frontend web application that is primarily maintained by an AI agent, especially internal dashboards, admin tools, authenticated apps, or tools with a small user base. Applies when the user asks to scaffold, refactor, or extend a React app — even if they don't explicitly mention "SPA", "Next.js", or "architecture". Also use when deciding between Next.js (or any SSR framework) and a plain React + API setup for AI-maintained codebases.

Use this skill for ANY interaction with the local Home Assistant development environment — querying the HA API, managing entities/services/add-ons, controlling the HAOS dev VM (start/stop/ssh), deploying the Pi Agent add-on, or searching HA documentation. Triggers on any mention of Home Assistant, HA entities, the dev VM, add-on deployment, or HA docs lookup.

Home Assistant developer documentation. Use when the user asks about Home Assistant integrations, add-ons, architecture, APIs, entities, config flows, or any HA development topic. Also use when explicitly asked to update or search HA developer docs.

Research and persist coding documentation using Perplexity AI. Use when user asks about documentation, APIs, frameworks, libraries, best practices, coding patterns, or needs to research technical topics. Always checks existing research first.