Set up an Android CI/CD pipeline with lint, static analysis, unit tests, dependency review, and build verification. Use when: creating CI for Android, adding Gradle checks. Do not use: for local development setup, non-CI automation.
Reproduce, diagnose, regression-test, and fix a bug through the smallest root-cause change. Use when behavior violates intent. Do not use for new features or behavior-changing refactors.
Design or review a ChromaDB-backed RAG workflow. Use when: creating collections, choosing embedding functions, chunking documents, writing retrievers. Do not use: for general LLM integration, non-RAG patterns.
Create, review, or debug a CI/CD workflow. Use when: editing GitHub Actions, fixing CI failures, adding release/deploy automation. Do not use: for general DevOps, infrastructure as code.
Structure consequential decisions with explicit trade-offs. Use when choosing architecture, tools, or strategy. Do not use for obvious fixes or time-critical emergencies.
Maintain project docs, glossary, ADR/MADR, or RFC artifacts through focused modes. Use when code, terminology, or accepted decisions need durable documentation. Do not use for feature specifications or unrelated prose.
Use when enemy or NPC behavior needs perception, decision state machines, navigation, pathfinding, groups, encounters, or bosses in 2D Phaser or Godot. Do not use for player controls, procedural maps, UI, saves, or test strategy.
Use when creating or auditing 2D runtime art such as sprites, tilesets, backgrounds, animation, VFX, maps, or UI assets for Phaser or Godot. Do not use for UI behavior, audio, build delivery, 3D, or marketing art.
Use when 2D game music, ambience, sound effects, Web Audio, buses, volume, crossfades, spatial sound, or voice limits change. Do not use for visual feedback, accessibility-only cues, art, or release packaging.
Use when building or verifying Phaser/Vite bundles, Godot exports, web delivery, CI, versioning, compression, or release smoke tests. Do not use for gameplay implementation or to publish, tag, upload, or deploy without authority.
Use when tuning 2D controls, jumps, input buffering, hit stop, recoil, camera shake, particles, telegraphs, or moment-to-moment feedback. Do not use to change gameplay rules, UI accessibility, performance budgets, or tests.
Use when measured FPS, frame time, stutter, loading, memory, draw calls, pooling, tilemaps, particles, or web-export performance needs diagnosis. Do not use for speculative optimization, gameplay design, build delivery, or tests.
Use when 2D game saves, slots, settings persistence, checkpoints, progression, schema migrations, recovery, autosave, or storage adapters change. Do not use for transient gameplay state, engine-object serialization, maps, or UI.
Use when designing deterministic 2D game tests for simulation, combat, collisions, seeded maps, replays, browser behavior, or exported builds. Do not use to implement gameplay, optimize performance, or replace human playtesting.
Use when game HUD, menus, localization presentation, canvas/DOM labels, responsive layout, focus, touch, contrast, accessible names, captions, or reduced motion change. Do not use for combat rules, AI, persistence, audio, or art production.
Use when implementing 2D player movement, combat rules, abilities, interactions, physics, inventory, or scene flow in Phaser or Godot. Do not use for enemy AI, procedural generation, UI, persistence, art, audio, or release work.
Run or prepare a safe Google Cloud CLI operation. Use when: using gcloud, changing GCP resources, deploying to GCP. Do not use: for local CLI exploration, non-GCP operations.
Create a safe Git commit with Conventional Commits format. Use when: committing changes, reviewing staged changes. Do not use: for commit history rewriting, interactive rebasing.
Set up a Go CI/CD pipeline with formatting, vetting, static analysis, tests, vulnerability scanning, and container build. Use when: creating CI for Go, adding checks to workflow. Do not use: for local development setup, non-CI automation.
Design or review a LangGraph agent workflow. Use when: creating a graph, choosing state schema, nodes, tools, checkpoints, interrupts. Do not use: for simple chains, non-agent patterns.
Design or review an LLM integration in a service. Use when: adding model calls, tools, structured outputs, retries, rate limits. Do not use: for prompt engineering alone, non-service LLM work.
Zustand v5 recipes for middleware setup, immer mutations, persistence, and XState sync. Use when: zustand middleware, zustand persist, store patterns. Do not use: for state design patterns, non-Zustand stores.
Guide migration from React Router v6 to v7 framework mode. Use when: migrating routes, upgrading react-router, v6 to v7. Do not use: for initial React Router setup, general routing patterns.
XState v5 recipes for React integration, testing with createActor, and actor patterns. Use when: xstate react, testing state machine, actor patterns. Do not use: for simple component state, non-XState management.
★not rated 10 1mo agoA52 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: