← ClaudeAtlas

scroll-lock-cyber-brutalismlisted

Build a privacy, security or encryption product website in postmodern cyber brutalism — night-graphite ground, an asymmetric 12-column grid drawn with thin technical rules and amber crosshair corners, big tight grotesk headlines, IBM Plex Mono labels and readouts, one brass/amber light — whose signature is a three.js 3D padlock that the visitor closes by scrolling (approach, shackle drops, recoil, amber pulse ring, "YOUR PRIVACY. YOUR CONTROL."), fully reversible. Also ships honest-claims sections - value cards with their source file, a protects / does-not-protect threat-model split, a crypto spec table, status badges, an encrypt-and-deliver flow, a real-screenshot app preview, and a download panel with SHA-256 and signing-certificate verification. Use for messengers, password managers, VPNs, wallets, encrypted storage, open-source security tools, or when the user asks for a scroll-to-lock animation, a 3D lock hero, or a cyber-brutalist, amber-on-graphite landing page. Produces a single HTML file (three.js fr
smyrna-pergamum/web-design-skills · ★ 1 · Web & Frontend · score 74
Install: claude install-skill smyrna-pergamum/web-design-skills
# Scroll-lock cyber brutalism A security product site that behaves like a technical document with one theatrical moment. The page is a precise, asymmetric grid of hairlines, mono coordinates and plain claims; the hero is a heavy metal padlock that the reader locks with their own scroll. It suits products whose promise is control and verifiability. It does not suit hype. The reference build is `example/index.html`: the real site for **Kilit Messenger** (a post-quantum, serverless messenger over Tor), EN/TR, with the app's real screenshots in `example/assets/`. Detailed code is in `references/components.md`; `screenshots/` shows every section on desktop, mobile, reduced motion and in Turkish. If the user names a reference site, take its *style* only. Never copy its renders, product names, copy or logo. ## 1. Before designing 1. Read the product's own sources first: README, threat model, privacy policy, security policy, release notes, and the app's colour tokens. Every claim on the page must point to one of them. Put the source under each value card. 2. **Security copy rules.** Never write "military-grade", "unbreakable", "zero tracking", "audited" or "independently verified" unless a document proves it. Do not list features the product lacks (self-hosting, multi-device, perfect forward secrecy, automatic key rotation…). If it is alpha or unaudited, say so in red, near the top of the security section and in the FAQ. 3. Collect the real release: version, file nam