Who it is forA creative coder or hobbyist who has a scene idea, such as a fantasy village, and wants a working first view without choosing a renderer or writing a spec first.
The problemStarting a 3D scene from a blank project means choosing a renderer, lighting, camera and art direction before anything appears on screen.
The outcomeA runnable Three.js scene with a distinct art direction and moving creatures, plus a report of what was built and what was observed in the rendered frames.
What you need first
- Claude Code or Codex installed, with the ability to load a skill folder
- A local checkout of the viettranx/3dviz-pro-max repository
- Your agent's project stack for building Three.js scenes (the skill uses the existing project stack)
- Optional: Playwright, needed only for the capture helper
Steps
- Clone the repository:
git clone https://github.com/viettranx/3dviz-pro-max.git - Copy the whole
skills/3dviz-pro-max/folder into your agent's skill directory, for example~/.claude/skills/, and start a new session. - Name the skill in your first prompt so the agent loads it.
- Give the agent the starting sentence and let it pick the representation and refine the scene from observed results.
- Review the scene in the browser and ask for changes to the art direction or motion.
Prompt for your agent
Using the 3dviz-pro-max skill in the repository at <repo-path>, build a small fantasy village I can explore in Three.js. Choose a distinctive art direction, add a few moving creatures, and inspect the result. Report what you built and what you observed in the rendered frames.
Caveat. The skill supplies guidance and starter files, and your agent must supply the tools that build and run the scene; the repository states it does not render or judge a scene itself.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page