Unlinked · playground
Visual lab
Ideas, live.
Fifteen live demos below — five visual directions, plus nine borrowed patterns on trial, and one data-driven homepage candidate.
1. Site-wide cursor glow
The launcher tile's spotlight, but page-wide — a soft violet light trails your cursor everywhere. Move your mouse over the panel.
2. Build log as a timeline
The plain "Building lately" list becomes a vertical timeline with a gradient spine and glowing dots.
Fleet app launcher shipped — all ten apps in one place.
Feedback button fleet-wide — floating glass pill on all eleven sites.
Umami analytics live — cookieless stats across the fleet.
Subdomain migration complete — every app on its own scribnet.io subdomain.
3. 3D tilt on homepage cards
The launcher's hover physics brought to the main page's project cards. Hover it.
SE Command Center
Vendor intel, deal tools, and the app launcher — the flagship dashboard.
4. Branded link previews
Custom social-card art so sharing scribnet.io unfurls with branding instead of a blank box. Same copy everywhere — only the art changes. Tell me which letter wins and I'll generate the real 1200×630 images.
scribnet.io — ScribNet: Building AI in Public
Direction A · Monogram
Direction B · Aurora
Direction C · The fleet
Direction D · By the numbers
5. Animated gradient text
The violet→cyan gradient slowly drifts instead of sitting still. Could apply to headlines or the logo mark.
Building in public.
Borrowed ideas
Steal-worthy patterns, on trial.
Nine borrowed patterns, rebuilt here as working demos so they can be kicked around live before anything ships to the real pages.
6. Install-prompt packaging
Borrowed idea #1: every capability ships as one copy-paste prompt — no accounts, no setup docs. Pick a workflow, copy the prompt, paste it into any fresh chat. The safety checklist rides along at the bottom.
Paste into any fresh assistant chat to install the workflow.
7. Honest caveats
Borrowed idea #2: every artifact carries a short structured block saying what wasn't verified. Toggle it on the mock briefing item below.
Acme Storage launches HyperArray X9
Acme's new all-flash array promises 2× the throughput of the X8 at the same price point, with a ransomware-detection engine built into the OS.
Why it matters: a credible answer when a customer asks "what's new in primary storage" — and a wedge against incumbents on refresh cycles.
Honest caveats
Pricing is vendor-listed, not verified against a real quote.
"2× faster" is a vendor claim from the press release — no independent benchmark yet.
Coverage limited to public announcements in the last 24h; partner-only briefings not included.
Single-sourced — only the vendor's announcement so far; no third-party reviews.
8. Five daily-agent lessons
Borrowed idea #3: five rules for working with an AI agent every day — each mapped to this fleet's pipeline.
One clear decision per batch
Don't hand the agent five fuzzy tasks. One crisp decision per work unit.
In your pipeline: the battlecard updater only touches qualifying items — one cron run, one job, no sprawl.
Hard stops are sacred
Time-box the session; when the stop hits, stop. Prevents half-done sprawl.
In your pipeline: battlecard research capped at 2–3 page reads; sessions end when they end.
Show, don't describe
Make the agent show the actual output — not describe what it did.
In your pipeline: the deployed-bytes rule — curl the live file before debugging a QA report.
Batch everything
Group similar work into one run instead of many small ones.
In your pipeline: single-commit deploys; the 06:15 / 07:15 morning production line.
Boring stuff compounds
Changelogs, validation scripts, checklists — the unglamorous scaffolding is what makes a daily pipeline reliable.
In your pipeline: dated CHANGELOG on every push; the midnight fleet QA.
9. Skill safety checklist
Borrowed idea #4: the manual vetting flow — fetch, summarize, scan, install, verify. Tick the steps as you go; it's all client-side.
0 of 5 steps checked
10. /links page — "One page, every door"
Borrowed idea #5: a link-in-bio hub — one URL for the social bio, every property one line. Mock of what scribnet.io/links could look like.
ScribNet
Building AI in public · @scribnet.ai
AApp LauncherAll ten apps, one page→ DDaily Tech NewsThe 8-minute AI briefing, every morning→ ZZero to DangerousFree guides: Kubernetes, Terraform, APIs, GitHub→ PPrompt PacksInstallable AI workflows, copy-paste ready→ IInstagram@scribnet.ai — the face of Sparky→ YYouTubeScribNet Labs→ CContactSay hi→11. Homepage hero with a live demo
Borrowed idea #6: dock the real product in the hero — visitors experience it instead of reading about it. Direction mock: a podcast now-playing card with a working play/pause toggle (visual only, no audio).
ScribNet
Building AI in public.
Presales engineer by day, building with AI by night. Ten apps, a daily podcast, and the receipts — shipped in the open.
12. Kicker/eyebrow labels on section headers
Borrowed idea #7: a 12px 800-weight wide-tracked uppercase kicker above the headline — you know what section you're in before reading it. Before vs after:
Before
Shipped this week
After
Build log
Shipped this week
One CSS class, site-wide: build-log timeline, guides index, prompts page.
13. App tiles with job-to-be-done sub-captions
Borrowed idea #8: give every nav item a sub-caption — names are forgettable, jobs are scannable. Copy-only mock for apps.html:
SE Command Center
Vendor intel, deal tools, and the fleet launcher.
TCO Calculator
Price the real cost of your stack.
Prompts
Installable AI workflows, copy-paste ready.
Daily Tech News
The 8-minute AI briefing, every morning.
14. Native <details> FAQ accordion
Borrowed idea #9: native <details> expanders — zero JS, keyboard-accessible, animatable. Proposed for the FAQ and the prompts page "how it works" blocks. Click to expand:
Is this affiliated with your employer?
No — this is a personal project, built on my own time with my own gear. Nothing here represents my company.
What does ScribNet actually do?
Presales systems engineering by day; building with AI by night. This site is the public workshop: ten apps, a daily podcast, free guides, and every change shipped in the open.
Why no service worker?
Another cache layer would serve stale builds after deploys — the same footgun that bit us once already. iOS "Add to Home Screen" doesn't need one, so the sites stay installable without it.
Fresh from the workbench
Homepage candidates, in the raw.
New material being tried here first, fed by live data from the homelab.