What problem does it solve? Adding a second artifact to a Replit pnpm monorepo triggers non-obvious failures—blank previews, port conflicts, broken API routes, and duplicate dependency instances—that cost multiple debugging turns because none of the rules are documented in the artifact creation walkthrough. ## Core Features & Use Cases - BASE_URL prefix discipline: Enforces prepending import.meta.env.BASE_URL to every route and API call so requests stay inside the artifact's path-based mount. - PORT and workflow rules: Requires reading the PORT env var, setting allowedHosts: true in Vite, and using managed workflow names (artifacts/<slug>: <service-name>) instead of configureWorkflow replacements. - pnpm catalog and workspace wiring: Prevents catalog drift from off-catalog pins and wires cross-artifact shared libraries via workspace:* dependencies. - Use Case: When a preview pane goes blank after adding a second artifact, work through the seven-step debug checklist covering workflow state, openPorts, allowedHosts, PORT reading, BASE_URL usage, restarts, and catalog drift. ## Quick Start Ask the agent to diagnose why your Replit artifact preview is blank or why API calls 404 after adding a second artifact to the monorepo.