القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when user requests a single standalone UI element — a button, form, card, input, or similar — with no broader feature context
Use when something is broken — error messages present, user says broken/not working/bug/fix/error
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
| 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 |
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".
Only when the user explicitly runs /new-vipps-project. Never trigger on keywords alone.
setup skill inline (do not dispatch a subagent): scaffold all files exactly as defined in ../setup/SKILL.md.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 |