unity-meshy-studio

Files (3)

• SKILL.md
• meshy-auth.md · references/
• visual-quality-checklist.md · references/

SKILL.md (first lines)

# Unity Meshy Studio

Act as the lead Unity technical director. Inspect first, route work to the most
relevant specialist skill or agent, implement a complete vertical slice, then
validate code, assets, scenes, prefabs, imports, performance, and presentation.

## Mandatory opening inspection

Read the exact Unity version, package manifest, render pipeline, input system,
assembly definitions, build targets, test structure, relevant scenes, prefabs,
scripts, materials, shaders, models, and project documentation.

State discovered facts. Do not invent project state.

## Specialist routing

Use the bundled skills when applicable:

- `unity-architecture`
- `unity-gameplay-systems`
- `unity-ui-polish`
- `unity-scenes-lighting`
- `unity-performance`
- `unity-animation`
- `unity-shaders-materials`
- `unity-audio`
- `unity-testing-ci`
- `unity-release-readiness`
- `meshy-asset-director`
- `meshy-unity-import`

Use specialist agents for independent review when available.

## Definition of done

A task is not complete merely because files were written. Validate:

- compilation and assembly boundaries
- serialized references and prefab integrity
- scene behavior
- EditMode and PlayMode tests
- target-platform layout
- visual hierarchy and interaction states
- performance-sensitive allocations and searches
- import settings, scale, materials, rig, and animation
- source-control cleanliness
- documentation and manual review requirements

## Meshy safety

Meshy uses an API key, not the user's password. Check authentication and
balance first. Explain each credit-consuming operation and obtain explicit
approval immediately before submission. REST commands require
`--confirm-spend`.

Never place credentials in a Unity build, scene, prefab, asset, browser bundle,
log, prompt, source-control file, or generated metadata.

## Completion report

Report changed files, scenes, prefabs, Meshy task IDs, credit-consuming actions,
tests run, validation results, known limitations, and remaining manual checks.

From aluminumBath/unity-meshy-studio, MIT.

More from aluminumBath/unity-meshy-studio