← ClaudeAtlas

network-journey-webgllisted

Build an immersive, scroll-driven 3D product website in the igloo.inc tradition — one continuous Three.js world behind real HTML chapters, a camera that flies through it on a single scroll value, HUD corners with mono labels, leader-line tags pinned to 3D objects, a particle cloud that morphs into line drawings, and forest-green + lime on a near-black night — with production engineering - SvelteKit static build, quality tiers (Full / Lite / Mobile / Static with pre-rendered stills), lazy-loaded scene and scroll libraries, self-hosted fonts, a strict CSP, no third-party requests, SEO files, Playwright + axe tests and a GitHub Pages workflow. Use for network, security, infrastructure, data or developer tools, or when the user asks for an experimental / immersive / "igloo-like" 3D site, a scroll camera journey, a network-sphere hero or a WebGL site that still scores well on Lighthouse. Produces a SvelteKit project and its static build.
smyrna-pergamum/web-design-skills · ★ 1 · Web & Frontend · score 74
Install: claude install-skill smyrna-pergamum/web-design-skills
# Network journey WebGL An experimental product site that feels like entering a digital installation, but loads like a fast document. The visitor scrolls into the product's world (here: a home network), stops at one object per chapter, and leaves with real, checkable facts. Structure and HUD follow igloo.inc's single-scene journey; colours, objects and copy belong to the product. The reference build is the real website for **[LANORA](https://github.com/smyrna-pergamum/Lanora)**, a free, open-source network scanner for Windows: `example/` is the static build (open `example/index.html` through a web server), `source/` the SvelteKit project. Detailed code is in `references/components.md`; `screenshots/` shows every chapter on desktop and mobile. If the user names a reference site, take its *structure and rhythm* only. Never copy its renders, models, copy or logo. ## 1. Before designing 1. Read the product's own sources: README, release notes, rule or data files, the app's colour tokens and icon. Every claim must map to one of them. Watch for absolute phrases ("100% local", "finds all…") that the code does not support, and write the exact version instead. 2. Turn the product's workflow into a camera route: one chapter per step the user takes (discover → inspect → understand → report), plus an opening object and a closing "boundary" or "call to action" object. 3. Build sample data from what the product really shows (a screenshot, a demo dataset) and label it "Sample