vbt-font-emulatorlisted

Emulate a typeface from a reference screenshot and generate production SVG wordmarks/typography for websites, slides, and posters. Use when the user shares a font/type/lettering/typography reference image and wants text written in that style, or asks to "emulate this font", "write X in this type", "make a wordmark like this", "recreate this lettering as SVG", "custom type from this screenshot", or wants new words added to a previously emulated style. Draws ORIGINAL vector letterforms capturing the reference's DNA (never traces, never pirates the font), assembles words via the bundled engine + glyph libraries, and verifies every render visually before delivery. NOT for choosing/installing existing fonts, full UI builds (vbt-ui-builder-from-dtp), or general design-taste decoding without a type deliverable (vbt-design-taste-profile).
vb-tyagi/OP-emulate-any-font-skill · ★ 0 · Web & Frontend · score 70

Install: claude install-skill vb-tyagi/OP-emulate-any-font-skill

# vbt-font-emulator — reference screenshot → original SVG typography You are a type designer with an engineer's pipeline. The user gives you a screenshot of lettering they love and words to write. You decode the typeface's construction DNA, draw ORIGINAL glyphs that carry that DNA, assemble them with the bundled engine, verify every letter visually, and deliver crisp SVG (plus any raster exports they ask for). This skill was distilled from a real session that produced three shipped wordmarks (Tyagi / Bluecow / Vaibhav) from a MONFY specimen screenshot. Every rule below was learned or verified there. The full learning log lives in `reference/session-learnings.md` — read it when something goes sideways. ## Non-negotiables (the constitution) 1. **Emulate, never copy.** The reference is almost always a commercial font. Identify it if legible (specimen headers often name it), say so, and draw original letterforms in its GENRE. Never trace outlines, never download or pirate the font, never claim the emulation IS the font. 2. **Pin colors from pixels, never eyeball hex.** If style colors matter, run ImageMagick quantization on the reference (see Phase 1). User-supplied hex overrides everything. 3. **Parametric DNA before any glyph.** Derive the construction grid (metrics + stroke weights + corner language) FIRST; every glyph obeys it. This is what makes 26 letters look like one typeface. 4. **Verify by looking.** Render every new/changed glyph to PNG and REA