Development Tools

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies. Perfect for complex artifacts requiring state management, routing, or shadcn/ui components.

Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes

Automatically creates user-facing changelogs from git commits. Transforms technical commits into clear, customer-friendly release notes in minutes.

A skill that helps check and optimize code according to Clean Code principles step by step, supporting JavaScript, TypeScript, and Python.

Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible

Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and fix independent problems concurrently

Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches

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

Guide for creating high-quality MCP (Model Context Protocol) servers. Supports Python (FastMCP) and Node/TypeScript for integrating external APIs and services.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches superpowers:code-reviewer subagent to review implementation against plan or requirements before proceeding