vr-ar
VR/AR development principles. Comfort, interaction, performance requirements.
database-design
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
pc-games
PC and console game development principles. Engine selection, platform features, optimization strategies.
multiplayer
Multiplayer game development principles. Architecture, networking, synchronization.
game-design
Game design principles. GDD structure, balancing, player psychology, progression.
lint-and-validate
Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, types, static analysis.
webapp-testing
Web application testing principles. E2E, Playwright, deep audit strategies.
seo-fundamentals
SEO fundamentals, E-E-A-T, Core Web Vitals, and Google algorithm principles.
mcp-builder
MCP (Model Context Protocol) server building principles. Tool design, resource patterns, best practices.
game-art
Game art principles. Visual style selection, asset pipeline, animation workflow.
mobile-games
Mobile game development principles. Touch input, battery, performance, app stores.
game-audio
Game audio principles. Sound design, music integration, adaptive audio systems.
parallel-agents
Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.
nodejs-best-practices
Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.
templates
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
behavioral-modes
AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.
bash-linux
Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.
systematic-debugging
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
game-development
Game development orchestrator. Routes to platform-specific skills based on project needs.
deployment-procedures
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
architecture
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
code-review-checklist
Code review guidelines covering code quality, security, and best practices.
web-games
Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
3d-games
3D game development principles. Rendering, shaders, physics, cameras.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
2d-games
2D game development principles. Sprites, tilemaps, physics, camera.
intelligent-routing
Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.
geo-fundamentals
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
i18n-localization
Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
wagmi-development
Creates Wagmi features across all layers - core actions, query options, framework bindings. Use when adding new actions, hooks, or working across packages/core, packages/react, packages/vue.
autoresearch
Orchestrates end-to-end autonomous AI research projects using a two-loop architecture. The inner loop runs rapid experiment iterations with clear optimization targets. The outer loop synthesizes results, identifies patterns, and steers research direction. Routes to domain-specific skills for execution, supports continuous agent operation via Claude Code /loop and OpenClaw heartbeat, and produces research presentations and papers. Use when starting a research project, running autonomous experiments, or managing a multi-hypothesis research effort.
dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
dev
Development workflows for the playwright-cli repository. Use when the user asks about rolling dependencies, releasing, or other repo maintenance tasks.
preline-theme-generator
Generates beautiful, consistent Preline Theme CSS files. Agent interprets user request, runs build script, delivers complete CSS.
check-rust-coverage
Check which Rust lines are not covered by Rust tests. Use this when you developed new Rust code and want to ensure it is tested.
lint
Check code quality and formatting before committing changes. Use this to verify your changes meet our coding standards.
port-c-module
Guide for porting a C module to Rust. Use this when starting to port a C module to Rust.
analyze-rust-ffi-crate-surface
Determine which parts of the C codebase use Rust-defined C symbols. Use this when you want to understand which C code files may be impacted by changes to a Rust FFI crate.
jj-fix-conflicts
Fix merge conflicts in a jj change and its ancestors, starting from the oldest conflict. Use this when a jj change or its ancestors have conflicts that need resolving.
verify
Run full verification before committing or creating a PR. Use this when you want to create a PR.
rust-tests-guidelines
Guidelines for writing Rust tests. Use this when you want to write Rust tests.
read-unmodified-c-module
Read the source of the C module we are working on, before we made any changes.
run-python-tests
Run end-to-end Python tests after making changes to verify correctness. Use this when you want to verify your changes from an end-to-end perspective, after ensuring the build and Rust tests pass.
review-rust-docs
Review the documentation of a Rust crate to ensure it meets our requirements and standards. Use this when you have done changes to Rust code.
run-rust-benchmarks
Run Rust benchmarks and compare performance with the C implementation. Use this when you work on migrating C code to Rust and want to ensure performance is not regressed.
write-rust-tests
Write Rust tests to verify correctness of Rust code. Use this when you want to write Rust tests.
run-rust-tests
Run Rust tests after making changes to verify correctness. Use this when you want to verify your changes to Rust code.
rust-review
Review Rust code changes for unsafe correctness, documentation quality, and C-to-Rust porting fidelity. Use this when you want to review Rust changes before merging.
minimize-rust-ffi-crate-surface
Remove Rust-defined C symbols that are either unused or only used in C/C++ unit tests. Use this when you are refactoring a Rust FFI crate and want to remove unused symbols.
Page 106 of 1746 · 87259 results
