auto-authoring

Generates Unity DOTS Baker code from field-for-field Authoring Inspector mappings to IComponentData structs.

6|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/dyCuong03/unity-agent-team --skill auto-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-authoring
Source: https://github.com/dyCuong03/unity-agent-team/tree/main/.claude/skills/unity-dots/auto-authoring
Command: npx skills add https://github.com/dyCuong03/unity-agent-team --skill auto-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AutoAuthoring eliminates repetitive Unity DOTS Baker boilerplate by automatically wiring an authoring Inspector class’s fields to a runtime IComponentData struct when the mapping is direct.

Core Features & Use Cases

  • Zero-boilerplate Baking: Generates the Baker via reflection for a field-for-field Inspector → IComponentData mapping, so simple components don’t need custom Bake methods.
  • Inspector-driven Entity field resolution: Resolves Entity references from Inspector GameObject references using PropertyContainer, accelerating authoring-to-entity workflows.
  • Graduation path to explicit logic: Helps you switch to an explicit Baker<T> when conversions, Blob assets, nested assets, or DependsOn registration become necessary, keeping your pipeline correct as requirements grow.

Use it when prototyping data-oriented components where authoring fields map directly to runtime fields with no special conversion logic, and when the IComponentData struct is marked [Serializable].

Quick Start

Use the auto-authoring skill to create an IComponentData struct and an AutoAuthoring<YourComponent> authoring class so the Baker is generated automatically from matching Inspector fields.

Frequently Asked Questions about auto-authoring

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

FAQPage Schema
How do I eliminate Unity DOTS Baker boilerplate for simple components?

You eliminate Unity DOTS Baker boilerplate by using auto-authoring to generate baking code via reflection, directly mapping authoring Inspector class fields to a runtime IComponentData struct. This avoids writing custom Bake methods for simple components.

What is the best way to bake authoring Inspector fields directly into an IComponentData struct?

The best way to bake authoring Inspector fields directly is using auto-authoring, which performs a field-for-field mapping between the Inspector and the runtime IComponentData struct. The runtime component must be marked [Serializable].

Can I use auto-authoring for Unity DOTS buffer and shared components?

Yes, you can use auto-authoring for Unity DOTS buffer and shared components through specialized variants. The system supports BufferAutoAuthoring and SharedAutoAuthoring to handle these specific component types.

When should I avoid auto-generating Bakers and write an explicit Baker<T> instead?

You should avoid auto-generating Bakers and write an explicit Baker<T> when your components require data conversions, Blob asset creation, nested assets, multi-entity spawning, or DependsOn registration during the baking process.

How does auto-authoring resolve Entity references from Unity Inspector GameObjects?

Auto-authoring resolves Entity references from Unity Inspector GameObjects by using PropertyContainer. This mechanism accelerates the authoring-to-entity workflow by directly wiring Inspector GameObject references to runtime Entity fields.