develop-flutter-scene-extensions

Build, change, review, and release packages and playground apps in the flutter_scene_extensions workspace. Use for Flutter Scene fork work, flutter_scene_vrm APIs, VRM parsing or humanoid behavior, renderer validation, Island or VRM playground changes, model provenance, MCP automation, upstream preparation, and pub.dev readiness.

Ir a la instalación

Repositorio: K9i-0/flutter_scene_extensions
Última actividad en el origen: 24 de agosto de 2026 a las 09:22
Idioma detectado de SKILL.md: inglés
Estrellas: 0
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/K9i-0/flutter_scene_extensions --skill develop-flutter-scene-extensions

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

Explorador de archivos

3 archivos

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

Develop Flutter Scene Extensions

Read the root AGENTS.md, then open only the directly relevant ground-truth document it names.

Workflow

Identify whether the change belongs to generic glTF/Scene behavior, the VRM extension layer, or a non-published playground.

Keep generic glTF behavior in the pinned Flutter Scene fork. Keep VRM types in packages/flutter_scene_vrm. Keep cameras, UI, platform channels, and game state in playgrounds.

Add targeted tests with each behavior change. Do not promote parsed-only features to supported status.

For UI or scene behavior, run the app through Dart MCP and verify the state through Marionette custom extensions. Capture a screenshot when appearance changes.

Run mise exec -- dart run tool/check.dart. Use --build when platform or renderer compatibility can change.

Update public API docs, the feature matrix, changelog, and upstream plan when their claims change.

Asset changes

Before adding an asset, record its source URL, exact revision, SHA-256, license, attribution, redistribution permission, and modification permission. Keep the license beside the asset and update THIRD_PARTY_NOTICES.md. Do not infer that a repository code license covers models, textures, audio, logos, or mascots.

Release and upstream boundary

Keep flutter_scene_vrm at 0.x and publish_to: none while it has a Git dependency. Prepare upstream work as small generic glTF pull requests with focused tests. Publish only after the package resolves exclusively through SDK and hosted pub.dev dependencies.

Read references/commands.md when choosing validation commands or MCP extensions.

name	develop-flutter-scene-extensions
description	Build, change, review, and release packages and playground apps in the flutter_scene_extensions workspace. Use for Flutter Scene fork work, flutter_scene_vrm APIs, VRM parsing or humanoid behavior, renderer validation, Island or VRM playground changes, model provenance, MCP automation, upstream preparation, and pub.dev readiness.