Skein for design teams
We can swap the parameter directly in the call to the form service:
https://skein.app/go/formline/hb2U7?source=skein.app#email=marit%2Bwaitlist%40skein.app
Yep, this should be possible since we already do it on Web.
On web we return redirectURL from sendPasswordlessLoginEmail. When you enter your email to get a magic link, we check whether you have an activated account or a valid waitlist code. We then send you to sign up for the waitlist.
We could also move that logic into getSignInOptions. When we start to support SSO on Web, Web should also use the getSignInOptions endpoint.
{ redirectRequired: { error: title, description, actionURL, actionText } }mailto:bex@skein.app or something like thatPost a proposal, collect feedback, and argue through two directions in one thread. Media attachments, Facet embeds, and inline replies keep every stakeholder on the same page without another status meeting.
Skip the export-rename-upload loop. The Skein plugin for Facet links live frames into a thread in about four seconds, so you can add the context around them while the ideas are still warm.
To me it makes the most sense to reach every saved draft from an open composer view. The flow would be Compose → Select draft → Post.
“The Facet plugin rewrote how quickly I can put design changes in front of people.”
Context and images aren’t limited to a single scroll. Switch any thread into presentation mode and walk the room through your work slide by slide, in one click.
While we were designing Skein, @Corin smuggled in a bit of analog nostalgia — the plotter grid, the character picker with its little mechanical clicks. I felt that intention and wanted the brand to earn the same reaction, because of how much more distinctive it made the product.
Skein should feel worn-in, even when it’s doing something new.
Explain the build the way it makes sense to explain it — screen recording, written spec, or a two-minute voice note. Engineers get the reasoning, not just the redlines.
This covers every unfurl and embed across the product — a polish pass on the current thread unfurls plus the remaining ones: blocks, comment replies, chat messages, and channels.
Collect the relevant threads in a channel and you’ve built the archive nobody had time to write. Proposals, dissent, and the final call — grouped by project, surface, or platform.
Build the internal answer archive you keep meaning to write, wire up alerts and reports, and put out fires from one place.
Fewer status pings means more of the day spent in the editor.
Double the decisions you can actually facilitate in a week.
Automate the routine updates, get a bird’s-eye view of where every proposal stands, and stop chasing people for a verdict.
Aligned teams make for calmer customers. Give people more than one way to reach you, triage feedback quickly, and loop in whoever actually owns the fix.