/clarify
Ask only the questions whose answers materially change cost, architecture, safety or user experience. Put the recommended answer first.
Slash commands are not universal. This reference names the exact product surface, links to first-party documentation and labels every entry as a literal control, documented workflow or portable prompt pattern.
These seven labels are Maviter shorthand, not secret platform commands. Paste the full instruction after the label, or save it in the platform’s supported instruction system.
Ask only the questions whose answers materially change cost, architecture, safety or user experience. Put the recommended answer first.
Identify time-sensitive claims, prefer primary sources and separate sourced fact from inference.
Convert the approved outcome into phases, dependencies, acceptance checks and freeze boundaries.
Inventory existing behaviour, data and infrastructure that the next change must preserve.
Repeat act, test, inspect evidence and correct—then stop at completion, the attempt limit or an approval boundary.
Evaluate the result against approved requirements and report evidence-backed defects by severity.
Record exact state, revision, next action, risk, secret boundary and rollback for the next operator.
Ongoing writing, study, research and mixed-media projects
Official reference: OpenAI: Projects in ChatGPT ↗Keep related chats, files and project instructions together for ongoing work.
Set project-specific guidance for tone, format and working method without changing global instructions.
State which supplied files and approved web sources may support the answer.
Repository work that needs instructions, evidence and code review
Official reference: OpenAI: Codex developer commands ↗Store repository and directory-scoped working agreements in version control.
Replace an overlong transcript with a concise continuation summary when context grows.
Start a review of uncommitted changes or compare the current work against a base branch.
Long-running coding work with project rules and bounded permissions
Official reference: Anthropic: Claude Code memory ↗Provide concise project standards, common commands and architecture context.
Generate or improve a starting project instruction file after repository analysis.
Inspect first, name affected files and checks, then edit only the approved scope.
Multimodal analysis, long context and terminal-based project work
Official reference: Google: Gemini CLI commands ↗Load hierarchical project instructions into Gemini CLI sessions.
Inspect the concatenated context currently supplied by instruction files.
Attach the contents of a named file or directory to the current prompt.
Repository-aware assistance, code review and team conventions
Official reference: GitHub: Custom instruction support ↗Provide repository-wide instructions in the Copilot surfaces listed in GitHub’s compatibility matrix.
Where supported, apply specialist rules only to matching files instead of overloading global context.
Name the desired behaviour and required tests before requesting implementation.
Long documents, reference-led synthesis and structured writing
Official reference: Moonshot AI: Prompt best practices ↗Tell Kimi to answer from supplied reference text and say when the answer is absent.
Summarise long material in bounded sections before producing a summary of summaries.
Separate context, task, constraints and output format with visible delimiters.
Current-web research that should retain sources and project context
Official reference: Perplexity: Projects (current page on a legacy permalink) ↗Keep searches, files, instructions and collaborators inside one persistent workspace.
Add trusted links or domains when the research must privilege named sources.
Return each material claim beside its source and note any unresolved disagreement.
Web and X research combined with code-backed analysis
Official reference: xAI: Tools overview ↗Combine web sources with X posts when both evidence classes are relevant.
Use code execution for calculations and analysis instead of prose arithmetic.
Separate official facts, reported claims and social signals in the final answer.
OpenAI-compatible API workflows with explicit output contracts
Official reference: DeepSeek: Models and capabilities ↗Choose thinking or non-thinking behaviour deliberately for the task and latency budget.
Use the documented structured-output capability when downstream code requires JSON.
Test the selected model, schema and tool behaviour before changing production traffic.
Self-hosted or enterprise inference with observable health
Official reference: NVIDIA: NIM LLM API reference ↗Inspect the model identifier currently served before sending inference requests.
Route traffic only after the loaded model reports readiness.
Record the endpoint format, model ID, tool support and fallback before deployment.
Work grounded in Microsoft 365 files, pages and notebooks
Official reference: Microsoft: Copilot Notebook instructions ↗Set persistent topic, tone and response-format guidance for a Copilot Notebook.
Ground the notebook in the relevant Word, Excel, PowerPoint, PDF or OneNote material.
Pattern source ↗Return recommendation, evidence, trade-offs, owner and next action in one reusable page.
Professional chat, coding and knowledge-backed agents
Official reference: Mistral AI: Vibe overview ↗Choose the product mode that matches professional work, coding or turn-based chat.
Connect an agent to an approved Library when its answers must use a controlled knowledge set.
Pattern source ↗Name allowed references, prohibited assumptions and the required evidence in the output.
Use the reference to choose product-native controls. Use Maviter when the job needs decisions, phases, checks and a saved handoff.