- Webapp TestingToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.JetBrains/skills249
- Webgpu Threejs TslComprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or GPU compute in Three.js.JetBrains/skills249
- YeetUse only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).JetBrains/skills249
- Ai TellsReviews any draft for AI writing tells and produces a clean rewrite. Catches structural fingerprints (negative parallelism like "It's not X, it's Y", bullet-everything, Title Case headings, adjective triads), analysis fingerprints (superficial -ing clauses, passive voice, vague attribution, hedge stacking), and tone fingerprints (throat-clearing, closing phrases like "In conclusion"). Use this skill whenever the user asks to humanize, de-AI, edit, polish, or sanity-check writing, including phrasJetBrains/youtrackdb145
- Analyze ChangesAnalyze git changes (branch, commit, or current branch) and produce a design-oriented markup document with Mermaid diagrams, query/usage examples, data walkthroughs, PR context, and impact assessment.JetBrains/youtrackdb145
- Code ReviewReview code, test, and workflow-machinery changes across multiple dimensions using specialized agents with triage-based selection.JetBrains/youtrackdb145
- Create PlanResearch the codebase and create an implementation plan with architecture notes, design document, and track decomposition. Use when starting a new feature or large change.JetBrains/youtrackdb145
- Create PresentationGenerate a PPTX presentation explaining code changes on the current branch, with matplotlib diagrams and dark theme slides.JetBrains/youtrackdb145
- Edit DesignApply an edit to `design.md` or `design-mechanics.md` through the mutation discipline: apply → auto-review → iterate → present. Use this instead of directly Editing those files.JetBrains/youtrackdb145
- Execute TracksExecute the implementation plan: autonomous plan review (Phase 2) on first invocation, then track-by-track execution (Phase A review + decomposition, Phase B implementation, Phase C code review). Use after /create-plan to implement the planned work.JetBrains/youtrackdb145
- Fix Ci FailureDiagnose and fix a CI test failure from a GitHub PR or workflow run. Includes root cause analysis, dimensional code review, and PR creation.JetBrains/youtrackdb145
- Migrate WorkflowMigrate a branch's docs/adr/<dir>/_workflow/** artifacts by replaying workflow-format commits from the per-artifact stamp base through HEAD. Resumable across /clear. TRIGGER: branch has stale _workflow/ after a workflow-format change on develop. SKIP: branches with no _workflow/.JetBrains/youtrackdb145
- Profile Jmh RegressionsProfile JMH benchmark regressions using async-profiler on a Hetzner CCX33 server. Reads regressions from a PR benchmark comment, profiles both HEAD and BASE with collapsed-stack output, compares self-time and inclusive-time per method, and identifies root causes. Use when the user asks to profile regressions after a benchmark comparison run.JetBrains/youtrackdb145
- Profile Query BottleneckProfile and diagnose YouTrackDB SQL/MATCH query bottlenecks. Accepts one or more LDBC query names (e.g., IC5, IS7, IC1,IC10). Combines async-profiler flame graphs, step-by-step selectivity measurement, and fan-out analysis on a Hetzner CCX33 server against the LDBC SF 1 dataset.JetBrains/youtrackdb145
- Readability FeedbackAudit a finished design document for hard-to-read or hard-to-understand paragraphs, then harden the house-style rules so future design docs avoid them. Fans out audit sub-agents, classifies each obscure passage as caught-by-an-existing-rule or a gap, and proposes plus (on approval) applies rule changes across the style docs. Use when the user wants to feed a design doc back into the style guide, find obscure paragraphs and fix the rules, harden the writing rules from a real DD, or close the readJetBrains/youtrackdb145
- Review DocsReview documentation files for grammar, factual accuracy, and query correctness. Use when the user asks to review docs, validate documentation, or check YQL examples. Accepts a path to a file or directory as argument.JetBrains/youtrackdb145
- Review PlanManually re-run the autonomous plan review (Phase 2 — consistency + structural). The same review runs automatically as the first phase of /execute-tracks; this command is for re-runs after inline replanning or whenever the plan needs explicit re-validation. TRIGGER when: user asks to re-validate the plan after inline replanning; user requests explicit plan review outside /execute-tracks. SKIP: /execute-tracks already running State 0 in this session (autonomous Phase 2 path will fire) — do not doJetBrains/youtrackdb145
- Review Workflow PrReview a workflow-style PR's design, plan, and track files in research-mode Q&A; auto-records observations and submits a line-anchored review via gh api. TRIGGER when: user asks to review a workflow PR or run /review-workflow-pr. SKIP: non-workflow PRs without docs/adr/<dir>/_workflow/.JetBrains/youtrackdb145
- Run Jmh Benchmarks HetznerProvision a Hetzner CCX33 server, deploy the project, run JMH benchmarks, collect results, and destroy the server. Use ONLY when the user explicitly asks to run JMH benchmarks on a Hetzner server. Do NOT trigger for general benchmark requests or local benchmark runs.JetBrains/youtrackdb145
- Migrate To TeamcityMigrating CI/CD pipelines to TeamCity. Use when the user wants to migrate, convert, or switch to TeamCity from GitHub Actions (.github/workflows/) or Bamboo (bamboo-specs/*.yml), even if they only say "move our CI". Other CI systems (GitLab, Jenkins, CircleCI, Azure DevOps, Travis, Bitbucket) are not supported yet.JetBrains/teamcity-cli110
- Teamcity CliUse when working with TeamCity CI/CD or when a user provides a TeamCity build URL — drives the `teamcity` CLI for builds, logs, jobs, queues, agents, pools, projects, and pipelines.JetBrains/teamcity-cli110
- Update Test Sbt VersionsUpdates the latest sbt test versions. Use when the user asks "update the latest sbt versions".JetBrains/sbt-structure76
- Php Code ReviewReview PHP code using PhpStorm inspections. Use when editing PHP files, reviewing code quality, fixing PHP issues, or when asked about PHP best practices.JetBrains/phpstorm-claude-marketplace29
- Php Project GuideFoundational PHP project knowledge for AI agents. Use when working on a PHP project, setting up a PHP development environment, understanding PHP project structure, following PHP coding standards, running PHP tests, using Composer, or when guidance on PHP-specific tools and workflows in PhpStorm is needed.JetBrains/phpstorm-claude-marketplace29
- Upgrade PhpPHP Upgrade Assistant. Use when upgrading PHP version, fixing deprecations for a target PHP version, or scanning for PHP compatibility issues.JetBrains/phpstorm-claude-marketplace29
- AndroidSenior Android engineer workflows — Kotlin-first (Java legacy supported), Jetpack Compose + View system, MVVM, Coroutines/Flow, Room, Retrofit, Hilt, plus device orchestration via plugin tools (device management, logcat, crash reports, app run) and mobile-mcp for UI interaction (element tree, taps, swipes). Use when implementing features, debugging crashes, fixing builds, writing tests, reviewing Android code, or running QA on an emulator.JetBrains/junie-extensions16
- Context7Up-to-date library and framework documentation via Context7 MCP. Use when setup, API, or version-specific questions require current documentation.JetBrains/junie-extensions16
- Java EngineerJava 17–25 policy and pitfalls. Use when writing, reviewing, or refactoring Java code — enforces idioms around records, sealed types, switch exhaustiveness, Optional, virtual threads, and null-safety that LLMs frequently get wrong.JetBrains/junie-extensions16
- Kotlin EngineerKotlin 2.x policy and pitfalls. Use when writing, reviewing, or refactoring Kotlin code — enforces coroutine-safety, Flow correctness, null-safety, and API-design rules that LLMs frequently get wrong.JetBrains/junie-extensions16
- Laravel EngineerUse when working on Laravel projects. Covers architecture decisions (Services vs Actions), thin controllers, Form Requests, API Resources, and API versioning. Enforces Larastan verification after code generation.JetBrains/junie-extensions16
- Php EngineerModern PHP 8.x policy and pitfalls. Use when writing, reviewing, or refactoring PHP code — enforces strict types, enum/readonly/match/DNF policy, PHPStan discipline, and catches the subtle traps (type coercion, mixed abuse, readonly mutation through references, enum serialization, fiber lifecycle, PDO emulation) that LLMs get wrong by default.JetBrains/junie-extensions16
- Redis Best PracticesRedis policy & pitfalls — key naming, atomicity, TTL strategy, distributed locks, cache patterns, production traps. Use when designing Redis-backed caches, locks, queues, rate limiters, or sessions. Covers the traps LLMs get wrong by default: SETNX + EX (deprecated), KEYS on production, Pub/Sub no-persistence, HGETALL on big hashes, maxmemory-policy defaults, cluster hash tags, RDB fork memory.JetBrains/junie-extensions16
- Spring Boot EngineerUse when building, modifying, or reviewing Spring Boot 4.x applications (Spring Framework 7, Spring Security 7, Hibernate 7, Jackson 3) in Java or Kotlin — REST controllers, Spring Data JPA repositories, OAuth2 / JWT, WebFlux reactive endpoints, Kafka / event-driven code, Resilience4j, Spring Cloud, or Spring Boot tests. Covers common pitfalls that break in production: @Transactional self-invocation, N+1 queries, Kotlin + JPA plugins, blocking calls inside WebFlux. Migrating from Boot 3.x? See SJetBrains/junie-extensions16
- Sql PatternsSQL policy & pitfalls — query correctness, indexing strategy, safe migrations. Use when writing SQL, diagnosing slow queries, designing schemas, or reviewing Flyway/Liquibase migrations. Covers the traps LLMs miss by default: NOT IN with NULLs, function-on-column breaking indexes, OFFSET on large tables, NOT NULL column lock, CREATE INDEX blocking writes, immutable migrations.JetBrains/junie-extensions16
- Architecture DesignCreate a system-wide architecture design document. Use when the user wants to document the overall system architecture, data flow, and design decisions for their project.JetBrains/thinkrail7
- Bug FixReactive, symptom-driven skill for bug fixes. Edits the project's thinkrail specs to capture the correct intent (or bootstraps a properly-connected spec when the area was uncovered), then suggests a follow-up session to align code to the corrected spec. Treats a bug as a spec/code discrepancy: fix the spec half here; code half is handed off.JetBrains/thinkrail7
- Cli ProgressShow and track specification-driven development progress. Displays phase progress, milestone completion, and workflow status using thinkrail_visualize. Use at the beginning of any phase or to check overall progress.JetBrains/thinkrail7
- Goal And RequirementsDefine goal and requirements for a feature, improvement, or change in an existing project. Analyzes the existing codebase first, then helps scope and document what needs to be built. Use when code already exists.JetBrains/thinkrail7
- Investigate ProjectRead an existing codebase and produce a technical DESIGN_DOC.md plus a draft GOAL&REQUIREMENTS.md from what the code reveals. Use for the existing-project onboarding flow when the user has code but no specs yet.JetBrains/thinkrail7
- Module DesignCreate a detailed module-level design specification (README.md for a major component). Use when the user wants to document a specific module's architecture, interfaces, and design.JetBrains/thinkrail7
- New ProjectStart a brand-new project from scratch. Defines vision, MVP scope, success criteria, and technology through a focused conversation. Creates GOAL&REQUIREMENTS.md. Use when the project folder is empty and you have an idea to explore.JetBrains/thinkrail7
- Spec From CodeReverse-engineer specifications from existing code. Analyzes directory structure, public APIs, data flow, and generates spec skeletons. Use when adding specs to an existing codebase.JetBrains/thinkrail7
- Spec InitInitialize a project for specification-driven development. Creates directory structure, registry, CLAUDE.md, and skeleton specifications. Use at the start of any new or existing project.JetBrains/thinkrail7
- Spec LintValidate specification structure, links, completeness, and consistency. Use to check that specs follow templates and are internally consistent.JetBrains/thinkrail7
- Spec NextSuggest what to specify next based on current coverage, dependencies, and priority. Use when you're unsure what specification to create next.JetBrains/thinkrail7
- Spec ReviewReview and validate existing specifications against code. Use when the user wants to check if their specifications are accurate, complete, and follow best practices.JetBrains/thinkrail7
- Spec StatusShow specification coverage, health, and gaps for the current project. Use to check which modules have specs, which are stale, and what needs attention.JetBrains/thinkrail7
- Submodule DesignCreate a design specification for a sub-component within a module. Use for documenting specific algorithms, sub-systems, or focused components.JetBrains/thinkrail7
- Task SpecCreate an actionable task specification for a bug fix, feature implementation, or improvement. Use when the user wants to document a specific piece of work to be done.JetBrains/thinkrail7
- Thinkrail BrainstormYou MUST ALWAYS use this skill for any task that involves creativity or design work, such as brainstorming ideas, designing or developing features, adding to or extending functionality, as well as any refactoring or behavioural changes.You MUST elicit and articulate the user’s intent, constraints, requirements, and design decisions, and produce a well-structured specification and design document prior to any implementation (including any changes to source code).JetBrains/thinkrail7
- Ticket Amend SpecsUse when a ticket is in the `technical-design` state and the project specs under `{{TR_DIR}}/design_docs/*.md` need amending to reflect what the technical-design says. Symptoms: technical-design.md introduces concepts absent from existing specs, contradicts the current architecture, or adds new modules/submodules.JetBrains/thinkrail7
- Ticket ImplementOrchestrate execution of a meta-ticket's implementation plan. Reads the plan, proposes steps for execution, and tracks progress. Use when a ticket is in the `implementation-plan` state.JetBrains/thinkrail7
- Ticket Implementation PlanCreate an implementation plan for a meta-ticket. Reads product-design.md + technical-design.md and the (now-amended) project specs, breaks the work into ordered steps. On entry the previously-approved spec-diff.patch is applied to project specs. Use when a ticket is in the `spec-diff` state.JetBrains/thinkrail7
- Ticket OrchestratorDrive a ticket's whole stage pipeline. Bootstraps the stage DAG from the request, launches each stage as an interactive session, adjusts the plan on the fly, and runs the implementation stage. Use as a ticket's long-lived orchestrator from creation.JetBrains/thinkrail7
- Ticket Product DesignProduce the product-design.md artifact for a ticket. Asks product clarifying questions (purpose, user stories, value, product/feature success criteria, user scenarios, essence and product outcomes of the feature, feature delivery), presents the design section by section, writes the file, and updates the ticket body with a brief blurb. Use when a ticket is in the `idea` state.JetBrains/thinkrail7
- Ticket Technical DesignProduce the technical-design.md artifact for a meta-ticket. Reads product-design.md, asks technical clarifying questions, proposes 3-5 architectural approaches with trade-offs, presents the technical design section by section, self-reviews across both designs, writes the file. Use when a ticket is in the `product-design` state.JetBrains/thinkrail7
- VisualizationUtility skill for generating rich visualizations using the thinkrail_visualize MCP tool. Provides patterns for progress trackers, summary boxes, comparisons, data tables, status lists, and diagrams. Other skills reference this for consistent visual output.JetBrains/thinkrail7
- Blast RadiusExperimental jbcontext org-wide blast-radius analysis across multiple repositories. Use when Codex needs to estimate the impact of changing an API, endpoint, schema, event, shared library, config, feature flag, data model, behavior, or dependency by finding producers, consumers, owners, tests, and related repos.JetBrains/context4
- Context InstallInstall jbcontext and complete first-time setup — login and configure agent integration. Use when `jbcontext` is not found or the user asks to install jbcontext.JetBrains/context4
- Context ResearchResearch and understand unfamiliar codebases using semantic search with `jbcontext search`JetBrains/context4