max-the-prompter

Performs a broad project audit across correctness, architecture, UX, accessibility, security, performance, runtime behavior, and maintainability. Use when diagnosing quality or asking what is wrong with the current project.

Implements an approved plan in coherent, verifiable slices while preserving existing architecture and behavior. Use for actual implementation after requirements and constraints are understood.

Reset Max Prompter's project-context memory boundary so unrelated projects and prior-project notes do not influence the current workspace. Preserve the current chat and current project files. Use when the user wants to start clean or remove cross-project context.

Establishes and enforces a measurable project quality bar, normally persisted as CONSTRAINTS.md. Use when quality standards are missing, inconsistent, or when the user invokes /constraints.

Pressure-tests meaningful decisions through a five-advisor Council using Contrarian, First Principles, Expansionist, Outsider, and Executor perspectives, peer review, and chairman synthesis. Use when the user asks to council, debate, pressure-test, stress-test, validate, or resolve a genuine multi-option decision.

Designs or redesigns user interfaces with a coherent visual system, appropriate component sources, motion, responsive behavior, and rendered-browser verification. Use for website/app UI work and visual polish.

Turns rough ideas, requirements, product requests, code tasks, design goals, research questions, and implementation plans into extremely detailed, execution-ready prompts and orchestrates the appropriate engineering, design, verification, and shipping skills. Use when the user wants a long/detailed prompt, wants an idea expanded into a build specification, asks for an implementation prompt for an AI coding agent, requests architecture-level detail, or wants multiple specialized skills coordinated. Universal across websites, apps, APIs, automations, scripts, data systems, games, tooling, infrastructure, and mixed projects.

Converts a project specification into dependency-ordered, atomic, verifiable implementation tasks. Use after requirements are known and before substantial implementation.

Generates an execution-ready implementation prompt from a user request or project context using the Max Prompter workflow. Use when the user asks for a detailed, comprehensive, long, or production-grade prompt.

General reverse-engineering and debugging workflow for authorized software. Use with /re <program or path> for the default IDA Pro workflow, /re x64dbg [program or PID] for x64dbg, or /re gdb [program or PID] and /re gdp [program or PID] for GDB. Can scan active processes, resolve files, fingerprint targets, launch the selected tool, persist sessions, generate evidence-backed analysis tasks, and resume follow-up queries without losing the target context.

Runs a structured pre-merge review of changes for correctness, architecture, readability, maintainability, security, performance, tests, and accidental scope creep. Use before merging or finalizing substantial changes.

Prepares and verifies a project for production release, including tests, build, deployment configuration, security, observability, rollback, documentation, and launch checks. Use when the user asks to ship, release, deploy, or prepare production.

Install a third-party or local Agent Skill into the current workspace under a clean skills/<skill-name>/ directory, optionally discovering the repository from a skill name, validating the skill, and wiring it into Antigravity's .agents/skills discovery path.

Creates a complete, implementation-ready project or feature specification before code. Use for greenfield projects, substantial features, or ambiguous requests that need explicit requirements and acceptance criteria.

Proves that a project or change works using the smallest useful combination of unit, integration, component, browser, end-to-end, performance, and security checks. Use to verify implementation rather than merely compile it.