Command Claude Code
Test and refine simulation accuracy with validation loops, bias detection, and continuous improvement frameworks.
Professional slash commands for Claude Code that provide structured workflows for software development tasks including code review, feature creation, security auditing, and architectural analysis.
Command Claude Code
Test and refine simulation accuracy with validation loops, bias detection, and continuous improvement frameworks.
Command Claude Code
Accelerate scenario testing with rapid iteration cycles, confidence intervals, and compressed decision timelines.
Command Claude Code
Build production-ready Claude Code Skills in minutes!
Command Claude Code
Create comprehensive Claude Code Skills through elicitation-driven development.
Command Claude Code
Validate and package a Claude Code Skill into a distributable zip file.
Command Claude Code
This skill {{WHATITDOES}}. This skill should be used when {{TRIGGERSCENARIOS}}. {{DEPENDENCIESIFANY}}.
Command Claude Code
This skill {{WHATITDOES}}. This skill should be used when {{TRIGGERSCENARIOS}}. {{DEPENDENCIESIFANY}}.
Command Claude Code
Command "[object Object]" from qdhenry/Claude-Command-Suite, covering quick start, instructions, examples, example 1: {{example1name}} and requirements.
Command Claude Code
Command "[object Object]" from qdhenry/Claude-Command-Suite, covering quick start, instructions, examples, example 1: {{example1name}} and expected output.
Command Claude Code
Command "[object Object]" from qdhenry/Claude-Command-Suite, covering purpose, quick start, instructions, examples and example 1: {{example1name}}.
Command Claude Code
Display comprehensive help documentation for the /parallel-tasks command including usage examples, options, agent types, and best practices for deploying specialized agents to work on multiple tasks simultaneously.
Command Claude Code
Deploy specialized AI agents to work on multiple tasks simultaneously while maintaining coordination and task tracking. This command can reduce development time by 60-80% through intelligent agent coordination and task parallelization.
Command Claude Code
Rapid spec development for simpler tasks. Deep codebase analysis with opinionated recommendations and max 10 targeted questions. Use instead of spec-elicitation for straightforward features, refactors, and well-understood work.
Command Claude Code
Interview-driven spec development that transforms vague ideas into battle-ready specifications through structured, exhaustive questioning. Use when starting any non-trivial feature to ensure complete understanding before writing code.
Command Claude Code
Complete installation and configuration guide for integrating the spec-workflow MCP (Model Context Protocol) server with Claude Code to enable advanced task management and parallel execution capabilities.
Command Claude Code
Audit and improve accessibility in Svelte/SvelteKit applications, ensuring WCAG compliance and inclusive user experiences.
Command Claude Code
Create new Svelte components with best practices, proper structure, and optional TypeScript support.
Command Claude Code
Help debug Svelte and SvelteKit issues by analyzing error messages, stack traces, and common problems.
Command Claude Code
Migrate Svelte/SvelteKit projects between versions, adopt new features like runes, and handle breaking changes.
Command Claude Code
Optimize Svelte/SvelteKit applications for performance, including bundle size reduction, rendering optimization, and loading performance.
Command Claude Code
Scaffold new SvelteKit projects, features, or modules with best practices and optimal project structure.
Command Claude Code
Migrate Storybook configurations and stories to newer versions, including Svelte CSF v5 and @storybook/sveltekit framework.
Command Claude Code
Mock SvelteKit modules and functionality in Storybook stories for isolated component development.
Command Claude Code
Initialize and configure Storybook for SvelteKit projects with optimal settings and structure.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: