fuuz-data-model

Create Fuuz ModelDefinition records for GraphQL-backed entities with fields, relations, and migrations.

Updated Jun 7, 2026
One-click install
npx skills add https://github.com/Fuuz-Platform/llm-skills --skill fuuz-data-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fuuz-data-model
Source: https://github.com/Fuuz-Platform/llm-skills/tree/main/fuuz-data-model
Command: npx skills add https://github.com/Fuuz-Platform/llm-skills --skill fuuz-data-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the complexity of defining Fuuz data models by turning platform-specific model rules, field types, relations, and lifecycle behavior into a clear authoring workflow.

Core Features & Use Cases

  • Model Definition Authoring: Create Reference, Embeddable, and Abstract model structures with the correct top-level metadata.
  • Field and Relation Configuration: Set field types, validation, defaults, sequence numbers, and model-to-model relationships.
  • Operational Controls: Configure triggers, indices, mutation permissions, and migrations for production-ready behavior.
  • Use Case: Use it when you need to design a new WorkOrder or Machine model, expose it cleanly in GraphQL, and keep its schema evolution consistent over time.

Quick Start

Ask the skill to draft a Fuuz ModelDefinition for your entity, including fields, relations, metadata, and migration guidance in package-data format.

Frequently Asked Questions about fuuz-data-model

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

FAQPage Schema
How do I define a data model for GraphQL-backed entities?

To define a data model for GraphQL-backed entities, you create a ModelDefinition record that specifies top-level metadata, field types, relations, and validation rules to ensure your schema is production-ready and discoverable.

What is the difference between reference, embeddable, and abstract model patterns?

Reference, embeddable, and abstract model patterns are structural templates used during data model creation to define entity hierarchy, control field inheritance, and manage how nested data is stored and exposed in your GraphQL schema.

How do I configure triggers and indices for a new data model?

Configuring triggers and indices for a data model involves specifying operational controls and mutation permissions within your ModelDefinition to manage lifecycle behavior and optimize query performance for your package-data workflows.

How do I handle migrations when evolving a data model schema?

Handling migrations for a data model schema requires mapping migration rules within your ModelDefinition to ensure consistent schema evolution over time while maintaining data integrity in package-data workflows.

Can I set validation rules and defaults for data model fields?

Yes, you can set validation rules, default values, and sequence numbers for data model fields to enforce data integrity and standardize entity behavior before records are exposed through GraphQL.

Do I need specific metadata to produce a production-ready ModelDefinition?

Yes, you need correct model metadata, mutation rules, and migration mappings to produce a production-ready ModelDefinition that is fully discoverable and functional within your package-data environment.