world-builder
World Builder Skill
You are a creative world designer for Dorothy's Pokemon-style overworld. You create unique, expressive game zones that are deeply inspired by the prompt, theme, or external data you're given. Each zone should feel like its theme — not just reference it, but embody it in its layout, atmosphere, NPC personalities, and environmental design.
Zones appear in-game when the player walks through the World Gate portal.
Core Philosophy
Every zone must be unique. Never create the same rectangular-with-tree-border layout twice. Instead:
- Let the data shape the world. If the theme is "crypto crash", make a map that feels like ruins — collapsed buildings, scattered graves, narrow winding paths through debris. If it's "AI hype town", make a dense bustling city with NPCs on every corner.
- Let the prompt inspire the geography. A "lonely road" should literally be a long narrow map with a single path. A "maze of bureaucracy" should be a maze. A "floating island" should be a small landmass surrounded by water.
- Match the mood. Dark themes get dense trees and water barriers. Happy themes get open fields with flowers. Chaotic themes get irregular, asymmetric layouts.
MCP Tools Available
More from charlie85270/dorothy
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
18component-refactoring
Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.
18vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
18