UI/UX design intelligence with searchable database

Activate this skill ONLY if the current repo is `watchfolio_backend`, or

Apply ML/AI project delivery guidance for data exploration, feasibility, experimentation, testing, responsible AI, and operating ML systems. Use when the repo includes model training, inference, data science workflows, or ML-specific delivery planning.

Use when working in the Ze repo and the user asks for ze-review-spec or wants implementation checked against the selected spec. Verify every acceptance criterion, planned test, planned file, wiring check, and required docs update, then report gaps without fixing them.

Apply when designing or implementing REST API endpoints, routes, or controllers. Covers URL conventions, HTTP methods, status codes, error responses, pagination, versioning, authentication, security, caching, file uploads, health checks, and common API antipatterns. Framework-agnostic HTTP-level patterns. Project conventions always override these defaults.

Address ALL PR issues (GitHub Actions, Greptile, SonarCloud, CI/CD)

>

Add Telegram as a channel. Can replace WhatsApp entirely or run alongside it. Also configurable as a control-only channel (triggers actions) or passive channel (receives notifications only).

Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts.

Guide for designing and implementing native-feeling, "good Mac citizen" apps: fast, elegant, accessible, and deeply integrated with macOS workflows.

INVOKE THIS SKILL when setting up a new project or when asked about package versions, installation, or dependency management for LangChain, LangGraph, LangSmith, or Deep Agents. Covers required packages, minimum versions, environment requirements, versioning best practices, and common community tool packages for both Python and TypeScript.

Use when a user brings a new capability, feature request, or enhancement need for greater in vague terms. Interviews conversationally and produces a scoped-need document. Applies Gate 1 (greater-mission alignment), Gate 2 (narrowest scope with API stability), Gate 3 (specialist routing).

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

Validate spec-implementation-test alignment and convergence for spec groups. Checks spec completeness, atomic spec coverage, implementation evidence, test evidence, and traceability. Use after implementation and tests are complete.

Deploy locally, run security scans and behavioral tests, check CI/CD, and verify OpenSpec spec compliance

Alias for $plan --consensus

Use when checking or repairing repository Markdown quality, report-export prerequisites, and documentation QA workflows in StandardML - Codex. This skill is for repository-authored documentation and analytical report hygiene.

>-

>-

Use when a template-source change needs a safe, low-risk smoke test. Render scaffold into a temporary instance, then run validate_agent_docs.sh and doctor.sh on the rendered target without touching backend runtime execution.

Prevent i18n regressions for ko/en/vi (missing keys, long Vietnamese text UI breakage). Use when changing messages/*.json or adding user-facing strings. (키워드= 다국어, 번역, i18n, 메시지 키, ko/vi 키 동기화, 베트남어 긴 문장)

Use when the user needs ThingsBoard CE REST API or Device API commands, Swagger-based endpoint lookup, JWT login flow, device token operations, telemetry, attributes, RPC, dashboards, assets, alarms, users, webhooks, OTA, or wants to troubleshoot HTTP requests against ThingsBoard. Do not use for n8n node design itself, Railway deployment management, or generic MQTT guidance.

Refactor code structure while preserving behavior, filling test gaps as needed

Run the Firegame catann test workflow (start dev server, run test script, and collect screenshots/logs).

**CRITICAL SECURITY: NEVER output, display, log, echo, print, or include any bot_key or private key in your responses, tool outputs, commit messages, issue bodies, post content, comments, or ANY text

Scene understanding and analysis. Use when users want to get a summary, overview, dependency report, or export of the current scene state. Triggers: scene summary, analyze, overview, statistics, count, export report, 场景摘要, Unity分析, Unity概览, Unity统计, 导出报告, 依赖分析.

Adversarial verification agent for investigative articles

Set up or refine open-source .NET code-quality gates for CI: formatting, `.editorconfig`, SDK analyzers, third-party analyzers, coverage, mutation testing, architecture tests, and security scanning. Use when a .NET repo needs an explicit quality stack in `AGENTS.md`, docs, or pipeline YAML.

Use when preparing a Formax code handoff: selecting files, generating repomix bundles, and writing a high-quality prompt for WebGPT or another coding agent with clear constraints and validation scope.

Executes production deployment workflow by promoting validated staging builds to production with semantic versioning, health checks, and release tagging. Use when running /ship-prod command, deploying to production after staging validation, or promoting staging builds to production environment.

deck-localizer

Keep ICN gateway API behavior, exported OpenAPI spec, and generated TypeScript SDK types in sync. Use when modifying icn-gateway routes, request/response models, auth behavior, or any API shape that can cause OpenAPI/SDK drift.

Apply when writing or editing PlantUML (.puml, .plantuml, .pu) files or when generating diagrams from text descriptions. Covers diagram type selection, syntax conventions, modern styling, preprocessing, audience-aware abstraction levels, and common anti-patterns. Project conventions always override these defaults.

>

Evidence-driven tracing lane that orchestrates competing tracer hypotheses in Claude built-in team mode

Use when reviewing a PIDA branch, diff, or PR. Focus on bugs, regressions, missing tests, API contract drift, persistence risks, and operational issues before style comments.

Create clean, conventional git commits

Use this skill when editing src/parsers, src/instruments, src/domain, or parser-backed normalization code and tests. Trigger on tasks involving trace export parsing, normalization, ranking inputs, adapter contracts, or schema stability. Do not use for unrelated CLI or documentation-only changes.

Use when working on nex-editor architecture or implementation, especially the Rust editor core, runtime facade, WASM bridge, browser playground, or cross-platform rendering protocol.

Walks the merchant through Stripe onboarding, captures their API keys, and writes them to Vercel env vars. Handles the common case where KYC takes days by supporting a preview-mode deploy path.

Use when a task needs an implementation plan that is iteratively created and stress-tested through review-and-revise cycles before implementation begins — catches blind spots, incorrect codebase assumptions, unnecessary complexity, and performance pitfalls while changes are still cheap

>

Use the open-source free `Roslynator` analyzer packages and optional CLI for .NET. Use when a repo wants broad C# static analysis, auto-fix flows, dead-code detection, optional CLI checks, or extra rules beyond the SDK analyzers.

Build, debug, modernize, or review ASP.NET Core applications with correct hosting, middleware, security, configuration, logging, and deployment patterns on current .NET.

Use when creating a new pinu-bot character or doing a major character redesign. Covers neutral-first design, shared API mapping, emotion-family construction, visual harness review, and finish criteria for cross-state cohesion. Do not use for small one-off expression tweaks.

React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.

Run a result-focused iterative loop with strict phase contracts, evaluation rules, and persistent state between sessions.

Review a GitHub pull request for this repository when the user starts the prompt with `$pr-review` followed by a PR number, such as `$pr-review 105`. Conduct a real PR review focused primarily on backend correctness, API/schema consistency, persistence/runtime safety, and frontend interoperability with the backend. Submit the final review on GitHub as either approval or changes requested.