vippsas

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

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.

Use when user starts a new project, says "new project", "start", "set up", or "scaffold"

Use whenever running tests in this project — verifying a fix, validating a PR, running the suite after changes, or checking a single file. Covers which command to use, how the `better-sqlite3` ABI rebuild fits in, and how to target individual files.

Detect documentation pages whose covered code has drifted and open one doc-sync PR per stale page. Use when running the documentation wiki's self-firing lint (scheduled or on demand), or when asked to sync the architecture docs with the code.

Create GitHub issues from agent findings, bugs, regressions, UX problems, or follow-up work. Use when the user asks to create, file, or draft a GitHub issue and the result should be a structured issue body plus a `gh issue create` command.

Sweep the GitHub issue queue and deliver one reviewable PR per labeled issue. Use when running the autonomous issue pipeline's self-firing sweep (scheduled or on demand), or when asked to process issues labeled `llm-github-issue`.

Watch a video that Manifold has pre-staged. Manifold's main process downloads the video, extracts auto-scaled frames with ffmpeg, and produces a timestamped transcript (native captions or gpt-4o-transcribe). This skill receives the report path and tells Claude to read each frame.

Create GitHub pull requests for completed fixes or features. Use when the user asks to prepare, push, or open a PR and the result should include a meaningful remote branch name, commit, and PR title tied to the actual bug fix or main change rather than an agent or worktree name.

Manifold design system — philosophy, principles, and patterns for UI work. Use when creating or modifying UI components, styling, theming, layout, or any visual aspect of the application.