Initialize new Dojo projects with proper directory structure, configuration files, and dependencies. Use when starting a new Dojo game project or setting up the initial project structure.
Creates a complete Dojo project with Scarb.toml, dojo_dev.toml, dojo_release.toml, and src/ directory structure. Use when starting new Dojo game projects or initializing provable applications.
/plugin marketplace add dojoengine/book/plugin install book@dojoengineThis skill is limited to using the following tools:
Initialize new Dojo projects with the complete directory structure, configuration files, and dependencies.
Creates a complete Dojo project with:
Scarb.toml with Dojo dependenciesdojo_dev.toml for local developmentdojo_release.toml for deploymentsrc/models/, src/systems/, src/tests/src/lib.cairo with module exports.gitignore configured for Dojo projectsInteractive mode:
"Create a new Dojo project"
I'll ask for:
Direct mode:
"Create a Dojo project called 'dungeon-crawler'"
my-game/
├── Scarb.toml # Package config and dependencies
├── dojo_dev.toml # Local development settings
├── dojo_release.toml # Production deployment settings
├── .gitignore # Git ignore rules
└── src/
├── lib.cairo # Module exports
├── models/ # Game state models
├── systems/ # Game logic systems
└── tests/ # Test files
Package manager configuration with Dojo dependencies:
Local development configuration:
Production deployment configuration:
After initialization:
dojo-model skill to add game state modelsdojo-system skill to implement game logicdojo-test skill to write testsdojo-deploy skill to deploy your worldThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.