gpd-validate-conventions

Validate physics convention consistency across project phases.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/CharGrnmn/roomtemp-superconductor-gpd --skill gpd-validate-conventions-chargrnmn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-validate-conventions
Source: https://github.com/CharGrnmn/roomtemp-superconductor-gpd/tree/main/.agents/skills/gpd-validate-conventions
Command: npx skills add https://github.com/CharGrnmn/roomtemp-superconductor-gpd --skill gpd-validate-conventions-chargrnmn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gpd-consistency-checker, gpd-notation-coordinator, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining consistent physics conventions across multiple project phases, crucial for accurate scientific research.

Core Features & Use Cases

  • Convention Validation: Checks for consistency in metric signature, Fourier convention, natural units, gauge choice, etc.
  • Cross-Phase Consistency: Compares conventions across all completed phases for discrepancies.
  • Error Detection: Identifies and reports any mismatches or drift in conventions, such as sign errors or notation changes.
  • Resolution Tools: Spawns additional agents for conflict resolution and re-validation of affected phases.

Quick Start

Run the 'gpd-validate-conventions' Skill with optional phase number argument: gpd-validate-conventions [phase number].

Frequently Asked Questions about gpd-validate-conventions

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

FAQPage Schema
How do I check for physics convention drift across different project phases?

To check for physics convention drift across project phases, you can validate metric signature, Fourier convention, natural units, and gauge choice consistency. This process identifies notation changes and sign errors across completed phases to ensure accurate scientific computations.

What is convention validation in scientific computing simulations?

Convention validation in scientific computing simulations is the process of verifying that mathematical notations, such as metric signatures and natural units, remain uniform throughout the project. It detects mismatches and sign errors to prevent computational inaccuracies in physics research.

How do I validate metric signature and Fourier convention consistency in a research project?

You validate metric signature and Fourier convention consistency by running a validation check across all or specified project phases. This detects mismatches and convention drift, ensuring that mathematical notation remains uniform for accurate physics simulations.

Can I check physics notation consistency for just one specific project phase?

Yes, you can check physics notation consistency for a single project phase by providing the specific phase number as an argument. This isolates the validation to target metric signatures, gauge choices, and natural units within that particular phase.

Does this validation process detect sign errors and natural unit mismatches?

Yes, the validation process detects sign errors and natural unit mismatches by comparing conventions across completed project phases. It identifies discrepancies in Fourier conventions and gauge choices, ensuring mathematical consistency for scientific research.

What should I do if convention mismatches are found during scientific project validation?

When convention mismatches are found during scientific project validation, the system provides resolution tools that spawn additional agents. These agents handle conflict resolution and re-validate the affected project phases to restore notation consistency.