ogp-proof-and-analysis-toolkit

Verify third-party library behavior and geometry code claims in the Open Garden Planner.

16|2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/cofade/open-garden-planner --skill ogp-proof-and-analysis-toolkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ogp-proof-and-analysis-toolkit
Source: https://github.com/cofade/open-garden-planner/tree/main/.claude/skills/ogp-proof-and-analysis-toolkit
Command: npx skills add https://github.com/cofade/open-garden-planner --skill ogp-proof-and-analysis-toolkit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides first-principles proof methods for the Open Garden Planner, ensuring claims about code behavior are verified before implementation.

Core Features & Use Cases

  • Empirical Verification: Prove third-party library behavior with minimal probe scripts.
  • Coordinate-Frame Proof: Validate coordinate frame consistency in rendering and geometry.
  • Geometry Invariant Derivation: Ensure transform code maintains geometric invariants.
  • Headless Numeric Trace: Refute numeric theories with automated code execution.
  • Adversarial Input Probing: Test trust boundaries against hostile inputs.
  • Tolerance Derivation: Derive tolerances from physical scale and observer.
  • Signal/Timing Analysis: Identify event-driven bugs through signal and timing analysis.
  • Refutation by Primary Source: Validate code claims with primary source reading.
  • Counting/Exhaustiveness Proofs: Ensure universal claims hold for all members of a class.

Quick Start

Load the ogp-proof-and-analysis-toolkit skill when you need to verify a claim about third-party library behavior or geometry code.

Frequently Asked Questions about ogp-proof-and-analysis-toolkit

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

FAQPage Schema
How do I verify third-party library behavior in geometry code before implementation?

Verify third-party library behavior by writing minimal probe scripts to empirically test claims. This ensures code behavior in your geometry model is backed by reproducible experiments before integration.

What is the best way to validate coordinate frame consistency in garden planning software?

Validate coordinate frame consistency by applying coordinate-frame proof methods to rendering and geometry code. This ensures transforms maintain geometric invariants across the Open Garden Planner architecture.

How do you derive geometric tolerances from physical scale in rendering applications?

Derive geometric tolerances from physical scale and the observer's perspective. This ensures engineering-grade precision by aligning numeric tolerances with real-world garden planning dimensions.

Can I test trust boundaries against hostile inputs in a geometry application?

Test trust boundaries against hostile inputs using adversarial input probing. This refutes numeric theories and identifies vulnerabilities by executing automated headless numeric traces.

How do I identify event-driven bugs through signal and timing analysis in code verification?

Identify event-driven bugs through signal and timing analysis to trace execution paths. This code verification method isolates race conditions and timing discrepancies in the geometry model.

When do I need refutation by primary source for code verification?

Use refutation by primary source when validating universal code claims about library behavior. This ensures counting and exhaustiveness proofs hold by checking claims against primary documentation.