Build Vesperfall Review Assets logo

Build Vesperfall Review Assets

CommunityPopular
MengTo
build-vesperfall-review-assets

Build truthful Vesperfall asset-library review pairs from transparent PNG references and live Three.js, FBX, or img2threejs models. Use when adding a character, enemy, prop, or equipment asset to the Vesperfall catalog; creating a card-PNG plus inspector-model treatment; exposing an isolated model or moveset route; or standardizing provenance, grounding, tests, and Codex-browser validation for game art review.

Overview

PublisherMengTo
RepositorySkills
Skill namebuild-vesperfall-review-assets
Stars
6.1K
Forks
717
Bundled files
3
LicenseMIT
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by MengTo on GitHub. Read the source before you install it.

Installation

Install the Build Vesperfall Review Assets AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/MengTo/Skills.git /tmp/Skills
mkdir -p .claude/skills
cp -r /tmp/Skills/agent-skills/game-development/build-vesperfall-review-assets .claude/skills/build-vesperfall-review-assets
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Build Vesperfall Review Assets in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Build Vesperfall Review Assets on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Build Vesperfall Review Assets is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Build Vesperfall Review Assets

Create one reviewable asset pair without confusing catalog media, imported files, procedural factories, and future contracts.

Workflow

  1. Inspect repository truth before choosing a model path.
    • Locate shipped PNG, FBX, GLB, textures, runtime factories, and declared-but-missing paths.
    • Prefer a shipped FBX/GLB when it is the actual runtime source.
    • Use $img2threejs only when reconstructing from an image in code. Never relabel imported geometry as img2threejs.
    • Do not claim a GLB or texture exists because code declares a future URL.
  2. Produce the transparent catalog reference.
    • Reuse or derive from the production portrait when it already matches the asset identity.
    • Normalize catalog copies to 512×512 RGBA unless the project contract says otherwise.
    • Keep transparent corners and avoid baked floor, halo, or shadow.
    • Store project-bound output under public/asset-catalog/<category>/.
  3. Build the live model preview.
    • Put loading/model construction in a small asset-specific module.
    • Preserve runtime provenance in userData: source paths or factory, action count, sockets, and review-only status.
    • Attach equipment to named sockets. Keep materials, renderer, mixers, events, and animation frames disposable.
    • Frame from measured bounds. Ground from foot/contact geometry, not the lowest weapon tip.
  4. Pair the catalog surfaces.
    • Card/grid: transparent PNG only, with no canvas.
    • Selected inspector: one live model canvas plus truthful format label.
    • Add a button to an isolated preview or moveset route.
    • Keep fallback media visible until WebGL/model loading is ready.
  5. Build the isolated review route.
    • Expose the real action library when clips exist.
    • Provide restart, pause/play, action selection, drag rotation, source paths, and provenance.
    • For procedural motions, mark runtime, contract, and candidate actions separately.
  6. Validate before committing.
    • Run scripts/validate_pair.py <png> <model-source>.
    • Add inventory tests for exact paths, RGBA dimensions, preview kind, and route.
    • Test every motion/contact point deterministically when grounding changes with animation.
    • Run build, lint, full tests, and git diff --check.
    • Use the Codex in-app browser only. Verify desktop and mobile, card PNG/no canvas, inspector model/one canvas, preview navigation, grounding, scroll, overflow, broken media, and console warnings/errors.
  7. Commit the narrow task and hand off its exact SHA before deployment reconciliation.

Read references/catalog-contract.md when changing catalog types, provenance language, or review-route behavior.

Required reporting

Report:

  • PNG path, dimensions, and alpha status
  • model source or procedural factory
  • whether the model is imported, runtime procedural, or review-only reconstruction
  • preview route and available actions
  • test/build/browser proof
  • exact commit SHA

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Build Vesperfall Review Assets AI skill do?

Build truthful Vesperfall asset-library review pairs from transparent PNG references and live Three.js, FBX, or img2threejs models. Use when adding a character, enemy, prop, or equipment asset to the Vesperfall catalog; creating a card-PNG plus inspector-model treatment; exposing an isolated model or moveset route; or standardizing provenance, grounding, tests, and Codex-browser validation for game art review.

Why use Build Vesperfall Review Assets on TypingMind?

Because you install it once and use it with any model. Build Vesperfall Review Assets is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Build Vesperfall Review Assets in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/MengTo/Skills/tree/main/agent-skills/game-development/build-vesperfall-review-assets. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Build Vesperfall Review Assets?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Build Vesperfall Review Assets?

As many as you like. As long as a model supports skills, you can use Build Vesperfall Review Assets with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Build Vesperfall Review Assets AI skill free?

Yes. It is published on GitHub by MengTo under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
obra logo

Writing Plans

obra
CommunityPopular

Use when you have a spec or requirements for a multi-step task, before touching code

25.8K
288.1K
1 files
View
mattpocock logo

Ask Matt

mattpocock
CommunityPopular

Ask which skill or flow fits your situation. A router over the skills in this repo.

22.3K
264.4K
2 files
View
mattpocock logo

Code Review

mattpocock
CommunityPopular

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what…

22.3K
264.4K
1 files
View
mattpocock logo

Codebase Design

mattpocock
CommunityPopular

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or…

22.3K
264.4K
3 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇