domain-type-creator

Scaffold domain types with JSON I/O, table I/O, and repository support.

25|5|Updated Jun 15, 2024
One-click install
npx skills add https://github.com/OreStudio/OreStudio --skill domain-type-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: domain-type-creator
Source: https://github.com/OreStudio/OreStudio/tree/main/.claude/skills/domain-type-creator
Command: npx skills add https://github.com/OreStudio/OreStudio --skill domain-type-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized blueprint for scaffolding new domain types within OreStudio projects, ensuring consistent discovery metadata and starter artifacts.

Core Features & Use Cases

  • Frontmatter-driven discovery: ensures each domain-type skill exposes a machine-readable name and description.
  • Structured guidance: covers domain class definitions, JSON I/O, table I/O, test data generation, and repository integration.
  • Extensibility: supports optional resources via scripts/, references/, and assets/ to tailor automation and documentation.

Quick Start

Create a new directory for your domain type, add a SKILL.md with the required frontmatter, and begin following the documented workflow to bootstrap I/O, tests, and repository support.

Frequently Asked Questions about domain-type-creator

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

FAQPage Schema
How do I scaffold a new domain type with JSON and table I/O support?

To scaffold a new domain type, you create a directory with a SKILL.md file containing required frontmatter, then follow the structured workflow to bootstrap domain classes, JSON serialization, table I/O, and test data generation.

What is domain-type scaffolding and when do I need repository integration for it?

Domain-type scaffolding is the process of generating standardized domain class definitions alongside I/O and persistence support. You need it to ensure consistent discovery metadata and ORM-style repository integration across project components.

Can I add custom automation scripts when generating domain types?

Yes, you can extend domain-type generation with custom automation by adding optional scripts, references, and assets directories alongside the required SKILL.md file to tailor tooling and documentation.

What's the best way to standardize ORM-style persistence and test data across components?

The best way to standardize persistence and test data is using a scaffolding blueprint that defines domain classes, generates test data, and integrates ORM-style repository support across all components.

Do I need specific frontmatter to enable domain-type discovery and generation?

Yes, domain-type generation requires a SKILL.md file with machine-readable name and description frontmatter to ensure proper discovery metadata before bootstrapping I/O and repository support.