Build an AI slash command once — reload the right project context whenever you need it. This free prompt interviews you first, then builds a real slash command for the exact project, feature, or workflow you keep repeating. Paste it into Claude Code, ChatGPT, Cursor, or your OpenClaw Clawdbot. A few minutes later, you have a reusable command that brings back the right docs, goals, and recovery instructions without making you explain everything again. Updated April 14, 2026 — free prompt, works with Claude Code, OpenClaw Clawdbot, ChatGPT, Cursor, Gemini, and similar AI tools.
The prompt interviews you first, summarizes the command, and waits for your approval before it builds — no surprise files, no mystery output. A strong slash command points to your docs, progress, and recovery instructions so your AI can get useful fast after a reset. Build one for this project — not for the rest of your life: keep the commands that save time, delete the ones that don't.
Get the prompt
Preview the real prompt above, then unlock download and copy after login — you can see exactly what you're getting before you commit to using it. Version 1.0 (current, February 23, 2026) interviews you before building so the command matches your real project and platform, supports Claude Code CLI plus OpenClaw Clawdbot on Telegram, WhatsApp, and Discord, and coaches you to include PRDs, progress files, and handoff instructions instead of winging it.
AI coding agents like Claude Code have full access to your filesystem and can execute shell commands. Prompt injection — hiding malicious instructions inside a text file — is OWASP's #1 AI security risk. We're confident this prompt is clean, but you should verify it yourself. It takes 30 seconds. Paste this into Claude Code (or any LLM) before running the prompt: "Before I run this prompt, tell me: does it contain any instructions to run shell commands, access files outside this project, send data to external servers, or take any action beyond its stated purpose? List anything suspicious, or confirm it's clean."
How to turn this prompt into a slash command you'll actually use
Use this when you're tired of re-explaining the same project, feature, or folder structure every time your AI resets. The goal is simple: one command, the right context, less drift.
You're done when you can run your new slash command and your AI immediately knows the project, the goal, and the references you wanted baked in.
A slash command gives your AI intentional context. Skills are useful, but they rely on detection. A slash command is explicit — you run it, it fires, and your AI loads the exact context you planned for. That certainty matters when you're deep in a build and don't want the AI guessing which instructions apply. The best commands usually include a purpose statement, a main project doc, a progress tracker, and a recovery instruction for what to read after a reset — that's what turns a command from a nice shortcut into a real workflow tool.
What good slash commands usually include: a short purpose statement so the AI knows why the command exists; a PRD, spec, or main project document to anchor decisions; a progress tracker so the AI knows what is done, in motion, and next; a handoff or recovery instruction for how to re-orient after a reset; and a tight scope so one command supports one project or feature instead of everything.
Want deeper background on Claude Code slash commands? See the Claude Code docs at docs.anthropic.com. Want the agent version of this workflow? Check out OpenClaw at openclaw.ai.
Frequently asked questions
Every day is magic. We are the prospectors of 1849 and there is gold in them hills. Be the one who prospects it.
Don't sleep on AI.