Verify approved user-visible acceptance criteria through browser or desktop UI scenarios with traceable evidence; excludes general service/API acceptance testing.
Skills in this repository
visionarycoder/vc.Agentic - Page 17
SkillsMP has collected 728 skills from visionarycoder/vc.Agentic. Open a skill to review its source and details.
visionarycoder/vc.AgenticShowing 40 of 728 collected skills.
Enforce WCAG-aligned semantics, keyboard support, focus management, contrast, screen-reader support, and accessible naming when an agent builds or reviews UI.
Apply visual hierarchy, responsive layout, typography, color, feedback, and interaction-quality patterns when an agent designs or reviews user interfaces.
Implement UI automation and visual verification for WPF, .NET MAUI, and WinUI 3 with platform-fit tools, stable selectors, deterministic data, and observable waits.
Design, critique, read, write, render, and implement UML and UML-like software diagrams. Use when the user mentions UML, sequence diagrams, class diagrams, activity diagrams, state machines, use case diagrams, component diagrams, deployment diagrams, object…
Add and repair unit tests with Microsoft .NET best practices, deterministic assertions, and coverage-gated validation. Use this for unit-test alignment after refactors, generator/analyzer test hardening, and enforcing 80% minimum coverage with explicit…
Always use collocated `.razor.js` files with `export` — never global `window.*` functions or `(script)` tags.
Build, optimize, quantize, compile, and benchmark ONNX models for Windows ML using the `winml` CLI. Covers the Build-Your-Own-Model (BYOM) pipeline across NPU (Qualcomm QNN, Intel OpenVINO, AMD VitisAI), GPU, and CPU execution providers. Use this skill…
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Maintain legacy UWP apps with adaptive UI, MVVM boundaries, Windows integration, and explicit migration decisions toward WinUI 3 when an agent changes user-facing features.
Validate whether an analysis is accurate, well-supported, and ready to share or use for a decision. Use when reviewing methodology, calculations, comparisons, visuals, caveats, or conclusions.
Apply MVVM validation patterns for observable view models, async rules, UI error presentation, and .NET 10 validation flows in desktop applications.
Use when Codex is already in the validation phase of a security scan or the user explicitly asks to determine whether one or more candidate security findings are valid. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Create, evolve, and review VBD Access components using accepted contracts and design, with scoped authoring and review modes.
Review split, merge, communication, proxy, compatibility, scaling, and ownership decisions after base VBD scope exists.
Generate and run automated conformance checks for proxy-only calls, contract dependencies, vault isolation, provider behavior, and naming rules.
Use the dependency-free `vbd-artifacts.js` CLI to validate, graph, plan, score, checkpoint, and report on VBD analysis artifacts.
Fix volatility-driven contract coupling by restoring local DTO ownership, local mapper code, and immediate-layer dependencies.
Design VBD boundaries, contracts, role authority, and team relationship policy without false canonical claims.
Generate normalized candidate estimates for contracts, services, tests, clients, Ifx, Aspire, analyzers, rollout work, and stable `EST-*` records.
Simulate credible policy, workflow, integration, failure, scale, and rollout changes against a VBD candidate and record `CSIM-*` blast-radius evidence.
Apply Juval Löwy Volatility-Based Decomposition (VBD) to code changes. Place each change in the component that owns that volatility.
Scaffold an accepted VBD Manager, Engine, or Access boundary with contracts, services, tests, and explicitly requested hosting or persistence projects.
Convert a selected candidate into a dependency graph with contract-first sequencing, parallel component work, traceability, gates, and resumable checkpoints.
Plan phased cutover with coexistence, routing, data authority changes, observability, rollback, and `CUT-*` wave records.
Validate VBD designs with change simulations, anti-examples, role checks, and acceptance-to-test evidence.
Define immutable VBD DTO records with scope ownership, fluent builders, and explicit mapper boundaries for Manager, Engine, and Access components.
Create, evolve, and review VBD Engine components using accepted contracts and design, with scoped authoring and review modes.
Audit VBD evidence for coverage, confidence, staleness, traceability, and candidate readiness.
Route VBD requests to the minimum skill set by classifying intent, lifecycle phase, boundary type, and correction-versus-authoring scope before loading detailed guidance.
Create, evolve, and review VBD Manager components using accepted contracts and design, with scoped authoring and review modes.
Apply source-backed Volatility-Based Decomposition method guidance with explicit evidence labels and limits.
Score candidates with visible rationale, track actuals against plan, recompute critical path, and publish program metrics in `PORT-*` records.
Standardize versioning, compatibility, observability, health, and correlation contracts across VBD components.
Orchestrate phased modernization from baseline evidence through candidate comparison, selected-plan construction, cutover, and governed artifact checkpoints.
Canonical Juval Lowy volatility-based decomposition rules shared by analyzers, code fixes, generators, and human-authored components.
Combined vbd service contracts guidance with task/provider-specific modes. Generate .NET components that follow Volatility-Based Decomposition (VBD) ServiceModel/RPC patterns with strict boundary enforcement, async-first design, and standardized error…
Build traceable symbol-level evidence that links code, resources, tests, effects, and change drivers.
Design and review volatility-based decompositions using change evidence, owned authority, stable contracts, and repository manager-engine-access conventions.
Build and run a migration harness with routing, shadow execution, tolerance comparison, replay, rollback, and drift monitoring for `UC-*` outcomes.