| name | new-vipps-project |
| description | 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. |
| user-invocable | true |
New Vipps Project Skill
This skill is the explicit entry point for the Vipps frontend stack. It exists to avoid clashes with other installed plugins that may catch generic phrases like "make a webpage" or "new project".
When This Fires
Only when the user explicitly runs /new-vipps-project. Never trigger on keywords alone.
What To Do
- Tell the user in plain English: "Starting your Vipps frontend project — React, Vite, TypeScript, Tailwind, and IndexedDB"
- Ask: "What is this project for? (One sentence is fine — or just say 'skip' and I'll scaffold a blank project.)"
- Run the
setup skill inline (do not dispatch a subagent): scaffold all files exactly as defined in ../setup/SKILL.md.
- After scaffolding, tell the user in plain English: "Your project is ready. Describe what you want to build and I'll get started."
After Setup: Plugin Lock-In
Once this skill fires, all subsequent user requests in this conversation are routed through the frontend plugin skill table defined in the plugin CLAUDE.md — regardless of what other plugins are installed. Do not hand off to other skills that are not within this plugin unless asked directly to do so.
Skill routing priority (from CLAUDE.md):
| Priority | Skill | Trigger |
|---|
| 1 | debug | Error present, or "broken / not working / bug / fix / error" with primary intent to resolve a failure |
| 2 | deploy | "deploy / publish / go live / release" |
| 3 | setup | "new project / start / set up / scaffold" |
| 4 | indexeddb | Data persistence primary intent, no UI requested |
| 5 | component | Single named standalone UI element, no broader context |
| 6 | feature | Default — everything else |
Rules
- Never ask about technology choices — the stack is fixed
- Never ask about infrastructure — deployment is always AKS
- Speak in plain English — no technical jargon unless the user initiates it
- On ambiguity: assume and state the assumption briefly, then proceed
