Skills
99,448 packaged capabilities and playbooks for agents. Install any of them with one command.
Development
Expertise in real-time multiplayer networking, lag compensation, and authoritative server architectureUse when "multiplayer game, netcode, client-server game, P2P networking, lag compensation, rollback networking, game server, matchmaking, lobby system, player synchronization, state replication, dedicated server, authoritative server, tick rate, network prediction, interpolation, extrapolation, GGPO, lockstep, real-time multiplayer, networking, multiplayer, gamedev, realtime, client-server, p2p, netcode, synchronization, lag-compensation, matchmaking" mentioned.
Generate a project's Technical Design Document + ADRs (MADR format) + acceptance criteria, interviewing the user decision by decision starting from their PRD (and optionally their Design.md or an existing repo). Use when the user asks to generate, draft, or create a technical design document, system architecture, or architecture decision records (ADRs) for a project, greenfield or brownfield.
Git workflow management with atomic commit principles. Capabilities: commit organization, branching strategies, merge/rebase workflows, PR management, history cleanup, staged change analysis, single-responsibility commits. Actions: commit, push, pull, merge, rebase, branch, stage, stash git operations. Keywords: git commit, git push, git pull, git merge, git rebase, git branch, git stash, atomic commit, commit message, conventional commits, branching strategy, GitFlow, trunk-based, PR, pull request, code review, git history, cherry-pick, squash, amend, interactive rebase, staged changes. Use when: organizing commits, creating branches, merging code, rebasing, writing commit messages, managing PRs, cleaning git history, analyzing staged changes.
GoldRush x402 — pay-per-request blockchain data access using the x402 protocol (HTTP 402 Payment Required). Use this skill whenever the user is building an AI agent that needs blockchain data without API keys, wants wallet-based micropayments for on-chain data, needs autonomous or no-account access to the GoldRush API, mentions the x402 protocol, or wants no-signup/no-onboarding blockchain data access. This is the right skill for autonomous agents, serverless applications, and prototyping without onboarding. Provides access to 60+ Foundational API endpoints through a transparent reverse proxy with stablecoin payments on Base. If the user needs a traditional API key with monthly billing, use goldrush-foundational-api instead. If the user needs real-time streaming data via WebSocket, use goldrush-streaming-api instead.
Plan the implementation of an approved requirement or specification: produce an executable, dependency-aware delivery plan covering work breakdown, dependency mapping, critical path, ownership, parallelism and sequencing, rollout strategy, rollback and recovery paths, and verification against the original requirement. Supports cross-team, cross-repository, migration, and staged-rollout scenarios. Do not use for pre-approval discovery or needs-finding, authoring a specification from scratch, coding or implementation, the neckbeard issue-to-PR delivery flow itself, or any work whose prerequisite decision has not been approved — planning unapproved work is an explicit stop condition.
Create and revise irudd-plan canvases or implement a selected work item through its required authenticated MCP integration. Use when a task names an irudd-plan human link or MCP reference, or requests collaborative canvas planning. Keep implementation retrieval focused on the selected packet.
Design the architecture for a Juspay payment integration — collaborative, step-by-step decisions that ground the integration in real Juspay docs and produce a consistent implementation guide. Use when the user says "design the Juspay integration", "create integration architecture", or after jp-prd to turn the PRD into a technical design.
Fix or build responsive layout: page shells, grids, card layouts, sidebars, breakpoint strategy, container queries. Use when the user says 'this breaks on mobile', 'the layout is messy', 'things don't line up', 'our spacing is inconsistent between sections', 'make this responsive', 'center this properly', or asks for a dashboard/page/grid layout. Inspects existing CSS for layout smells (fixed widths, absolute positioning, media-query sprawl), then produces working layout code — refactored CSS/JSX with Grid/Flexbox decision rules applied, breakpoints derived from content, and a responsive verification checklist. Hands off pure spacing-token questions to design-foundation and text-readability questions to typography-system.
Author, render, troubleshoot, and review Mermaid diagrams for documentation, architecture, processes, and technical communication. Use when a versionable diagram must communicate a defined audience job across a real renderer, including narrative, hierarchy, labels, legends, accessibility fallback, and uncertainty. Do not use for C4 level/model ownership, architecture decisions, or full accessibility conformance.
Use when the user says 'migrate elementor to gutenberg', 'convert elementor to blocks', 'remove the elementor dependency', or 'go back to native wordpress'. Maps Elementor widgets to core blocks and creates draft duplicates for review.
Use when the user asks to build Android screens, Jetpack Compose layouts, Material components, or any Android app UI. Also use when styling, redesigning, or beautifying any Android interface. Covers Material 3 Expressive for Android 16, spring motion, shape variety, and platform-native patterns.
Module organization patterns including ports and adapters (hexagonal), module communication, and data isolation. Use when structuring modular monoliths, defining module boundaries, setting up inter-module communication, or isolating database contexts. Includes MediatR patterns for internal events.
CommunityToolkit.Mvvm (the MVVM Toolkit) core: source generators ([ObservableProperty], [RelayCommand], [NotifyPropertyChangedFor], [NotifyCanExecuteChangedFor], [NotifyDataErrorInfo]), base classes (ObservableObject / ObservableValidator / ObservableRecipient), commands (RelayCommand / AsyncRelayCommand), and validation. Companion skills: mvvm-toolkit-messenger for pub/sub, mvvm-toolkit-di for Microsoft.Extensions.DependencyInjection wiring. Works across WPF, WinUI 3, MAUI, Uno, and Avalonia.
Wire CommunityToolkit.Mvvm ViewModels into Microsoft.Extensions.DependencyInjection. Covers the .NET Generic Host composition root, constructor injection, service lifetimes (Singleton / Transient / Scoped), IMessenger registration, resolving ViewModels in Views, keyed services, testing seams, and the legacy Ioc.Default escape hatch. Use across WPF, WinUI 3, .NET MAUI, Uno, and Avalonia.
Guide for using Netlify DB (managed Neon Postgres). Use when the project needs a relational database, structured data storage, SQL queries, or data that will grow over time. Covers provisioning, raw SQL via @netlify/neon, Drizzle ORM integration, migrations, and deploy preview branching. Also covers when to use Netlify Blobs instead.
(NS) Interview to map the five-block reference architecture, decompose a workflow into subtasks, decide agent vs rule vs approval gate per subtask, assign trade-off budget per component, lock an architecture change signal, then recommend LangGraph vs CrewAI, topology, personas, tools, and models — after conceptual adaptation design from `ns-agent-engineering` when agent vs RAG vs fine-tune is not yet locked. Use when building multi-agent systems, choosing LangGraph/CrewAI, designing crews/graphs, HITL workflows, "agents working together", producing official architecture decision records, or reverse-documenting an agent that already exists. Do NOT use for conceptual Prompt/RAG/Agent/Fine-Tune ladder (`ns-agent-engineering`), general app requirements (`/ns-spec-driven` Clarify), or coding without architecture intent.
Design the theme and component-style architecture of a Panda CSS project. Use when setting up theming, adding brand colors, wiring dark mode or a color-mode toggle, shipping more than one theme with theme.themes, staticCss.themes, data-panda-theme or injectTheme, naming or restructuring design tokens, deciding what belongs in tokens vs semanticTokens vs textStyles vs a recipe, designing a component's variant API, or deciding whether something should be a css() call, a cva, a config recipe, or a slot recipe, including converting a recipe into a slot recipe. Also use when tokens or recipes have grown messy and need a cleanup plan. Do not use for writing styles against a system that already exists (use panda-css), or for upgrading v1 to v2 (use panda-css-migrate).
Install, check or upgrade the papercut toolchain. Runs the doctor, asks how much to set up (Minimal, Standard, Full), then runs install.sh with flags and fixes dependency errors. Use for "set up papercut-explainer", "install papercut", "check my papercut install", "set up the voice", "why won't it render"
Use when setting up Git hooks for a polyglot or monorepo project with Lefthook — wiring fast format/lint checks on staged files at pre-commit and slower type-check/test gates at pre-push, across mixed-language subtrees (e.g. TypeScript and Python) from a single lefthook.yml, in parallel. Covers install + activation, the lefthook.yml schema (commands/jobs, glob, root, run with {staged_files}/{push_files}, stage_fixed, skip/only, parallel), a genuinely polyglot worked example, the hooks-vs-CI division of labor, and the --no-verify bypass. Teaches the hook wiring; references the per-tool skills (biome, ruff, ty, typescript-typecheck) and turborepo rather than re-teaching them. Keywords: git hooks, pre-commit, pre-push, lefthook, staged files, monorepo hooks, polyglot lint format.
Apply distilled coding principles from 14 classic software books to code review, refactoring, design, and implementation decisions. Do not use for language- or framework-specific tutorials, tool manuals, or tasks already governed by a project's established conventions.
Use when a Meta Quest app drops frames, overheats, or needs profiling: frame budgets, foveation, SpaceWarp, OVR Metrics, Perfetto, RenderDoc. NOT for the render loop (quest-native) or non-Quest profiling. Opt out: no xr, без xr. Triggers: “dropped frames” / “просадка кадров,” “шлем греется”.
Use when setting up or driving the Meta Quest toolchain on a dev machine: metavr CLI and MCP, Meta's agent skills, a connected headset, XR Simulator. NOT for app code (quest-native), captures (quest-perf), or submission (quest-store). Opt out: no xr, без xr. Triggers: “metavr,” “подключить шлем”.
Complete React TypeScript system. PROACTIVELY activate for: (1) Component props typing, (2) Event handler types, (3) Hooks with TypeScript, (4) Generic components, (5) forwardRef typing, (6) Context with type safety, (7) Utility types (Partial, Pick, Omit), (8) Discriminated unions for state. Provides: Props interfaces, event types, generic patterns, type-safe context, polymorphic components. Ensures type-safe React with proper TypeScript patterns.
Provides comprehensive guidance for Redis including data structures (string/hash/list/set/zset/geo/hyperloglog/bitmap/stream), common commands with examples, caching patterns, persistence (RDB/AOF), replication & sentinel, cluster, Lua scripting, transactions, pub/sub, pipelining, security hardening, and production best practices. Use when the user asks about Redis, needs to implement caching, choose Redis data structures, configure persistence or cluster, or troubleshoot Redis performance.
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.