// Use this skill when bringing up a new model family, re-basing an existing family onto the current platform contract, or deciding what belongs in core workflow orchestration versus family or host code.
Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.
Use this skill when working on MLXR runtime debugging, log triage, validation discipline, benchmark-backed claims, or deciding whether runtime behavior is strong enough to count as evidence rather than a one-off run.
Design static and light-motion media assets such as posters, slides, cards, flyers, invitations, social graphics, thumbnails, hero images, banners, certificates, README art, and short promo reels. Use when Codex needs to turn text, images, icons, or video into polished layout-driven visuals, especially through a reproducible Python, Pillow, SVG, or ffmpeg workflow.
Use this skill when debugging real LTX-2.3 output quality, running safe manual smoke tests, interpreting stage snapshots, or deciding whether a result is specific enough to count as a clear dog or other visually coherent subject.
| name | family-bringup |
| description | Use this skill when bringing up a new model family, re-basing an existing family onto the current platform contract, or deciding what belongs in core workflow orchestration versus family or host code. |
Use this skill for the narrow slice where MLXR is onboarding a new family or reshaping a family boundary in a way that affects workflow ownership, capability claims, or the truthful first slice.
This skill is for:
Do not use this skill for routine bug fixes or the common implementation path. The default repo loop still lives in AGENTS.md, MEMORY.md, and docs/agent-native-development.md.
docs/workflow-orchestration-design.md.docs/family-bringup/README.md, docs/family-bringup/checklist.md, and docs/family-bringup/template.md.docs/family-bringup/debugging-decision-tree.md.docs/technical-design.md, docs/phased-delivery-plan.md, and docs/research/09-open-questions-and-validation-plan.md.docs/workflow-orchestration-design.mddocs/family-bringup/README.mddocs/family-bringup/checklist.mddocs/family-bringup/template.mddocs/family-bringup/debugging-decision-tree.md when isolating runtime-quality or runtime-contract failuresdocs/product-requirements.mddocs/technical-design.mddocs/phased-delivery-plan.mddocs/research/09-open-questions-and-validation-plan.mdLoad the relevant family research doc and adapter code only when needed for the specific family.
For LTX-2.3 family pressure, also load:
docs/research/07-ltx-integration-seams.md