# 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.

- Skill: `k9i-0/develop-flutter-scene-extensions` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add k9i-0/develop-flutter-scene-extensions`
- Raw SKILL.md: https://api.skillmd.com/api/skills/k9i-0/develop-flutter-scene-extensions/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: k9i-0 (https://skillmd.com/u/k9i-0)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/k9i-0/develop-flutter-scene-extensions

---


# Develop Flutter Scene Extensions

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

## Workflow

1. Identify whether the change belongs to generic glTF/Scene behavior, the VRM
   extension layer, or a non-published playground.
2. 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.
3. Add targeted tests with each behavior change. Do not promote parsed-only
   features to supported status.
4. 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.
5. Run `mise exec -- dart run tool/check.dart`. Use `--build` when platform or
   renderer compatibility can change.
6. 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](references/commands.md) when choosing validation
commands or MCP extensions.