agent sidequestsIdeas worth trying

Fix missing letters and awkward spacing in your AI handwriting font

Give your agent the exact words that look wrong and ask it to identify the kind of defect before editing the font. A missing character, an invented letter shape and an awkward gap need different repairs. Build a small evidence table, fix one cause at a time, and compare the same words again. This guide works through a fictional trip-title font so you can make that diagnosis without asking for a complete redesign.

Start with one line you actually want to type

Bring the delivered font file, its editable source, the handwriting images you own or have permission to adapt, and the character-to-crop map if one exists. Add the exact failing text, the app where you see it and the intended size. Keep an untouched copy of the current font. If all you have is a screenshot, ask for the font and source files first.

For our fictional example, the text is Jo’s Tokyo trip — 2026. It will become a heading on a personal trip booklet. The file is jo-trip-v1.ttf, and the intended trial is that heading at 28 pt in the chosen layout app. Those are example inputs, not a font we generated or tested. Keep the curly apostrophe and long dash in the text you send; retyping them as different punctuation changes the trial.

Ask what each suspicious character comes from

Harshpreet931’s Harshpreet Hand README describes using Claude Code to make a font from college notes. Its limitations qualify the broad handwriting claim: G, J, X and much punctuation were assembled from other letter parts rather than directly traced. This is the creator’s own project account, not our independent test; we did not run its pipeline or validate its speed, cost or visual quality.

When a letter feels wrong, ask for its source crop or a clear constructed, missing or unknown label. If fidelity matters, supply a real new sample or leave the character unfinished. A constructed replacement can be deliberate, but approve and label it separately.

Separate character mapping from the shape you see

A font’s character map connects typed characters to glyphs, the shapes stored in the font. The fontTools cmap documentation describes this mapping and a method to inspect a Unicode map. Ask an agent with font-inspection tools to check the actual export; a familiar-looking mark on screen is not enough to establish the mapping.

In our fictional file, curly apostrophe U+2019 in Jo’s is unmapped; straight U+0027 is present. Request an approved shape and mapping, or agree to change punctuation. Spacing cannot repair that absence. Compare mapped glyphs with their source crops too: a mapping can select the wrong shape. Mapping checks alone do not verify complex-script shaping.

Use a diagnosis table before asking for changes

Here is the fictional agent’s investigation. The evidence is invented to show how decisions differ; it does not describe the creator’s font. The long dash, numerals and other letters in our trial have already been checked and found acceptable in this imagined run. In your own run, unknown entries must stay unknown until inspected.

Illustrative repair decisions for Jo’s Tokyo trip — 2026
What looks wrongEvidence to establishRepair to requestKeep unchanged
The apostrophe disappears or changes styleThe exact curly character is absent from the exported mapAdd its approved source shape and mapping, then check the same textThe intended wording and all unrelated characters
J does not look like the writer’s JIts map is correct, but the outline was constructed with no matching cropCapture a real J or explicitly approve the constructed versionThe other approved letter shapes
Tokyo has an odd gap after TThe shapes look right; compare this pair with each letter beside other neighborsInvestigate spacing at the level supported by those comparisonsThe source handwriting and unaffected spacing

Locate a spacing problem before moving everything

FontForge’s metrics tutorial distinguishes general glyph spacing from kerning adjustments for particular pairs. Compare a letter with several neighbors before choosing a repair. Recurring trouble suggests checking general spacing; one awkward combination suggests checking that pair. These are clues, not proof.

For the fictional Tokyo gap, compare To with Ta, Te, no and ho at the same size, using characters whose mappings and shapes are confirmed in this font, with no fallback. If only To looks too open, request a pair adjustment and another proof, preserving the outlines and other spacing.

Run a small repair cycle with visible stop conditions

  1. Have the agent return the diagnosis and its evidence before editing: exact affected text, inspected file, source-crop reference if relevant, and proposed scope. If it cannot inspect a mapping or render the font, mark that part unverified.
  2. Resolve missing inputs first. In the example, provide an apostrophe and J sample or approve a clearly labeled alternative. Do not ask the agent to reconstruct someone’s absent handwriting as fact.
  3. Request one repair at a time and retain each revision. Compare the original trial text and a short control line containing already-approved characters after every change. A successful local correction should not quietly replace the rest of the font.
  4. Open the final export in the intended app and confirm the revision actually loaded. If a preview and the app disagree, investigate which file and settings each used before changing more outlines. If the tools cannot establish the cause, return the source map, files and the unresolved observation for a font editor or human review.
  5. For a printed booklet, make a small proof at the intended size. Mark the result with what you actually checked: this text, this revision, this app and this size. That result does not establish that every word, language or application will work.

Give your agent a bounded repair brief

An illustrative follow-up brief: Inspect [font file] and [editable source] against [permissioned handwriting and confirmed crop map]. My exact failing text is [paste text], used in [app] at [size]. Before editing, return a table separating missing or incorrect character mappings, shape/source disagreements and spacing observations. For each issue, show the evidence, proposed change and unaffected controls. Do not invent missing handwriting. Make only the repair I choose, keep the prior version and return a new export with the same text rendered from it. State which checks you performed and which need my review.

Use the handwriting-font prompt below for a full starting brief. This diagnostic method is our original, untested adaptation. Muse, Instinct, Dots and Grok Bot need suitable image, file, font-building and preview capabilities for different parts of the work; a brand name alone does not establish those tools. If your assistant cannot inspect or export fonts, have it organize the evidence and repair request for a tool that can. Installing or publishing the font is a separate action.

Copy a prompt and try it

Each idea has a complete starter prompt, the inputs to bring, and the tools it needs.

Common questions

Why can a font look right in an alphabet preview but wrong in my title?

Your title may contain characters or combinations absent from that preview. Use the exact title, punctuation and size as the trial, then investigate the specific mismatch. An attractive specimen is not a record of every case you will type.

Should I ask the agent to make every letter more consistent?

Only if that is your design goal. First identify the defect you want repaired and preserve the irregularities you like. A broad consistency request can erase the character of your handwriting while leaving the original problem unexplained.

Does a constructed letter mean the font has failed?

It is a choice to review. If you want a faithful record of supplied handwriting, request a real sample. If you want an inspired typeface, you can approve an openly labeled construction. Newly typed text should not be passed off as an original handwritten note.

Sources and further reading

These are practical editorial examples. The prompts have not been independently run-tested across every assistant.

Keep exploring

For platform setup, read the Muse, Instinct, Dots and Grok Bot guides.