gvm-design-system

Provide shared design assets and reference files for GVM skills.

5|Updated May 4, 2026

Search Tags:#design system #html/css #gvm #reference files #cross-cutting rules

Ready to run

npx skills add https://github.com/gerquinn1978/gvm --skill gvm-design-system

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gvm-design-system
Source: https://github.com/gerquinn1978/gvm/tree/main/grounded-vibe-methodology/skills/gvm-design-system
Command: npx skills add https://github.com/gerquinn1978/gvm --skill gvm-design-system

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides shared design assets, expert reference files, and cross-cutting rules for all GVM skills. It ensures consistent visual identity and domain reasoning across the skills.

Core Features & Use Cases

Shared Design Assets: Provides core HTML/CSS design specifications and components following Tufte and Few principles.
Expert Reference Files: Includes architecture, domain, and stack specialist files for grounding domain reasoning.
Cross-Cutting Rules: Defines structural contracts between pipeline phases and scoring methodologies.
Use Case: When creating a new GVM skill, this Skill helps ensure consistency in design, domain knowledge, and cross-cutting rules across all documents and reviews.

Quick Start

Load the design reference files from the gvm-design-system skill into your context before starting any new GVM skill development.

Frequently Asked Questions about gvm-design-system

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

FAQPage Schema

How do I maintain a consistent visual identity across multiple HTML/CSS design system components?▼

To maintain a consistent visual identity, load shared HTML/CSS design specifications and reference files before starting development. This ensures all components follow Tufte and Few principles, enforcing consistent domain reasoning and structural contracts across documents.

What are cross-cutting rules in a design system and when do I need them?▼

Cross-cutting rules in a design system define structural contracts between pipeline phases and scoring methodologies. You need them when creating new skills to ensure consistent domain knowledge and architectural grounding across all reviews and documents.

How do I ground domain reasoning when developing new software engineering skills?▼

You ground domain reasoning by loading expert reference files containing architecture, domain, and stack specialist specifications. These files ensure accurate domain knowledge representation and consistent reasoning across all newly developed skills.

Do I need access to the GVM framework to use shared design assets?▼

Yes, you need access to the GVM framework and design principles to use these shared design assets. The framework provides the foundational environment required to apply the cross-cutting rules and HTML/CSS specifications correctly.

What's the best way to ensure design consistency when building a collection of HTML/CSS skills?▼

The best way to ensure design consistency is to load shared design reference files into your context before starting any new skill development. This provides core specifications, expert references, and structural contracts for uniform implementation.

Why does my design system implementation lack consistent domain reasoning across pipeline phases?▼

Your implementation lacks consistent domain reasoning because cross-cutting rules defining structural contracts between pipeline phases are not loaded. Loading architecture and stack specialist reference files ensures consistent scoring methodologies and domain grounding.