blackviperxiii-ui/vstack
Viper's skill stack: viper-mode, how, why, architect, blast-radius, interrogate, follow-through, qa-walkthrough, principle and formal verification skills for Cursor agents.
Sketch types, signatures, and module boundaries before code; implement against the sketch. "Design this". /architect.
AV ship gate. Playback, sync, codecs, devices; ffprobe/ffmpeg; ship/no-ship. /av-qa-walkthrough
Promote beta to main, bump VERSION/CHANGELOG, bag and tag vX.Y.Z, publish GitHub Release artifacts, verify install paths. Explicit user ask required. /bag-and-tag
Vet a perf number before you report or act on it. /benchmark-checklist.
What a change could break beyond the diff; prove the one fact it's safe because of by running real code. /blast-radius.
Google Chrome's Manifest V3 guide for building, debugging, and publishing Chrome extensions (manifest, service worker, content scripts, side panel, chrome.* APIs, Web Store review). Use only for Chrome extension work. /chrome-extensions
Make repeated agent mistakes impossible; architecture, types, lint, test, docs last. /correct.
Project skill that formally verifies a high-cost, low-test property. /create-formal-verification-skill.
Project skill that drives the real app and proves behavior. /create-verification-skill.
Raise UI craft toward premium, modern, fluid feel. Hierarchy, type, color, space, motion, states, anti-slop. Not a feel diagnosis. /elevate
Design an auditable playbook when none fits; big migrations, multi-part changes, work reviewed later. /figure-it-out.
Ledger, check-ins, stall detection, status updates; proven done and handoff. /follow-through
How does X work? Walkthroughs before a change, where code should live. Use why for motivation. /how.
Goals.
Adversarial review; only findings proven by a run survive. "Tear this apart". /interrogate.
Catch user up since last message; list waiting decisions decidable from the reply alone. Use for /ketchup.
/ketchup as short subtitled slide video; waiting calls under it. Use for /ketchup-video.
Whole-app feel dive. Find where UX, interactivity, QoL, and code miss the mark; ranked low-effort fixes. /land-it
Resync formal verification after code drifts. /maintain-formal-verification-skill.
Audit verify skill + feature map; one PR max. /maintain-verification-skill.
Google Chrome's modern web platform guides (HTML, CSS, client JS, a11y, forms, performance, security), read locally. Use when writing or changing web frontend UI code; not backend, infra, or tooling. /modern-web-guidance
App performance optimization. Measure the real artifact, find hot spots, fix root causes, remeasure. Not a number-vetting checklist or a product-feel dive. /optimize
Fixes sharing one premise keep failing the same gate. Test the premise first.
Validation, errors, adapters. Guard at boundaries; trust types inside; pure logic.
Non-trivial work. Build the script, codemod, or check that does or proves it.
Product or UX tradeoffs. User delight over implementation convenience.
Before measuring or trusting a measured number. Find its limiter.
Debugging. Fix first wrong decision; guards only for legitimate state.
Before writing logic. Data structures first; scaffold before features.
Steps that run amid crashes and retries. Same end state however prior runs ended.
Hard-to-trace code. Fewer layers to trace, less state to hold.
Stateful logic or heavy branching. Encode the domain in a structure.
About to ask "should I?" on reversible work. Do it, show it.
Planned rewrites and migrations with phase boundaries. Converge on the target; skip throwaway compatibility code.
Before declaring done. Verify the real artifact, not a proxy.
New requirement. Redesign as if it was day one.
Concurrent writers to one target. Remove the sharing; lock only for a real invariant.
Multi-step work and commit stacks. Small units, each checked before the next.
Before adding or refactoring. Remove dead code and stubs first.
Writing or keeping a test. Assert what users observe, not internals.
Designing types or signatures. Make illegal states unrepresentable.
Ultimate ship check. Walk the real app, review all code, hunt security holes, vulnerabilities, slop, missing tests and optimizations; fix safe items; one ranked ship/no-ship report. /qa-walkthrough
Rebuild recent working context from chat history, live repo state, and the shared record; tight current-state brief. "Where did I leave off". /recall.
Mine this conversation for durable learnings and route each to a concrete skill edit, after your approval. Use when the user says reflect. /reflect.
Install and configure Viper Stack for the current coding agent (Cursor, Claude Code, Codex, Antigravity, Muse, Windsurf, OpenCode, Grok Build).
Deepen then rewrite. /sharpen.
Reviewable decision trail for long or unattended work; append-only TSV, one row per decision. Local by default, commit when a reviewer needs it. /show-me-your-work.
Build faux product UI that looks like a real product, as a still or an animated cursor demo. Browser and app windows, dashboards, phones, notifications, terminals, bento grids and walkthroughs, framed for a marketing page, feature card or docs hero. Use for any fake or mocked UI, product demo animation, hero or feature-card illustration, or animated cursor in an interface. React and plain CSS. /stageshow.
Mermaid statechart of how a system moves; bugs as numbered paths. Use for /statechart.
Fan out N parallel workers, drain them, one report. Coverage, races, gauntlets. /swarm.
Failing test first for a bug, only when asked or the test path is cheap and obvious. /tdd.
Explain a body of work so a person truly understands it. Runs how and why, then one plain account at their pace. "Teach me this". /teach.
Layered writing standard (Diátaxis, Google developer style, STE, Global English) for docs, RFCs, readmes, PR descriptions, commit messages. /technical-writing.
TypeScript rules for .ts/.tsx files.
Cut AI tells from any writing.
Find everything in an app that needs updating (deps, advisories, toolchains, CI, game addons, mod sources, model ids, APIs); safe bumps as PRs, the rest as cards. /updater
Viper Stack rigor with concise replies, deliberate subagents, verified work. Auto or Composer 2.5 Standard. /viper-mode or serious playbooks.
Why does X work this way? Design rationale, regressions, postmortems, where a number came from. Cited read across every evidence source. Use how for runtime. /why.