nesting-orientation-review-gate

Gate orientation-preference changes in the nesting heuristic to preserve determinism.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/BSchafer01/PanelNester --skill nesting-orientation-review-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nesting-orientation-review-gate
Source: https://github.com/BSchafer01/PanelNester/tree/main/.squad/skills/nesting-orientation-review-gate
Command: npx skills add https://github.com/BSchafer01/PanelNester --skill nesting-orientation-review-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate orientation-preference changes in the nesting heuristic to prevent loss of fit behavior and determinism.

Core Features & Use Cases

  • Separate the preference case from the necessity case to preserve deterministic results.
  • Prove the rule on the real service path by asserting actual placement geometry and Rotated90.
  • Add a preserved-rotation counterexample to show old rotate-to-fit behavior remains valid after changes.
  • Re-run the same request twice and compare placement order, coordinates, dimensions, and rotation flags to ensure determinism.
  • Keep one no-fit regression check to guard against misleading reason codes.
  • Prefer a narrow priority key over a heuristic rewrite to maintain deterministic ordering.

Quick Start

Generate a regression test plan to validate orientation-preference changes in the nesting heuristic while preserving fit and determinism.

Frequently Asked Questions about nesting-orientation-review-gate

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

FAQPage Schema
How do I prevent loss of determinism when changing nesting orientation preferences?

You can preserve rotation behavior by adding a preserved-rotation counterexample to your test suite, which demonstrates that the old rotate-to-fit behavior remains valid and unbroken after applying changes to the nesting heuristic.

What is the best way to test nesting heuristic changes for regression?

You can validate nesting determinism by re-running the exact same nesting request twice and comparing the resulting placement order, coordinates, dimensions, and rotation flags to ensure identical outputs across both runs.

How do I validate rotation defaults on a real nesting service path?

To validate rotation defaults on a real nesting service path, you must assert actual placement geometry and verify Rotated90 flags directly against the service response rather than relying on simulated or mocked outputs.

Why does my nesting heuristic lose fit behavior after updating tie-break rules?

Nesting heuristics lose fit behavior after updating tie-break rules because broad heuristic rewrites disrupt deterministic ordering, which you can fix by applying a focused priority key instead of a full rewrite.