Vise runs on your machine. It fetches public social.plus documentation and SDK version information, but it does not upload your source code, file contents, or search queries.
Who should use Vise
- Developer using an AI coding agent — Install the skill, ask for the SDK feature, answer project-specific questions, and let Vise drive the loop through plan, check, and sensors.
- Technical lead or reviewer — Review the
sp-vise/contract, deterministic findings, attestations, andvise check --ciresult before accepting the integration. - Partner or solutions engineer — Use Vise as a repeatable delivery workflow across customer apps so each integration ends with the same local evidence, not just a prompt transcript.
- Product or design owner — Use advisory design and experience outputs to review whether the generated surface fits the product intent. Correctness and explicit completeness checks remain the gates.
Install
Install Vise globally:Install the AI skill
Vise includes a bundled skill that teaches your AI coding tool when to inspect, plan, fetch docs, edit code, validate, and ask you for missing decisions. Choose the target for your tool:Typical workflow
Open your project in your AI coding tool
Work inside the app repository where you want to add social.plus SDK features.
Let the agent run Vise
The skill guides the agent through
vise inspect, vise plan, vise init, docs lookup, implementation, vise check, and vise run-sensors.Answer project-specific questions
Vise asks for values the agent should not invent, such as region, feed target, community ID source, platform scope, or design-system source.
What Vise checks
Vise focuses on the mistakes that commonly slip through AI-generated SDK code:- SDK setup and region configuration
- session renewal and login lifecycle
- secret handling and committed environment files
- Live Object and Live Collection usage
- feed, comment, chat, notification, community, follow, story, and moderation patterns
- feature completeness such as pagination, composers, unread state, and selected optional capabilities
- local project sensors such as build, lint, typecheck, and SDK import smoke checks
Vise and the docs MCP server
The two tools work well together:| Tool | Best for | Runs where |
|---|---|---|
| Docs MCP server | Searching and reading social.plus documentation inside an AI chat | Hosted at https://learn.social.plus/mcp |
| Vise | Planning, validating, and sensor-running an integration in your app repository | Local CLI in your project |
Add Vise to CI
After the first successful integration, commit the generatedsp-vise/ contract with your app and run Vise in CI:
vise check --ci for read-only verification. Use vise sync locally during implementation after a green check to persist deterministic-pass evidence.
Related docs
AI / MCP overview
Connect your AI tool to the hosted social.plus documentation MCP server.
SDK Quick Start
Install and initialize social.plus SDKs for your platform.
Authentication
Understand user login, session renewal, and regional configuration.
Live Objects and Collections
Build realtime SDK features with the correct lifecycle.