Menu
Use when something is broken — error messages present, user says broken/not working/bug/fix/error
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | debug |
| description | Use when something is broken — error messages present, user says broken/not working/bug/fix/error |
Systematic root-cause investigation. Never guess. Always verify the fix.
debugger-prompt.md with all available error information — include the verbatim error message and any file paths the user mentioned. If no error message was provided, instruct the debugger to begin investigation from layer 1 of the stack layers list.vitest run and confirm passing (takes priority over build check)vite build and confirm no errorsvitest runDebug does not use the implement → reviewer control flow. The debugger is self-contained.
Use when user requests a single standalone UI element — a button, form, card, input, or similar — with no broader feature context
Use when the user wants to share their app with others or get a public URL — triggers include "deploy", "publish", "go live", "release", "share it", "I want a URL", "give me a link", "make it live", "show others", "put it online", "launch it"
Use when user describes anything to build — this is the default skill for all feature requests not matched by a higher-priority skill
Internal skill — called by other skills after code is approved and tested. Commits and pushes changes to main. Handles missing git identity and GitHub auth in plain English for non-technical users.
Use when user needs to store, retrieve, or persist data with no UI involved — pure data layer work
User-invocable entry point for the Vipps frontend stack. Triggered explicitly by `/new-vipps-project`. Activates the React/Vite/TypeScript/Tailwind/IndexedDB/AKS plugin context, scaffolds the project, then routes all subsequent requests through this plugin.