REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Agent skill for creative 3D visualization: turn an idea into a Three.js/Blender scene worth exploring. Claude Code + Codex plugin, 223 recipes, 440 knowledge records, 22 proved kits, 37 runnable studies.
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/viettranx-3dviz-pro-max)同じ作業で AI をサービスにつなぐ MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
同じ種類の作業。Skill 一覧と同じ並び
| これ 3dviz-pro-max | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 作者 | viettranx | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 数 | 1 | 1 | 1 | 1 | 1 |
| GitHub スター | 1,408 | 467,235 | 234,125 | 149,873 | 144,332 |
| 最終コード更新 | 2026年9月11日 | 2026年11月18日 | 2026年4月20日 | 2026年11月18日 | 2026年11月18日 |
| ライセンス | MIT | MIT | – | Apache-2.0 | MIT |
viettranx による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeClaude (เว็บ/แอป)Codex
提供元の README と repo のフォルダから判断
GitHub account viettranx (person), 13 years old
★ 1,408 stars · code last changed 2026年9月11日
67 scripts that can run on a computer: scripts/blender_locate.py, scripts/capture.py, scripts/capture_view_quality.py, scripts/catalog.py and 63 more
Could not check every script (some are too large); read them first
No hooks or writes to machine settings found
Checked automatically from the repo files at commit d077e0e (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
This skill is over 5 MB or 300 files, so we do not build a ZIP. Use "Let the AI install it" instead
この文をコピーして Claude Code のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code を開き直し、/3dviz-pro-max と入力するか関連する作業を頼むと Claude が自動で使います
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
/plugin marketplace add viettranx/3dviz-pro-max
/plugin install 3dviz-pro-max@3dviz-pro-max提供元の README から引用。提供元のコードをダウンロードして実行します
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/viettranx/3dviz-pro-max.git /tmp/popnx-skill-viettranx-3dviz-pro-max-d077e0e && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-viettranx-3dviz-pro-max-d077e0e/skills/3dviz-pro-max' ~/.claude/skills/3dviz-pro-maxChatGPT デスクトップアプリには Codex が組み込まれていて、Codex は ~/.agents/skills フォルダから Skill を読み込みます
ChatGPT デスクトップアプリで Codex を開き、この文をチャットに貼り付けます
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
3dviz-pro-max フォルダを ~/.agents/skills/3dviz-pro-max に置きます
~ はホームフォルダ($HOME)です
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/viettranx/3dviz-pro-max.git /tmp/popnx-skill-viettranx-3dviz-pro-max-d077e0e && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-viettranx-3dviz-pro-max-d077e0e/skills/3dviz-pro-max' ~/.agents/skills/3dviz-pro-maxChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
自分でインストールした Skill は使えません。ディレクトリのプラグインに含まれる Skill だけが使えます
この Skill を ChatGPT で使うには、上の方法で ChatGPT デスクトップアプリを使ってください
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
この文をコピーして Codex のチャットに貼り付けます · ChatGPT デスクトップアプリ内の Codex、Codex CLI、IDE 拡張機能で使えます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex は新しくインストールした Skill を自動で見つけます。表示されない場合は Codex を再起動してください · 使い方:ChatGPT では @ を入力して Skill を選びます · Codex CLI や IDE 拡張機能では /skills を実行するか、$ に続けて Skill 名を入力します
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/viettranx/3dviz-pro-max.git /tmp/popnx-skill-viettranx-3dviz-pro-max-d077e0e && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-viettranx-3dviz-pro-max-d077e0e/skills/3dviz-pro-max' ~/.agents/skills/3dviz-pro-maxこの文をコピーして Cursor のチャットに貼り付けます
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Cursor の Agent チャットで / を入力し 3dviz-pro-max を選ぶ
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/viettranx/3dviz-pro-max.git /tmp/popnx-skill-viettranx-3dviz-pro-max-d077e0e && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-viettranx-3dviz-pro-max-d077e0e/skills/3dviz-pro-max' ~/.cursor/skills/3dviz-pro-maxSkill を読めるほかのアプリ向けです。この文には Claude Code、Codex、Cursor のパスが入っていて、AI が使っているアプリに合わせて選びます · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、SKILL.md のあるフォルダをコピーしてください。
2026年11月11日 に Claude Code、Codex、Cursor の公式ガイドで skill フォルダを確認
✓ コマンド確認済み 2026年11月19日
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · GitHub で全文を開く
---
name: 3dviz-pro-max
description: Design and build expressive 3D scenes, explainers and interactive models with grounded subject knowledge. Use for 3D creation or edits, including scientific visualization and spatial puzzles.
---
# 3Dviz Pro Max
Use the agent's spatial reasoning, geometry, composition and programming abilities to realize the
user's idea. The catalog, kits, rigs and scripts accelerate decisions and construction; they do not
set the boundaries of what you can make. A runnable scene still needs visual judgment.
## Workflow
For a new scene, work through the decisions below. For an existing artifact, inspect it first and
apply only the steps affected by the change. User constraints override suggested tooling and records.
1. **Intent and visual direction.** Identify what the viewer should see, feel, understand or do.
Choose a distinctive visual idea, useful references and the intended viewing distance. Decide how
shape, material, light, camera and motion work together. Time of day matters for some environments;
an anatomical study or mathematical object may need a studio, diagrammatic or invented setting.
2. **Reason about the important objects.** Before selecting a template, identify the silhouette,
proportions, parts, connections, surface identity and behavior that make each important object
convincing. Use [object reasoning](references/object-reasoning.md) and
[object craft](references/object-craft.md). Solve the hardest or most distinctive object early.
3. **Ground the representation.** Choose illustration, discrete state, simulation or playback; a
scene can combine them if their boundaries are clear. For established academic, scientific or
technical claims, research the actual passages and fact-check claim → model → rendered result
using [research and truth](references/research-and-truth.md). A decorative mesh, imported anatomy
or physics engine does not certify a scientific claim. Identify the authoritative state.
4. **Choose construction per object.** Use the routing table below. Search for the missing decision
when useful; do not force a subject into the closest lexical match. Recipes, numerical defaults
and look profiles are candidates to adapt, not instructions to copy every value.
At important joins, decide whether the object needs a continuous skin, a layered covering or
separate articulated parts. Use [surface continuity](references/object-craft.md#choose-continuity-at-the-join)
when attached volumes look accidental; mesh merging is not a universal cleanup prescription.
```sh
python3 scripts/search.py "<subject and unresolved decision>"
python3 scripts/resolve.py <record-id>
python3 scripts/design-context.py "<objective>" --blueprints --look <style-id>
```
5. **Set quality targets and discover tools.** State what the object must withstand at overview,
inspection and close-up distances, including factual fidelity where relevant. Discover available
tools without treating tool availability as artistic quality:
```sh
python3 scripts/host-probe.py --out host.json
python3 scripts/design-context.py "<objective>" --blueprints --host host.json \
--delivery web-desktop --hero <blueprint-id>
```
T0–T4 describe the existing kit pipelines and their declared proof status. The legacy
`quality_ceiling` field is a shipped-kit pipeline recommendation, not a limit on custom geometry,
external assets, procedural materials or the agent's creativity. A missing kit tier does not
prohibit another construction method. Blender availability does not make an object high quality;
Three.js-only construction does not make it low quality.
6. **Build a convincing first view.** Keep the user's stack. Reuse shared scripts, renderer setup,
[rigs and scaffold](templates/README.md), material utilities and geometry operations where they
help. For a large scene or collection, inspect one representative demanding object or scene before
multiplying the approach. A kit-shaped prototype should not silently become the finished hero.
Author custom geometry, shaders, materials, textures, lighting and interactions as needed. Use
Blender for suitable modeling, sculpting, rigging, UV or baking work; use Three.js for suitable
procedural geometry, interactive state and rendering. Choose their handoff deliberately.
For a distinctive finish, develop [palette and material direction](references/object-craft.md#develop-a-material-direction)
from useful references: translate them into part assignments, surface scale and light response.
Material refinement can strengthen a good form; keep evaluating shape and attachments separately.
When adding or changing directional, practical, day/night or rescaled lighting, read
[lighting direction and scale](references/lighting-direction-and-scale.md) before implementing the
rig. Identify emitter/receiver ownership and final world scale; choose the artistic treatment freely.
7. **Make behavior belong to the model.** Keep transforms, joints, contacts and controls tied to
their authoritative state. Inspect surrounding objects too: a stand needs support, a light ray
must stop at an opaque obstacle in its modeled scene, a creature needs clearance. An illustration
may simplify physics, but should not accidentally imply a simulation it does not perform.
Allocate reusable geometry once where practical; update transforms, uniforms or buffers during
motion. Park static scenes and respect reduced-motion preferences. Do not remove identity-defining
detail merely to meet an unmeasured budget; optimize what actually costs work.
Use [subject clarity and meaningful motion](references/subject-clarity-and-motion.md) when
identity, mechanism or control effects are unclear. Explain what changes and stays fixed; keep
landmarks, color meanings and readouts synchronized with the visible state. Check local deformation
and attachments through relevant extremes, not just the resting silhouette.
8. **Run and inspect the real output.** Build through the project's existing commands, then view
the artifact in an available authorized browser. Inspect overview, meaningful close-ups and the
important interactions. If automated capture is allowed, the optional shared command is:
```sh
pnpm build
python3 scripts/capture.py --dir dist --all-views --click "#control" --out captures
```
Add `--motion-check 2000 --expect-motion` only when the tested state should visibly move.
`--expect-usable` can flag gross visibility failures; it does not judge art. A visible-browser
inspection is valid when headless execution is excluded. Never describe an unobserved frame.
For lighting changes, inspect source isolation at fixed exposure, an informative direction change,
and any output/reset controls. Check affected receivers and occluders, not just glowing bulbs.
Preserve the user's motion and camera choices across lighting modes unless a control promises reset.
9. **Refine by subject and evidence.** Use [visual review](templates/checklists/visual-anti-slop.md)
and [interaction/frame inspection](templates/checklists/inspection-per-frame.md) as conditional
prompts. Correct factual errors, broken controls and misleading relationships, then improve the
most consequential visual weakness. A failed shape may require a different construction method,
not more texture or a higher kit tier. For pinching, detached attachments or repeated pose fixes,
use [regional deformation diagnosis](references/object-craft.md#diagnose-deformation-at-the-region-that-fails):
solver accuracy, surface deformation and visual quality need separate evidence. Revisit ownership
and rig assumptions after changing geometry. Continue useful refinement; reassess an approach that keeps
failing rather than applying a fixed number of cosmetic passes.
10. **Report honestly.** Separate what was built, observe質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。