alt Hacker NewsAbsolutely agree. There's an insane "feature" of Claude Design which means you can only share the link to the design with other users on your account?! You can export the design, though, but then you need somewhere to quickly drop a bunch of HTML + assets. This would be perfect for that.
Replies
deeprack4sure • today at 2:02 AM
Wow, that does sound like a serious hardship for someone who lets Claude write all their code for them.
Creating a folder for some files. Dude, maybe you should file for disability for repetetive stress disorder for "double clicking" or even single clicking twice.
This aggression will not STAND man!
We need computers to go back to pencil and paper but STILL be computers! But not operated by me? Wierd operated by a fake bot me? Wait! thats malware! Wha?
Trying to solve this here: https://jlnk.us
Here's the instructions my agents have:
> Shareable Deliverables → jlnk.us (default) The jlnk MCP server is configured machine-wide for all team agents. It publishes disposable public links: create_link(content, ttl) returns an unguessable URL anyone can open without logging in; it self-destructs after its TTL (4h/24h/72h, default 4h, max 5 MB). Also list_my_links() and delete_link(id).
> When handing a human (Founder, CEO reviewer) something to look at — QC screenshots, prototypes, reports, before/after comparisons — default to a jlnk.us link instead of a repo file path or local path. Use 72h for Founder review, shorter when the review window is same-day.
> Content must be ONE self-contained HTML file: inline CSS/JS, embed screenshots as base64 data URIs ().
> Downscale images to stay under the 5 MB cap.
> Links are public to anyone holding the URL. NEVER publish secrets, API keys, credentials, or private client data.
> Links expire — they are a viewing convenience, not the system of record. Durable artifacts still go to the repo and issue attachments as usual.