Narrow file-writing skill for creating only a Digitable game folder and game.json after the user explicitly asks to scaffold project metadata or after new-game-discovery has established the title, player count, component scope, and prototype direction.
Automate browser interactions, test web pages and work with Playwright tests.
Define typed, serializable error variants with defineErrors from wellcrafted. Use when creating error types, handling domain errors, or reviewing error definitions.
Error handling patterns using wellcrafted trySync and tryAsync. Use when writing or reviewing try-catch blocks, refactoring try-catch to linear control flow, working with Result types, or returning HTTP error responses from route handlers.
Architectural patterns for code that uses wellcrafted. Covers control flow with trySync/tryAsync, factory function composition, service layers with Result types, error composition across boundaries, and the single-or-array pattern.
Working with Result types, Ok, Err, trySync, tryAsync, and utility functions from wellcrafted. Use when wrapping unsafe code, handling errors with Results, or destructuring { data, error } responses.
Explore board game component directions for Digitable, generating several distinct options for cards, boards, resources, factions, powers, scoring, conflict, economy, or unusual mechanics before the user commits to implementation.
Narrow file-writing skill for creating only a Digitable game folder and game.json after the user explicitly asks to scaffold project metadata or after new-game-discovery has established the title, player count, component scope, and prototype direction.