← ClaudeAtlas

aperture-topology-storylisted

Build a developer-tool, data, network or OSINT product website as a dark engineering grid with one bright idea inside it — a glowing SVG node topology hero (circular icon nodes, mono labels, dashed curved links, packets travelling out and back), a huge glowing condensed display headline, then a pinned scroll story where a circular aperture opens from the central node onto a light paper-grid workspace in which white cards, chips and connectors move between nodes in four phases, and the aperture closes back to dark on a glowing closing line. Ends with calm technical sections - a mono integration strip, a tab-switched architecture diagram with real screenshots, puzzle-tab module blocks, a searchable and filterable catalog table, an honest does / never-does scope split, a tabbed terminal with copy, and link-card footer. Use when the user asks for a site in the style of a distributed-systems or infra landing page, a "scroll story that opens into a light workspace", a glowing network/topology hero, or wants a tool'
smyrna-pergamum/web-design-skills · ★ 1 · Web & Frontend · score 74
Install: claude install-skill smyrna-pergamum/web-design-skills
# Aperture topology story A product page that behaves like a quiet engineering document with one cinematic move: the reader scrolls *into* a node of the network and the dark page opens like a camera aperture onto a bright paper workspace where the product's real workflow is acted out with cards. It suits tools whose value is a pipeline you can show (inputs → sources/peers → results → output): inference meshes, OSINT and research tools, data pipelines, CI, sync engines, package registries. It does not suit lifestyle or fashion brands. The reference build is `example/index.html`: the real website for **OSINT-Book** (a passive, source-first OSINT notebook for Android and Windows), EN/TR, in the app's own colours. Detailed code is in `references/components.md`; `screenshots/` shows every section, every story phase, Turkish, reduced motion and mobile. If the user names a reference site, take its *style* only. Never copy its renders, product names, copy, logo or data. ## 1. Before designing 1. **Read the product's sources first**: README, user guide, privacy/threat model, API or source registry, release notes, CHANGELOG. Every claim on the page maps to one of them. Copy numbers exactly (versions, file names, sizes, SHA-256, ports). If two sources disagree (e.g. "22 modules" vs a 20-row table), show what the table proves. 2. **Take the colours from the product itself**: launcher icon, Android `colors.xml` / Compose `lightColorScheme` and `darkColorScheme`, web CSS cust