---

code: wize-customize
description: "Use quando precisar personalizar um agente, skill ou workflow built-in sem alterar os arquivos originais do kit."
name: Customize
module: core
status: ready
---

# Customize

**Goal.** Guide the user through creating an override (customize.toml) for a built-in agent, skill, or workflow. The override lives at `.wize/custom/{type}/{code}/customize.toml` and is loaded by the adapter at sync time.

Wizer drives. Tony on call for agent structure.

## When to use

- "Override the persona of `wize-agent-pm`."
- "Customize the wording in `wize-product-brief`."
- "Add a tool to `wize-orchestrator`."

## When NOT to use

- Creating a brand-new agent/skill/workflow → use `wize-create-agent` (or `wize-create-skill` / `wize-create-workflow`).
- Updating built-ins directly (the kit does not support forking built-ins; the next update would clobber your changes).

## Inputs

- A target: agent code, skill code, or workflow code.
- A scope: what to override (name, title, persona, tools, body).

## Output

- A new file at `.wize/custom/{type}/{code}/customize.toml` (or update of an existing one).
- A re-run of `wize-dev-kit sync` to apply the override.

## Steps

### 1. Identify the target

The user names the code (e.g., `wize-agent-pm`). The skill validates:

- Code shape: `wize-{kind}-{slug}`.
- Exists in the kit's built-in roster.

If the target does not exist, suggest `wize-create-agent` instead.

### 2. Inspect the existing override

If `.wize/custom/{type}/{code}/customize.toml` exists, read it. The user is updating; otherwise creating.

### 3. Ask what to change

The skill asks the user to pick from the overrideable fields:

- `name` (display name)
- `title` (job title)
- `persona` (markdown body)
- `tools` (list of tool names the agent can call)
- `icon` (emoji)

One field per run. Re-run for additional fields.

### 4. Generate the customize.toml

Write the new (or merged) customize.toml. Keep the structure as comments so the user can see the template.

```toml
# Override for {code} — generated by /wize-customize
# Re-running the skill merges; lines you delete are restored on next install.

[persona]
# name = "Your name here"
# title = "Your title here"

[tools]
# Add tool names the agent can call. Empty = default set.
# tools = []
```

### 5. Re-sync

Run `wize-dev-kit sync` (or instruct the user to). The override is loaded by the adapter and emitted to the IDE targets.

### 6. Hand off

Notify the user of:

- File written: `.wize/custom/{type}/{code}/customize.toml`.
- Sync completed (or instructions to run it).
- Where to verify the override (e.g., `.claude/skills/{code}/SKILL.md`).

## Output template

The skill does not write a markdown output; it writes the customize.toml and re-syncs.

```toml
# Override for wize-agent-pm — generated by /wize-customize

[persona]
name = "Hill"  # shortened from "Maria Hill"

[tools]
# tools = []   # default set
```

## Anti-patterns Wizer rejects

- Suggesting direct edits to built-in files in `node_modules/wize-dev-kit/`. (Next update clobbers.)
- Creating a customize.toml with no overrideable fields filled. (Empty = no-op.)
- Auto-running `wize-dev-kit sync` silently. (Confirm with the user first.)
- Customizing the same field twice in one run. (One field per run.)

## Hand-off

> "Override written at `.wize/custom/{type}/{code}/customize.toml`. Sync applied. Verify in `.claude/skills/{code}/SKILL.md` (or your IDE target)."