Menü
Run health checks and fix problems. Checks if the dev server is running, runs lint and build checks, verifies file integrity, and automatically fixes any issues found.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Set up a Mac to run the project. Installs Node.js if needed and runs npm install.
Begin the guided building experience. Helps the user brainstorm an idea and start building their first app.
Set up a Windows PC to run the project. Sets PowerShell execution policy, installs Node.js if needed, and runs npm install.
Context-aware help for when someone is stuck, confused, or needs guidance. Reads the conversation and project state to give specific, relevant help.
Deploy the app to the internet and get a shareable link. Triggers on "$deploy", "deploy my app", "push this live", "put it on the internet", or any deployment request. Handles build verification, deployment to Vercel, and guides the user through sharing their creation.
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
| name | fixit |
| description | Run health checks and fix problems. Checks if the dev server is running, runs lint and build checks, verifies file integrity, and automatically fixes any issues found. |
stop and think:
bugs live where the thinking stopped too soon. the obvious fix isn't always the right one. trace the problem back to where it actually started.
run through this diagnostic checklist. stop and fix at the first failure before moving on.
curl -s -o /dev/null -w "%{http_code}" http://localhost:3000
If it's not responding:
npm run dev &
Wait for it to come up, then continue. If the background process fails to hold, try starting it again with npm run dev &. If it still fails, check npm run build for errors — the dev server likely can't start because of a build error. Fix the build error first, then retry the dev server.
Verify these files exist and are valid:
app/page.tsx — has a default exportapp/layout.tsx — has a default export, wraps children in <Providers>app/providers.tsx — exports Providers component with HeroUIProviderapp/globals.css — has @import "tailwindcss", @plugin '../hero.ts', @custom-variant dark, and a @theme blockhero.ts — has a default export from heroui()If any are missing or broken, recreate them with these essentials:
app/page.tsx — must have "use client" at top and a default export componentapp/layout.tsx — must import Providers from ./providers, wrap {children} in <Providers>, have suppressHydrationWarning on <html>app/providers.tsx — must have "use client", import HeroUIProvider from @heroui/react, export Providers wrapping children in <HeroUIProvider>app/globals.css — must have @import "tailwindcss", @plugin '../hero.ts', @source '../node_modules/@heroui/theme/dist/**/*.{js,ts,jsx,tsx}', @custom-variant dark (&:is(.dark *)), and a @theme block with --font-sans: var(--font-geist-sans), system-ui, sans-serif and --font-mono: var(--font-geist-mono), monospacehero.ts — must import { heroui } from "@heroui/react" and export default heroui()Scan files in app/ and components/ (if it exists) for imports. Check that:
@heroui/react imports are validpackage.jsonFix any broken imports.
npx eslint app/ --fix
The --fix flag auto-corrects what it can. If errors remain after --fix, they need manual fixes — read the errors, edit the code, and re-run to confirm. Don't show raw lint output to the user.
npm run build
If the build fails, read the errors, fix them, and run the build again. Translate any errors to plain language for the user.
tell the user in plain language what was wrong and that it's fixed:
"found a small issue — [description]. fixed it up, you're good now. check your browser."
"everything looks good — your app is running clean."
don't stop. the checklist catches common problems, not all problems.
if you truly can't find the issue after digging:
"hey — i ran through everything and it all looks clean on my end. can you tell me exactly what's happening? like what do you see vs what you expected?"
then work from their description to find the real problem.