Email signature
Two formats — HTML (for rich-text clients) and plain text (for everything else). Both inline-styled where required, with no remote font loading (Geist falls back to system fonts cleanly when not available; the lockup uses inline SVG so the Signal block always renders).
In context
How the signature reads inside an actual email body. The lockup sits below a thin horizontal rule, with the Signal block rendered inline (as an SVG, so it survives image-stripping). Full contact line in mono, comma-separated, single line.
Quick note — the eval pass landed at 0.91 trigger rate on the first generation, no rewrites needed. Skill is live in your library; should fire next time you're working on agent design.
Let me know how it lands.
HTML version
Inline-styled. Paste this into Gmail's signature settings, Apple Mail's signature box, or any rich-text-capable client. The Signal block is an inline SVG, so it renders even when external images are blocked.
Plain text version
For email clients that strip HTML, for terminal-mode mail readers, and for replies in conversation threads where rich formatting clutters. Same information, mono-set hierarchy implied by spacing alone.
-- [■] Enact Paul Dabrowski Founder · independently built enact.app · paul@enact.app · @enact
Variants
Default fits most threads. Compact is for replies and ongoing threads where the full signature is noise. Both are inline-style portable.
Compatibility & production notes
Tested for the major rich-text clients. Inline-styled, no <style> blocks, no remote fonts (Geist falls back gracefully).
Gmail
Settings → General → Signature. Paste HTML source. Inline SVG renders.
Apple Mail
Mail → Settings → Signatures. Paste HTML or drag rendered signature.
Outlook
Drops some letter-spacing. Use HTML source. Test before deploying.
Plain-text fallback
Clients that strip HTML show the plain-text version. Provide both.