Who it is forA web designer or personal site owner who wants a custom handwritten headline or body font.
The problemWeb fonts need several formats and a CSS snippet, which is tedious to set up by hand.
The outcomeWeb-ready WOFF and WOFF2 files plus a CSS @font-face snippet for your site.
What you need first
- Node.js 18 or newer installed
- A photo of your handwritten alphabet on paper, or a printed template filled in by hand
- Claude Code installed if you want the skill route; the CLI works without it
Steps
- Build the font from your photo with
npx draw-your-font make photo.jpg --chars "ABCabc" --name "My Hand". - Add web formats by running
npx draw-your-font make photo.jpg --chars "ABCabc" --name "My Hand" --formats ttf,woff,woff2,css. (inferred, check the README) - Copy the generated @font-face snippet into your site stylesheet.
- Load a test page and confirm the font renders in the browser.
Prompt for your agent
Use the draw-your-font repo to build a font from <photo-path> with --formats ttf,woff,woff2,css and save the outputs to <site-assets-dir>. Expected output is WOFF, WOFF2, and a CSS @font-face snippet. Verify that the CSS references both the WOFF2 and WOFF files.
Caveat. The README lists web formats and a CSS snippet, but it does not describe how the font is tested across browsers, so check rendering yourself.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page