PrimeUI Page Builder

Use this skill when the user asks to build or edit a local page in an exported PrimeUI project.

PrimeUI Responsibilities

PrimeUI supplies candidate scoring, registry metadata, component delivery, props validation, and automatic external-planning diagnostics. The coding agent owns task interpretation, exported-project inspection, local file edits, ordered block state, and local verification.

Readiness

1. Confirm .primeui/project.json exists at the exported project root. If it is missing, run npx @primeuicom/cli setup --ai-preset <agent> only after classifying the target as an empty directory or an existing Next.js project. The setup command exports a complete starter into an empty directory and performs a non-overwriting connection for an existing Next.js project. In an interactive local task with no organization profile, allow guided setup to collect or accept email and organization name, complete the emailed command through its masked prompt, and resume without Prime Studio or GitHub OAuth. In a non-interactive local chat, pass only the non-secret email and organization name so setup can send the email, ask the user to run the secret emailed command in their terminal, and then rerun setup. Never copy bootstrap secrets into chat or artifacts. Stop on any other non-empty target.
2. If the MCP client starts outside the exported project, pass explicit projectRoot to PrimeUI MCP tools.
3. Verify PrimeUI MCP health before planning with npx @primeuicom/mcp@latest --health /absolute/project/path.
4. For local or staging Studio, set PRIMEUI_API_BASE_URL to the intended Studio URL before health checks or MCP calls. For production, use the linked project config unless the environment intentionally overrides it.
5. Stop before planning or editing if readiness still fails after safe setup. Ask the user to complete the CLI-guided email step, rerun PrimeUI AI setup, pass the correct projectRoot, or fix the API base/key.

Task Intake

Before planning, identify: