poker-game-router

Route Stacked Poker Next.js frontend requests to the appropriate skill modules.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Stacked-Labs/poker-game --skill poker-game-router
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: poker-game-router
Source: https://github.com/Stacked-Labs/poker-game/tree/main/.claude/skills/poker-game-router
Command: npx skills add https://github.com/Stacked-Labs/poker-game --skill poker-game-router

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill reduces cognitive load and context leakage by acting as a lightweight dispatcher that decides which sub-skill(s) to apply and then loads only the chosen skill(s) and relevant files.

Core Features & Use Cases

  • Lightweight dispatcher to select the minimal set of skills based on the task
  • Context-controlled routing that loads only the relevant skill modules and files
  • Guides users to key repo areas such as UI, Web3/SIWE, WebSocket/game state, chat/media, poker hand evaluation, and build hygiene

Quick Start

Load this skill at the start of a task to route to the appropriate sub-skills and assets.

Frequently Asked Questions about poker-game-router

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route frontend tasks to the right skill modules in a Next.js poker app?

To route frontend tasks, load this dispatcher skill first so it can evaluate your request against a minimal decision tree and load only the appropriate skill modules for UI, wallet, or game state tasks.

What is skill dispatch for a poker frontend and how does it reduce context leakage?

Skill dispatch is a routing mechanism that evaluates task requirements and loads only the necessary skill files, reducing context leakage by preventing irrelevant modules from being injected into the working context.

Can I use this routing decision tree for both Web3 wallet authentication and WebSocket game state tasks?

Yes, you can use this routing decision tree for Web3 wallet authentication and WebSocket game state tasks, as it supports routing across UI, auth, chat/media, and poker hand evaluation domains.

What's the best way to manage context when switching between poker hand evaluation and UI build tasks?

The best way to manage context is to load this dispatcher at the start of your task, which applies a minimal-dispatch decision tree to load only the selected skill and its related files for the specific domain.

Do I need to manually load individual skill files for QA and release tasks in a Stacked Poker repository?

No, you do not need to manually load individual skill files because this dispatcher relies on repository landmarks to automatically guide routing and load the correct build hygiene and QA skills for you.