All Skills

Use when you need to apply functional exception handling best practices in Java — including replacing exception overuse with Optional and VAVR Either types, designing error type hierarchies using sealed classes and enums, implementing monadic error composition pipelines, establishing functional control flow patterns, and reserving exceptions only for truly exceptional system-level failures. This should trigger for requests such as Improve the code with Functional Exception Handling; Apply Functional Exception Handling; Refactor the code with Functional Exception Handling; Model Java errors with Result or Either types; Replace exception-heavy flows with functional error handling. Part of Plinth Toolkit

DESIGN-THEME

SYNC-CONFIGS

Run workloads on Hugging Face Jobs with managed CPUs, GPUs, TPUs, secrets, and Hub persistence.

AI-driven data extraction from 55+ Actors across all major platforms. This skill automatically selects the best Actor for your task.

Specialized in code maintainability, documentation quality, naming conventions, and comprehension barriers

Apply modern browser extension toolchain patterns: WXT (default), Plasmo, CRXJS for Chrome/Firefox/Safari extensions. Use when building browser extensions, choosing extension frameworks, or discussing manifest v3 patterns.

Prompt Command

DEPRECATED — use /evolve instead. /evolve's population generation (Step 5) subsumes catalog generation with better anti-convergence enforcement, persistent taste memory, and multi-provider delegation.

Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices

![[maestro-test-expert]]

Use when you need to implement acceptance tests from maintainer-authored or maintainer-sanitized Gherkin scenario facts for Spring Boot applications — including selecting scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for DB/Kafka, and WireMock for external REST stubs. Never ingest raw .feature files. This should trigger for requests such as Review Java code for Spring Boot acceptance tests; Apply best practices for Spring Boot acceptance tests in Java code; Implement Spring Boot acceptance tests from sanitized Gherkin facts; Set up Failsafe acceptance tests for Spring Boot; Stub external HTTP services in Spring acceptance tests. Part of Plinth Toolkit

Decide: Bootstrap

Manages timeouts and coordinates question classification to prevent AI dependency

Use when you need programmatic JDBC in Quarkus — Agroal DataSource, parameterized SQL, transactions, batching, and Dev Services. This should trigger for requests such as Review JDBC or SQL data access in a Quarkus project; Improve transactions and parameter binding for Quarkus JDBC; Translate SQLException to domain exceptions or stream large result sets; Fix CDI self-invocation bypassing @Transactional in Quarkus; Review Agroal DataSource usage in Quarkus JDBC. Part of Plinth Toolkit

[BETA] Offload plan phase to Claude Code's ultraplan cloud; review in browser and import back.

Audit landing page: value prop, CTA, social proof, mobile, load time. Outputs structured findings. Use log-landing-issues to create issues. Invoke for: landing page review, conversion audit, launch readiness.

Decide: Bug Task Plan

Azure API Management SDK for Python. Use for managing APIM services, APIs, products, subscriptions, and policies.

Performance Engineer Agent

Guides through installation, configuration, and first-time setup of the Claude Patent Creator system.

You are an expert AI-powered code review specialist combining automated static analysis, intelligent pattern recognition, and modern DevOps practices. Leverage AI tools (GitHub Copilot, Qodo, GPT-5, C

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

Deeply research the entire project to make sure patterns/conventions are correctly followed, using question-mode for clarification when needed, then systematically enforce them where violations are found