microsoft/hve-core

Public

mirrored fromhttps://github.com/microsoft/hve-coreAvailable

CodeCommitsIssuesPull requestsActionsInsightsSecurity
d3bdd7aad16075f6869150a5fe6e74c2865b2c80

Branches

Tags

  • No tags available.
0Branches0Tags
Go to file
Add file
Code

Clone

HTTPS

Download ZIP

docs/architecture/README.md

83lines · modecode

1---
2title: Architecture Overview
3description: HVE Core system design and component relationships
4author: Microsoft
5ms.date: 2026-01-22
6ms.topic: concept
7---
8
9HVE Core provides a Copilot customization framework that enables teams to extend GitHub Copilot with project-specific context, workflows, and automation. The framework organizes reusable AI artifacts, development scripts, and documentation into a cohesive system that integrates with VS Code and GitHub workflows.
10
11## System Architecture
12
13The following diagram illustrates the primary components and their relationships:
14
15```mermaid
16graph TD
17 EXT[Extension] --> AGENTS[Agents]
18 EXT --> PROMPTS[Prompts]
19 EXT --> INSTRUCTIONS[Instructions]
20 EXT --> SKILLS[Skills]
21 SCRIPTS[Scripts] --> LINTING[Linting]
22 SCRIPTS --> SECURITY[Security]
23 SCRIPTS --> DEVTOOLS[Dev Tools]
24 DOCS[Documentation] --> GUIDES[User Guides]
25 DOCS --> ARCH[Architecture]
26```
27
28## Component Summary
29
30| Component | Location | Purpose |
31|---------------------|----------------------------|-------------------------------------------------------------------------|
32| Extension | `extension/` | VS Code extension providing contribution points for AI artifacts |
33| Scripts | `scripts/` | PowerShell automation for linting, security validation, and dev tools |
34| Documentation | `docs/` | User guides, architecture docs, and contribution guidelines |
35| GitHub Assets | `.github/` | Workflows, instructions, prompts, agents, and issue templates |
36| Skills | `.github/skills/` | Self-contained packages combining scripts with domain-specific guidance |
37| Dev Container | `.devcontainer/` | Codespaces and local container development environment |
38| Frontmatter Schema | `scripts/linting/schemas/` | JSON schemas for AI artifact validation |
39| GitHub Workflows | `.github/workflows/` | CI/CD pipelines for validation, security, and release automation |
40| Access Control | `.github/CODEOWNERS` | Path-based review requirements and ownership |
41| MCP Configuration | `.vscode/mcp.json` | Model Context Protocol server definitions |
42| Test Infrastructure | `scripts/tests/` | Pester test suites with fixtures and mocks |
43
44## Core Subsystems
45
46### Extension
47
48The VS Code extension serves as the integration layer between HVE Core artifacts and the Copilot experience. It registers contribution points that allow Copilot to discover and use agents, prompts, instructions, and skills defined within the repository. The extension follows VS Code extension packaging conventions and includes its own README and license.
49
50### Scripts
51
52Automation scripts handle quality assurance and development workflows. The scripts directory organizes functionality into specialized subdirectories:
53
54* Linting scripts validate markdown formatting, link integrity, YAML structure, and PowerShell code quality
55* Security scripts verify dependency pinning and SHA staleness for workflow actions
56* Dev tools assist with PR reference generation and other development tasks
57* Library modules provide shared utilities like verified downloads
58
59### Documentation
60
61User-facing documentation guides teams through installation, configuration, and effective use of the framework. The RPI (Researcher, Planner, Implementor) methodology documentation helps teams structure their AI-assisted development workflows. Contributing guides explain how to author AI artifacts that follow project conventions.
62
63### GitHub Assets
64
65The `.github/` directory contains workflow definitions, issue templates, and the AI artifacts that define Copilot behavior. Instructions files provide context-specific guidance that Copilot applies when working with certain file types or directories. Agents define specialized personas for different tasks. Prompts offer reusable starting points for common operations.
66
67Skills package executable utilities with cross-platform scripts and domain-specific guidance; each skill is self-contained with a SKILL.md file describing capabilities and usage patterns.
68
69## Package Relationships
70
71Components interact through well-defined boundaries. The extension registers contribution points for agents, prompts, and instructions, making them available to Copilot Chat. Skills use a separate discovery mechanism: Copilot scans `.github/skills/` for `SKILL.md` files that describe executable capabilities. Scripts operate independently of the extension but share configuration files like `PSScriptAnalyzer.psd1` and schema definitions in `scripts/linting/schemas/`.
72
73Documentation references both the extension capabilities and script utilities, providing guidance on how to use each component effectively. The tracking directory (`.copilot-tracking/`) serves as a workspace for AI-assisted workflows, storing work item discoveries, plan artifacts, and change records that bridge human and AI collaboration.
74
75GitHub workflows orchestrate script execution for continuous integration, running linting and security checks on pull requests. The extension packaging scripts prepare the VS Code extension for distribution, bundling required assets and generating the installable VSIX package.
76
77## Further Reading
78
79* [AI Artifacts Architecture](ai-artifacts.md) - Four-tier artifact delegation model
80* [Build Workflows](workflows.md) - GitHub Actions CI/CD pipeline architecture
81* [Testing Architecture](testing.md) - PowerShell Pester test infrastructure
82
83🤖 *Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.*
84