Kismet
Sign inDownload

Documentation / User guides

Customize the agent

Give the agent standing instructions for your project — naming conventions, base classes, folders to avoid — with an AGENTS.md file, and import the rules you already wrote for other AI tools.

Add an instruction file

Kismet reads a project instruction file and adds it to the agent on every turn, so you do not have to repeat the same guidance in each prompt. Place the file in your project root — the folder that contains your .uproject. The recommended filename is AGENTS.md, the cross-tool open standard also read by Cursor, GitHub Copilot, Codex, Gemini CLI, Aider, Windsurf, and Zed. Kismet also recognizes a few other names; see File priority below.

File priority

When several instruction files are present, Kismet does not merge them — it loads the first one it finds and ignores the rest. Files are checked in this priority order, highest first:

1. KISMET.mdKismet-specific override. Use only when you want Kismet guidance to win over a shared AGENTS.md.
2. AGENTS.mdRecommended for almost everyone. The cross-tool open standard.
3. CLAUDE.mdClaude Code instructions. Read when no higher-priority file exists.
4. GEMINI.mdGemini CLI instructions. Read when no higher-priority file exists.
5. KISMETAI.mdLegacy Kismet name, still supported for older projects.
Only the first file is used. If you keep both an AGENTS.md and a CLAUDE.md, Kismet reads AGENTS.md and ignores CLAUDE.md. To combine guidance from several files into one, use Import (below). Stick with AGENTS.md unless you have a specific reason to override it with KISMET.md.

Create one with /init

You do not have to write the file by hand. Type /init in the Kismet panel and Kismet sets it up for you — importing any other-tool rules it finds, or writing a short starter template when it finds none. It opens the file so you can fill in the project-specific sections.

/init never overwrites an instruction file that already exists. If one is already present, Kismet tells you which file it found and leaves it untouched.

Import from other tools

If you already keep instructions for Cursor, Claude, Copilot, or another AI tool, you do not need to rewrite them. Type /import in the Kismet panel to open the import panel. Kismet scans your project root, lists every tool config it finds, and lets you choose which ones to pull into your Kismet instruction file.

Cursor.cursorrules, .cursor/rules/
GitHub Copilot.github/copilot-instructions.md
ClaudeCLAUDE.md
GeminiGEMINI.md
Windsurf.windsurfrules, .windsurf/rules/
AiderCONVENTIONS.md
Cline.clinerules
Roo Code.roorules, .roo/rules/
Continue.continue/rules/
Amazon Q.amazonq/rules/
Firebase Studio.idx/airules.md
JetBrains Junie.junie/guidelines.md
GenericAI.md, AI_INSTRUCTIONS.md, README.ai.md
  1. 1.

    Open the import panel.

    Type /import in the Kismet panel. On a fresh project that has other-tool configs but no Kismet instruction file yet, Kismet opens this panel automatically the first time you open the editor.

  2. 2.

    Choose what to import.

    Every detected config is listed with its file path and checked by default. Uncheck any you want to leave out.

  3. 3.

    Click Import selected.

    Kismet merges the chosen configs into AGENTS.md — or appends them to your existing KISMET.md or AGENTS.md — under a labeled section for each source, then opens the file so you can review it.

Import copies content — it never deletes or changes your original tool files. Your own KISMET.md and AGENTS.md are never offered as sources. You can reopen the panel any time with /import to pull in configs you add later; each import appends to your existing file rather than overwriting it.

Write the instructions

Use plain Markdown. Keep it to durable facts the agent cannot infer from the Blueprints, because these instructions are sent on every turn.

Example prompt

# Project conventions - Custom events are prefixed Evt_. - Gameplay logic lives in BP_GameMode and its components, never in level Blueprints. - Never place Delay nodes inside an Event Tick. - After any graph edit, compile and report errors before continuing.

Apply changes

Kismet reads the instruction file the first time the agent runs and caches it for the editor session. After you edit the file, restart Unreal Editor so Kismet picks up the new version. Keep the file short and high-signal, since it is included on every turn.