Name: engin3d-maui-tests
Author: weslleymurdock

Imported from weslleymurdock/Engin3D (.github/skills/engin3d-maui-tests/SKILL.md). Install upstream with npx skills add weslleymurdock/Engin3D --skill engin3d-maui-tests. Copyright stays with the author.

Engin3D MAUI Tests Skill

Use this skill for client-side tests, including MAUI presentation tests and state/graphics behavior.

Test boundaries

Prefer unit tests for Domain, Application, and State. Use bUnit for Blazor-based UI only when the feature under test is actually hosted by a Blazor component; do not force bUnit onto native MAUI XAML views.

Graphics tests should exercise engine-neutral abstractions with deterministic doubles. GPU tests are integration tests and must be explicitly requested by the issue.

Models and resources

When a test needs a 3D model, use repository test resources under:

Resources/Models/<ModelName>/

Model variations and future supported formats live inside the model directory. Textures live under:

Resources/Models/<ModelName>/Textures/

Keep large binary resources under Git LFS when repository policy requires it.

Editor behavior

Cover authoritative state rather than screenshot-only behavior whenever possible. For transform/rotation tools test both directions: viewport operation updates the selected object's state/Inspector, and Inspector edits update the rendered representation through the same state path.

Verify that selecting a second object never inherits transform/rotation values from the first. Verify cancellation and stale callback protection.

Validation honesty

Never claim a test ran unless it was actually executed. Tests that require local assets, GPU drivers, or external services must declare those prerequisites rather than silently skipping behavior.

Install engin3d-maui-tests and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "weslleymurdock-engin3d-engin3d-maui-tests", "kind": "skill", "name": "engin3d-maui-tests", "description": "Test Engin3D MAUI presentation, State, graphics abstractions, and model-driven editor behavior.", "publisher": "weslleymurdock", "version": "1.0.0", "capabilities": { "domains": [ "coding" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Test Engin3D MAUI presentation, State, graphics abstractions, and model-driven editor behavior." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/weslleymurdock/Engin3D", "path": ".github/skills/engin3d-maui-tests/SKILL.md", "ref": "1141d99b2595b3261ae29901f8f031f7bcabb228", "url": "https://github.com/weslleymurdock/Engin3D/blob/1141d99b2595b3261ae29901f8f031f7bcabb228/.github/skills/engin3d-maui-tests/SKILL.md", "key": "weslleymurdock/Engin3D/.github/skills/engin3d-maui-tests/SKILL.md" } }, "instructions": "# Engin3D MAUI Tests Skill\n\nUse this skill for client-side tests, including MAUI presentation tests and state/graphics behavior.\n\n## Test boundaries\n\nPrefer unit tests for Domain, Application, and State. Use bUnit for Blazor-based UI only when the feature under test is actually hosted by a Blazor component; do not force bUnit onto native MAUI XAML views.\n\nGraphics tests should exercise engine-neutral abstractions with deterministic doubles. GPU tests are integration tests and must be explicitly requested by the issue.\n\n## Models and resources\n\nWhen a test needs a 3D model, use repository test ", "cost": { "context_tokens": 390 } }

engin3d-maui-tests

About