phase1-domain-contracts

Define UI-agnostic domain contracts for import and nesting logic.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establish a stable, UI-agnostic seam between the import and nesting logic by clearly separating domain models, contracts, and service boundaries. This ensures early vertical slices can progress without coupling to WPF, persistence, or presentation concerns.

Core Features & Use Cases

  • Stabilizes domain models and contracts in src/PanelNester.Domain and src/PanelNester.Domain/Contracts.
  • Keeps request/response/data shapes in the domain layer and minimizes UI coupling to the shipping logic.
  • Defines compact representations for import rows and deterministic expansion during nesting to support predictable results.

Quick Start

Stand up or extend the backend seam between bridge handlers and the nesting/import logic using the guidance in this phase.

Frequently Asked Questions about phase1-domain-contracts

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

FAQPage Schema
How do I decouple backend domain logic from UI concerns during early integration?

To decouple backend domain logic from UI concerns, establish a stable, UI-agnostic domain seam between import and nesting logic. This separates domain models and contracts from presentation layers, ensuring vertical slices progress without coupling to persistence or UI frameworks.

What is a deterministic import-to-nest seam in backend domain modeling?

A deterministic import-to-nest seam is a stable domain boundary bridging import and nesting logic. It applies compact data shapes and explicit geometry handling to produce predictable, serializer-friendly contracts that ensure consistent nesting expansion behavior.

Can I use this domain seam approach for backend construction without WPF dependencies?

Yes, you can use this domain seam approach without WPF dependencies. The contracts are designed to be UI-independent, keeping request and response shapes in the domain layer to prevent coupling to specific presentation frameworks or persistence logic.

How do I define serializer-friendly contracts for import rows and nesting expansion?

Define serializer-friendly contracts by stabilizing domain models in the domain layer and using compact representations for import rows. This ensures deterministic expansion during nesting and maintains explicit geometry handling for predictable data processing results.

Why does my nesting logic produce inconsistent results from imported data?

Nesting logic produces inconsistent results when import and nesting boundaries lack a deterministic domain seam. Establishing compact data shapes and explicit geometry handling in the domain layer ensures predictable, serializer-friendly contracts for stable nesting behavior.