Health & Fitness

Redesign React components and pages for healthcare SaaS with premium Apple/Uber-like aesthetics while preserving ALL existing logic, hooks, state management, API calls, and event handlers. Use this skill when the user requests to redesign, make premium, improve the look of, or beautify existing React code. Also use when the user provides design inspiration screenshots to adapt. The skill treats all functionality as sacred and focuses purely on visual transformation - layout, styling, typography, colors, spacing, and modern component structures can change freely, but hooks order, state management, backend communication, and all interactions must remain 100% intact.

Staging and production deployment using Laravel Deployer with health checks, cache management, and rollback support (HUMAN-ONLY execution)

Automated Next.js build management - runs builds, analyzes errors/warnings, and automatically fixes issues iteratively until build succeeds or encounters unfixable errors. Use when running builds, fixing build errors, or validating build health. Standalone skill with no external integrations.

Monitor database health and detect issues across environments

Manage and develop AI agents using kubani-dev CLI. Use for checking agent health, versions, deployment status, running tests, and evaluations.

Build and provision Ollama models from Modelfiles, verify health, and hot-swap personas. Use to translate Modelfile text into runnable models.

Production observability with tracing, OpenTelemetry, and Prometheus metrics including structured logging, instrumented functions, distributed tracing, health checks, and request correlation. Use when adding logging, metrics, tracing, or health endpoints to Rust services.

Diagnose and fix claude-mem installation issues. Checks PM2 worker status, database integrity, service health, dependencies, and provides automated fixes for common problems.

Comprehensive project status evaluation using hive-mind coordination, GOAP planning, neural analysis, and AgentDB memory. Use when assessing architecture health, planning refactoring, or generating status reports.

Track performance benchmarks and detect regressions exceeding 10% threshold. Analyze historical trends and alert on degradation. Calculate regression score (0.00-1.00) for performance health. Integrate with Serena for continuous monitoring. Use when: monitoring performance, detecting regressions, analyzing performance trends, optimizing slow components, validating performance fixes.

Run local system diagnostics and model benchmarks across CPU, memory, GPU, NPU, Docker, and Kubernetes; use when asked to benchmark, health-check, or collect environment diagnostics, and store a summary in memory.

Runs this project's full suite of validation and health checks. Use when 'something is wrong' or for a general checkup.

Production monitoring, observability, SLO/SLI management, and incident response. Trigger terms: monitoring, observability, SRE, site reliability, alerting, incident response, SLO, SLI, error budget, Prometheus, Grafana, Datadog, New Relic, ELK stack, logs, metrics, traces, on-call, production monitoring, health checks, uptime, availability, dashboards, post-mortem, incident management, runbook. Completes SDD Stage 8 (Monitoring) with comprehensive production observability: - SLI/SLO definitions and tracking - Monitoring stack setup (Prometheus, Grafana, ELK, Datadog, etc.) - Alert rules and notification channels - Incident response runbooks - Observability dashboards (logs, metrics, traces) - Post-mortem templates and analysis - Health check endpoints - Error budget tracking Use when: user needs production monitoring, observability platform, alerting, SLOs, incident response, or post-deployment health tracking.

Verify that each plugin has a CHANGELOG.md with an entry for the current version from plugin.json. Use when (1) before creating a pull request or release to ensure version history is documented, (2) after bumping version numbers with bump-version, (3) when asked to verify project health or release readiness, (4) during release preparation to confirm all changes are documented, (5) as part of comprehensive validation alongside check-versions and check-skill-counts, (6) when onboarding a new plugin to ensure proper version documentation.

Verify architecture health including layer violations, circular dependencies, package structure, and design pattern compliance

This skill should be used when the user asks to "validate requirements", "review requirements quality", "check requirements completeness", "verify traceability", "check INVEST compliance", "validate user stories", "requirements health check", "quality gate check", or when running /re:review validation.

Railway deployment, CI/CD workflows, GitHub Actions, and smoke tests.Handles Railway configuration, GitHub Actions workflows, deployment automation, and health checks.Use when working with deployment, CI configuration, Railway setup, or infrastructure automation,or when user mentions Railway environments, GitHub Actions, deployment issues, CI failures,"Build failed" errors, smoke test errors, CI/CD pipelines, Docker configuration, or devops workflows.

Create health check endpoints for Kubernetes, Docker, monitoring. Check database, Redis, external APIs. Liveness and readiness probes. Keywords - health check, liveness probe, readiness probe, kubernetes health, monitoring, healthz, docker healthcheck

Manages founder business portfolio, signals, vault, and snapshots. Tracks business health, stores credentials securely, and generates AI-powered business analytics and recommendations.

Verify version consistency across plugin.json and marketplace.json for all plugins. Use when (1) before creating a pull request or release to ensure metadata consistency, (2) after manually editing version numbers in either plugin.json or marketplace.json, (3) repository health verification or preflight checks are requested, (4) after using bump-version to confirm both files were updated correctly, (5) during debugging if plugins aren't appearing correctly in the marketplace, (6) as part of comprehensive validation alongside check-skill-counts and check-changelogs.