What problem does it solve? Designing Infrahub schemas by hand is error-prone: naming pattern violations, mismatched relationship identifiers, missing human_friendly_id values, and mandatory-by-default attributes all cause validation failures or silent data-model bugs that surface only after data is loaded. ## Core Features & Use Cases - Schema Authoring Guidance: Step-by-step workflow for building schema YAML with generics, nodes, extensions, dropdowns, computed Jinja2 attributes, and hierarchical location trees. - Rule Library by Category: Prioritized rules covering naming conventions, Component/Parent relationship pairing, display properties, uniqueness constraints, migrations with state: absent, and branch-first rollout. - Validation & Migration Support: infrahubctl schema check/load commands, common error explanations, and a pre-validation checklist. - Use Case: You need to model a new DCIM domain with devices, racks, and module bays. The skill walks you through defining the generics, wiring bidirectional relationships with matching identifiers, setting human_friendly_id, and loading the schema on a dedicated branch. ## Quick Start Ask the assistant to create an Infrahub schema for a given namespace and node names, for example by invoking the skill with arguments like a namespace followed by the node names you want modeled.
