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.
83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Scarb.toml configuration
cairo-version field
0%
100%
edition field
0%
100%
starknet-contract target
100%
100%
sierra = true
100%
100%
build-external-contracts
0%
100%
dojo dependency version
0%
100%
starknet dependency version
0%
100%
cairo_test dev-dependency
0%
100%
dojo_cairo_test dev-dependency
0%
100%
allow-prebuilt-plugins
0%
100%
Without context: $0.2343 · 1m 1s · 15 turns · 1,915 in / 3,350 out tokens
With context: $0.3296 · 57s · 20 turns · 26 in / 3,081 out tokens
Dev environment configuration
world section present
100%
100%
world name field
100%
100%
world seed field
100%
100%
env section present
100%
100%
rpc_url localhost
77%
100%
namespace section present
100%
100%
namespace default field
100%
100%
writers section present
100%
100%
writers maps namespace to system
100%
100%
Without context: $0.1800 · 47s · 10 turns · 54 in / 2,961 out tokens
With context: $0.3055 · 54s · 20 turns · 24 in / 2,933 out tokens
Project structure and starter files
lib.cairo exists
100%
100%
models.cairo exists
100%
100%
actions.cairo exists
100%
100%
test_world.cairo exists
100%
100%
Position model
100%
100%
Moves model
100%
100%
Direction enum
100%
100%
spawn function
100%
100%
move function
100%
100%
event emission
0%
100%
spawn_test_world usage
100%
100%
Without context: $0.2693 · 1m 8s · 16 turns · 22 in / 4,415 out tokens
With context: $0.4601 · 1m 34s · 23 turns · 276 in / 6,126 out tokens
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.