hydraia plugin

• /hydraia:agile<the epic-sized idea or goal>

  Deliver a large or multi-stage effort through Hydraia Agile Mode — decompose into an epic, user stories, tasks, subtasks + QA, optionally sync to Jira, then autonomously execute stage by stage with tiered approval gates.

• /hydraia:architect<the idea — e.g. "a booking system for small clinics">

  Design a new app or service from scratch — guided elicitation, architecture proposals, stack choice, API contract, ADRs — then build it through the full pipeline

• /hydraia:dashboard[port]

  Launch the local Hydraia dashboard (status, usage telemetry, editable config) in the browser

• /hydraia:db<symptom or query — e.g. "orders list times out when filtering by date">

  Diagnose and fix a database bottleneck evidence-first — EXPLAIN, indexes, N+1, locks, pooling, safe migrations

• /hydraia:devops<what to set up — e.g. "GitHub Actions CI + Dockerfile">

  Author CI/CD, containers, or IaC following the repo's platform — deploy and secrets flagged for human approval, never executed

• /hydraia:docs<optional focus — e.g. "the API reference">

  Sync README, API docs, CHANGELOG, and the ADR index with the actual code — reports drift, never invents behavior

• /hydraia:doctor(no arguments)

  Validate, install, and update Hydraia's external dependencies (codegraph, markitdown, E2E browser binaries)

• /hydraia:e2e<optional focus — e.g. "the checkout journey">

  Generate and run an end-to-end suite for the critical user flows — Playwright, auto-detected, never imposed

• /hydraia:explainme<what to explain — a subsystem, path, PR, or "how does X work">

  Explain a codebase, subsystem, or PR to a human — visually and verifiably. Grounds a diagram in codegraph's real structure and delivers a self-contained interactive HTML map with guided walkthrough chapters.

• /hydraia:feature<what you want to build>

  Build a feature through the full Hydraia pipeline (analyze → plan → execute → double-review)

• /hydraia:graph<symbol, file, or question>

  Query the code graph for structure, call sites, and blast radius

• /hydraia:observability<what to instrument — e.g. "add tracing to the order service">

  Instrument logging, metrics, traces, health checks, and alerts — OpenTelemetry-first, never logging secrets or PII

• /hydraia:perf<symptom — e.g. "checkout endpoint p95 went from 200ms to 900ms">

  Diagnose and fix a performance problem measurement-first — baseline, profile, numeric target, implement, re-measure

• /hydraia:plan<what you want to plan>

  Run only Hydraia analysis + spec + detailed plan (with self-review loop), then stop

• /hydraia:resume[optional run-log name; defaults to the most recent]

  Resume an interrupted Hydraia pipeline from the last incomplete phase

• /hydraia:review[optional focus, e.g. "the payin module"]

  Run only the Hydraia double code-review + security gate on the current branch

• /hydraia:story<user story, ticket text, or path to a file/PDF>

  Analyze a user story like a Product Owner, then produce spec + QA cases + a frozen plan — no code

• @agent-hydraia:angular-reviewersonnet

  Expert Angular code reviewer specializing in change detection, RxJS/subscription hygiene, signals, standalone components, dependency injection, and template security. Use for any change touching Angular components, services, or templates. MUST BE USED for Angular projects.

• @agent-hydraia:architectsonnet

  Software architecture specialist for system design, scalability, and technical decision-making. Use PROACTIVELY when planning new features, refactoring large systems, or making architectural decisions.

• @agent-hydraia:code-architectsonnet

  Designs feature architectures by analyzing existing codebase patterns and conventions, then providing implementation blueprints with concrete files, interfaces, data flow, and build order.

• @agent-hydraia:code-reviewersonnet

  Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.

• @agent-hydraia:csharp-reviewersonnet

  Expert C# code reviewer specializing in .NET conventions, async patterns, security, nullable reference types, and performance. Use for all C# code changes. MUST BE USED for C# projects.

• @agent-hydraia:database-reviewersonnet

  PostgreSQL database specialist for query optimization, schema design, security, and performance. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance. Incorporates Supabase best practices.

• @agent-hydraia:db-performance-tunersonnet

  Database bottleneck specialist for the Hydraia pipeline. Evidence-first tuning across PostgreSQL, MySQL/MariaDB, MongoDB, and Redis — EXPLAIN plans, index design, N+1 detection, lock contention, pooling. Dispatched by the perf/DB route at design time. Read-only; proposes changes as plan tasks. NOT a

• @agent-hydraia:devops-engineersonnet

  DevOps specialist for the Hydraia pipeline. Authors CI/CD workflows, Dockerfiles/compose, and IaC following the repo's existing platform. Deploy steps, secrets, and destructive infra are written as human-approval plan tasks — never executed by the agent. Opt-in via /hydraia:devops.

• @agent-hydraia:docs-engineersonnet

  Documentation specialist for the Hydraia pipeline. Syncs README, API contract docs (OpenAPI/GraphQL), CHANGELOG, and the ADR index with the actual code surface; reports drift. Runs in Phase 6 (updates, never blocks) and on demand via /hydraia:docs. Never invents API behavior.

• @agent-hydraia:e2e-runnersonnet

  End-to-end testing specialist for the Hydraia pipeline. Detects the repo's E2E framework (Playwright/Cypress) from evidence, derives critical user journeys from acceptance criteria, writes and runs them, quarantines flaky specs. Phase 6 gate — a failing critical flow means the run is not done. Never

• @agent-hydraia:explainmesonnet

  Visual code-explanation specialist for the Hydraia pipeline. Grounds a diagram in codegraph's verified structure, authors the typed IR, and drives the explainme (vendored Archify) CLI's validate→deliver loop to produce a self-contained interactive HTML map with guided walkthrough chapters. Dispatche

• @agent-hydraia:go-reviewersonnet

  Expert Go code reviewer specializing in idiomatic Go, error handling, concurrency (goroutines/channels/context), interface design, and performance. Use for all Go code changes. MUST BE USED for Go projects.

• @agent-hydraia:hydraia-executorsonnet

  Executes a single task from a Hydraia implementation plan. Dispatched fresh per task during Phase 4. Writes code, tests it, commits. Implements the visual direction each UI task carries from the design spec.

• @agent-hydraia:hydraia-revieweropus

  Whole-branch code reviewer for Hydraia Phase 5 — the judge. Reviews spec compliance, correctness, quality, and hidden coupling, with evidence for every claim. Runs on Opus (one of the only two Opus agents).

• @agent-hydraia:java-reviewersonnet

  Expert Java code reviewer for Spring Boot and Quarkus projects. Automatically detects the framework and applies the appropriate review rules. Covers layered architecture, JPA/Panache, MongoDB, security, and concurrency. MUST BE USED for all Java code changes.

• @agent-hydraia:perf-engineersonnet

  Performance diagnosis specialist for the Hydraia pipeline. Measurement-first — establishes a baseline, profiles, ranks bottlenecks by measured contribution, and proposes hypotheses with expected gains. Dispatched by the performance route at design time. Read-only; never edits source. NOT a Phase 5 r

• @agent-hydraia:performance-optimizersonnet

  Performance analysis and optimization specialist. Use PROACTIVELY for identifying bottlenecks, optimizing slow code, reducing bundle sizes, and improving runtime performance. Profiling, memory leaks, render optimization, and algorithmic improvements.

• @agent-hydraia:python-reviewersonnet

  Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.

• @agent-hydraia:qa-automationsonnet

  QA automation specialist for the Hydraia pipeline. Implements Given/When/Then cases from a QA case document as real tests in the repo's existing test framework and fills the traceability matrix with file:line refs (Phase 4). Verify mode re-checks full matrix coverage (Phase 6).

• @agent-hydraia:qa-functionalsonnet

  Functional QA specialist for the Hydraia pipeline. Derives Given/When/Then test cases and a requirement-traceability matrix from a design spec and story artifact. Dispatched during Phase 3 in parallel with plan writing. Never invents behavior — spec gaps are reported, not guessed.

• @agent-hydraia:react-reviewersonnet

  Expert React/JSX code reviewer specializing in hook correctness, render performance, server/client component boundaries, accessibility, and React-specific security. Use for any change touching .tsx/.jsx files or React component logic. MUST BE USED for React projects.

• @agent-hydraia:security-revieweropus

  Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.

• @agent-hydraia:silent-failure-huntersonnet

  Review code for silent failures, swallowed errors, bad fallbacks, and missing error propagation.

• @agent-hydraia:sre-observabilitysonnet

  Observability specialist for the Hydraia pipeline. Instruments structured logging, metrics (RED/USE), traces (OpenTelemetry), health checks, and alert rules as plan tasks. Vendor-agnostic — OTel first, vendor SDKs only if already present. Never logs secrets or PII. Opt-in via /hydraia:observability.

• @agent-hydraia:type-design-analyzersonnet

  Analyze type design for encapsulation, invariant expression, usefulness, and enforcement.

• @agent-hydraia:typescript-reviewersonnet

  Expert TypeScript/JavaScript code reviewer specializing in type safety, async correctness, Node/web security, and idiomatic patterns. Use for all TypeScript and JavaScript code changes. MUST BE USED for TypeScript/JavaScript projects.

• @agent-hydraia:vue-reviewersonnet

  Expert Vue.js code reviewer specializing in Composition API correctness, reactivity pitfalls, component architecture, template security, and Vue-specific performance. Use for any change touching .vue, .ts/.js files with Vue imports, or Vue ecosystem code (Pinia, Vue Router, Nuxt). MUST BE USED for V

• adr

  Use when a design decision is made that is expensive to reverse, affects multiple components, or rejects a plausible alternative — record it as an Architecture Decision Record under docs/hydraia/adr/. Also use to supersede an old decision. Not for trivial choices.

• agency-tier-ui

  Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.

• api-design

  No description in the file.

• banner-design

  Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with AI-generated visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage. Uses ui-ux-pro-max, frontend-design, ai-artist, ai-multimodal skills.

• brainstorming

  You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

• brand

  Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.

• caveman

  Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.

• coding-standards

  Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.

• db-optimization

  Use when the bottleneck is database-shaped — slow queries, lock timeouts, connection exhaustion, N+1 patterns, index questions, schema migrations on hot tables. Evidence-first DB playbook for PostgreSQL, MySQL/MariaDB, MongoDB, and Redis backing the db-performance-tuner agent.

• design

  Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.

• design-system

  Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.

• design-to-code

  Elite render-to-code skill. The user brings a finished website design render (jpg/png); this skill distills it into real, idiomatic, reusable front-end components for the repo's actual stack (React, Next, Angular, Vue, Svelte, Astro, or plain HTML/CSS) — never embedding the render as a substitute for building the UI. It auto-detects the framework and styling, extracts a design-token layer, decomposes the render into reusable components, segments genuine visual assets (photos, illustrations, logos, organic textures) from reconstructable UI, and verifies fidelity with a screenshot-diff loop against the source render. Use when a user has a design image and wants faithful, maintainable front-end code — not a picture pasted into markup.

• dispatching-parallel-agents

  Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

• django-security

  Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.

• dotnet-patterns

  No description in the file.

• e2e-testing

  No description in the file.

• executing-plans

  Use when you have a written implementation plan to execute in a separate session with review checkpoints

• explainme

  Explain a codebase, subsystem, or PR to a human — visually and verifiably. Turns real code structure into a polished, validated, explorable standalone HTML map (architecture, workflow, sequence, data-flow, or lifecycle/state) with inline SVG, dark/light themes, guided walkthrough chapters, source-pinned nodes, and PNG/SVG/WebM export. Use for onboarding, "how does this system work / how does this flow work", visual PR/architecture review, or converting/beautifying Mermaid. In Hydraia it is grounded in codegraph's verified structure, not a guessed topology.

• finishing-a-development-branch

  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

• golang-patterns

  Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications.

• greenfield-architect

  No description in the file.

• hydraia

  Use whenever the user asks to build, add, implement, or change a feature or functionality — or brings a user story or ticket to analyze, reports a bug or unexpected behavior, asks for a branch review, or wants a new app or service designed from scratch. Phase -1 triages the intent and routes it. Runs the complete non-negotiable development pipeline end to end — deep analysis and planning, sub-agent execution, and a double code-review loop — without asking the user which model, skill, or step to use. This is the default way features get built.

• karpathy-guidelines

  Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

• microservices-architect

  Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.

• mobile-design-frames

  Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured surfaces, image-led composition, tasteful custom iconography, and clean phone mockup framing. By default, screens should be shown inside a subtle premium iPhone or similar phone mockup with a visible frame, while the main focus stays on the app content itself. This skill generates images only. It does not write code.

• node-patterns

  No description in the file.

• performance-tuning

  No description in the file.

• production-audit

  Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service.

• python-patterns

  Pythonic idioms, PEP 8 standards, type hints, and best practices for building robust, efficient, and maintainable Python applications.

• react-patterns

  React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.

• receiving-code-review

  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

• redesign-uplift

  Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.

• repo-scan

  Cross-stack source code asset audit — classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports.

• requesting-code-review

  Use when completing tasks, implementing major features, or before merging to verify work meets requirements

• security-bounty-hunter

  Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.

• security-review

  Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.

• security-scan

  Scan your Claude Code configuration (.claude/ directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.

• slides

  Create strategic HTML presentations with Chart.js, design tokens, responsive layouts, copywriting formulas, and contextual slide strategies.

• springboot-patterns

  Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.

• springboot-security

  Spring Security best practices for authn/authz, validation, CSRF, secrets, headers, rate limiting, and dependency security in Java Spring Boot services.

+12

• PostToolUsecommand

  Bash

• PostToolUseFailurecommand

  Bash

• PreToolUsecommand

  Edit|Write|MultiEdit, Task|Agent, Bash

• SessionStartcommand

  startup|clear|compact

• Stopcommand

  No description in the file.

• SubagentStopcommand

  No description in the file.