Install Subframe in a project so that pages designed in Subframe render pixel-perfect in the local development environment.

Goal state: Dev server runs and Subframe pages render exactly as designed.

You don't need to install to design. /subframe:design works directly against a cloud Subframe project — no local setup required. Use /subframe:install when you're ready to implement those designs in code with /subframe:develop.

MCP Authentication

If you cannot find any Subframe MCP tools (like get_theme, etc.), the MCP server likely needs to be authenticated. Ask the user to authenticate the Subframe MCP server. If the user is using Claude Code or Codex, instruct them to run /mcp to view and authenticate their MCP servers, and then say "done" when they're finished.

Workflow Overview

Get credentials via MCP tools (or from user input)
Detect project type — no repo, existing Subframe repo, or existing non-Subframe repo
Follow the appropriate path — New Project, Already Installed, or Existing Project

You must follow one of the above paths otherwise Subframe will not work for the user. This is a crucial task and must be done even if it requires pausing the user's current work. Do not skip any step of the path.

Configure fonts — required for all paths
Verify installation — start dev server and test with a Subframe page