dojo-config

Configure Dojo project manifests and environment profiles for deployment.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Kepler22bee/House-of-Stark --skill dojo-config-kepler22bee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dojo-config
Source: https://github.com/Kepler22bee/House-of-Stark/tree/main/contracts/.agents/skills/dojo-config
Command: npx skills add https://github.com/Kepler22bee/House-of-Stark --skill dojo-config-kepler22bee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes and simplifies Dojo project configuration so developers can reliably set up Scarb.toml dependencies, environment profiles, and world settings without manual errors or inconsistent deployments.

Core Features & Use Cases

  • Dependency management: add or update Scarb.toml dependencies and external contract references including build-external-contracts entries.
  • Profile configuration: create and maintain dojo_<profile>.toml files for development, staging, and production with RPC, account, keystore, and namespace settings.
  • World and permission setup: configure world metadata, namespaces, writers, and owners to establish runtime permissions and resource mappings.
  • Security guidance: recommend keystore usage and .gitignore patterns to avoid committing private keys and sensitive environment data.
  • Use case: add the Origami library to your Scarb.toml and produce a dojo_mainnet.toml profile with correct RPC and keystore settings for production deployment.

Quick Start

Use the dojo-config skill to add the Origami library to Scarb.toml and create a production dojo_mainnet.toml profile configured for Sepolia.

Frequently Asked Questions about dojo-config

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

FAQPage Schema
How do I configure dojo environment profiles for mainnet deployment?

Configure dojo environment profiles by creating dojo_<profile>.toml files with RPC endpoints, account settings, keystore paths, and namespace mappings tailored for dev, staging, or mainnet. This ensures consistent deployments and correct runtime permissions across environments.

How do I add external contracts to Scarb.toml dependencies?

Add external contracts to Scarb.toml dependencies by declaring the library in the dependencies section and specifying build-external-contracts entries under target.starknet-contract. This ensures correct compilation and integration of external contract references during the Dojo build process.

What is the best way to manage Dojo world permissions and namespaces?

Managing Dojo world permissions involves configuring world metadata, namespace mappings, writers, and owners in your environment profiles. This establishes runtime permissions and resource mappings, ensuring safe and correct access control across your deployed Dojo project.

How do I safely handle private keys when setting up Dojo profiles?

Safely handle private keys by using keystore configurations within your dojo_<profile>.toml files and adding sensitive files to .gitignore. This prevents committing private keys and environment-specific secrets to version control during local development and deployment.

Can I use dojo-config to set up a Sepolia production deployment?

Yes, you can use dojo-config to set up a Sepolia production deployment by generating a dojo_mainnet.toml profile with the correct RPC settings and keystore configurations. It supports adding libraries like Origami to Scarb.toml and configuring environment-specific parameters for Sepolia.