General SOP for generating complex crossover alternate history scenarios involving sci-fi, anime, and fantasy franchises.

General SOP for common requests related to ōtsutsuki, daisaigai, from.

General SOP for common requests related to self, data, torch.

Generates a structured Standard Operating Procedure (SOP) or checklist with specific HTML formatting, context prioritization, and detailed failure handling. Applicable to general workflows, release notes, gameproxy, solidity claims, articles, philosophy, social media, wellness, health, financial domains, and DAW operations (set, scale, tcp).

Execute a univariate time series forecasting pipeline using StatsForecast and Polars. Includes ID concatenation, cross-validation, ensemble generation (AutoARIMA, AutoETS, DynamicOptimizedTheta), non-negative constraints, outlier-aware metrics, and formatted output with specific type casting for split IDs.

Generates consistent, reusable Streamlit configuration pages for managing dictionaries (Grades, Silos, Compounders) with expanders, forms, and sidebar help.

Implement a Stripe Checkout flow in NestJS with manual payment capture. Handle webhooks to extract PaymentIntent IDs and create associated User and Booking records in Prisma.

Generates sophisticated, prose-based astrological interpretations for specific Sun and Moon sign combinations, featuring a creative title and deep analysis of personality, relationships, growth, and potential challenges.

Develop a Telegram bot using python-telegram-bot 3.17 to automate the processing of local zip files. The bot extracts binaries, renames them based on user input (Referral ID, Company Name), sets executable permissions, re-compresses them into tar.gz archives, and sends them to users. It includes referral validation via JSON, user ID whitelisting for authentication, and specific command handlers.

Expands, rewrites, or summarizes theological and ethical content while strictly preserving in-text citations and maintaining a Harvard-style reference list.

Analyzes, calculates, and recommends track cycling gear ratios. Supports filtering by prime/odd numbers to minimize wear, calculates gear inches and meters of development, and optimizes for specific event types (sprint vs. endurance).

Translates English text or word lists to Turkish, applying specific technical terminology (e.g., roller/bobin) and adapting output format (natural text vs. 'English - Turkish' list) based on input structure.

Translates text into target languages (e.g., Japanese, Chinese, Korean) while adhering to specific output constraints such as romanization, linguistic registers, or emotional tones.

Generates hypothetical marketing materials, story pitches, and screenplay scenes for the alternate 'Traveller' universe, adhering to specific retro-futuristic styles, era constraints, and unique lore.

Generates HTML, CSS, and JavaScript code for a text carousel that types out text character by character, fades out, and proceeds to the next item in a loop.

Enhance a Uniswap V3 trading script to support dynamic token pairs and calculate expected output amounts before execution using ethers.js.

Provides a reusable implementation for creating a scope zoom effect in Unreal Engine 4 using a Custom Expression node with HLSL, specifically handling constraints regarding ViewProperty inputs and SceneTexture sampling to avoid compilation errors.

Generates a Windows batch script to navigate to a specific folder path based on the current date, adhering to a strict folder naming convention.

Drafts an analytic philosophy paper that challenges a specific author's view on criminal responsibility for opioid addicts, adhering to strict structural guidelines, word counts, and formal academic style while avoiding AI-detection patterns.

Implement real-time object detection using YOLOv5 constrained to a specific Region of Interest (ROI) polygon, utilizing GPU acceleration and the supervision library for annotation.

SOP for extracting evidence from offline OpenAI-format conversations, distinguishing primary user questions from secondary context, and handling specific constraints (e.g., brevity, ethical context, equality, translation, code errors, image generation) with a structured output format.

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.

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.

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.

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.