>

Verify that implemented code changes match their specification. Use after a spec has been implemented.

>

>

Remove AI-generated code slop and clean up code style

Runs tests, lint, and format checks; explains CI workflows. Use when running or debugging tests, lint, or GitHub Actions.

Creates production-ready pull requests with automatically updated AGENTS.md and project docs. Use when the user asks to create a PR, make a PR, is ready to merge, has finished a feature and wants a PR, or says they're done for the day with changes to commit.

Update the tarkov.dev GraphQL schema and regenerate the Go client code

Used to supplement the data LLMs can use when answering questions by supplying them with custom data generated and managed by llama-index.

>-

Reviews changes for security, scalability, performance, code reuse, and maintainability using a structured checklist. Use when the user asks for a code review, wants feedback on a PR, or wants to harden code quality.

Review React/Next.js components, server actions, and data-fetching logic in the ClipRace repo to prevent performance regressions by checking RSC vs client boundaries, bundle size, waterfalls, CLS, and large list rendering. Use when the user asks for a performance review of specific routes, components, or flows.

Debug issues specific to mobile applications including platform-specific problems, device constraints, and connectivity issues.

Generate structured test cases from requirements and specification documents using test model-based approach per ISO 29119-4.

Ruby Style Guide (rubystyle.guide) conventions. Use when writing, formatting, or reviewing Ruby code for layout, naming, flow of control, methods, classes, and idioms. Complements RuboCop.

Create a six-frame storyboard that shows a user's journey from problem to solution. Use when you need a fast narrative for alignment, concept reviews, or demos.

'Work with Cargo commands, workspace configuration, dependency management, and build systems. Use when managing dependencies, configuring workspaces, building projects, running tests, or publishing crates. Handles Cargo.toml configuration, workspace setup, dependency resolution, and build commands.'

Builds and optimizes DSPy (dspy) programs end-to-end: signatures, modules, compilation/optimization, evaluation, and debugging. Use when the user mentions dspy/DSPy, Signature, Module, teleprompter/optimizer, compile, evaluate, few-shot, RAG, tool use, or local LLM endpoints (Ollama/vLLM/LM Studio).

> Use this skill when creating or modifying any public-facing `page.tsx` in the clip.art project.

Use this skill for Pest PHP testing in Laravel projects only. Trigger whenever any test is being written, edited, fixed, or refactored — including fixing tests that broke after a code change, adding assertions, converting PHPUnit to Pest, adding datasets, and TDD workflows. Always activate when the user asks how to write something in Pest, mentions test files or directories (tests/Feature, tests/Unit) or architecture tests. Covers: test()/it()/expect() syntax, datasets, mocking, browser testing, arch(), Livewire component tests, RefreshDatabase, and all Pest 3 features. Do not use for editing factories, seeders, migrations, controllers, models, or non-test PHP code.

>-

Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.

>-

name: CI

Use when resolving random JIRA issues. Fixes bugs, refactors code, performs code and security reviews, ensures 100% test coverage, runs CI checks, and creates pull requests. Links PRs to JIRA issues and updates issue status.

Plans a user-provided feature idea by reading SPEC and code (read-only), analyzing scope, proposing a design aligned with existing architecture, optionally clarifying underspecified requirements with focused questions, and opening a GitHub issue that documents requirements, assumptions, design, subtasks with dependencies, and acceptance criteria—without modifying the repository. Use when the user wants a feature scoped and filed as an issue before any implementation, spec edits, or PR work.

Styling and structure conventions for stream-chat-react. Use when adding or editing components, SCSS, or icons in this repo—file layout, styling folder structure, SCSS imports, and icon placement.

E2E testing conventions for Protocol Designer and Labware Library using Playwright + pytest in e2e-testing/. Use when writing, running, or modifying end-to-end tests, page objects, or Playwright tests.

Integrate Convex static self hosting into existing apps using the latest upstream instructions from get-convex/self-hosting every time. Use when setting up upload APIs, HTTP routes, deployment scripts, migration from external hosting, or troubleshooting static deploy issues across React, Vite, Next.js, and other frontends.

Code cleanup, docs update, and git push workflow

Triage and review all open GitHub issues and PRs against project templates and contribution guidelines

Given a Sentry issue URL (direct or Slack), fetches details via MCP, analyzes root cause against the current repo code, and generates code fix suggestions. Use when the user provides a Sentry issue link or URL to investigate and fix.

Talk to Claude asynchronously about a specific task by asking it to write its response into a file, then wait for that file to appear.

Run a systematic health check over `wiki/` following the pattern in `llm-wiki.md` and the conventions in `.cursor/rules/wiki-maintainer.mdc`.

>-

Scaffold a new design system component with all required files, Ark UI integration, Storybook stories (docs/controls), optional Vitest browser tests, and barrel export wiring. Use when the user asks to create, scaffold, or add a new component.

Dedicated non-functional requirements analysis per ISO/IEC 25010 quality model covering performance, security, usability, reliability, maintainability, and portability.

Read and interpret ebookarr production logs to debug stuck jobs, pipeline failures, and service issues. Use when investigating a bug using logs, a user reports a job not completing, or when asked to check what happened to a specific request.

Single source of truth for iOS-native mobile web UX. Covers viewport units, safe areas, Dialog-to-Drawer conversion, Tabs-to-vertical-stacking, touch targets, input zoom prevention, and responsive patterns. Use when building any UI component, fixing mobile issues, reviewing responsive code, or when mobile UX is mentioned.

>-

Reviews a pull request from a PR URL by directly fetching the URL content (no `gh` dependency) and verifies compliance with CONTRIBUTING.md. Use when the user asks for a PR review, to review changes before merge, or to check contribution guidelines.

Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.

Formats or checks C/C++ and project code style using env/bin/format-all-sources.py and clang-format. Use when the user asks to format code, fix style, run format check, or when lint fails due to formatting.

Create and configure Claude Agent SDK applications with TypeScript or Python, including MCP integration, subagents, permissions, and custom tools. Use when building Claude Code agents, integrating MCP servers, or creating specialized AI agents.

All HTML generation for the rendered PDF lives in [src/template.ts](src/template.ts). Every page's appearance is a deterministic function of `buildHtml(BuildHtmlOptions)` + the loaded theme CSS in [sr

>-

Improves UI/UX in this Next.js + Tailwind app by running a structured design pass (IA, flows, accessibility, responsive, components). Use when the user asks for UI polish, UX improvements, redesign, landing page tweaks, component library work, Tailwind styling, accessibility fixes, or visual consistency.

Generates git commit messages following this repository's conventions. Analyzes staged changes and outputs properly formatted commit messages. Use when user asks to write, generate, or format a commit message.

When triggered, execute the following steps in order. Each step should be a distinct phase with a clear handoff.