Start the CoreAI Sandbox dev server and open it using available browser tools. USE WHEN: the user asks you to "start the app", "run the dev server", "open the app", or "launch CoreAI Sandbox".
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Run the app startup and then open the app using the available browser tools. Use terminal commands and process-management tools appropriate to the current operating system.
Read the local setup guide before starting the app. Run commands from this app's directory.
Complete the Replica canvas preflight before preview startup. Use the running app's URL in the Replica canvas for the visual preview and the browser workflow for separate rendered checks.
First, check whether CoreAI Sandbox is already running at http://127.0.0.1:5174/. Verify the page belongs to this app before reusing the server. Vite defaults to strict port 5174; if another app occupies it, leave that server untouched and use npm run dev -- --port <available-port>. Use the URL printed by the server.
If startup fails because dependencies are missing, run npm ci from this app's directory. Report persistent setup errors.
If no CoreAI server is running, start npm run dev using the available terminal tool's background execution. Keep the returned process or session identifier so the server can be stopped later. If the user needs the server left running after the response, use supported persistent background execution when permitted. Stop assistant-owned session-attached validation servers before finishing, and never stop a user-owned server without permission. If persistent background execution is unavailable, explain the limitation instead of promising a persistent server.
Do not poll the terminal or add artificial delays. Use the initial execution output or an automatic notification, when provided, to identify readiness or errors, and verify that the app responds at its URL. Use the available terminal tools with the returned identifier when background output is needed or the server must be stopped. Target the specific process or session, not all processes with the same executable name. A persistent server need not exit to be ready.
Once the server is ready, discover the available browser tools to open, inspect, and interact with its printed URL. If the first navigation occurs while Vite is still compiling and renders blank, confirm the server is responsive and reload once.
If browser tools are unavailable, give the user the URL instead of restarting the workflow. Leave a user-owned or permitted persistent background development server running; apply the assistant-owned session-attached-server cleanup rule above.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Audits actual components and routes against applicable WCAG 2.2 A/AA criteria using consumer-owned design-system evidence and repository tools. Use when asked for an accessibility audit, a11y check, keyboard or focus review, contrast check, or screen-reader verification.
The English summary is being prepared. Showing the original description.
Creates or updates believable deterministic raw fixture scenarios without breaking an existing prototype. Use when asked to add or change fixtures, seed data, sample data, scenarios, or cross-record relationships. Not for UI redesign, live-data infrastructure, or unrelated commands.
The English summary is being prepared. Showing the original description.
Use for explicit agent-browser CLI checks or a named browser capability neither the Copilot canvas nor configured Playwright MCP can supply. Ordinary rendered checks and browser selection belong to browser-canvas-validation.
The English summary is being prepared. Showing the original description.
Use the Copilot browser canvas first for rendered route checks, interaction tests, screenshots and visual, responsive or accessibility evidence. Use configured isolated Playwright MCP only when the canvas is unavailable for a required check.
The English summary is being prepared. Showing the original description.
Review Replica pull requests using the same shared conventions and project guides as implementation agents. Use when reviewing changes to code, tests, workflows, or documentation in this repository.
The English summary is being prepared. Showing the original description.
Reviews existing UI components for design-system consistency, states, responsiveness and accessibility using consumer-owned context. Use when asked to review component quality, check design-system adherence or audit component consistency.
The English summary is being prepared. Showing the original description.