mud-onchain-dev

Develop full-stack blockchain MUD games with ECS schema design and deployment.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/mashharuki/Re-Autonomus-World-Game --skill mud-onchain-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mud-onchain-dev
Source: https://github.com/mashharuki/Re-Autonomus-World-Game/tree/main/.agents/skills/mud-onchain-dev
Command: npx skills add https://github.com/mashharuki/Re-Autonomus-World-Game --skill mud-onchain-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @latticexyz/*, viem, solidity, foundry, mud-cli, mprocs, eslint, prettier, solhint, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides comprehensive support for developing full-stack MUD (Multi-User Dungeon) games or applications on the blockchain. It helps with requirements gathering, ECS schema design, world/system implementation, client synchronization, testing, deployment, and operational troubleshooting, making it suitable for consistent progress from new project setup to modification, performance/gas optimization, and establishing a repeatable development workflow.

Core Features & Use Cases

  • Requirements Gathering: Document "who", "when", "which system to call", and "how the tables change" in writing.
  • ECS Schema Design: Normalize around Entity, plan for future expansion, and optimize read/write access.
  • World/System Implementation: Assign single responsibilities to each system, ensure failure conditions are verifiable, and handle external calls.
  • Client Synchronization: Design clients based on state transitions, use optimistic UI with rollback conditions, and provide fallbacks for delayed events.
  • Verification and Quality Assurance: Confirm schema integrity, major system paths, gas increase, and client display consistency.
  • Deployment and Operations: Deploy with confirmed chain settings, permissions, and environment variables, perform smoke tests, and investigate issues with separated state checks.

Quick Start

Ensure the project targets MUD v2 or later. Separate the change targets into contracts (World/System/Schema) and client (synchronization/UI). Decide on the data model (tables, primary keys, integrity) before writing systems. Perform system-level tests and scenario tests, verify client synchronization, and reconfirm chain settings, permissions, and environment variables during deployment.

Frequently Asked Questions about mud-onchain-dev

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

FAQPage Schema
How do I design an ECS schema for on-chain games using MUD?

To design an ECS schema for on-chain games using MUD, normalize data around the Entity, plan for future schema expansion, and optimize read/write access. This approach maintains schema integrity and efficient state transitions.

What is the best way to synchronize a MUD client with blockchain state transitions?

The best way to synchronize a MUD client is to design based on state transitions, use optimistic UI with rollback conditions, and provide fallbacks for delayed events to ensure consistent display.

How do I implement and test MUD world systems for blockchain applications?

Implement MUD world systems by assigning single responsibilities to each system, ensuring failure conditions are verifiable, and handling external calls. Verify implementation by performing system-level and scenario tests for major paths.

Can I use Foundry and Solidity with MUD v2 for on-chain game development?

Yes, you can use Foundry and Solidity with MUD v2 for on-chain game development. The workflow supports these dependencies for compiling, testing, and deploying World and System smart contracts.

How do I deploy a MUD world and troubleshoot operational issues?

Deploy a MUD world by confirming chain settings, permissions, and environment variables, then perform smoke tests. Troubleshoot operational issues by investigating with separated state checks to isolate failures.