- Home
- Skills
- Dojoengine
- Book
- Dojo Config
dojo-config_skill
- TypeScript
51
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill dojoengine/book --skill dojo-config- SKILL.md6.5 KB
Overview
This skill manages Dojo project configuration files and environment profiles, including Scarb.toml, dojo_<profile>.toml files, world settings, and dependencies. It helps set up development, staging, and production environments, and ensures consistent namespaces, permissions, and deployment parameters. Use it to add libraries, update manifests, and secure secrets for deployments.
How this skill works
It edits and validates Scarb.toml for package metadata, dependencies, and build targets, and creates or updates dojo_<profile>.toml files for environment-specific settings (rpc_url, account keys, keystore paths). It configures world metadata (name, seed, cover/icon URIs), namespaces, writers/owners permissions, and maps external contract dependencies. It enforces best practices like ignoring secret profiles and suggests keystore usage for production.
When to use it
- Initializing or updating project dependencies in Scarb.toml
- Creating or switching deployment profiles (dev/staging/mainnet)
- Configuring world metadata and resource namespaces
- Setting writers and owners permissions before first deployment
- Moving secrets from plain private_key to keystore for production
Best practices
- Keep dojo_dev.toml in repo and ignore production profile files with .gitignore
- Use keystore_path for production instead of embedding private_key
- Add external libraries in [dependencies] and list model contracts under build-external-contracts
- Use a deterministic world seed for stable address generation across environments
- Name profile files dojo_<profile>.toml and match --profile flags exactly
Example use cases
- Add Origami or Alexandria as a dependency and update Scarb.toml with the git tag or repo entry
- Create dojo_staging.toml with staging RPC, keystore, and namespace mappings
- Configure world settings (name, seed, cover_uri, icon_uri) for a new game deployment
- Set namespace mappings and writers/owners before running sozo migrate for a fresh world
- Switch build targets to include external contract models in Scarb.toml for composing crates
FAQ
Add production profile files to .gitignore and use keystore_path in dojo_<profile>.toml. Keep only dojo_dev.toml in the repo.
What file names does Dojo expect for profiles?
Profile files must be named dojo_<profile>.toml (dojo_dev.toml default). Use the same profile name with sozo build/migrate --profile <profile>.