> ## 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.

# Evaluate Vise in 15 minutes

> Inspect a real app and review a grounded Vise plan before using production credentials or changing code.

This evaluation shows how Vise reads an app, identifies the integration surface, and asks for decisions an AI agent should not invent. It deliberately stops before implementation, so you can assess the workflow without production credentials or source changes.

<Info>
  Vise requires Node.js 20 or newer. Vise itself runs locally and does not upload your source code, file contents, or search queries. Your AI coding host follows its own data policy.
</Info>

## Run the evaluation

Use a clean branch or disposable copy of a real app repository.

<Steps>
  <Step title="Verify the package">
    ```sh theme={null}
    npx -y -p @amityco/social-plus-vise vise doctor
    ```

    Confirm that the command reports the installed version and hosted documentation source.
  </Step>

  <Step title="Inspect the app">
    ```sh theme={null}
    npx -y -p @amityco/social-plus-vise vise inspect .
    ```

    Review the detected platform, app surfaces, design signals, sensors, and scan coverage. If the scan is incomplete or several app surfaces are detected, select the concrete app before continuing.
  </Step>

  <Step title="Request a compact plan">
    ```sh theme={null}
    npx -y -p @amityco/social-plus-vise vise plan . \
      --request "Add a social feed to this app" \
      --summary
    ```

    A useful plan identifies the implementation path, cites relevant social.plus documentation, and lists unresolved project decisions such as region, route, feed scope, and target source.
  </Step>

  <Step title="Review the stopping boundary">
    Do not invent answers or run `vise init` during this short evaluation. The expected result is a grounded route and a reviewable decision list—not generated code or runtime proof.
  </Step>
</Steps>

## What this proves

* The package can run in your environment.
* Vise recognizes the intended app surface and supported platform.
* The plan is grounded in social.plus documentation and local project signals.
* Missing product and integration decisions are explicit instead of silently guessed.

## What this does not prove

* That an SDK or UIKit integration has been implemented.
* That `vise check`, project sensors, or the app runtime will pass.
* That the selected social surface works with your tenant data and credentials.

## Choose the next path

<CardGroup cols={3}>
  <Card title="Custom SDK UI" icon="code" href="/ai-mcp/vise/sdk-custom-ui">
    Build a differentiated app-owned experience directly on the social.plus SDK.
  </Card>

  <Card title="UIKit quick launch" icon="window" href="/ai-mcp/vise/uikit-quickstart">
    Use prebuilt social.plus UIKit surfaces and the lowest suitable customization level.
  </Card>

  <Card title="Brownfield and day 2" icon="rotate" href="/ai-mcp/vise/brownfield-day2">
    Add a feature to an app that already uses social.plus without losing earlier evidence.
  </Card>
</CardGroup>