docs: update Slot CLI and add Controller integration (#432)

docs: update Slot CLI commands and add Controller integration

Fix deprecated slot deployments flags (--world, --rpc) by using --config instead.
Add Controller integration to dojo-client skill using starknet-react pattern.
Enable controllers indexing by default in Torii across all deployments.

Co-authored-by: Claude Haiku 4.5 <noreply@anthropic.com>

Author: kronosapiens

docs/pages/tutorials/deploy-to-mainnet/main.md

@@ -159,14 +159,22 @@ slotup
 slot auth login
 ```
 
+- Create a [Torii configuration file](/toolchain/torii/configuration) with your world address and RPC endpoint:
+    - `WORLD_ADDRESS`: from your Dojo config file `dojo_sepolia.toml` or from the deployment output
+    - `RPC_URL`: your RPC provider url
+
+```toml
+# torii.toml
+world_address = "<WORLD_ADDRESS>"
+rpc = "<RPC_URL>"
+```
+
 - Create Torii service with this command, replacing...
     - `SERVICE_NAME` can be the name of the game/dapp. Once you create it, you own that name.
     - `DOJO_VERSION`: your Dojo version (ex: `v1.0.1`)
-    - `WORLD_ADDRESS`: from your Dojo config file `dojo_sepolia.toml` or from the deployment output
-    - `RPC_URL`: your RPC provider url
 
 ```sh
-slot deployments create <PROJECT_NAME> torii --version <DOJO_VERSION> --world <WORLD_ADDRESS> --rpc <RPC_URL>
+slot deployments create <SERVICE_NAME> torii --config torii.toml --version <DOJO_VERSION>
 ```
 
 - slot will output something like this. Save it for later, you will need the endpoints on your client.

docs/pages/tutorials/deploy-using-slot/main.md

@@ -28,10 +28,18 @@ slot auth login
 rm ~/Library/Application\ Support/slot/credentials.json
 ```
 
-Once successful, you can create a new deployment with a unique `DEPLOYMENT_NAME`. To do this, run the following command:
+Once successful, you can create a new deployment with a unique `DEPLOYMENT_NAME`.
+
+The simplest way to get started is using `--optimistic` mode:
 
 ```sh
-slot deployments create DEPLOYMENT_NAME katana
+slot deployments create DEPLOYMENT_NAME katana --optimistic
+```
+
+Alternatively, you can provide a [Katana configuration file](/toolchain/katana/configuration) via `--config`:
+
+```sh
+slot deployments create DEPLOYMENT_NAME katana --config katana.toml
 ```
 
 After that, you should receive the RPC endpoint for the katana slot. Now, you can use that and update your `Scarb.toml` file with the new RPC endpoint as follows:
@@ -85,10 +93,24 @@ Congratulations! You have successfully deployed your project with a Katana slot.
 
 ## Torii
 
-To initiate a Torri indexer slot, execute the following command:
+To deploy a Torii indexer slot, first create a [Torii configuration file](/toolchain/torii/configuration) with your world address and RPC endpoint:
+
+```toml
+# torii.toml
+world_address = "YOUR_WORLD_ADDRESS"
+rpc = "YOUR_NEW_RPC_URL"
+```
+
+Then create the deployment:
+
+```sh
+slot deployments create DEPLOYMENT_NAME torii --config torii.toml
+```
+
+You can also specify a Dojo version with `--version`:
 
 ```sh
-slot deployments create DEPLOYMENT_NAME torii --world YOUR_WORLD_ADDRESS --rpc YOUR_NEW_RPC_URL --start-block 1
+slot deployments create DEPLOYMENT_NAME torii --config torii.toml --version v1.8.0
 ```
 
 Once deployment is successful, you should receive the endpoints for GraphQL and gRPC.

skills/dojo-client/SKILL.md

@@ -52,8 +52,8 @@ pnpx @dojoengine/create-dojo start
 # Essential packages
 pnpm add @dojoengine/core @dojoengine/sdk @dojoengine/torii-client
 
-# For React integration
-pnpm add @dojoengine/create-burner @dojoengine/utils
+# Controller + starknet-react (recommended)
+pnpm add @cartridge/connector @cartridge/controller @starknet-react/core @starknet-react/chains starknet
 
 # For state management
 pnpm add @dojoengine/state zustand immer
@@ -104,12 +104,81 @@ async function main() {
     // Use in React
     createRoot(document.getElementById("root")!).render(
         <DojoSdkProvider sdk={sdk} dojoConfig={dojoConfig} clientFn={setupWorld}>
-            <App />
+            <StarknetProvider>
+                <App />
+            </StarknetProvider>
         </DojoSdkProvider>
     );
 }
 ```
 
+### Controller Integration (starknet-react)
+
+[Cartridge Controller](https://docs.cartridge.gg/controller/getting-started) is the recommended way to handle account management in Dojo games.
+It provides session-based authentication via starknet-react.
+
+**Define policies and create the connector (outside React components):**
+
+```typescript
+import { ControllerConnector } from "@cartridge/connector";
+import { SessionPolicies } from "@cartridge/controller";
+
+const policies: SessionPolicies = {
+    contracts: {
+        [ACTIONS_CONTRACT_ADDRESS]: {
+            methods: [
+                { name: "spawn", entrypoint: "spawn" },
+                { name: "move", entrypoint: "move" },
+            ],
+        },
+    },
+};
+
+const connector = new ControllerConnector({ policies });
+```
+
+**Wrap your app with StarknetConfig:**
+
+```typescript
+import { StarknetConfig } from "@starknet-react/core";
+import { sepolia, mainnet } from "@starknet-react/chains";
+
+function StarknetProvider({ children }: { children: React.ReactNode }) {
+    return (
+        <StarknetConfig
+            autoConnect
+            chains={[mainnet, sepolia]}
+            connectors={[connector]}
+            provider={provider}
+        >
+            {children}
+        </StarknetConfig>
+    );
+}
+```
+
+**Connect/disconnect:**
+
+```typescript
+import { useConnect, useDisconnect, useAccount } from "@starknet-react/core";
+
+function ConnectWallet() {
+    const { connect, connectors } = useConnect();
+    const { disconnect } = useDisconnect();
+    const { address } = useAccount();
+
+    return address ? (
+        <button onClick={() => disconnect()}>Disconnect</button>
+    ) : (
+        <button onClick={() => connect({ connector: connectors[0] })}>
+            Connect
+        </button>
+    );
+}
+```
+
+The `useAccount()` hook used in the "Executing Systems" section below returns the Controller session account once connected.
+
 ### Querying Entities
 
 ```typescript

skills/dojo-deploy/SKILL.md

@@ -234,7 +234,7 @@ sozo build && sozo migrate
 
 **Terminal 3: Start Torii**
 ```bash
-torii --world <WORLD_ADDRESS>
+torii --world <WORLD_ADDRESS> --indexing.controllers
 ```
 
 ## Sample Deploy Script
@@ -270,6 +270,52 @@ PROFILE=staging ./scripts/deploy_local.sh
 - `TORII_URL`: Torii endpoint (default: `http://localhost:8080`)
 - Add project-specific post-deploy steps (e.g., seeding data, running migrations)
 
+## Slot Deployment (Remote)
+
+[Slot](https://docs.cartridge.gg/slot) provides hosted Katana and Torii instances.
+
+### Authentication
+
+```bash
+slot auth login
+```
+
+### Katana on Slot
+
+**Optimistic mode (simplest):**
+```bash
+slot deployments create <PROJECT_NAME> katana --optimistic
+```
+
+**With configuration file:**
+```bash
+slot deployments create <PROJECT_NAME> katana --config katana.toml
+```
+
+See the [Katana configuration guide](/toolchain/katana/configuration) for TOML options.
+
+### Torii on Slot
+
+Create a `torii.toml` with your world address and RPC endpoint, then deploy:
+
+```bash
+slot deployments create <PROJECT_NAME> torii --config torii.toml --version <DOJO_VERSION>
+```
+
+See the `dojo-indexer` skill for full Torii configuration details.
+
+### Useful Commands
+
+```bash
+# Stream logs
+slot deployments logs <PROJECT_NAME> katana -f
+slot deployments logs <PROJECT_NAME> torii -f
+
+# Delete a deployment
+slot deployments delete <PROJECT_NAME> katana
+slot deployments delete <PROJECT_NAME> torii
+```
+
 ## Manifest File
 
 After deployment, `manifest_<profile>.json` contains:

skills/dojo-indexer/SKILL.md

@@ -35,9 +35,14 @@ This starts Torii with default settings:
 - gRPC API at `http://localhost:8080`
 - In-memory database (for development)
 
+**With Controller indexing (recommended):**
+```bash
+torii --world <WORLD_ADDRESS> --indexing.controllers
+```
+
 **Production configuration:**
 ```bash
-torii --world <WORLD_ADDRESS> --db-dir ./torii-db
+torii --world <WORLD_ADDRESS> --db-dir ./torii-db --indexing.controllers
 ```
 
 ## What is Torii?
@@ -282,11 +287,47 @@ const { data } = await client.query({
 
 | Option | Description | Default |
 |--------|-------------|---------|
-| `--world` | World contract address | Required |
+| `--world` | World contract address | Optional (since Torii 1.6.0) |
 | `--rpc` | RPC endpoint URL | `http://localhost:5050` |
 | `--db-dir` | Database directory | In-memory |
+| `--config` | Path to TOML configuration file | None |
 | `--http.cors_origins` | CORS origins | `*` |
 
+## Slot Deployment (Remote)
+
+[Slot](https://docs.cartridge.gg/slot) provides hosted Torii instances. Slot requires a TOML configuration file.
+
+### Create Configuration
+
+```toml
+# torii.toml
+world_address = "<WORLD_ADDRESS>"
+rpc = "<RPC_URL>"
+
+[indexing]
+controllers = true
+```
+
+See the [Torii configuration guide](/toolchain/torii/configuration) for all TOML options (indexing, polling, namespaces, etc.).
+
+### Deploy
+
+```bash
+slot auth login
+
+slot deployments create <PROJECT_NAME> torii --config torii.toml --version <DOJO_VERSION>
+```
+
+### Manage
+
+```bash
+# Stream logs
+slot deployments logs <PROJECT_NAME> torii -f
+
+# Delete and recreate (safe — all data is on-chain)
+slot deployments delete <PROJECT_NAME> torii
+```
+
 ## Development Workflow
 
 **Terminal 1: Start Katana**