vcoding

Enforce data-centric engineering standards across code review and generation.

Updated May 28, 2026
One-click install
npx skills add https://github.com/Kagayachan/md_files --skill vcoding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vcoding
Source: https://github.com/Kagayachan/md_files/tree/main/cursor
Command: npx skills add https://github.com/Kagayachan/md_files --skill vcoding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates vague, bloated, and unverified code generation by enforcing a strict, data-first engineering doctrine that prioritizes simplicity, hardware reality, and reproducible verification.

Core Features & Use Cases

  • Surgical Code Review: Provides a framework to identify and reject bogus abstractions, enterprise sludge, and hack-upon-hack implementations.
  • Verification-First Development: Mandates that every technical claim, performance improvement, or bug fix be backed by reproducible tests, benchmarks, or explicit execution records.
  • Use Case: When refactoring a complex legacy module, use this Skill to define the data structure first, identify the smallest defensible change, and generate a test-backed implementation that preserves existing userspace contracts.

Quick Start

Invoke the vcoding skill to audit the current repository changes against the Torvalds Doctrine and generate a task_details.md file for the requested feature.

Frequently Asked Questions about vcoding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce evidence-driven coding standards during code review?

Evidence-driven coding standards are enforced by mandating reproducible tests, benchmarks, or explicit execution records to back every technical claim and bug fix during peer review.

What is the best way to refactor complex legacy modules while preserving existing userspace contracts?

Refactoring complex legacy modules requires defining the data structure first, identifying the smallest defensible change, and generating a test-backed implementation that preserves existing userspace contracts.

How do I eliminate vague abstractions and enterprise sludge in architectural design?

Vague abstractions and enterprise sludge are eliminated by applying a data-first engineering doctrine that prioritizes simplicity, minimal abstraction, and strict adherence to system contracts.

Can I use a data-centric doctrine for debugging complex technical projects?

A data-centric coding doctrine applies to debugging complex technical projects by requiring explicit verification and strict adherence to existing system performance constraints.

When do I need verification-first development for software engineering?

Verification-first development is needed when generating code for complex technical projects to ensure performance improvements and bug fixes are backed by reproducible tests and benchmarks.

Why does unverified code generation fail in complex technical projects?

Unverified code generation fails by producing bloated implementations that ignore hardware reality and system contracts, which evidence-based coding standards eliminate through strict data-first verification.