Generates high-quality English Midjourney prompts for illustrations, strictly preserving user subjects while integrating artistic styles and professional visual details. Supports style iteration and specific formatting constraints.

Translates user input into natural, native American English, adopting an American persona. Supports strict adherence to specified grammar tenses and ensures linguistic purity without mixing source languages.

Expert guidance on SqlSugar transaction management, specifically solving partial rollback scenarios (e.g., A->B->C execution) where intermediate operations must be preserved while others are rolled back.

将英文文本准确翻译成中文，并保持逐句对照的格式输出。

Generates or converts technically accurate, audience-appropriate long-form articles optimized for Microsoft Word compatibility — including clean heading hierarchy using Chinese numbering (e.g., '一、', '（二）', '1．'), plain-text formatting (no emojis/special symbols/Markdown), paragraph-based flow, fully fleshed-out sections with concrete examples, data points, and implementation details, strict de-identification of proprietary entities, and replacement of internal engineering jargon with plain-language functional equivalents.

Add integration/E2E tests to existing codebase using Design Docs

Guides subagent coordination through implementation workflows. Use when orchestrating multiple agents, managing workflow phases, or determining autonomous execution mode.

Builds React mobile UIs with Ant Design Mobile (antd-mobile) components including Button, Form, List, Modal, Picker, Tabs, PullToRefresh, InfiniteScroll, and 50+ mobile-optimized components. Use when the user needs to create mobile-first React interfaces, implement mobile navigation, forms, or data display with Ant Design Mobile.

Generate TAAG/FIGlet-style ASCII art banners using figlet.js (FIGfont spec), with layout controls (horizontal/vertical layout, width, whitespaceBreak) and optional ANSI 256 coloring.

Design ASCII progress bars and spinners for CLI UX (determinate/indeterminate, TTY single-line refresh, non-interactive log fallback) with copy-pastable style specs. Use when the user needs terminal progress indicators, loading animations, or CLI feedback elements.

Guides PostgreSQL development including table design, indexing, constraints, PL/pgSQL, JSONB, full-text search, window functions, CTEs, EXPLAIN ANALYZE tuning, backup/restore, replication, and extensions like pgvector. Use when the user needs to write or optimize PostgreSQL queries, design schemas, or manage PostgreSQL databases.

Generates structured technical documentation including API docs (OpenAPI/Swagger), README files, user guides, developer guides, and changelogs. Use when the user needs to create or improve project documentation, generate API reference docs, write onboarding guides, or structure documentation for a codebase.

Generates unit, integration, and end-to-end tests using frameworks like pytest, Jest, JUnit, and Playwright. Use when the user needs to write tests for existing code, create test suites for a module, add edge-case coverage, or set up a testing framework from scratch.

Provides comprehensive guidance for GitHub Actions including workflow creation, CI/CD pipelines, secrets management, matrix strategies, and reusable workflows. Use when the user asks about GitHub Actions, needs to create workflows, automate processes, or configure CI/CD.

Provides comprehensive guidance for GitLab CI/CD including pipeline configuration, runners, artifacts, environments, and deployment automation. Use when the user asks about GitLab CI, needs to create pipelines, configure runners, or automate builds and deployments.

Generate API documentation by scanning Controller classes, extracting endpoint URLs, HTTP methods, parameters, and response structures, then producing standardized docs from templates. Use when the user explicitly mentions generating API documentation, creating API docs, scanning interfaces, or documenting REST APIs. Do not trigger for generic documentation requests without explicit API mention.

Set default Node versions via nvm aliases, create .nvmrc files for project-specific versions, and configure shell auto-switching per directory. Use when the user asks about nvm alias default, .nvmrc configuration, auto-switching Node versions on directory change, or pinning a Node version for a project.

Provide nvm overview, output color customization, tests, and automation examples like Ansible. Use when users ask for an nvm intro, color settings, running nvm tests, or Ansible install tasks.

Diagnose and fix nvm issues on Linux and WSL, including profile not loading, PATH errors, distro-specific differences, and Alpine compatibility problems. Use when the user reports nvm not found on Linux, nvm command not working in WSL, or distro-specific nvm issues.

Manage Node.js versions with everyday nvm commands: install specific versions, switch active versions, list installed and remote versions, and use LTS releases. Use when the user asks about nvm install, nvm use, nvm ls, listing available Node versions, or switching between Node versions.

Verify nvm installation is working correctly by checking nvm, node, and npm commands, diagnosing PATH order, and inspecting profile loading. Use when the user reports nvm command not found, wants to verify nvm is installed, or needs to diagnose why nvm is not loading in new terminal sessions.

Use **`/opsx:apply`** to implement tasks from a change. The agent reads `tasks.md`, works through tasks one by one, writes code, creates files, runs tests as needed, and checks off completed items wit

Use **`/opsx:archive`** to finalize a completed change. Archives by merging delta specs into the main `openspec/specs/` directory and moving the change folder to `openspec/changes/archive/`.

Use **`/opsx:bulk-archive`** to archive multiple completed changes at once. Validates each change, detects spec conflicts across changes, and resolves them by checking what is actually implemented.

Use **`/opsx:explore`** to think through ideas, investigate problems, compare options, and clarify requirements — all without creating any artifacts or committing to a structure. When insights crystal

Use **`/opsx:ff`** to fast-forward through all planning artifact creation at once. Creates all artifacts in dependency order (proposal -> specs -> design -> tasks) in a single pass.

Run **openspec init** to initialize OpenSpec in a project: creates the `openspec/` directory (specs, changes, config) and configures AI tool integrations (skills and slash commands). This skill assume

Install the [OpenSpec CLI](https://github.com/Fission-AI/OpenSpec) so that `openspec` is available globally. This skill covers only **installing the CLI**; it does not run `openspec init`. For project

Use **`/opsx:new`** to start a new change. This creates the change folder structure under `openspec/changes/<name>/` with metadata (`.openspec.yaml`) and prepares the first artifact for creation.

Use **`/opsx:onboard`** for a guided, interactive tutorial through the complete OpenSpec workflow. The tutorial uses the user's actual codebase — finding real improvement opportunities, creating a rea

Use **openspec schema** subcommands to create and manage custom workflow schemas. Schemas define what artifacts exist and their dependencies. The default `spec-driven` schema provides proposal -> spec

Use **`/opsx:sync`** to merge delta specs from a change into the main `openspec/specs/` directory without archiving the change. The change remains active after sync. This is optional — **openspec-arch

Run **openspec update** to regenerate AI tool configuration files (skills, commands, rules) after upgrading the OpenSpec CLI package. This ensures your project uses the latest slash commands and skill

Use **`/opsx:verify`** to validate that the implementation matches the change artifacts. Checks three dimensions — completeness, correctness, and coherence — and reports issues categorized as CRITICAL

Provides comprehensive guidance for React Native development including components, navigation, native modules, platform-specific code, and mobile app development. Use when the user asks about React Native, needs to create mobile applications, implement React Native components, or work with React Native features.

Perform a read-only cross-artifact consistency analysis across spec.md, plan.md, and tasks.md, detecting duplications, ambiguities, coverage gaps, and constitution violations with severity ratings. Use when the user has all three artifacts and needs a quality check before implementation, or wants to identify inconsistencies across specifications.

Generate a technology-agnostic feature specification by analyzing existing source code, extracting user stories, functional requirements, and acceptance criteria from code patterns. Use when the user needs to document an existing or legacy codebase, create a spec before refactoring, or reverse-engineer requirements from source files.

Run **specify check** to verify that the Spec Kit CLI and required tools (git, AI agents, editors) are installed and detectable. Use this after **speckit-install** or **speckit-initial** to confirm th

Generate a requirements-quality checklist ('unit tests for English') that validates completeness, clarity, consistency, and measurability of spec/plan/tasks artifacts. Use when the user needs a quality gate before implementation, wants to audit requirement coverage, or needs domain-specific checklists (UX, API, security, performance).

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Create or update the project constitution at .specify/memory/constitution.md by collecting governance principles, filling template placeholders, versioning with semver, and propagating changes to dependent templates and agent config files. Use when setting up initial project governance, amending principles, or syncing constitution changes across spec/plan/tasks templates.

Execute the implementation plan by processing tasks from tasks.md phase-by-phase, following TDD order, respecting task dependencies and parallel markers, setting up ignore files, and marking completed tasks. Use when the plan and tasks are ready and the user wants to begin coding, or when resuming implementation after a pause.

Run **specify init** to initialize a Spec Kit project: pull `.specify/` (memory, scripts, templates, specs) and register `/speckit.*` slash commands with the chosen AI Agent. This skill assumes the Sp

Install the [Specify CLI](https://github.com/github/spec-kit) so that `specify` is available in PATH (or use one-time `uvx`). This skill covers only **installing the CLI**; it does not run `specify in

Generate a technical implementation plan from a feature spec by filling the plan template, resolving unknowns via research, producing data-model.md, API contracts, and quickstart.md artifacts. Use when the feature spec is ready and the user needs architecture decisions, data models, API schemas, or a structured plan before task generation.

Create or update a feature specification from a natural language description by generating a branch, filling the spec template with user stories, functional requirements, success criteria, and running quality validation. Use when the user provides a feature idea and needs a structured, technology-agnostic spec ready for planning.

Generate a dependency-ordered tasks.md organized by user story, with phased execution (Setup, Foundational, User Stories, Polish), parallel markers, and strict checklist format (checkbox, TaskID, Story label, file path). Use when the implementation plan is ready and the user needs an executable task breakdown before coding.

Convert tasks.md entries into GitHub issues in the matching remote repository using gh issue create, preserving task IDs for traceability. Use when the user wants to create GitHub issues from an existing tasks.md, needs issue tracking for implementation tasks, or wants to sync task progress with GitHub project boards.

Provides comprehensive guidance for Spring Data JPA including repositories, entity management, query methods, and database operations. Use when the user asks about Spring Data JPA, needs to work with JPA repositories, implement data access layers, or configure JPA in Spring.

Factory skill for creating new Stitch Scenario Skills with the Design First, Execute Last SOP. Use when you need to add a new domain (e.g. Music Apps, Social Networks, Login Pages) to the Stitch ecosystem. Generates SKILL.md templates, directory structure, and examples via automated script or manual workflow.