Start a new chat
Separate the job from unrelated context.
PLATFORM GUIDE · GEMINI
Use a Loadout
with Gemini
Upload the Markdown file or paste its complete contents into a chat. Ask Gemini to collect inputs first and use structured Markdown when no specialized renderer is available.
RUN IT
Four controlled steps
The interface differs; the safety contract stays the same.
Add the file or paste Markdown
Use Add files, or paste the complete `.loadout.md` contents.
Confirm the order
Tell Gemini to collect inputs before Steps and never skip Never or approval.
Accept the fallback
When a specialized renderer is absent, return tables, status and diagrams as structured Markdown.
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
Reads Markdown and follows the core workflow
Tested02
File
Gemini Apps accepts most file types and code within account limits
Supported03
Tools / MCP
Do not claim a tool until the client exposes that capability
Surface-dependent04
Visual
Charts are available for some data tasks; other output uses Markdown fallback
Task-dependentLIMITS
Know when to stop
A correct blocked result is safer than pretending a missing capability exists.
- File features and limits differ by account.
- Gemini Apps, API and coding clients do not expose identical tools.
- If a declared capability is unavailable, stop and return a blocked outcome.
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.