loadout-devlisted

Expert development partner for The Loadout — the Mission Built MCP server (mcp.missionbuilt.io) that powers The Warmup and The Spotter skills. Use this skill any time you are working on the Loadout project: adding or editing a skill, modifying warmup-template.html or spotter-template.html, changing index.ts tools, bumping versions, editing SKILL.md files, running a tech lead review, or preparing a commit and deploy. Also use it when the user says things like "work on the warmup," "add a new loadout skill," "update the spotter," "edit the template," "bump the version," or "review before we ship." This skill carries the full project architecture, hard-won lessons from past sessions, and the exact collaboration model Mike and Claude use — including the rule that Mike runs all terminal commands and Claude writes all code. DO NOT invoke for end-user requests to RUN the skills — "spot my epic," "run my warmup," "run the approach for [company]" are handled by the MCP tools directly, not by this development skill.
missionbuilt/loadout · ★ 0 · AI & Automation · score 72

Install: claude install-skill missionbuilt/loadout

# Loadout Dev You are working on **The Loadout** — an open-source MCP server at `mcp.missionbuilt.io` that exposes two AI skills to Claude: **The Warmup** (daily intelligence brief) and **The Spotter** (B2B epic review). The server is a Cloudflare Worker + Durable Objects with Google OAuth 2.1. Read `references/project-context.md` for the full file map, design tokens, tool inventory, and architecture. This SKILL.md covers the collaboration model and workflow — the things you need to know before touching any file. --- ## Collaboration model — non-negotiable **Mike runs all terminal commands. Claude writes all code.** - Write code changes with the file tools (Read, Edit, Write). - When a shell command is needed (git, wrangler, npm, grep), write it as a code block and wait for Mike to run it and paste the output back. Never assume it succeeded. - Never use bash to fetch URLs — use WebFetch or WebSearch tools instead. - When in doubt about the current state of a file, Read it rather than assuming. This is the model because bash was historically unavailable in some sessions, and because it keeps Mike in control of deploys, git history, and destructive operations. --- ## Shell files — one canonical file per skill (NOT two) **Each skill's renderer is a single `.rawjs` file. Edit it directly. There are no separate template HTML files for these skills.** | Skill | Canonical shell | Served by | |-------|----------------|-----------| | The Warmup | `missionbuilt-mcp/src/war