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의 Skill(지시 묶음) 1개, 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질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.