Subject
Project name, service lane, or the route you are referencing.
#>contact_frame
direct
public
current
fast routes first
contact • visibility • discussion • services
Contact
The fastest way to get in contact with me is to use one of my services listed on /services, start from the current funding surface, or make the request concrete with a Local Proof Card. Otherwise, the best direct route right now is a DM on X, TikTok, or Instagram.
Course signups are currently once per season and include reasonable surfaces for visibility and discussion. Public surfaces like captioned YouTube work, Discord discussion, software notes, and the blog are useful for context, but they are not the fastest path for outreach.
If you are arriving from the component glossary or RPG Wednesday, send a short DM with the route, the component or card lane, and whether you are thinking about screen-readable hooks, SVG cleanup, or JSON/video wizard surfaces. That keeps the design conversation concrete from the first message.
Helpful inquiry shape
A good first message should make the next step obvious. If you are writing for work, use this structure so I can answer without back-and-forth.
What exists now
One or two lines about the current state, constraints, or live links.
What you need
Support, referral, commission, clarification, or a smaller next step.
Budget or timing
A range, deadline, or milestone if the work needs one.
If the request is paid work, start from Services. If the request is a public ask or offer, a Local Proof Card will usually make it easier to share.
Fastest Routes
⚡ @services
Services
The fastest and most structured way to get in contact. Best for serious inquiries, project context, and clearer response surfaces.
✉ ~x_dm
X — @spwashi
Very easy DM route. Preferred for quick outreach, direct questions, and current public context.
✦ @tiktok_dm
TikTok — @spwashi
Preferred DM path with strong public context around ongoing work, design, and engineering direction.
◌ >instagram_dm
Instagram — @spwashi
Preferred DM path for visual context, creative conversation, and lightweight contact.
Contact Register
✉ ~x
X
@spwashi — currently one of the easiest DM routes.
✦ @tiktok
TikTok
@spwashi — direct messages plus short-form public context.
◌ >instagram
Instagram
@spwashi — direct messages and visual/public surface.
☁ ~bluesky
BlueSky
@spwashi.com — public surface and message-adjacent context.
▶ ^youtube
YouTube
@spwashi — public iteration around engineering, design, and long-arc direction.
⌘ #>github
GitHub
Current code, repositories, implementation depth, and active technical context.
For Curious Designers
If the interesting part is not only the story but the surface itself, follow this order: learn the parts, inspect the live pressure, then DM with a specific seam.
#>component_glossary
Start in components
Use the glossary to identify the exact card, chip, frame, or SVG host you want to improve before you try to describe the whole site.
*rpg_wednesday
Inspect the live pressure
RPG Wednesday is where the components get stressed by real session rhythm, screenshots, read-aloud use, and asset handoff expectations.
@tiktok_dm
DM with the seam
TikTok is a good first DM route when you want to talk through a concrete component, capture lane, or design hook out loud while the public context is still fresh.
Courses and Seasonal Visibility
Once per season
Course signups currently happen once per season rather than continuously.
Reasonable surfaces
Those signups include reasonable surfaces for visibility, discussion, and sustained attention.
Best route for now
For immediate outreach, use services or send a DM on X, TikTok, or Instagram.