Professional macro design with MCP
Use Codex, Antigravity, Kiro, Claude Code and other compatible tools to turn complex goals into small, testable workflows.
What should a connected assistant know?
The current program contract, central AI Guide, real module settings, project resources and the connected device’s open-project state. Check timestamps and distinguish an old cloud revision from a local draft.
Ask the right question
“Which game should I launch?” is not appropriate for every request. If the user is already in the desired scene, begin there. Ask only for missing details that block progress: a path, target window, image resource or turning keys.
Let the assistant structure the work
- Define the goal and completion criterion.
- Inspect existing steps and resources.
- Separate preparation, main actions, common checks and recovery.
- Use loops for repetition, conditions for state differences and group calls for reusable tasks.
- Observe the results of real input.
- Give one clear local-selection instruction and save the pending action in the design task.
- Verify the resource when the user returns and resume that task.
- Report structural validation separately from actual desktop testing.
Prompt: organize a large project
“Inspect my open project from current device data. Preserve step, image and group IDs. Find repetition and propose helper groups. Replace unnecessary fixed waits with appropriate observations. Add failure paths and loop limits. Explain planned changes, then update only relevant steps and validate.”
Prompt: start from the current scene
“The application is already open where the task starts. Verify its window and current resources. If a target needs a local image selection, explain only that action. Once saved, connect tracking to a condition, prevent actions on a missing target and add result verification and recovery.”
Credentials, rights and images
Place your personal key in the appropriate client settings. This site contains no access credential. MCP access differs from file-transfer permission. Workflow metadata can be inspected and edited, while image files are not downloaded/uploaded through MCP.
Human-controlled execution
An assistant saying “delivered” is not enough. Check queue state, device receipt, loading into the local project and local Start separately. Use dry run and a small real test before the full task.