system-constraints

Enforce architectural constraints for the XML Database Extraction System.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/timothyjmorris/XmlConversion --skill system-constraints
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: system-constraints
Source: https://github.com/timothyjmorris/XmlConversion/tree/main/.github/skills/system-constraints
Command: npx skills add https://github.com/timothyjmorris/XmlConversion --skill system-constraints

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill codifies the non-negotiable architectural principles and constraints of the XML Database Extraction System, ensuring data integrity and system stability.

Core Features & Use Cases

  • Architectural Guardrails: Defines and enforces critical design patterns like contract-driven architecture, schema isolation, and atomic transactions.
  • Developer Guidance: Provides a clear checklist for code reviews and a framework for documenting new constraints.
  • Use Case: When a developer proposes a change that hardcodes a schema name, this Skill's principles can be referenced to explain why it violates the schema isolation pattern and must be avoided.

Quick Start

Review the system constraints before making any architectural decisions.

Frequently Asked Questions about system-constraints

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

FAQPage Schema
How do I enforce architectural constraints during an XML database code review?

Architectural constraints are enforced during XML database code reviews by checking proposed changes against codified principles like contract-driven design, schema isolation, and atomic transactions to prevent system gotchas and maintain data integrity.

Why does hardcoding a schema name violate schema isolation in XML processing?

Hardcoding a schema name violates schema isolation because this architectural constraint requires decoupling schema references from application logic to maintain data integrity and stability during XML database extraction.

What architectural principles are non-negotiable for XML database extraction systems?

Non-negotiable architectural principles for XML database extraction systems include contract-driven design, schema isolation, atomic transactions, and Windows-specific requirements to ensure system stability and data integrity.

How do I document new design constraints for an XML extraction architecture?

Document new design constraints for XML extraction architecture by using a defined framework to record the principle, its rationale, and how it prevents common system gotchas during code reviews.

Does XML database extraction require atomic transactions to maintain data integrity?

Yes, XML database extraction requires atomic transactions as a non-negotiable architectural constraint to ensure all database operations complete successfully or fail safely, thereby maintaining strict data integrity.

Are Windows-specific requirements a mandatory design constraint for XML extraction systems?

Yes, Windows-specific requirements are a non-negotiable architectural constraint that must be enforced during design and code reviews to ensure the XML database extraction system maintains stability on its target platform.