start-app
Skill117 starsChanged 10 days agoMITView on GitHub
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".
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run the app startup and then open the app using the available browser tools.
- Distinctive: line 10
Read the local setup guide before starting the app.
- Very specific: line 16
If startup fails because dependencies are missing, run npm ci from this app's directory.
- Distinctive: line 24
If browser tools are unavailable, give the user the URL instead of restarting the workflow.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Start the App
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.
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- dimitrismistriotis/django-agentic-skills★ 3same name
- akimisri17/idea-to-app-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hub/AGENTS.mdAGENTS.md
- starters/coreai/AGENTS.mdAGENTS.md
- starters/minimal/AGENTS.mdAGENTS.md
- replica-pick-and-polishSkill
- replica-publish-prototypeSkill
- review-hub-feedbackSkill
- code-reviewSkill
- write-testsSkill
- coreai-ds-fluentui-reactSkill
- css-stylingSkill
- features-variantsSkill
- iconsSkill
- interpreting-htmlSkill
- lintSkill
- new-variantSkill
- react-componentsSkill
- routingSkill
- state-managementSkill
- context-templatesSkill
- accessibility-auditSkill
- add-seed-dataSkill
- agent-browserSkill
- browser-canvas-validationSkill
- component-design-system-reviewSkill
- create-prototypeSkill
- developer-handoffSkill
- prepare-feedback-proposalsSkill
- product-designSkill
- prototype-controlsSkill
- responsive-auditSkill
- review-hub-feedbackSkill
- setup-skillsSkill
- visual-design-reviewSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.