Skip to content
Back to search

nc-worlds

MarketplaceWorks with Claude CodeGitHub

Procedural WebGPU world-building skills by nilesh-0608.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/nilesh-0608--nc-world-forge/badge.svg)](/listings/nilesh-0608--nc-world-forge)

HTML

<a href="/listings/nilesh-0608--nc-world-forge"><img src="/api/listings/nilesh-0608--nc-world-forge/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

With the skills CLI:

npx skills add nilesh-0608/nc-world-forge

Or, on Claude Code 2.1.275 or later, as a plugin:

/plugin install nc-world-forge --marketplace nilesh-0608/nc-world-forge

Then, in your agent session, ask for a world. The skill triggers on requests like "build me a procedural world", "a flooded cathedral I can fly through", or by name.

**You need:** Node, and a browser with WebGPU and graphics acceleration switched on — in Chrome, `chrome://settings/system` → *Use graphics acceleration when available*. The build works without a GPU; the verification does not.

---

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 14 lines
  1. {
  2. "name": "nc-worlds",
  3. "description": "Procedural WebGPU world-building skills by nilesh-0608.",
  4. "owner": { "name": "nilesh-0608", "url": "https://github.com/nilesh-0608" },
  5. "plugins": [
  6. {
  7. "name": "nc-world-forge",
  8. "source": "./",
  9. "description": "Interviews you about a world, then builds it as a single self-contained procedural WebGPU HTML file and verifies it against a ten-gate visual protocol.",
  10. "category": "creative",
  11. "tags": ["webgpu", "procedural-generation", "3d", "wgsl"]
  12. }
  13. ]
  14. }
README.md · README · 215 lines
  1. # nc-world-forge
  2. **An agent skill that interviews you about a world, then builds it.**
  3. You install it, describe a place, and answer twelve questions about it. The agent maps your
  4. answers onto a bundled procedural WebGPU engine, makes the edits, builds it, and checks the
  5. result against a ten-gate visual protocol. What you get back is **one self-contained HTML
  6. file** you can fly through — terrain, vegetation, light shafts, creatures, haze, six fixed
  7. viewpoints, three detail levels, a day/night toggle. No images, no 3D models, no audio
  8. files, nothing fetched over the network. The whole world is generated from mathematics when
  9. the page opens.
  10. ---
  11. ## See it first
  12. **[Open Skylight Cavern →](https://nilesh-0608.github.io/nc-world-forge/engine/)** — the
  13. reference world that ships with the engine, running in your browser.
  14. A limestone cavern under a collapsed roof: shafts falling through the openings onto a moss
  15. mound, dust lit only inside the beams, swiftlets wheeling under the roof and kites circling
  16. the sky above it. It renders the moment you clone the repo, and it fills all eight content
  17. slots the interview asks about — so there is always a working example to read the docs
  18. against.
  19. ---
  20. ## Install
  21. With the skills CLI:
  22. ```
  23. npx skills add nilesh-0608/nc-world-forge
  24. ```
  25. Or, on Claude Code 2.1.275 or later, as a plugin:
  26. ```
  27. /plugin install nc-world-forge --marketplace nilesh-0608/nc-world-forge
  28. ```
  29. Then, in your agent session, ask for a world. The skill triggers on requests like "build me
  30. a procedural world", "a flooded cathedral I can fly through", or by name.
  31. **You need:** Node, and a browser with WebGPU and graphics acceleration switched on — in
  32. Chrome, `chrome://settings/system` → *Use graphics acceleration when available*. The build
  33. works without a GPU; the verification does not.
  34. ---
  35. ## How to use it
  36. **1. Install it** (above), then open an agent session in the folder where you want the world
  37. to live — an empty folder is fine.
  38. **2. Ask for a world.** Say what you want in your own words:
  39. ```
  40. Build me a procedural world: a flooded gothic cathedral, knee-deep in
  41. still water, light coming down through broken rose windows.
  42. ```
  43. Or invoke it directly — in Claude Code the skill's name is its slash command:
  44. ```
  45. /nc-world-forge
  46. ```
  47. You do not need to know the engine, WGSL or WebGPU. There is nothing else to configure: the
  48. skill registers on install, and it also triggers on its own when you describe a world.
  49. **3. Answer the twelve questions.** They come a few at a time, and each one maps onto
  50. something the engine actually draws, so there are no throwaway answers. "I don't know" is a
  51. usable answer — the skill proposes something and you correct it.
  52. **4. Let it build and verify.** It copies `engine/` into `./<your-world>/`, runs
  53. `npm install`, edits the seam, builds, and then works through the ten gates. Expect to be
  54. asked to look at screenshots: **the visual gates need a real GPU, so they run in your
  55. session, not in a subagent.**
  56. **5. You get back:**
  57. | | |
  58. |---|---|
  59. | `<your-world>/index.html` | the world — one self-contained file, open it in Chrome |
  60. | `<your-world>/WORLD-BRIEF.md` | your answers, and which slots you left empty |
  61. | `<your-world>/source/` | the readable source, to keep tuning |
  62. | the gate table | ten gates with evidence, and an honest list of what still looks wrong |
  63. **6. Keep tuning, or publish it.** `cd source && npm run build` rebuilds after any edit.
  64. `index.html` works offline and can be emailed; to put it online, push the folder to a repo
  65. and switch on GitHub Pages, which is how the two worlds below are hosted.
  66. ### If something goes wrong
  67. - **A blank screen** usually means WebGPU or graphics acceleration is off. Check
  68. `chrome://gpu`. Every generated world shows a plain message instead of a broken scene.
  69. - **"It built fine" is not done.** A green build is not the bar — see the gates.
  70. - **Keep the installed `engine/` clean.** Each world is a copy; never edit the original.
  71. ---
  72. ## What a session looks like
  73. 1. **The interview.** Twelve questions, asked a few at a time. What the setting is; whether
  74. distance here reads as colour loss, occlusion or darkness; what the ceiling is and what
  75. punches holes in it; what the light through those holes looks like; what pattern it casts
  76. on the floor; what stands vertically; what drifts in the air; what moves in groups; what
  77. moves alone and large; how the air changes with height; the palette and what night looks
  78. like; and what it is called. Each question maps onto something the engine actually draws,
  79. which is why there are twelve of them and not one open-ended one.
  80. 2. **The build.** The engine is copied into a new folder and edited at its seam —
  81. `world.js`, `shaders.js`, and the resource/pass/draw section of `main.js` — then bundled
  82. into a single file.
  83. 3. **The verification.** Six viewpoints screenshotted with performance read at each, a
  84. pinned-resolution flythrough benchmark, all three detail levels loaded, the console read,
  85. the camera checked against the geometry, and a reload compared for reproducibility. Ten
  86. gates, each recorded with its evidence.
  87. A green build is explicitly not the finish line. Every known defect in the worlds built
  88. before this skill existed passed a green build, including a canopy that stayed
  89. daylight-green at night.
  90. 4. **The handover.** The file, the gate table, the screenshots, the benchmark numbers, the
  91. brief, a tuning table for your world, and an honest list of what looks wrong.
  92. ---
  93. ## Honest scope
  94. **The engine is built for enclosed layered volumes lit from above.** A rainforest, an
  95. ocean, a cavern and a volcanic basin are not four settings — they are one shape: something
  96. overhead with holes in it, light coming through, a floor patterned by that light, things
  97. standing between the two, and air with a density gradient. If your world is that shape, the
  98. engine's content slots all have an obvious occupant and the result is strong.
  99. **The skill will attempt any world you name.** It does not refuse, and it does not shape-test
  100. you first. But be clear about the trade: a world outside that family comes out weaker, and
  101. not because the agent gave up. A desert empties most of the content slots — no ceiling, so no
  102. shafts, so no floor pattern — and it turns haze into heat shimmer, which is a different
  103. shader than the one that ships. An open plain has the same problem. You will get something,
  104. and the agent will tell you which slots went empty, but you will be getting a world the
  105. engine was not shaped for.
  106. The family is guidance so you can self-select. It is not a gate.
  107. Also honest:
  108. - **No world has been built end to end with this skill yet.** The engine and the reference
  109. world are verified on a real GPU — shaders compile, all six viewpoints render, the ten
  110. gates were walked. The interview-to-finished-world path has not been run once. You may be
  111. the first, and it may be rough.
  112. - **There are no download counts, cross-machine benchmarks, or user reports**, because there
  113. are none.
  114. - **One performance figure has been measured:** median frame time 5.6 ms at 1440×900 on an
  115. RTX 4060 Ti. That run was refresh-capped, so it is a floor on what the engine can do, not
  116. a ceiling. Nothing has been measured on phones, on integrated graphics, or on any other
  117. GPU.
  118. - **Quality depends on your answers.** The interview is twelve questions because twelve
  119. questions is what the engine can act on. Vague answers get concrete defaults, and the
  120. agent will say which defaults it chose, but it cannot invent a world you have not
  121. described.
  122. ---
  123. ## Worlds built this way
  124. Both of these were built by hand on the same lineage, before the skill existed. They are
  125. what the output looks like, not output of the skill.
  126. - **nc-3d-world-amazon** — an Amazon rainforest. Buttressed trunks, light shafts through
  127. canopy gaps, fireflies in the understorey, stars above the canopy at night.
  128. [Open it →](https://nilesh-0608.github.io/nc-3d-world-amazon/) ·
  129. [source](https://github.com/nilesh-0608/nc-3d-world-amazon)
  130. - **nc-3d-world-volcano** — an active volcano. A breached crater rim, a lava lake, a cascade
  131. down a gorge with a rock bridge over it, and a lava river out across the basin floor.
  132. [Open it →](https://nilesh-0608.github.io/nc-3d-world-volcano/) ·
  133. [source](https://github.com/nilesh-0608/nc-3d-world-volcano)
  134. Those two are linked to each other: each has a doorway standing in it that you can fly
  135. through to reach the other. Press `1` in either and look for it.
  136. ---
  137. ## What's in the repo
  138. ```
  139. SKILL.md the skill: interview, map, edit, build, verify
  140. README.md this file
  141. LICENSE MIT
  142. docs/question-set.md the twelve questions, what each determines, and what a weak answer looks like
  143. docs/verification.md the ten gates, and four traps that produce confident garbage
  144. docs/architecture.md the seam, the file roles, the build, the constraints, the tuning table
  145. engine/ the neutral engine, with a reference world that renders on install
  146. index.html the reference world, built
  147. source/ build.mjs, package.json, template.html, src/*.js
  148. REFERENCE-WORLD.md what the reference world puts in each content slot
  149. ```
  150. The engine ships with a working reference world, so you can see it render before you build
  151. anything of your own.
  152. ---
  153. ## Credit and licence
  154. MIT. Published by [nilesh-0608](https://github.com/nilesh-0608).
  155. The engine descends from **[Abyssal Garden](https://github.com/Noniv/abyssal-garden)** by
  156. **Maksymilian Dendura**, MIT licensed. The renderer, the adaptive-resolution controller, the
  157. surface-nets terrain, the instancing and the single-file build are all its work. That
  158. attribution travels two hops on purpose: into this engine, and into every world the skill
  159. generates. The skill will not build you a world that drops it.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.