SuperAPI AI Directory

blender-quality-validation

Design & creation

View repository

Updated 10-15 21:47

About this skill

Blender quality validation

Use only explicit targets and intent supplied by the task: objects, armature bones, frame intervals, contact points, collision proxies and numeric limits. Do not infer every performance intention from scene geometry.

Run the relevant validation.* checks and return the measured value, affected object or bone, frame range, limit and pass/fail result. Character work commonly combines limb length, planted-foot drift, prop handoff and floor penetration; camera work adds visibility and motion-discontinuity checks.

Technical thresholds are necessary but do not replace visual review. After numeric checks, inspect silhouette, balance, contact readability and composition. If a check lacks a required proxy or frame interval, identify that exact missing input; do not silently broaden the target set.

When to Use

Use when a task provides measurable acceptance criteria for geometry, characters, props, collisions, motion, or cameras and pass/fail evidence must be produced.

Prerequisites

  • Explicit target objects, bones, frame ranges, contact points, proxies, units, and tolerances.
  • Acceptance criteria must come from the task or an approved brief; when intent is missing, thresholds must not be derived independently.

Workflow

Step 1. Map each criterion to a specific validation.* check and input. Step 2. Fix the scene revision and frame range, run the checks, and save the raw measurements. Step 3. For failed items, locate the object, bone, and frame without expanding the target set. Step 4. After the numerical checks, supplement with a visual review of silhouette, balance, contact, and composition. Step 5. Output item-by-item PASS, FAIL, or UNVERIFIED, and state any missing inputs.

Validation and Delivery Evidence

Each item includes the check name, target, revision, frame range, measured values, units, threshold, tolerance, status, and preview reference.

Rules and Capability Boundaries (Not Applicable Scenarios)

Technical thresholds cannot replace aesthetic acceptance; without a proxy or frame range, it must be marked UNVERIFIED and must not default to pass.

Gotchas (Common Issues and Recovery)

  • Unit errors: return to scene units and object scale, then re-measure.
  • Target does not exist: stop that item and report the exact name.
  • Missed boundary frames: extend explicit sampling points, but do not exceed the approved frame range.