[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C4M9D400A6HAVWVYA6S4DW":3,"skill-same:01M6C4M9D400A6HAVWVYA6S4DW":100},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":14,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6C4M9D400A6HAVWVYA6S4DW","vhl-concepts",null,"Architectural foundation for Virtual Hardware Laboratory (VHL). Explains the four fundamental VHL concepts (Module vs Assembly, Interface Boundary, Git Worktree Workspace Isolation, and Shared Circuit Understanding Document), why VHL uses them, their core invariants, and when an agent must reason about them. Trigger this skill whenever reasoning about VHL architecture, defining boundaries, identifying module\u002Fassembly scope, or referencing SCUD artifacts.","vivekvjnk\u002Fthree-wise-monkeys","vivekvjnk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F57674825?v=4","01M6C4KWVXPJ0AG14HH8G6R07Y","Vivek Vijayan","01M6C4KX0DKKJ9JGJKMV2K2W54",0,"GPL-2.0","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FVHL_Concepts\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40],"vhl concepts","architecture","core","reasoning","git","artifacts","worktree","boundary","why","git worktree","virtual","workspace","assembly","SCUD","2026-11-10 10:12:30",false,"---\nname: vhl-concepts\ndescription: Architectural foundation for Virtual Hardware Laboratory (VHL). Explains the four fundamental VHL concepts (Module vs Assembly, Interface Boundary, Git Worktree Workspace Isolation, and Shared Circuit Understanding Document), why VHL uses them, their core invariants, and when an agent must reason about them. Trigger this skill whenever reasoning about VHL architecture, defining boundaries, identifying module\u002Fassembly scope, or referencing SCUD artifacts.\n---\n\n# VHL Concepts\n\nThis skill provides the architectural model, core invariants, and progressive-disclosure mapping for the four fundamental concepts in the Virtual Hardware Laboratory (VHL): **Module vs Assembly**, **Interface Boundary**, **Git Worktree Workspace**, and **Shared Circuit Understanding Document (SCUD)**.\n\n---\n\n## 1. Architectural Principle & Knowledge Tiers\n\nVHL separates engineering knowledge into three distinct, decoupled tiers:\n\n```text\nVHL Concepts\n    = What things are and why they exist (Architectural definitions & invariants)\n\nEngineering Methodologies\n    = How engineering reasoning is performed using those concepts\n\nEngineering Workflows\n    = How specific multi-step VHL tasks are executed\n```\n\nThis ECP focuses strictly on **VHL Concepts**. It teaches an agent to recognize and reason about these foundational concepts and their constraints. Detailed operational procedures, multi-step reconciliation logic, task workflows, and automated verification pipelines are progressively disclosed through referenced Methodologies and Workflows.\n\n---\n\n## 2. Core VHL Concepts\n\n### 2.1 Module & Assembly\n\n#### What it means\nVHL partitions every hardware design into a two-tier structural hierarchy:\n\n* **Module**: A self-contained, isolated functional building block (e.g., power supply, microcontroller block, battery monitor).\n  * **Sub-units**: Discrete electronic components, ICs, passives, and semiconductors.\n  * **Scope**: Resides in a dedicated module Git branch and isolated Git worktree workspace.\n* **Assembly**: A top-level integration circuit that connects modules through their interface boundaries to achieve system-level functionality and define board physical layout.\n  * **Sub-units**: Hardware **Modules** (not raw loose discrete components).\n  * **Scope**: Resides in the root Git worktree (`main`\u002F`master` branch).\n\n#### Why VHL uses it\n* **Decoupling**: Splits complex multi-domain hardware designs into manageable, independent sub-problems.\n* **Parallel Agent Execution**: Enables isolated development by dedicated agent teams without cross-module interference.\n* **Domain Separation**: Distinguishes internal schematic implementation (Module) from top-level interconnect and layout (Assembly).\n\n#### Fundamental invariants \u002F constraints\n1. **Sub-unit Hierarchy Invariant**: Sub-units of a Module are discrete components\u002FICs; sub-units of an Assembly are Modules. Assemblies do not contain raw loose components unless required for top-level interconnect logic.\n2. **Workspace Isolation Invariant**: Each Module MUST operate inside its own dedicated Git worktree and branch. Assemblies MUST operate in the root worktree.\n3. **Agent Ownership**: A Module is owned by a Module Archy agent; an Assembly is owned by the System Archy agent.\n\n#### When an agent needs to think about it\n* When assigned a design task, to determine whether the task scope is a single functional sub-block (Module) or top-level integration (Assembly).\n* When structuring circuit code (`.tsx`) or determining component vs. module instantiation.\n\n#### Progressive-disclosure references\n* **Concept Deep Dive**: [Module and Assemblies](references\u002Fmodule_and_assemblies.md)\n* **Execution Workflows**:\n  * [Module Synthesis Workflow](..\u002FModule_Synthesis\u002FSKILL.md)\n  * [Assembly Integration Workflow](..\u002FAssembly_Integration\u002FSKILL.md)\n\n---\n\n### 2.2 Interface Boundary\n\n#### What it means\nAn **Interface Boundary** is a formal, black-box contract that defines and constrains how a hardware module interacts with other modules and the external environment.\n\nEvery boundary explicitly articulates **4 Pillars**:\n1. **Consumes**: Required input resources, supply voltages, reference clocks, and incoming signals.\n2. **Produces**: Output resources, regulated power rails, telemetry, and status signals generated for external consumption.\n3. **Enforces**: Spatial, electrical, and mechanical constraints (e.g., maximum voltage ripple, differential impedance, isolation barriers, operating temperature limits).\n4. **Functional Contract**: Black-box behavioral transformation definition (what the module does, independent of internal schematic implementation).\n\nVHL distinguishes between **Module Boundaries** (owned by Module Archy) and **System Boundaries** (owned by System Archy).\n\n#### Why VHL uses it\n* **Contractual Autonomy**: Serves as an absolute contract between independent modules, enabling asynchronous development.\n* **Verifiable Interconnect**: Allows downstream synthesis, validation, and layout tools to verify compatibility without inspecting internal module implementation details.\n* **Boundary Encapsulation**: Prevents scope creep and uncontrolled inter-module signal pollution.\n\n#### Fundamental invariants \u002F constraints\n1. **Signal Encapsulation Invariant**: Internal feedback nodes, current-sense feedback loops, and local bias nets MUST remain encapsulated inside the module and MUST NOT be exposed on the module boundary.\n2. **Structural Phase Enforcement Invariant**: Boundary contracts MUST be enforced deterministically through runtime verification gates and artifact checks, not by relying on LLM agent cognitive discipline.\n3. **Contract Completeness**: Every signal or power rail entering or leaving a module MUST belong to an explicit boundary port declared under Consumes or Produces.\n\n#### When an agent needs to think about it\n* When defining a module specification or establishing interface contracts between modules.\n* When evaluating whether a proposed schematic change alters external pinouts or electrical constraints.\n* When validating system-level electrical compatibility across module interfaces.\n\n#### Progressive-disclosure references\n* **Concept Deep Dive**: [Boundary Concept & Interface Contracts](references\u002Fboundary.md)\n* **Related Methodologies**:\n  * [Boundary Alignment](..\u002FBoundary_Alignment\u002FSKILL.md)\n  * [Boundary Reconciliation](..\u002FBoundary_Reconciliation\u002FSKILL.md)\n\n---\n\n### 2.3 Git Worktree \u002F Workspace Isolation\n\n#### What it means\nIn VHL:\n* The central repository acts as the shared object database and single source of truth(the trunk branch\u002Fworktree).\n* Each agent operates in a dedicated workspace provisioned as a Git worktree linked to a specific feature branch.\n\n#### Why VHL uses it\n* **Performance & Disk Efficiency**: Worktree creation is instantaneous and avoids full filesystem cloning (`shutil.copytree`), sharing a single `.git` object database.\n* **Native Versioning & Auditability**: Agent progression is recorded via standard Git commits, providing clear auditability and standard merge capabilities.\n* **Context Protection**: Prevents concurrent agents working on different modules from overwriting each other's workspace files.\n\n#### Fundamental invariants \u002F constraints\n1. **Single Repository Anchor**: All agent worktrees MUST originate from the central project repository object database (`.git`).\n2. **Workspace-Branch One-to-One Binding**: Each active worktree MUST be bound to a distinct Git branch corresponding to its target module.\n3. **Deterministic Persistence**: Progress MUST be saved using Git commits (`git commit`), mapping state snapshots directly to Git history.\n\n#### When an agent needs to think about it\n* When initializing an agent session or context, to ensure execution occurs within the designated worktree.\n* When committing state iterations or preparing module branches for merging into the assembly.\n\n#### Progressive-disclosure references\n* **Concept Deep Dive**: [Git Worktree Workspace Management](references\u002Fgit_worktree_workspace_management.md)\n\n---\n\n### 2.4 Shared Circuit Understanding Document (SCUD)\n\n#### What it means\nThe **Shared Circuit Understanding Document (SCUD)** is the canonical, human- and LLM-readable representation of VHL's current understanding of a circuit.\n\nIt serves as a **semantic anchor** and **single source of interpreted circuit intent** between agents.\n\nSCUD is structured into **5 mandatory sections**:\n1. `Module Overview & System Context`\n2. `Components Inventory`\n3. `Connectivity & Signal Flow`\n4. `Uncertainties, Assumptions & Confidence`\n5. `Library Mapping`\n\n#### Why VHL uses it\n* **Intent Bridge**: Connects high-level architectural specifications to low-level executable code (`.tsx`).\n* **Uncertainty Visibility**: Prevents silent assumptions by explicitly recording incomplete knowledge, confidence levels, and engineering assumptions.\n* **Incremental Refinement**: Provides a human-auditable intermediate representation of design intent that evolves incrementally as new evidence becomes available.\n\n#### Fundamental invariants \u002F constraints\n1. **Semantic, Not Formal**: SCUD describes functional intent and understanding. SCUD is NOT a netlist, circuit graph, layout file, or executable code.\n2. **No Silent Inference**: Ambiguities and missing documentation MUST NOT be resolved through silent agent guessing; they MUST remain explicitly logged in Section 4 (`Uncertainties, Assumptions & Confidence`).\n3. **Evidence-Based Traceability**: Every statement in SCUD must be traceable to available evidence (boundary specs, datasheets, reference designs, or explicit engineering decisions).\n4. **Document Status Protocol (`IN_PROGRESS`)**: If incomplete data or unresolved ambiguities block SCUD completion, the token `IN_PROGRESS` MUST be appended as a standalone line at the end of the file.\n\n#### When an agent needs to think about it\n* When parsing reference schematics or specifications to extract circuit intent.\n* When transferring circuit understanding to downstream synthesis agents (e.g., ANA).\n* When recording engineering decisions, component choices, or uncertainties.\n\n#### Progressive-disclosure references\n* **Concept Deep Dive**: [Shared Circuit Understanding Document (SCUD)](references\u002FShared_Circuit_Understanding_Document.md)\n* **Artifact Methodologies**:\n  * [SCUD Creation Methodology & Guidelines](..\u002FSCUD\u002FSKILL.md)\n\n---\n\n## 3. Workflow & Operational Execution (Progressive Disclosure)\n\nVHL operationalizes its core concepts through specialized **Engineering Workflows** and **Artifact Methodologies**. When an agent transitions from conceptual reasoning to task execution, it defers to these specific capability packages:\n\n* **Single-Module Design Lifecycle**:\n  To provision a Git worktree, extract SCUD intent, prepare component libraries, and synthesize module code, consult the [Module Synthesis Workflow](..\u002FModule_Synthesis\u002FSKILL.md).\n\n* **Top-Level System Composition**:\n  To integrate module branches into the root worktree, synthesize top-level interconnects, and coordinate placement, consult the [Assembly Integration Workflow](..\u002FAssembly_Integration\u002FSKILL.md).\n\n* **SCUD Extraction & Intent Drafting**:\n  To draft, structure, and incrementally refine a 5-section SCUD artifact from evidence documents, consult the [SCUD Creation Methodology & Guidelines](..\u002FSCUD\u002FSKILL.md).\n\n* **Boundary Alignment & Reconciliation**:\n  To validate cross-module interface contracts and perform atomic multi-artifact reconciliation passes, consult the [Boundary Alignment Document](..\u002FBoundary_Alignment\u002FSKILL.md) and [Boundary Reconciliation Methodology](..\u002FBoundary_Reconciliation\u002FSKILL.md).\n\n---\n## 4. Conceptual Integrity\n\nThe four concepts impose invariants that must remain true:\n\n- Module\u002FAssembly hierarchy remains valid.\n- Module boundaries do not expose internal signals.\n- Module workspace remains isolated from other module workspaces.\n- SCUD remains a semantic representation rather than executable\u002Fformal circuit representation.\n\nDetailed verification procedures are delegated to the relevant methodologies and validation workflows.\n","# VHL Concepts\n\nThis skill provides the architectural model, core invariants, and progressive-disclosure mapping for the four fundamental concepts in the Virtual Hardware Laboratory (VHL): **Module vs Assembly**, **Interface Boundary**, **Git Worktree Workspace**, and **Shared Circuit Understanding Document (SCUD)**.\n\n---\n\n## 1. Architectural Principle & Knowledge Tiers\n\nVHL separates engineering knowledge into three distinct, decoupled tiers:\n\n```text\nVHL Concepts\n    = What things are and why they exist (Architectural definitions & invariants)\n\nEngineering Methodologies\n    = How engineering reasoning is performed using those concepts\n\nEngineering Workflows\n    = How specific multi-step VHL tasks are executed\n```\n\nThis ECP focuses strictly on **VHL Concepts**. It teaches an agent to recognize and reason about these foundational concepts and their constraints. Detailed operational procedures, multi-step reconciliation logic, task workflows, and automated verification pipelines are progressively disclosed through referenced Methodologies and Workflows.\n\n---\n\n## 2. Core VHL Concepts\n\n### 2.1 Module & Assembly\n\n#### What it means\nVHL partitions every hardware design into a two-tier structural hierarchy:\n\n* **Module**: A self-contained, isolated functional building block (e.g., power supply, microcontroller block, battery monitor).\n  * **Sub-units**: Discrete electronic components, ICs, passives, and semiconductors.\n  * **Scope**: Resides in a dedicated module Git branch and isolated Git worktree workspace.\n* **Assembly**: A top-level integration circuit that connects modules through their interface boundaries to achieve system-level functionality and define board physical layout.\n  * **Sub-units**: Hardware **Modules** (not raw loose discrete components).\n  * **Scope**: Resides in the root Git worktree (`main`\u002F`master` branch).\n\n#### Why VHL uses it\n* **Decoupling**: Splits complex multi-domain hardware designs into manageable, independent sub-problems.\n* **Parallel Agent Execution**: Enables isolated development by dedicated agent teams without cross-module interference.\n* **Domain Separation**: Distinguishes internal schematic implementation (Module) from top-level interconnect and layout (Assembly).\n\n#### Fundamental invariants \u002F constraints\n1. **Sub-unit Hierarchy Invariant**: Sub-units of a Module are discrete components\u002FICs; sub-units of an Assembly are Modules. Assemblies do not contain raw loose components unless required for top-level interconnect logic.\n2. **Workspace Isolation Invariant**: Each Module MUST operate inside its own dedicated Git worktree and branch. Assemblies MUST operate in the root worktree.\n3. **Agent Ownership**: A Module is owned by a Module Archy agent; an Assembly is owned by the System Archy agent.\n\n#### When an agent needs to think about it\n* When assigned a design task, to determine whether the task scope is a single functional sub-block (Module) or top-level integration (Assembly).\n* When structuring circuit code (`.tsx`) or determining component vs. module instantiation.\n\n#### Progressive-disclosure references\n* **Concept Deep Dive**: [Module and Assemblies](references\u002Fmodule_and_assemblies.md)\n* **Execution Workflows**:\n  * [Module Synthesis Workflow](..\u002FModule_Synthesis\u002FSKILL.md)\n  * [Assembly Integration Workflow](..\u002FAssembly_Integration\u002FSKILL.md)\n\n---\n\n### 2.2 Interface Boundary\n\n#### What it means\nAn **Interface Boundary** is a formal, black-box contract that defines and constrains how a hardware module interacts with other modules and the external environment.\n\nEvery boundary explicitly articulates **4 Pillars**:\n1. **Consumes**: Required input resources, supply voltages, reference clocks, and incoming signals.\n2. **Produces**: Output resources, regulated power rails, telemetry, and status signals generated for external consumption.\n3. **Enforces**: Spatial, electrical, and mechanical constraints (e.g., maximum voltage ripple, differential impedance, isolation barriers, operating temperature limits).\n4. **Functional Contract**: Black-box behavioral transformation definition (what the module does, independent of internal schematic implementation).\n\nVHL distinguishes between **Module Boundaries** (owned by Module Archy) and **System Boundaries** (owned by System Archy).\n\n#### Why VHL uses it\n* **Contractual Autonomy**: Serves as an absolute contract between independent modules, enabling asynchronous development.\n* **Verifiable Interconnect**: Allows downstream synthesis, validation, and layout tools to verify compatibility without inspecting internal module implementation details.\n* **Boundary Encapsulation**: Prevents scope creep and uncontrolled inter-module signal pollution.\n\n#### Fundamental invariants \u002F constraints\n1. **Signal Encapsulation Invariant**: Internal feedback nodes, current-sense feedback loops, and local bias nets MUST remain encapsulated inside the module and MUST NOT be exposed on the module boundary.\n2. **Structural Phase Enforcement Invariant**: Boundary contracts MUST be enforced deterministically through runtime verification gates and artifact checks, not by relying on LLM agent cognitive discipline.\n3. **Contract Completeness**: Every signal or power rail entering or leaving a module MUST belong to an explicit boundary port declared under Consumes or Produces.\n\n#### When an agent needs to think about it\n* When defining a module specification or establishing interface contracts between modules.\n* When evaluating whether a proposed schematic change alters external pinouts or electrical constraints.\n* When validating system-level electrical compatibility across module interfaces.\n\n#### Progressive-disclosure references\n* **Concept Deep Dive**: [Boundary Concept & Interface Contracts](references\u002Fboundary.md)\n* **Related Methodologies**:\n  * [Boundary Alignment](..\u002FBoundary_Alignment\u002FSKILL.md)\n  * [Boundary Reconciliation](..\u002FBoundary_Reconciliation\u002FSKILL.md)\n\n---\n\n### 2.3 Git Worktree \u002F Workspace Isolation\n\n#### What it means\nIn VHL:\n* The central repository acts as the shared object database and single source of truth(the trunk branch\u002Fworktree).\n* Each agent operates in a dedicated workspace provisioned as a Git worktree linked to a specific feature branch.\n\n#### Why VHL uses it\n* **Performance & Disk Efficiency**: Worktree creation is instantaneous and avoids full filesystem cloning (`shutil.copytree`), sharing a single `.git` object database.\n* **Native Versioning & Auditability**: Agent progression is recorded via standard Git commits, providing clear auditability and standard merge capabilities.\n* **Context Protection**: Prevents concurrent agents working on different modules from overwriting each other's workspace files.\n\n#### Fundamental invariants \u002F constraints\n1. **Single Repository Anchor**: All agent worktrees MUST originate from the central project repository object database (`.git`).\n2. **Workspace-Branch One-to-One Binding**: Each active worktree MUST be bound to a distinct Git branch corresponding to its target module.\n3. **Deterministic Persistence**: Progress MUST be saved using Git commits (`git commit`), mapping state snapshots directly to Git history.\n\n#### When an agent needs to think about it\n* When initializing an agent session or context, to ensure execution occurs within the designated worktree.\n* When committing state iterations or preparing module branches for merging into the assembly.\n\n#### Progressive-disclosure references\n* **Concept Deep Dive**: [Git Worktree Workspace Management](references\u002Fgit_worktree_workspace_management.md)\n\n---\n\n### 2.4 Shared Circuit Understanding Document (SCUD)\n\n#### What it means\nThe **Shared Circuit Understanding Document (SCUD)** is the canonical, human- and LLM-readable representation of VHL's current understanding of a circuit.\n\nIt serves as a **semantic anchor** and **single source of interpreted circuit intent** between agents.\n\nSCUD is structured into **5 mandatory sections**:\n1. `Module Overview & System Context`\n2. `Components Inventory`\n3. `Connectivity & Signal Flow`\n4. `Uncertainties, Assumptions & Confidence`\n5. `Library Mapping`\n\n#### Why VHL uses it\n* **Intent Bridge**: Connects high-level architectural specifications to low-level executable code (`.tsx`).\n* **Uncertainty Visibility**: Prevents silent assumptions by explicitly recording incomplete knowledge, confidence levels, and engineering assumptions.\n* **Incremental Refinement**: Provides a human-auditable intermediate representation of design intent that evolves incrementally as new evidence becomes available.\n\n#### Fundamental invariants \u002F constraints\n1. **Semantic, Not Formal**: SCUD describes functional intent and understanding. SCUD is NOT a netlist, circuit graph, layout file, or executable code.\n2. **No Silent Inference**: Ambiguities and missing documentation MUST NOT be resolved through silent agent guessing; they MUST remain explicitly logged in Section 4 (`Uncertainties, Assumptions & Confidence`).\n3. **Evidence-Based Traceability**: Every statement in SCUD must be traceable to available evidence (boundary specs, datasheets, reference designs, or explicit engineering decisions).\n4. **Document Status Protocol (`IN_PROGRESS`)**: If incomplete data or unresolved ambiguities block SCUD completion, the token `IN_PROGRESS` MUST be appended as a standalone line at the end of the file.\n\n#### When an agent needs to think about it\n* When parsing reference schematics or specifications to extract circuit intent.\n* When transferring circuit understanding to downstream synthesis agents (e.g., ANA).\n* When recording engineering decisions, component choices, or uncertainties.\n\n#### Progressive-disclosure references\n* **Concept Deep Dive**: [Shared Circuit Understanding Document (SCUD)](references\u002FShared_Circuit_Understanding_Document.md)\n* **Artifact Methodologies**:\n  * [SCUD Creation Methodology & Guidelines](..\u002FSCUD\u002FSKILL.md)\n\n---\n\n## 3. Workflow & Operational Execution (Progressive Disclosure)\n\nVHL operationalizes its core concepts through specialized **Engineering Workflows** and **Artifact Methodologies**. When an agent transitions from conceptual reasoning to task execution, it defers to these specific capability packages:\n\n* **Single-Module Design Lifecycle**:\n  To provision a Git worktree, extract SCUD intent, prepare component libraries, and synthesize module code, consult the [Module Synthesis Workflow](..\u002FModule_Synthesis\u002FSKILL.md).\n\n* **Top-Level System Composition**:\n  To integrate module branches into the root worktree, synthesize top-level interconnects, and coordinate placement, consult the [Assembly Integration Workflow](..\u002FAssembly_Integration\u002FSKILL.md).\n\n* **SCUD Extraction & Intent Drafting**:\n  To draft, structure, and incrementally refine a 5-section SCUD artifact from evidence documents, consult the [SCUD Creation Methodology & Guidelines](..\u002FSCUD\u002FSKILL.md).\n\n* **Boundary Alignment & Reconciliation**:\n  To validate cross-module interface contracts and perform atomic multi-artifact reconciliation passes, consult the [Boundary Alignment Document](..\u002FBoundary_Alignment\u002FSKILL.md) and [Boundary Reconciliation Methodology](..\u002FBoundary_Reconciliation\u002FSKILL.md).\n\n---\n## 4. Conceptual Integrity\n\nThe four concepts impose invariants that must remain true:\n\n- Module\u002FAssembly hierarchy remains valid.\n- Module boundaries do not expose internal signals.\n- Module workspace remains isolated from other module workspaces.\n- SCUD remains a semantic representation rather than executable\u002Fformal circuit representation.\n\nDetailed verification procedures are delegated to the relevant methodologies and validation workflows.\n",{"name":5,"description":7},"main","8413773f2869ef1060cdff2a70ff224b4fbb64a1","crazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FVHL_Concepts","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys","https:\u002F\u002Fgithub.com\u002Fvivekvjnk","2026-08-23 20:15:00",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add vivekvjnk\u002Fthree-wise-monkeys --skill vhl-concepts",{"tool":58,"command":59},"bunx","bunx skills add vivekvjnk\u002Fthree-wise-monkeys --skill vhl-concepts",{"tool":61,"command":62},"pnpm","pnpm dlx skills add vivekvjnk\u002Fthree-wise-monkeys --skill vhl-concepts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FVHL_Concepts\u002FSKILL.md",true,[66,72,76,80,84,88,92,96],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"manifest.json","REFERENCE","参考文档",109,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FPlatform\u002FOfficial-DotNet-Advanced\u002Fskills\u002Fnuget-trusted-publishing\u002Fmanifest.json",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fboundary.md",3865,"https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FVHL_Concepts\u002Freferences\u002Fboundary.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fgit_worktree_workspace_management.md",5489,"https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FVHL_Concepts\u002Freferences\u002Fgit_worktree_workspace_management.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fmodule_and_assemblies.md",2228,"https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FVHL_Concepts\u002Freferences\u002Fmodule_and_assemblies.md",{"path":85,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fpackage-types.md",8446,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FPlatform\u002FOfficial-DotNet-Advanced\u002Fskills\u002Fnuget-trusted-publishing\u002Freferences\u002Fpackage-types.md",{"path":89,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fpublish-workflow.md",3910,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FPlatform\u002FOfficial-DotNet-Advanced\u002Fskills\u002Fnuget-trusted-publishing\u002Freferences\u002Fpublish-workflow.md",{"path":93,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002FShared_Circuit_Understanding_Document.md",3791,"https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FVHL_Concepts\u002Freferences\u002FShared_Circuit_Understanding_Document.md",{"path":97,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":98,"sourceHtmlUrl":99},"tools\u002FREADME.md",1715,"https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FVHL_Concepts\u002Ftools\u002FREADME.md",[101,113,127,140,145,152],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":41},"01M6C4MJNVM205XN83K79M9B9M","cypress-tuning","Systematically diagnoses, tunes, and executes Cypress GPU-accelerated PCB placement optimization runs. Trigger when running DREAMPlace\u002FCypress component placement, diagnosing placement divergence or clumping, or tuning wirelength, density, rotation, and net crossing parameters.","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fprocesses\u002Fcomponent-placement\u002Fskills\u002Fcypress-tuning\u002FSKILL.md",[],[108,109,110,111,112],"cypress tuning","tuning","Optimization","gpu","component",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":120,"publishedAt":41},"01M6C4MFEJV3TJBTD6Q72R10SD","circuitjson-bookshelf-converter","Converts Circuit JSON PCB and schematic designs into Bookshelf physical design format (.nodes, .nets, .pl, .scl, .aux) with courtyard keep-out boundary modeling, and back-annotates Cypress placement optimization results back into Circuit JSON. Trigger this skill whenever converting circuit.json files to Bookshelf format or back-annotating .pl \u002F .gp.pl placement outputs into Circuit JSON.","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fprocesses\u002Fcomponent-placement\u002Fskills\u002Fcircuitjson-bookshelf-converter\u002FSKILL.md",[119],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[121,122,123,124,125,34,110,126],"circuitjson bookshelf converter","converter","format","results","json","design",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":41},"01M6C4MCGT8VE95H167GW3ZMSM","circuit-json-analysis","Analyzes Circuit JSON files for structural component relationships, domain mappings (source, schematic, pcb, cad), and geometric layout DRC violations (courtyard overlaps, solder paste misalignments, pad clearances). Trigger this skill whenever analyzing a circuit.json file, inspecting PCB placement, or performing design rule checks on Circuit JSON data.","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fprocesses\u002Fcomponent-placement\u002Fskills\u002Fcircuit-json-analysis\u002FSKILL.md",[133],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[135,125,136,126,137,112,138,139],"circuit json analysis","analysis","data","file","analyzing",{"skillNo":141,"name":40,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":41},"01M6C4M84NXPYJP0MQBK1KCPGR","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FSCUD\u002FSKILL.md",[],[40],{"skillNo":146,"name":147,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":41},"01M6C4M74376ZGW7PVHA3A7WZV","Module_Synthesis","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FModule_Synthesis\u002FSKILL.md",[],[151],"Module Synthesis",{"skillNo":153,"name":154,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":41},"01M6C4M5QGD7QHY9TZ153VJY6D","Boundary_Reconciliation","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FBoundary_Reconciliation\u002FSKILL.md",[],[158,34],"Boundary Reconciliation"]