Agent skills for Windsurf (legacy)

Implement, test, audit, debug, and harden Verify Checkout hosted-deposit flows in merchant backends, websites, and apps.

Verify all citations in a document against the research corpus

Prove a change actually works before it counts as done.

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session…

Generate a project-local verification skill that drives the app the way a user does — any language, framework, or platform.

Verify a test-program change or conclusion through fresh deterministic evidence and iterative repair.

Use when asked to verify UI changes, check the frontend visually, confirm a page looks correct, test UI interactions, or validate that…

How to check that a Minecraft plugin actually works on a running Paper/Purpur server using VitaminMCP - connecting a session, reading…

Verify the Omnigent CLI's setup/onboarding flow, terminal UI/UX, and critical user journeys in a completely isolated, reproducible loop.

Automatically handles semantic version updates across plugin.json and marketplace catalog when user mentions version bump, update version…

Implement API versioning with backward compatibility, deprecation notices,

Guide for optimizing SQL queries with EXPLAIN ANALYZE, index tuning, N+1 detection, covering indexes, and query plan analysis.

Decide which competitor to take on, and whether naming them helps or hurts, using battle rap matchup logic - the ladder, the crowd, the…

Execute use when provisioning Vertex AI infrastructure with Terraform.

Pre-Production validation — build a production-quality end-to-end build to confirm the full game loop is achievable before committing to…

Vertical Slice Architecture (VSA) for .NET applications — one of several supported architectures in dotnet-claude-kit.

Deep expertise in VHDL language constructs, IEEE 1076 standard compliance, and synthesis coding guidelines.

Use after a brand direction and source of truth are confirmed to produce or maintain VI manuals, logo packages, brand assets, landscape…

Use when making CTO decisions — tech debt, team scaling, architecture, and DORA metrics.

Use when building or auditing frontend UI — components, design systems, or avoiding generic AI aesthetics.

Use when making any code change — trunk-based development, atomic commits, change sizing (~100 lines), and the commit-as-save-point pattern.