Agent-ready workflow

Give coding agents safe context for Unreal projects

ForgeLore gives assistants the same product surface humans use: repository status, recent activity, locks, summaries, connection guidance, dry-runs, and scoped write actions. Keep access explicit and make every agent respect Unreal asset locks.

Safe by default

Start assistants with the scopes they need for the task. High-impact actions still require a human confirmation step.

Codex

Use AGENTS.md so every Codex task starts with project rules, test commands, and Unreal asset guardrails.

Claude Code

Use CLAUDE.md memory to keep project conventions, lock rules, and verification expectations close to the code.

Cursor

Use project rules so agent mode understands what to avoid and when to ask a human first.

MCP clients

Use ForgeLore tools for repository status, locks, activity, and connection info within explicit scopes.

Copy this starter prompt

Paste it into Codex, Claude Code, Cursor, or another assistant before assigning work.

You are helping on an Unreal Engine project hosted in ForgeLore. Project: - Repository: <repository-name> - Lore remote: <lore-remote> - Branch: <branch> - Allowed scopes: <repo:read, activity:read, locks:read, locks:write, summary:create> Before editing: - Read the project rules and Unreal folder conventions. - Check repository status, recent activity, and locks. - Use ForgeLore MCP, CLI, API, or SDK capability discovery before choosing tools. - Do not edit locked binary assets. - Do not commit generated folders such as DerivedDataCache, Intermediate, Saved, Binaries, or local build output. - Run dry-runs before supported writes. - Ask before force unlocks, permanent deletes, billing changes, provider-secret work, infrastructure changes, or destructive bulk actions. Goal: <describe task> Verify: - Run relevant build, test, or editor checks if available. - Summarize files changed, locks touched, and any manual Unreal Editor steps needed.

Agent checklist

Use this before granting an assistant access to a project.

Create or select an active ForgeLore repository.

Issue only the scopes the assistant needs, including write scopes when the task requires them.

Store the token outside source control.

Tell the assistant to inspect locks before editing.

Revoke the token after the task or rotation window.

Codex AGENTS.md

# AGENTS.md This is an Unreal Engine project hosted in ForgeLore. Before making changes: - Inspect the task, project layout, and relevant docs. - Check ForgeLore status, recent activity, and locks when tool access is available. - Do not edit locked binary assets. - Do not add generated folders: DerivedDataCache, Intermediate, Saved, Binaries, or local build output. - Use the repository's existing build and test commands. - Ask before deleting assets, force releasing locks, changing project settings, or touching credentials. When finished: - Report changed files. - Report any locks acquired or released. - Report checks run and manual Unreal Editor steps still needed.

Claude Code CLAUDE.md

# CLAUDE.md You are working in an Unreal Engine project hosted by ForgeLore. Use project context first: - Read local docs and folder rules before editing. - Treat .uasset and .umap files as binary assets that require lock awareness. - Avoid generated folders and local caches. - Keep secrets and access tokens out of commits and chat output. Prefer small, reviewable changes. Explain any Unreal Editor steps a human must complete.

Cursor project rule

# .cursor/rules/forgelore-unreal.md Always apply for Unreal Engine projects hosted in ForgeLore. - Respect ForgeLore locks before editing binary assets. - Do not modify DerivedDataCache, Intermediate, Saved, Binaries, or local build output. - Prefer existing project conventions and build scripts. - Ask before destructive asset operations or project-wide setting changes. - Summarize validation steps and Unreal Editor follow-up work.

Generic MCP instruction

Use this when an assistant connects through ForgeLore MCP tools. Tool access should be scoped, revocable, and guided by the capability manifest.

Use ForgeLore tools to inspect the repository before acting: 1. Get connection info. 2. Read recent activity. 3. List visible locks. 4. Continue only within granted scopes. 5. If a required action is outside scope, explain the missing scope and stop. Never expose bearer tokens, connect tokens, private keys, or payment information.