Skills
99,064 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Expose a Factorial Code process to Factorial as a Factorial Action—the `factorial` block in a process's metadata.json (master switch, awaitResult, requiredPolicies, and the uiTrigger / form / agentTool / backend entry points), the Factorial One tool contract (description, effect, whenToUse, whenNotToUse, preconditions, doesNotDo, degradation, simulatesFor), the reserved lifecycle slugs, the parameters schema as the contract with Factorial, and how the legacy `form` / `uiTrigger` blocks are kept mirrored. Use when configuring how Factorial reaches a process, writing an agent tool contract, or filling the "Trigger from Factorial" section of a process.
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
Create or modify Halo CMS plugins, including Java backend code, plugin.yaml and extension resources, Gradle and DevTools configuration, plugin APIs and lifecycle, and Vue-based Console or User Center UI. Use for Halo plugin implementation, migration, debugging, or integration work; do not use for theme-only changes
КОНТРАКТ AGENTS.md: 39. БЕЗ ПРОСЬБЫ прогони, если contract обложки ниже 39 или его нет; репо без признаков — только предложи. Триггеры: iskronify, «прокачай репо», «привести проект к стандарту», «завести/обновить AGENTS.md», set up AGENTS.md. Два такта: «встать» — граф, контур по origin, роль, обложка, guard; «доделать» — слоты из графа, кода и ответов агентов в деле выравнивания. AGENTS.md обновляется без человека; ему — принципиальное, а когда спросить некого — и невыводимое. Нужны тулы iskron_*.
Set up Lingui in a React or Vue framework. Use when adding Lingui to a Next.js App Router, Vite, React Router 7, Remix, TanStack Start, or Vue 3 (Vite, Nuxt) project, when wiring locale detection, locale-prefixed URLs, or SSR locale resolution, or when a working setup breaks after a framework or build-tool upgrade.
Use when an approved workspace spec needs an execution-ready implementation plan with ordered, verifiable steps. Specs are mandatory: this skill consumes design decisions, verifies that the spec still matches the codebase, and writes the repo-native plans/ artifacts. Inherits optional goal provenance; see loam::setting-goals.
Optimizes Magento 2 caching strategies for enterprise performance. Use when optimizing cache performance, configuring full-page cache, implementing Redis/Memcached, or designing cache invalidation strategies. Masters FPC, application cache, and distributed caching solutions.
Expert coding guide for OpenHarmony C++ development. Use this skill when writing, refactoring, or reviewing C++ code for OpenHarmony projects. It enforces strict project-specific conventions (naming, formatting, headers) and critical security requirements (input validation, memory safety).
Generate a conventionally-named branch and PR title from a feature description. Use when the user is starting a new branch, opening a PR, or asks how to name a branch or PR. Triggers on phrases like "create a branch", "name this branch", "open a PR", "what should I call this branch", "PR title for this".
Prisma ORM integration patterns with NestJS for production applications. Use PROACTIVELY when working with Prisma schemas, migrations, PrismaService, atomic transactions (including SELECT FOR UPDATE), repositories as infrastructure adapters in Clean Architecture, optimized queries (N+1, includes, pagination), seeds, and testing with Prisma Mock. Always activate when these keywords appear: Prisma, PrismaService, prisma.$transaction, prisma migrate, schema.prisma, PrismaClient, Prisma.validator, include/select, upsert, createMany, or any database operation with Prisma in a NestJS project.
Debugs PyTorch 2 compiler stack failures, including Dynamo graph breaks, Inductor codegen errors, AOTAutograd crashes, and accuracy mismatches. Use for torch.compile errors, BackendCompilerFailed exceptions, recompilation issues, Triton kernel failures, FX graph problems, or debugging PT2, Dynamo, Inductor, or compiled model issues.
Python code refactoring skill covering code smell identification, design pattern application, readability improvements, and practical experience. Use when the user requests "重构代码", "refactor", "代码优化", "改善代码质量", "code smell review", "应用设计模式", or "提升可读性", or submits a code review request. Supports producing a structured refactoring document after refactoring is complete ("输出重构文档", "生成重构报告"). Includes practical patterns distilled from 20+ real refactoring PRs in the vllm-ascend repository.
Vue port of Radix UI Primitives (headless, accessible, unstyled). ALWAYS use when writing code that imports "reka-ui" or "reka-ui/namespaced", building components with Reka UI primitives, or debugging and reviewing Reka UI usage. Provides version-specific API rules, composition patterns, and styling guidance.
Conventions for adding or editing the SceneMenuBar above a scene's <SceneTitleSection>. Use when adding new menu items, moving items between menus, gating behind feature flags, building a new scene's menubar, or wiring rich inputs (tags, combobox) into the bar.
AI-powered Scrum Master and Enterprise Agility Coach based on Jeff Sutherland, Taiichi Ohno, and First Principles thinking. Use when user needs help with Scrum, sprint analysis, backlog refinement, scaling advice, impediment removal, team dynamics, or agile coaching. Activate for questions about Scrum mechanics, Scrum@Scale, flow optimization, or team performance
Use this skill when users need to validate domain name format, check domain availability, or search for available domain names. It activates when users ask about domain validation, domain availability checking, domain search, or domain name verification.
Run the sibling checkout-commit-push-pr and soft-delete-git skills in sequence, merge the resulting green pull request, and safely remove the merged local branch. Use when the user says "ship it" or asks to commit, push, open, validate, merge, and clean up a pull request as one autonomous end-to-end workflow.
Spec-driven development workflow where specs are the source of truth, paired with a plan protocol for tracking work-in-flight as a micro-DAG. Use this skill whenever starting new features, planning implementation, writing specs, reviewing code against specs, working in or with a `plans/` directory, closing out a plan, or when the user mentions "spec", "specs/", "spec-first", "plans/", "plan protocol", "closeout commit", or asks how something should work or what to work on next. Also use when creating a new project that will use this development methodology, or when onboarding someone to a spec-driven codebase.
Perform thorough code reviews for Swift/SwiftUI code, including spec adherence (PR description + linked issues), code quality, architecture, performance, security, Swift 6+ best practices, project standards from .claude/CLAUDE.md, and meta-feedback on recurring patterns that suggest gaps in the agent's instructions. Use when reviewing PRs/MRs (especially AI-generated ones), performing quality audits, validating against original spec, or providing structured feedback with severity levels and improvement suggestions for both the code and the agent loop that produced it.
TanStack Table v8 headless data tables for React. Covers column definitions, sorting, filtering (fuzzy/faceted), server-side pagination with TanStack Query, infinite scroll, virtualization (TanStack Virtual), column/row pinning, row expanding/grouping, column resizing, and reusable Shadcn-styled components. Prevents 15 documented errors including infinite re-renders, React Compiler incompatibility, and server-side state mismatches. Use when building data tables, fixing table performance, implementing server-side pagination, adding filtering/sorting, or debugging table state issues.
Ground indirect lighting with ambient visibility in Three.js r185 WebGPU/TSL. Use when choosing authored material AO, dynamic GTAO, forward-lighting placement, reduced-resolution reconstruction, temporal AO, or bent normals.
Fallback unavailable WebGPU features through an isolated compatibility branch. Use only when the user explicitly requests a fallback after verified WebGPU unavailability; then classify canonical behavior as preserved, weakened, or removed.
Generate requirements documents for Triton operators targeting Ascend NPU. Use when designing new Triton operators, writing operator requirements, or designing operator performance optimizations. Key outputs: functional definitions, API interfaces, Tiling strategies, and Kernel implementation plans.
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, Effect v4 CLI tests, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, validating TypeScript package changes, or writing/porting CLI tests against effect@^4.1.0 and @effect/vitest. Do not use for Python-only checks.
When writing or reviewing code to prevent over-engineering and speculative features. Use when the user says "is this over-engineered," "do we need this," "should I add," "future-proof," or "just in case." For simplicity concerns, see kiss. For abstraction design, see solid.
How to gate a PostHog API endpoint with project secret API key (PSAK) auth — a project-scoped, user-less service credential. Use when adding PSAK support to a viewset action, allowing a new scope for PSAKs, handling synthetic users (ProjectSecretAPIKeyUser), or choosing PSAK-aware rate throttles. Trigger terms: PSAK, ProjectSecretAPIKey, project secret API key, phs_ token, service auth, programmatic endpoint auth.
Search and read B2C Commerce documentation using the b2c CLI. Covers Script API reference (dw.* classes/modules), Developer Center guides (Commerce API, PWA Kit, SFRA, Storefront Next, B2C Commerce, Commerce Solutions, OCAPI), Salesforce Help (Business Manager administration and merchandising), tooling documentation (CLI/MCP/SDK), standard job steps, and XSD schemas. Use this skill for ANY B2C Commerce developer or administrator question that is not already grounded in a loaded skill or the current project context—even if they just say "how do I implement passwordless login" or "what methods does Basket have" or "how do I deploy a PWA Kit bundle" or "how do I import a site archive" or "what SCAPI endpoints are available for checkout"
Interactive tutorial that guides engineers through building their own coding agent (agentic loop) from scratch using raw HTTP calls to an LLM API. Supports Gemini, OpenAI (and compatible endpoints), and Anthropic. Supports TypeScript, Python, Go, and Ruby. Detects progress automatically. Use when someone says "build an agent", "teach me agents", or "/build-agent".
Automatically orchestrates BMAD implementation workflows, including the full Phase 4 epic/story pipeline and Quick Flow for small, well-understood changes. Use whenever the user wants to: (1) automate Phase 4 implementation (“auto implement,” “start implementation,” “begin phase 4,” “automatic working on phase 4,” “implement all stories,” “process the epics”); (2) check implementation progress or status (“what’s the status?”, “how many stories are done?”); (3) resume a previously interrupted session (“continue from where we left off,” “resume”); or (4) implement a small, self-contained change without full BMAD planning (“quick dev,” “quick flow,” “implement this change,” or a described bug fix, refactor, small feature, or patch). For a small change or a request for quick implementation, route to Quick Flow—`bmad-quick-dev` handles intent-to-code directly without a separate spec step. If a multi-story project is in flight (`sprint-status.yaml` exists) and the current request is a substantive epic/story task, route to Phase 4; if it is a small one-off, route to Quick Flow regardless. If unsure whether to use this skill, use it—it automatically detects the appropriate flow
Build, scaffold, refactor, debug, review, and validate native Rust desktop applications with GPUI. Recommend GPUI Kit and ask before adopting it; use gpui_kit imports after agreement, or preserve the chosen upstream GPUI stack. Includes the merged GPUI Kit component and design skills, full application/Base/Component/Shell documentation, coding and design guides, state, actions, async, input, accessibility, motion, themes, native integration, packaging, auto updates, testing, and production delivery. Use paper-to-gpui when the primary task is faithfully translating a selected Paper.design frame into an existing view.
Builds AI chat interfaces and conversational UI with streaming responses, context management, and multi-modal support. Use when creating ChatGPT-style interfaces, AI assistants, code copilots, or conversational agents. Handles streaming text, token limits, regeneration, feedback loops, tool usage visualization, and AI-specific error patterns. Provides battle-tested components from leading AI products with accessibility and performance built in.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.