gaming
141
gds-test-automate
Generate automated game tests for gameplay systems. Use when the user says "automate tests" or "generate tests"
bmad-code-org
development
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
gaming
141
gds-performance-test
Design game performance testing strategy. Use when the user says "performance test" or "benchmark"
bmad-code-org
development
gaming
141
gds-game-architecture
Design scale-adaptive game architecture with engine systems and networking. Use when the user says "game architecture" or "design architecture"
bmad-code-org
development
gaming
141
gds-playtest-plan
Create structured playtesting plans for user feedback. Use when the user says "playtest plan" or "playtesting"
bmad-code-org
development
gaming
141
gds-retrospective
Facilitate a retrospective after completing a game development epic. Use when the user says "run a retrospective" or "lets do a retro"
bmad-code-org
development
gaming
141
gds-create-ux-design
Plan UX patterns and design specifications for game UI/HUD elements. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the game UX"
bmad-code-org
development
gaming
141
gds-domain-research
Conduct game domain and industry research. Use when the user says "lets create a research report on [game domain or industry]"
bmad-code-org
development
gaming
141
gds-create-game-brief
Interactive game brief creation guiding users through defining their game vision. Use when the user says "game brief" or "create brief"
bmad-code-org
development
gaming
141
gds-brainstorm-game
Facilitate game brainstorming sessions with game-specific techniques. Use when the user says "brainstorm game" or "game ideas"
bmad-code-org
development
gaming
141
digital-worked-example-sequence
Create an interactive digital worked example sequence with fading for online or blended delivery. Use when building e-learning modules, LMS content, or app-based instruction.
GarethManning
development
gaming
141
gds-agent-game-solo-dev
Elite indie game developer for rapid prototyping and solo quick-flow development. Use when the user asks to talk to Indie or requests the Game Solo Dev.
bmad-code-org
development
gaming
141
gds-agent-game-qa
Game QA architect for test automation, performance profiling, and quality assurance. Use when the user asks to talk to GLaDOS or requests the Game QA Architect.
bmad-code-org
development
gaming
141
gds-agent-game-dev
Game developer for story execution, code implementation, and code review. Use when the user asks to talk to Link Freeman or requests the Game Developer.
bmad-code-org
development
gaming
141
gds-agent-game-designer
Game designer for creative vision, GDD creation, and narrative design. Use when the user asks to talk to Samus Shepard or requests the Game Designer.
bmad-code-org
development
gaming
141
gds-agent-game-architect
Game systems architect for technical architecture, engine design, and infrastructure. Use when the user asks to talk to Cloud Dragonborn or requests the Game Architect.
bmad-code-org
development
scripting
141
gds-dev-story
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"
bmad-code-org
development
cms-platforms
140
large-content-skill
A skill with 500KB+ content for lazy loading testing
maxvaega
development
full-stack
140
nested-mid-skill
Example skill demonstrating nested directory structure at depth 2
maxvaega
development
full-stack
140
nested-deep-skill
Example skill demonstrating nested directory structure at depth 3
maxvaega
development
framework-internals
140
evo-memory
Manages persistent research memory across ideation and experimentation cycles. Maintains two stores: Ideation Memory M_I (feasible/unsuccessful directions) and Experimentation Memory M_E (reusable strategies for data processing, model training, architecture, debugging). Three evolution mechanisms: IDE (after idea-tournament), IVE (after experiment failure — classifies failures as implementation vs fundamental), ESE (after experiment success — extracts reusable strategies). Use when: updating memory after completing idea tournaments or experiment pipelines, classifying why a method failed (implementation vs fundamental failure), starting a new research cycle needing prior knowledge, user mentions 'update memory', 'classify failure', 'what worked before', 'research history', 'evolution'. Do NOT use for running experiments (use experiment-pipeline), debugging experiment code (use experiment-craft), or generating ideas (use idea-tournament).
EvoScientist
development
mobile
140
asupersync-mega-skill
Replace Tokio Rust stacks with Asupersync. Use when migrating tokio/axum/hyper/tonic apps, designing native Cx/region-based services, or debugging Asupersync internals.
Dicklesworthstone
development
package-distribution
140
update-llvm-version
Update a minor or patch LLVM version in this repository. Use when bumping LLVM_VERSION, creating llvm-<version>-<suffix> prebuilt branches, watching the LLVM Prebuilt Release workflow, collecting release SHA256 values, updating MODULE.bazel, and opening the stacked update-llvm-<version> pull request.
hermeticbuild
development