poker-game-router
Route requests for the Stacked Poker Next.js frontend repo to the right repo skill (Chakra UI/theme, thirdweb/SIWE auth, WebSockets/game state, chat/media, poker hand eval, QA/release). Use at the start of most tasks in this repo to decide which skill(s) to apply.
When & Why to Use This Skill
The Poker Game Router is a specialized orchestration skill designed to optimize AI agent workflows within complex Next.js repositories. It acts as an intelligent dispatcher that analyzes incoming requests and routes them to the most relevant sub-skills—such as UI/UX design, Web3 authentication, or WebSocket management. By minimizing context overhead and ensuring the right tools are applied to specific tasks, it significantly improves the accuracy and efficiency of automated code maintenance and feature development.
Use Cases
- Task Dispatching: Automatically determining whether a developer's request involves UI styling, Web3 logic, or game state management at the start of a session.
- Context Optimization: Reducing token usage and 'hallucinations' by loading only the specific sub-skills and files required for a targeted task rather than the entire codebase.
- Workflow Orchestration: Coordinating multi-step tasks that require switching between different domains, such as updating a Chakra UI component and then verifying its production readiness.
- Web3 & Auth Troubleshooting: Routing complex SIWE (Sign-In with Ethereum) or thirdweb integration issues to specialized handlers to ensure security and protocol compliance.
| name | poker-game-router |
|---|---|
| description | Route requests for the Stacked Poker Next.js frontend repo to the right repo skill (Chakra UI/theme, thirdweb/SIWE auth, WebSockets/game state, chat/media, poker hand eval, QA/release). Use at the start of most tasks in this repo to decide which skill(s) to apply. |
Poker Game Router
Use this skill as a lightweight dispatcher. Keep context small: decide which skill(s) to use, then load only the chosen skill(s) and relevant files.
Repo landmarks
- App Router entry:
app/layout.tsx,app/page.tsx,app/providers.tsx - Theme system:
app/theme.ts - Web3/thirdweb client:
app/thirdwebclient.ts,app/components/WalletButton.tsx - SIWE auth:
app/hooks/useWalletAuth.ts,app/contexts/AuthContext.tsx,app/hooks/server_actions.ts - WebSocket/game state:
app/contexts/WebSocketProvider.tsx,app/contexts/AppStoreProvider.tsx,app/hooks/server_actions.ts - Chat/media:
app/components/NavBar/Chat/,app/hooks/useTenor.ts,app/api/tenor/route.ts - Poker hand eval:
app/lib/poker/pokerHandEval.ts - Build hygiene:
package.jsonscripts,.eslintrc.json,.prettierrc,.husky/pre-commit
Skill selection (decision tree)
Pick the minimal set; multiple can apply.
UI, layout, theme, Chakra components
Use chakra-design-system when:
- Editing
app/theme.tsor Chakra tokens/variants - Adding/modifying UI components under
app/components/ - Fixing responsive layout, spacing, typography, color, dark/light mode
- Improving a11y for Chakra components (focus, aria, keyboard)
Web3, wallets, thirdweb, embedded wallet, SIWE
Use web3-thirdweb-siwe when:
- Touching wallet connect flows, account state, auth cookies/session
- Working with
thirdweb/reacthooks (useActiveAccount,useActiveWallet, etc) - Debugging auth loops, signature issues, disconnect behavior, or CSP issues
- Updating
next.config.jsCSP headers related to thirdweb embedded wallet
“Quality bar” / production readiness
Use frontend-quality-bar when:
- Doing UI polish passes, UX consistency, performance, accessibility
- Adding new components/features that should meet a consistent standard
- Preparing a PR/merge, or doing broad refactors
Use project rules and MCP
- Read
.cursor/rules/frontend-guidelines.mdcfor the repo’s frontend expectations. - Read
.cursor/rules/thirdweb.mdcfor thirdweb rules and documentation pointers. - See
.cursor/mcp.jsonfor MCP servers that can fetch thirdweb/Chakra documentation on demand.