Analyze and optimize React component performance issues (slow renders, re-render thrash, laggy lists, expensive computations). Use when asked to profile or improve a React component, reduce re-renders, or speed up UI updates in React apps.

Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.

Use when building or reviewing core Quarkus applications with CDI beans and scopes, SmallRye Config and profiles, lifecycle, interceptors and events, virtual threads, and test-friendly design. Part of the skills-for-java project

Guides developers through standardized pull request creation workflow: auto-detects JIRA issue key(s) from the branch name, commits any uncommitted changes with the issue key(s) in the message, generates a descriptive PR title and body from the diff, and creates the pull request to a chosen target branch. Supports one or multiple JIRA keys (e.g. MBL-1327, POS-1123) and two modes — streamlined (auto-creates PR, default) and review (shows draft before creating). USE FOR: create PR, open pull request, make PR, submit PR, raise PR, create pull request, standardize PR workflow, PR with JIRA, commit and PR, push and create PR, create PR detailed, create PR full, create PR with review. DO NOT USE FOR: general git operations, branch creation, hotfix procedures unrelated to PR creation.

Use when adding authentication (login, logout, protected routes) to Express.js web applications - integrates express-openid-connect for session-based auth.

Use when adding authentication to Next.js applications (login, logout, protected pages, middleware, server components) - supports App Router and Pages Router with @auth0/nextjs-auth0 SDK.

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).

Creates and coordinates teams of persistent AI teammates with shared task lists, messaging, and lifecycle management. Use when spawning teammates, creating a team, setting up reviewers or implementers, coordinating multi-agent work, or any skill references "kit:team-orchestration". Provides the scaffolding for TeamCreate, teammate spawning, task dependencies, SendMessage communication, and graceful shutdown.

Multi-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.

Enforces rigorous technical evaluation of code review feedback before implementation -- verifying suggestions against the codebase, pushing back when wrong, clarifying ambiguity, and avoiding performative agreement. Use when processing PR review comments, inline suggestions, change requests, reviewer feedback, or any list of code fixes to address. Applies to feedback from human partners and external reviewers alike. DO NOT TRIGGER when writing a review of someone else's code.

Removes git worktrees safely, cleans up associated branches, and pulls latest mainline after removal. Use when finished with a worktree, done with a branch, cleaning up after a merge or PR, abandoning work in a worktree, or when "git worktree list" shows stale entries. Checks for uncommitted changes, verifies no open PRs before branch deletion, and handles force-removal of locked worktrees.

Creates an isolated git worktree workspace with smart directory selection, gitignore safety verification, dependency installation, and baseline test validation. Use when starting feature work, beginning a new branch, needing workspace isolation, setting up before plan execution, or the user says "new feature", "set up a worktree", or "isolate this work". DO NOT TRIGGER for worktree cleanup or removal — use kit:worktree-cleanup instead.

Enforces strict test-driven development -- write a failing test first, implement minimal code to pass, then refactor. Use when implementing a feature, fixing a bug, adding behavior, refactoring, or any time production code will be written or changed. Also use when the user says "write tests", "add tests", "TDD", or "test first". DO NOT TRIGGER for throwaway prototypes, generated code, or config-only changes unless the user explicitly requests TDD.

Generates a categorized work summary from GitHub activity (PRs authored, issues created, code committed) for a given time period and organization, using parallel subagents for fast detail fetching. Use when the user asks "what did I work on", "what did I do last week", wants a work log, weekly update, standup notes, sprint recap, accomplishments list, performance review input, or any summary of their contributions. DO NOT TRIGGER for repository changelogs, release notes, or team-wide activity reports.

Creates detailed, bite-sized implementation plans with TDD structure, exact file paths, complete code, and test commands. Use when you have a spec, requirements, design doc, or feature request and need to plan before coding — especially for multi-step tasks, large features, or when handing off to another session. DO NOT TRIGGER when asked to write code directly or fix a simple bug.

Coordinates parallel subagent dispatch to solve multiple independent problems concurrently, with structured prompts and conflict-free integration. Use when there are 2+ independent failures, bugs, tasks, or investigations that do not share state -- e.g. multiple test files failing for different reasons, unrelated subsystems broken, or batch tasks that can run simultaneously. DO NOT TRIGGER when failures are related, require shared context, or agents would edit the same files.

Coordinates collaborative design sessions that explore requirements, analyze codebase context, and produce an approved design document with trade-offs. Use when building a new feature, adding functionality, creating components, modifying behavior, starting a project, or planning any creative work. DO NOT TRIGGER when the user already has a concrete design and just wants implementation.

Load this skill when a user wants to migrate, convert, port, translate, or move an AWS CDK application (including CDK stacks, constructs, or CloudFormation-synthesized templates) to Pulumi. Phrases such as "convert CDK to Pulumi", "migrate CDK app", "port CDK stacks", "replace CDK with Pulumi", "stop using CDK". Do NOT load for general CDK questions, CDK-only help, or CDK vs Pulumi comparisons where no migration is requested.

Guidance for working with Pulumi ESC (Environments, Secrets, and Configuration). Use when users ask about managing secrets, configuration, environments, short-term credentials, configuring OIDC for AWS, Azure, GCP, integrating with secret stores (AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, 1Password), or using ESC with Pulumi stacks.