Agent skill
quest-keeper-frontend
Frontend development skill for Quest Keeper AI Tauri application. Use when working on React components, Zustand stores, Three.js battlemaps, TailwindCSS styling, or Tauri shell integration. Triggers on mentions of frontend, React, Zustand, Three.js, battlemap, UI, viewport, or Tauri.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/quest-keeper-frontend
SKILL.md
Quest Keeper Frontend Development
Location
C:\Users\mnehm\Desktop\Quest Keeper AI attempt 2
Tech Stack
- Framework: Tauri 2.x (Rust shell + WebView)
- UI: React 19 + TypeScript + Vite
- State: Zustand stores
- 3D: Three.js via @react-three/fiber
- Styling: TailwindCSS (terminal/CRT aesthetic)
Directory Structure
src/
├── components/
│ ├── viewport/ # BattlemapCanvas, CharacterSheet, WorldMap
│ ├── adventure/ # Main layout (AdventureView.tsx)
│ ├── terminal/ # Chat interface
│ └── sidebar/ # Navigation
├── stores/ # Zustand state management
├── services/ # MCP client, LLM providers
├── hooks/ # Custom React hooks
└── utils/ # Helpers
Key Commands
npm run tauri dev # Development with hot reload
npm run build # Production build
MCP Response Parsing
import { parseMcpResponse } from '@/utils/mcpUtils';
const result = await mcpClient.callTool('get_character', { id });
const character = parseMcpResponse<Character>(result, null);
Terminal/CRT Aesthetic
Key classes: terminal-green, terminal-dim, terminal-dark, crt-glow, font-mono
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?