Choose chat or Project
Use a chat for one job, or add the file to Project Files for repeat use.
PLATFORM GUIDE · CLAUDE
Use a Loadout
with Claude
Attach the file in a chat for a one-off job, or keep it in Project Files for repeat use. Connect any declared MCP tools before starting.
RUN IT
Four controlled steps
The interface differs; the safety contract stays the same.
Attach `.loadout.md`
Use Add files or photos, or paste the complete Markdown.
Connect declared tools
Enable only the MCP or connector named by the Loadout and inspect its source first.
Request the suitable output
Claude can adapt among structured Markdown, a custom visual or an Artifact when those capabilities are available.
START COMMAND
Tell the client what must not drift
Paste this after attaching or pasting the Loadout.
Load this Loadout and follow it exactly. 1. Summarize Purpose, Risk, prerequisites and unavailable tools. 2. Ask only for missing inputs before doing the Steps. 3. Never skip Never, approval or Done means. 4. Use the declared output format; fall back to structured Markdown.
CAPABILITY
What is actually supported
Status separates the portable core from account-dependent capabilities.
01
Core Loadout
The chat follows the structure and workflow
Tested02
Project
Files can remain context across multiple project chats
Supported03
MCP
The connector must be enabled and authenticated by the user
Connected support04
Visual
Custom visuals and Artifacts depend on product surface and settings
Multiple pathsLIMITS
Know when to stop
A correct blocked result is safer than pretending a missing capability exists.
- Project files and chat memory are not the same thing.
- Do not install an MCP dependency without an inspectable source.
- Artifact or custom-visual rendering is optional, so Markdown fallback remains required.
PRIMARY SOURCES
Product facts, not assumptions
Capabilities can change; check these sources and the tested date.
Core flow tested by AILoadout on 23 Jul 2026; connected capabilities remain account- and surface-dependent.