sonarcloud-tools
>-
agent-builder
Creates and configures Claude Code agent files (.claude/agents/*.md) with YAML frontmatter, tool permissions, model selection, and system prompt structure. Use when building new agents, configuring agent frontmatter, designing discovery triggers, setting tool permissions, writing system prompts, or selecting agent models.
command-builder
Creates and configures Claude Code slash commands with YAML frontmatter, argument handling, and tool permissions. Use when building new commands, adding $ARGUMENTS or $1-$N parameters, configuring allowed-tools, organizing command namespaces, or fixing command failures.
context7-tools
>-
deep-research
>-
design-synthesis
>-
exa-tools
>-
github-tools
>-
hooks-builder
>-
hostinger-tools
>-
mermaid-diagramming
>-
n8n-builder
>-
nx-tools
>-
output-style-builder
>-
parallel-dispatch
Orchestrates concurrent workstreams via Task tool for non-trivial requests. Decomposes complex tasks into 3-10 parallel agents with independent scopes and synthesizes results. Use when requests involve: (1) multiple investigative paths or validation layers, (2) research, analysis, or debugging exceeding trivial scope, (3) implementation planning requiring facet exploration, or (4) any moderate+ complexity task benefiting from parallel execution.
perplexity-tools
>-
plan-decompose
>-
skill-builder
Creates and edits Claude Code skills with YAML frontmatter, folder structure, and depth-scaled content. Use when building new skills, updating existing skills, designing SKILL.md metadata, organizing skill folders, validating skill structure, or adding Python and TypeScript scripts for deterministic operations.
style-standards
Enforces style consistency for documentation and code with support for taxonomy, voice, and formatting domains. Use when creating or modifying files requiring: (1) markdown structure (headers, lists, tables, Dictums, separators), (2) code organization (comments, section dividers, naming conventions), (3) voice compliance (tone, grammar, imperative phrasing), or (4) formatting validation against project standards.
tavily-tools
>-
typescript-effect
>-