> ## Documentation Index > Fetch the complete documentation index at: https://learn.social.plus/llms.txt > Use this file to discover all available pages before exploring further. # CLI reference > The Vise commands you'll run most often, grouped by task. This page covers the commands most integrations use. For the complete list and every flag, run `vise --help` or `vise --help`. Each command has an [MCP tool equivalent](/ai-mcp/vise/mcp-server#what-it-exposes) in snake\_case. Most commands take a project path (default: the current directory) and write their state under `sp-vise/`. Commands that change generated code are run by your AI agent through the [skill](/ai-mcp/vise/overview#install-the-ai-skill); the commands below are the ones you or your reviewer run directly. ## Explore and plan | Command | Purpose | | ----------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `vise explore ""` | Map a request to what social.plus offers — no project or API key needed | | `vise inspect [path]` | Detect platform, monorepo surfaces, design signals, and available sensors | | `vise plan [path] --request "..."` | Grounded implementation plan with intake questions and docs citations (`--summary` for a compact view) | | `vise init [path] --request "..." --answer key=value` | Write the `sp-vise/` compliance contract once blocking intake is answered. Initializing a different outcome records the previous engagement to `sp-vise/engagements/` first; replacing a **green** engagement asks for `--supersede-engagement` | For broad requests that span several surfaces (feed + chat + profile), Vise sequences them: | Command | Purpose | | -------------------------------------------------------------- | ----------------------------------------------------------- | | `vise workplan next [path] --request "..."` | Print the next uncompleted surface and its focused commands | | `vise workplan status [path] --request "..."` | Show the sequence and which surfaces are done | | `vise workplan complete [path] --request "..." --surface ` | Record a green-checked surface with snapshot evidence | ## Validate and verify | Command | Purpose | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `vise check [path]` | Validate the code against the recorded contract | | `vise check [path] --ci` | Read-only; exits non-zero unless green | | `vise check [path] --new-only` | Gate only on *rule findings* introduced since the baseline — the outcome's completeness checklist and selected capabilities always gate (they are the engagement's deliverables) | | `vise check [path] --allow-proof-waiver` | Accept an honest `runtime-proof-waived` result as passing | | `vise check [path] --engagement ` | Re-verify one previously completed engagement against the current rules and code (exit `11` on drift, `0` when it still holds) | | `vise check [path] --all-engagements` | The normal check plus re-verification of every recorded engagement; exit `11` means your current work is green but a previously finished surface drifted | | `vise validate [path]` | Run the deterministic validators only (no attestation comparison) | | `vise status [path]` | Summarize the current compliance state, including `previousEngagements` — the last recorded state of surfaces built in earlier engagements | | `vise explain ` | Print a rule's rationale, evidence requirements, and remediation | See [Reading a check result](/ai-mcp/vise/how-it-works#reading-a-check-result) for what each state means. ## Evidence | Command | Purpose | | ---------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `vise baseline [path]` | Snapshot pre-existing rule findings so `--new-only` can exclude them. Record it right after `vise init`, before writing code; the feature you asked for is never baselined — it still has to be built | | `vise attest [path] --rule --signer host-agent --confidence high --evidence-file evidence.json --rationale "..."` | Record that a rule is satisfied through architecture the check can't see | | `vise sync [path]` | Persist deterministic-pass evidence after a green check | | `vise smoke [path] --log ` | Assess a captured mount-smoke log into a pass/fail verdict | | `vise smoke waive [path] --reason "..." --mode declined\|deviceless` | Record an auditable runtime-proof waiver | ## Docs and SDK facts | Command | Purpose | | -------------------------------------- | ---------------------------------------------------------------- | | `vise search-docs ""` | Search social.plus docs for relevant pages | | `vise get-doc-page ` | Fetch a specific doc page by path | | `vise sdk-facts --platform ` | Read bundled SDK surface facts (`--capability`, `--format json`) | | `vise debug [path] --error "..."` | Diagnose an SDK-specific runtime failure | ## Design (advisory) | Command | Purpose | | --------------------------------- | ------------------------------------------------------------------------------------------------------------- | | `vise design extract ` | Extract a graded design contract from an HTML/CSS prototype (`--from-project` to derive from your own tokens) | | `vise design check [path]` | Advisory token-conformance report, including computed WCAG for the brand palette | | `vise design preview [path]` | Write a self-contained visual review for human or VLM judgment | ## Skill and MCP | Command | Purpose | | ------------------------------------ | ---------------------------------------------------------------------------- | | `vise install-skill --target ` | Install the bundled skill (`claude`, `cursor`, `vscode`, `copilot`, `codex`) | | `vise print-skill` | Print the skill markdown to stdout | | `vise mcp` | Start the local [MCP server](/ai-mcp/vise/mcp-server) | | `vise doctor` | Verify the install — version, path, docs source | ## Related The loop behind these commands and how to read results. The MCP tool equivalents of these commands.