Refresh hackathon submission materials for this repo whenever features, docs, or product positioning change. Use when the user asks to update submission content, rewrite judging criteria answers, regenerate the latest product summary, or prepare current demo/pitch artifacts from the codebase state.

Use when refreshing RemDo dependencies. Run the workspace dependency refresh script, fix only straightforward fallout, then review CI warnings, tooling freshness, and notable release notes for simplification opportunities.

Analyze, trim, and optimize project dependencies

Structured code review checklist for torch_sipu changes. Use when reviewing code, a PR, a diff, or auditing operator implementation.

Manage GitHub Project v2 issue states, workpad comments, and related follow-up actions.

Use when the user asks to design, review, or debug authentication and onboarding flows for Finny, especially React Native + Supabase auth session handling and Plaid-linked account setup.

Apply SOLID, SRP, cohesion, composition-over-inheritance, and small-file discipline to code changes. Use when refactoring large files or classes, setting maintainability limits in `AGENTS.md`, documenting justified exceptions, or reviewing design quality.

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

Migrate codebase from try/catch or Promise-based error handling to better-result. Use when adopting Result types, converting thrown exceptions to typed errors, or refactoring existing error handling to railway-oriented programming.

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)

>

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

You are reviewing Go code in the VMARBLE Warehouse Management Service (modular monolith).

- Ensure the PR is conflict-free with `develop`.

Project delivery skills: planning, risk management, dependency tracking, communication. Use when: planning releases, managing risks, coordinating teams.

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

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

When a problem is found outside the current task scope, classify and act. Enforces strict triage rules: only direct regressions stay in the branch; everything else becomes a filed issue with full context, proper size split, and milestone set to match the current PR.

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.

Audit and clean unused files, dependencies, and manifest issues with Knip in this repository. Use when running `pnpm lint:knip` or `pnpm lint:knip:strict`, triaging findings, fixing real hygiene issues, or deciding whether a Knip finding should become a targeted ignore in `.knip.jsonc`.

Use when generating DB integration tests (*IT) for infra mapper/store semantics with Flyway + Testcontainers Postgres.

>

>

[OMX] Run a comprehensive security review on code

Review source files changed during a phase for bugs, security issues, and code quality problems

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.

Validates contract JSON Schemas and fixtures, fails fast on breaking format issues.

Expert application security engineer specializing in threat modeling, vulnerability assessment, secure code review, and security architecture design for modern web and cloud-native applications. Use when Codex needs this specialist perspective, workflow, or review style for related tasks in the current project.

Use when improving the Chokobot admin operational flow, especially dashboard usability, process tracking, handoff clarity, table-to-detail journeys, action priority, and operator-facing workflow design in the modern Next.js admin.

Use when auditing or repairing a specific podcast with recurring transcript quality issues such as inconsistent speaker labels, generic guest names, language mismatches, duplicate translations, or episodes that need source recovery before repolish.

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).

Use when writing or updating mobile-first Playwright coverage for the badminton H5 flow, including home CTA, upload readiness, candidate clip selection, processing progress, report rendering, history, compare, and error recovery.

Adversarial verification agent for investigative articles

Profile application performance, identify bottlenecks, design optimization strategies, implement changes, benchmark improvements, and review code quality.

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.

Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.

读取当前项目的 PR 审查结果，自动修复中等和严重问题，轻微问题需确认后再决定是否修复

Use when working in the Ze repo and the user asks for ze-review or for a focused review of current changes. Read the changed files and their intent, inspect edge cases, security risks, and missing tests, and report findings without fixing anything.

Work on the .NET solution for SphereIntegrationHub. Use this when editing services, components, JSON data, or tests.

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.

Review recently changed files for code reuse, quality, and efficiency issues, then fix them. Use when implementation is already complete and you want a final cleanup pass that mirrors Claude Code's `/simplify` behavior as closely as Codex can, without overriding Claude's native `/simplify`.

>