binder-modeling

Model Binder workspace schemas with fields, types, relations, and constraints.

39|5|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/mpazik/Binder --skill binder-modeling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: binder-modeling
Source: https://github.com/mpazik/Binder/tree/main/skills/binder-modeling
Command: npx skills add https://github.com/mpazik/Binder --skill binder-modeling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Binder schema changes can be difficult to get right—this Skill helps you define entity types, fields, relations, constraints, and file-rendering behavior so your workspace stays consistent as it grows.

Core Features & Use Cases

  • Define reusable fields (data types, defaults, options, uniqueness, and constraints) as first-class config entities.
  • Compose entity types by attaching fields with per-type validation like required fields, allowed enums, and relation target restrictions.
  • Model relationships correctly using inverseOf patterns for 1:M, M:M, and 1:1 synchronization.
  • Add field-level metadata via attributes to annotate relation values (e.g., roles on assignments) without creating new entity types.
  • Render and edit entities as files using View templates and Navigation mappings that control how entities become markdown/YAML and sync back.

Quick Start

Use this skill to design a Binder workspace schema by importing your Field, Type, View, and Navigation definitions with binder tx import.

Frequently Asked Questions about binder-modeling

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

FAQPage Schema
How do I model inverse relations to keep workspace schemas synchronized?

Model inverse relations by using `inverseOf` patterns to automatically synchronize 1:M, M:M, and 1:1 relationship updates. This ensures your workspace stays consistent as related records evolve.

What is the best way to define reusable fields with custom validation constraints?

Define reusable fields as first-class config entities with data types, defaults, uniqueness rules, and constraints. You can then attach these fields to entity types using per-type validation like required fields and allowed enums.

How do I render entity types as markdown or YAML files for file-based editing?

Render entities as files by applying `View` templates and `Navigation` mappings. These configurations control how your entity types become markdown or YAML files and sync edits back to the workspace.

Can I annotate relation values with extra metadata without creating new entity types?

Yes, you can annotate relation values by attaching field-level attributes. This allows you to add metadata like roles on assignments directly to the relation without needing to create an entirely new entity type.

Does binder schema modeling work for building AI agent memory and inbox queues?

Yes, schema modeling supports building record stores for trackers, catalogs, dashboards, and AI agent memory. It provides structured persistence and deterministic file-based editing required for these systems.

How do I import Field and Type definitions to start designing a schema?

Start designing a schema by importing your `Field`, `Type`, `View`, and `Navigation` definitions using binder tx import. This applies deterministic configuration namespaces and transactions to your workspace.