Review changes or finished work, check claims against tests, logs, running software, or source files, and explain the findings in plain language. It separates verified facts from assumptions and makes incomplete checks and remaining uncertainty clear.
Audit work, verify claims with concrete evidence, and explain the result in simple grade-5 language. Use when the user asks to review, audit, check, verify, explain a change, explain a fix, summarize test results, validate whether something works, or translate technical findings into plain language for non-technical readers.
Review the instructions the agent will receive before you install.
Treat every answer as three jobs:
Do not skip verification when local files, commands, logs, tests, screenshots, or source data are available. Do not pretend something was verified if it was only inferred.
Start by finding the real source of truth:
Look for:
Prefer evidence in this order:
When verification fails, report the blocker and what it means. When verification is partial, say exactly what was and was not checked.
For performance work, avoid overclaiming. Say "this removes repeated work" only when the code clearly does so. Say "should improve" only when no timing trace was captured. Say "measured faster" only when before/after measurements exist.
Use grade-5 language without talking down to the user:
Prefer this shape:
What changed:
- ...
Why it matters:
- ...
How I verified it:
- ...
What is still not proven:
- ...
For very small answers, use a short paragraph instead of forcing headings.
Translate technical ideas like this:
Do not say "everything works" unless the full workflow was tested. Say "the checked parts work" when verification covered only part of the system.
Lead with the answer. Keep the tone calm and clear.
Include file paths, commands, commit hashes, test names, or log snippets when they are the evidence. Keep them brief.
Separate facts from judgment:
End with the most useful next test only when another test would materially improve confidence.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Build woven fabric in Three.js with visible threads, realistic sheen, seams, and thick hems. The skill covers folds that preserve texture proportions, light passing through thin cloth, and variations in dye and wear.
Build falling leaves in Three.js and similar 3D scenes, with visible front, edge, and back views as they tumble and drift. Coordinate wind, scene depth, camera-aware recycling, and performance checks for a convincing autumn effect.
Add coordinated seasonal transitions to an existing 3D scene. Blend foliage, lighting, sky, ground, snow, and particles from one shared state while preserving camera controls and interactions, so the same place remains recognizable throughout spring, summer, fall, and winter.
Create or integrate detailed 3D models with smooth outlines and believable edges for close-up views. Prepare lower-detail versions for distant viewing, prioritize loading, and measure rendering costs in the actual scene.
Prepare detailed 3D materials that remain clear in close-up views. The skill guides texture resolution, physically based material maps, surface mapping, filtering, and progressive loading while checking download size and GPU memory use.
Create realistic metal surfaces in Three.js by combining structured reflections, studio lighting, scratches, fingerprints, and beveled edges. Includes polished, brushed, and aged finishes for objects such as tools, rings, and metal product parts.